Re: [Evergreen] apache systemd notify related log message

2016-05-18 Thread Per Jessen
Patrick Schaaf wrote:

> With the latest systemd etc. updates for 13.1 on my production
> webservers, I started to get these messages, several times a day:
> 
> 2016-05-12T13:13:01.494327+02:00 HOSTNAME systemd[1]: apache2.service:
> Got notification message from PID 14342, but reception only permitted
> for main PID 1621
> 
> Adding "NotifyAccess=all" to apache2.service [Service] section (done
> locally through a dropin at the moment), seems to fix the symptom.
> 
> Maybe that could be put into apache2.service in a future package
> update?

It might be a good idea to open a bugreport on that. 



-- 
Per Jessen, Zürich (11.1°C)
http://www.hostsuisse.com/ - virtual servers, made in Switzerland.

___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen


[Evergreen] apache systemd notify related log message

2016-05-12 Thread Patrick Schaaf
With the latest systemd etc. updates for 13.1 on my production
webservers, I started to get these messages, several times a day:

2016-05-12T13:13:01.494327+02:00 HOSTNAME systemd[1]: apache2.service:
Got notification message from PID 14342, but reception only permitted
for main PID 1621

Adding "NotifyAccess=all" to apache2.service [Service] section (done
locally through a dropin at the moment), seems to fix the symptom.

Maybe that could be put into apache2.service in a future package update?

best regards
  Patrick
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen