[naemon-users] Upgrading to .9.1 caused the backend processes to need to be manually started at the console

[Justin Laughlin]

Thanks for getting back to me Andreas!  No, restarting doesn't make a
difference.  I thought maybe the naemon startup script had changed in some
way that my system didn't like so I compared the new /etc/init.d/naemon to
the old one and they are identical.  I had made a clone of the system
before upgrading as it is running on a virtual machine.  I am running off
the clone now and awaiting the release of version 1.0 on Friday.  Perhaps
that will fix it.  I let aptitude figure out which repository to use.
Maybe there is some issue with the upstream packaging?

-Justin

On Wed, Feb 11, 2015 at 12:52 PM, Andreas Ericsson <ageric79 at gmail.com>
wrote:

> On 2015-02-09 23:13, Justin Laughlin wrote:
>
>> Hello Group,
>>
>> About an hour ago I upgraded from 0.8 to 0.9.1 using
>>
>>        apt-get install naemon
>>
>> I chose to keep my existing config files after looking at the differences.
>> Upon launching Thruk/Naemon from my browser it reports that the backend
>> processes are not running.  It is unable to read
>>
>>       /var/cache/naemon/live
>>
>> Ultimately, I manually launched Naemon at the console:
>>
>>        /usr/bin/naemon   /etc/naemon/naemon.cfg
>>
>> Everything seems to start up and the Thruk/Naemon web interface works as
>> expected.  In the past, it started up upon system boot.  Evidently that is
>> no longer the case.
>>
>> Do you have any advice for me?   The monitoring server is running Debian
>> 8.
>>
>>
> Umm, I think that could be a problem in the upgrade script rather
> than in the actual code or default settings as such. It worked nicely
> enough for me, although I'm on Linux Mint (a debian-based system), so
> maybe there are some changes there.
>
> Does it start as intended if you reboot the machine?
>
> /Andreas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/naemon-users/attachments/20150211/eeaa9a76/attachment.html>