From: "R. W. Rodolico" <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: Re: Possible bug in 13 -- FIXED
Date: Mon, 10 Sep 2012 13:51:48 -0500 [thread overview]
Message-ID: <assp.0600acdc0e.504E36C4.2000501@dailydata.net> (raw)
In-Reply-To: <1347265027.17767.174.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
Ok, something very basic and stupid. I stopped, then started the QOS
service and magically the red0 graph started showing up.
It appears the service must be restarted after making changes.
Sorry for the false report.
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
next prev parent reply other threads:[~2012-09-10 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 20:25 Possible bug in 13 R. W. Rodolico
2012-09-10 8:17 ` Michael Tremer
2012-09-10 18:50 ` R. W. Rodolico
2012-09-10 18:51 ` R. W. Rodolico [this message]
2012-09-12 14:56 ` Possible bug in 13 -- FIXED 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.0600acdc0e.504E36C4.2000501@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