Unfortunately I can't reproduce this. A restart of Smokeping is all I needed to add a monitored host, and the web interface updated immediately. Maybe someone else can reproduce?
On Sun, Jul 8, 2012 at 12:51 AM, <[email protected]> wrote: > I have the same behavior on two different boxes so far. Both are FreeBSD > (8.2 on one and 9.0 on another) with Apache2.2 and mod_fcgi 2.3.6 and > Smokeping 2.6.7.**** > > ** ** > > -Vinny**** > > ** ** > > *From:* Ryan Becker [mailto:[email protected]] > *Sent:* Sunday, July 08, 2012 12:49 AM > *To:* Abello, Vinny > *Cc:* [email protected] > > *Subject:* Re: [smokeping-users] fcgid and config changes**** > > ** ** > > I can't say I've ever seen that issue but I can test it on my end if you > like to see if I experience the same thing.**** > > On Sun, Jul 8, 2012 at 12:46 AM, <[email protected]> wrote:**** > > Literally any modification to the config file that affects the web > interface html content, including but not limited to adding or removing new > items being monitored by smokeping. The issue is not what’s being modified > but I think the fact that the old cgi process never dies and continues > using the old config file until…. I don’t know when. I’ve always had to > kill the process or restart Apache which also ends the process to make the > web interface reflect the current configuration file. I’m talking > specifically about the web interface and not the daemon. There is no > problem with that piece. I just never had this issue with SpeedyCGI. > Perhaps I have something configured wrong.**** > > **** > > -Vinny**** > > **** > > *From:* [email protected][mailto: > [email protected]] *On > Behalf Of *Ryan Becker > *Sent:* Sunday, July 08, 2012 12:40 AM > *To:* [email protected] > *Subject:* Re: [smokeping-users] fcgid and config changes**** > > **** > > What "changes" are we talking about?**** > > On Sun, Jul 8, 2012 at 12:24 AM, <[email protected]> wrote:**** > > I’ve noticed in the newer versions of smokeping using fgcid, that any > config changes aren’t reflected in the web interface until the existing > process is ended and a new one spawned. Is it just expected that after each > change you will kill the old process to get the web interface to reflect > the changes that the daemon is already aware of? Is the smokeping supposed > to kill the old web process on reload? I never had this issue with > SpeedyCGI in 2.4.2 and earlier.**** > > **** > > Thanks!**** > > **** > > -Vinny**** > > > _______________________________________________ > smokeping-users mailing list > [email protected] > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users**** > > **** > > ** ** >
_______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
