Hi Bas, yes, that seems to be the case. When I manually change the mode to 644, it keeps that. Maybe it's worth documenting this somewhere... I think we can consider this bug closed. Thanks for the hint,
Christian On 26.07.2017 15:52, Bas Couwenberg wrote: > Control: tags -1 moreinfo > > Hi Christian, > > On 2017-07-25 17:09, root wrote: >> in the version of icinga in stretch, the icinca log files are created >> with permissions 600, >> user and group nagios:nagios or nagios:adm. This prevents the web >> frontend (which is run as >> www-data in case of apache2) from accessing it and displaying history >> for a service: >> >> "Log file "/var/log/icinga/icinga.log" invalid! No timestamp found >> within first 16 bytes! >> >> I have found not way of fixing this via additional group memberships. >> This was not the case >> in nagios as distributed with the previous release. > > I have several stretch systems (upgraded from jessie and earlier) > running icinga, and they don't have this issue. > > On all those systems /var/log/icinga is owned by nagios:nagios with mode > 644. > > In a clean stretch chroot the log file is indeed created with mod 600, > but you should be able to change this with: > > chmod 644 /var/log/icinga.log > > This should be sufficient to let the webserver access the file. > > The logrotation performed by Icinga reuses the ownership and permissions > of the existing logfile, so you should only need to do this once. > > Does this resolve your issue? > > Kind Regards, > > Bas
