From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Possible bug in 13 -- FIXED Date: Wed, 12 Sep 2012 16:56:55 +0200 Message-ID: <1347461815.14788.23.camel@rice-oxley.tremer.info> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4301075228902754794==" List-Id: --===============4301075228902754794== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Okay, that looks like qosd, the daemon that is collecting the data for the graphs, did not start properly. It would be nice if you could keep an eye on that after reboots. If that happens again, we need to check what we can do. I have never had any problems with this. But still, thank you very much for doing the investigation. :D Michael On Mon, 2012-09-10 at 13:51 -0500, R. W. Rodolico wrote: > 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 > > > --===============4301075228902754794==--