public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: Possible bug in 13
Date: Mon, 10 Sep 2012 13:50:33 -0500	[thread overview]
Message-ID: <assp.0600bf9c4e.504E3679.5070605@dailydata.net> (raw)
In-Reply-To: <1347265027.17767.174.camel@rice-oxley.tremer.info>

[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]

Clock is set to pool.ntp.org, with updates, and it is working correctly.
I verified the system clock being set to now.

I have waited over 24 hours, and the graph is not updated yet; still has
the same error message.

Note that even prior to the problem, I was getting nothing on the RED0
graph even under heavy load. The IMQ map was (and still is, apparently)
working correctly.

Possible external problem: I ported this configuration over from a .62
machine that has been extensively played with, and so it is possible
that I have a bad config coming in (even though the it appeared to work
correctly before). Is there a way of clearing the QOS config completely
and allowing a default to be regenerated. I could then try this with a
known, clean config.

Possible ignorance problem: I really don't know what I'm doing. I noted
that class 1xx were on the red interface, so I created a parent class in
that numeric range (109). However, I noted that many classes were
duplicated in the 2xx range (for imq0, which I assume is vpn), and I did
not duplicate the 109 and create a 209. Would that cause this problem?
Is it simply operator error?

I would love to do some additional troubleshooting but if my ignorance
of this subject is causing the problem, I do not want to take away from
other testing.

Rod

On 09/10/2012 03:17 AM, Michael Tremer wrote:
> Hey,
> 
> firstly, check if the system's clock is set correctly. Normally there is
> the NTP server which does the job.
> 
> Secondly, wait. The graphs will take some time to show up.
> 
> Michael
> 
> On Sun, 2012-09-09 at 15:25 -0500, R. W. Rodolico wrote:
>> This may not be a bug. I am messing with something I do not understand
>> very well. However, I was able to get an error message when trying to
>> add a rule to QOS. Steps taken:
>>
>> 1. Add parent class
>>
>> 2. Class: 190, Interface Red0, Priority 1, Guaranteed Bandwidth 325,
>> Maximum Bandwidth 6514, Burst null, Ceil Burst null, TOS 0, Remark
>> "Daily Data ssh"
>>
>> 3. Add new port rule, tcp source 54555
>>
>> 4. Add new port rule, tcp destination 54555
>>
>> Red graph now shows error message
>>   The image "https://10.111.163.1:444/cgi-bin/qos.cgi?red0?hour" can not
>> be displayed, because it contains errors"
>>
>> Anything I should to to investigate? Or, possibly I need to simply wait
>> until the rrd's are updated, in which case I'd think the error message
>> should read "updating" or something.
>>
>> Rod
> 

-- 
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170


  reply	other threads:[~2012-09-10 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 20:25 R. W. Rodolico
2012-09-10  8:17 ` Michael Tremer
2012-09-10 18:50   ` R. W. Rodolico [this message]
2012-09-10 18:51   ` Possible bug in 13 -- FIXED R. W. Rodolico
2012-09-12 14:56     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=assp.0600bf9c4e.504E3679.5070605@dailydata.net \
    --to=rodo@dailydata.net \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox