[naemon-users] Release 1.0.7

[Greg Spath]

Interesting.

Standard update.   yum clean all && yum update.

I now remember the update failed trying to update some of the packages  
so I had to entirely remove the naemon packages in order to upgrade  I 
think the problem-child was libnaemon.

Anyway,

All works for me now, and if you cannot reproduce it, I'd say not to 
worry about it.  I have 3 others to upgrade and could take notes on 
those if you think it is beneficial.

-- Greg




On 06/05/2018 09:31 AM, Sven Nierlein wrote:
> Hi,
>
> I cannot reproduce that, i fired up a centos7 box, installed naemon 1.0.6, changed something in the naemon.cfg, ressource.cfg and removed the printer.cfg.
> Then i updated naemon:
>
>> #>yum update naemon\* libnaemon\*
>> ...
>> Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
>> libnaemon-1.0.7.rhel7.x86_64.rpm                                                                                                                                                                                                         | 215 kB  00:00:00
>> Running transaction check
>> Running transaction test
>> Transaction test succeeded
>> Running transaction
>>    Updating   : libnaemon-1.0.7-0.x86_64                                                                                                                                                                                                                     1/6
>>    Updating   : naemon-core-1.0.7-0.x86_64                                                                                                                                                                                                                   2/6
>> warning: /etc/naemon/naemon.cfg created as /etc/naemon/naemon.cfg.rpmnew
>> warning: /etc/naemon/resource.cfg created as /etc/naemon/resource.cfg.rpmnew
>>    Updating   : naemon-livestatus-1.0.7-0.x86_64
>> ...
> There is now a naemon.cfg.rpmnew, a resource.cfg.rpmnew and no printer.cfg. So everything as it should be.
> Looking at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnaemon%2Fnaemon-core%2Fblob%2Fmaster%2Fnaemon-core.spec%23L202&data=02%7C01%7Cgregory.spath%40bonton.com%7Cbdbf8183b6644a1c463c08d5cae89d77%7C75bc844fd0174dcdb75b2aee9e136eaf%7C1%7C0%7C636638022791684656&sdata=q2vZOcRGZuKQwQhSfG1elmYAnm03LSKcDPhy2DtJ%2FLc%3D&reserved=0 we install the example
> config in a examples folder and copy them on the first installation.
>
> How did you update naemon?
>
> Cheers,
>   Sven
>
>
>
>
> On 05.06.2018 14:59, Greg Spath wrote:
>> This is based solely on my command history restoring from git.  Some of it may have just been the permissions of the files changing.
>>
>> The broken configuration could have been a result of the following in /etc/naemon/conf.d, since my main configuration loads anything in that directory, it created duplicate services.  Perhaps those would be better placed in an examples location outside of the main configuration location?  Noreplace or not, they would be re-created since I deleted them.
>>
>> /etc/naemon/conf.d:
>> localhost.cfg
>> printer.cfg
>> switch.cfg
>> windows.cfg
>>
>>
>> In the main configuration, these were not matched with git, but perhaps you simply changed the file permissions as part of the install?
>>
>> /etc/naemon:
>> naemon.cfg
>> resource.cfg
>>
>> I wish I had more details, but I didn't think to take notes on the differences when I was getting things running again.
>>
>> -- Greg
>>
>>
>>
>>
>> On 06/05/2018 08:36 AM, Sven Nierlein wrote:
>>> On 05.06.2018 14:32, Greg Spath wrote:
>>>> Please use noreplace in the spec file for all configuration files in the future.
>>> Which ones did it overwrite, we use "%config(noreplace)" already in the spec file.
>>>
>>> Cheers,
>>>    Sven
>