[smokeping-users] fcgid and config changes

[Vinny_Abello at Dell.com]

Hi Tobi,

Monitoring the smokeping.log and apache log files while doing a 'touch' to the config file yields no output in the logs. What should I be seeing or looking for?

Thanks!

-Vinny

-----Original Message-----
From: Tobias Oetiker [mailto:tobi at oetiker.ch] 
Sent: Sunday, July 08, 2012 4:04 PM
To: Abello, Vinny
Cc: rb14060 at gmail.com; smokeping-users at lists.oetiker.ch
Subject: RE: [smokeping-users] fcgid and config changes

Hi Vinny,

Today Vinny_Abello at Dell.com wrote:

> Hi Tobi,
>
> No includes here? It must be something specific to the way I have
> things configured.  What that is I?m unsure?
>
> If you setup a FreeBSD VM and install Smokeping via ports, I
> think it should be reproducible?  unless I?ve somehow screwed up
> two totally different machines yielding the same result, which is
> very possible.  ?  Maybe it?s something with my Apache
> configuration.

hmm rather odd ... do you get any log messages when you 'touch' the
config file ?

cheers
tobi


>
> -Vinny
>
> From: Tobi Oetiker [mailto:tobi at oetiker.ch]
> Sent: Sunday, July 08, 2012 1:14 AM
> To: Ryan Becker
> Cc: Abello, Vinny; smokeping-users at lists.oetiker.ch
> Subject: Re: [smokeping-users] fcgid and config changes
>
> smokeping monitores changes to the config file and reloads the webif. But only the config file. If you use @include you have to touch the config file to force a reload.
>
> cheers
> tobi
> --
> Tobi Oetiker live from the iPhone
> OETIKER+PARTNER AG
>
> On 08.07.2012, at 06:54, Ryan Becker <rb14060 at gmail.com<mailto:rb14060 at gmail.com>> wrote:
> 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, <Vinny_Abello at dell.com<mailto:Vinny_Abello at dell.com>> 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:rb14060 at gmail.com<mailto:rb14060 at gmail.com>]
> Sent: Sunday, July 08, 2012 12:49 AM
> To: Abello, Vinny
> Cc: smokeping-users at lists.oetiker.ch<mailto:smokeping-users at lists.oetiker.ch>
>
> 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, <Vinny_Abello at dell.com<mailto:Vinny_Abello at dell.com>> 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: smokeping-users-bounces+vinny_abello=dell.com at lists.oetiker.ch<mailto:dell.com at lists.oetiker.ch> [mailto:smokeping-users-bounces+vinny_abello<mailto:smokeping-users-bounces%2Bvinny_abello>=dell.com at lists.oetiker.ch<mailto:dell.com at lists.oetiker.ch>] On Behalf Of Ryan Becker
> Sent: Sunday, July 08, 2012 12:40 AM
> To: smokeping-users at lists.oetiker.ch<mailto:smokeping-users at lists.oetiker.ch>
> Subject: Re: [smokeping-users] fcgid and config changes
>
> What "changes" are we talking about?
> On Sun, Jul 8, 2012 at 12:24 AM, <Vinny_Abello at dell.com<mailto:Vinny_Abello at dell.com>> 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
> smokeping-users at lists.oetiker.ch<mailto:smokeping-users at lists.oetiker.ch>
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>
>
>
> _______________________________________________
> smokeping-users mailing list
> smokeping-users at lists.oetiker.ch<mailto:smokeping-users at lists.oetiker.ch>
> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900