Yes free disk space. several hundred GB. No idea about logs. Whatever the default is for apache 2.4 on opensuse 42.1 It doesn't happen on other servers I use with the same configuration. Here is the service status after it stops. Any idea how I find out the exact cause? www1:~ # service apache2 status apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled) Active: failed (Result: signal) since Wed 2016-06-22 11:30:02 BST; 6min ago Process: 18785 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=0/SUCCESS) Process: 18777 ExecReload=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful (code=exited, status=0/SUCCESS) Process: 27361 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=killed, signal=ABRT) Main PID: 27361 (code=killed, signal=ABRT) Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec" Jun 20 10:41:02 www1 start_apache2[27361]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/default-server.conf:95 Jun 22 11:30:01 www1 start_apache2[18777]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/default-server.conf:95 Jun 22 11:30:02 www1 start_apache2[18785]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/default-server.conf:95 Jun 22 11:30:02 www1 start_apache2[18785]: httpd (pid 27361?) not running On 31 May 2016 at 17:44, Greg Freemyer wrote:

On Mon, May 23, 2016 at 4:33 AM, Paul Groves wrote:

...

I have a strange problem on OpenSUSE 42.1 where apache seems to stop itself ever few days for no obvious reason. Restarting it works and all the websites work fine.

How can I find the error log in 42.1? I have tried all the usual places in the apache and php documentation but the log file(s) are nowhere to be found!

Thanks

I recently had a similar issue with 13.2

Do you have free disk space? (I did)

Are your logs rotating? (mine weren't)

=== to verify logrotate is active === Is the logrotate timer active?

...

systemctl list-timers

If not:

...

systemctl enable logrotate.timer # enables at boot time systemctl start logrotate.timer # and start it now

Should now be active:

...

systemctl list-timers (now lists logrotate.timer) ============================================

Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

This is the output of systemctl list-timers It does not appear that logrotate.time is running. Is there a workaround for the bug you mentioned (as in do I just have to add the timer back in)? www1:~ # systemctl list-timers NEXT LEFT UNIT ACTIVATES Wed 2016-06-29 13:03:26 BST 23h left systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service n/a n/a systemd-readahead-done.timer systemd-readahead-done.service 2 timers listed. Pass --all to see loaded but inactive timers, too. On 22 June 2016 at 14:42, Greg Freemyer wrote:

...

...

=== to verify logrotate is active === Is the logrotate timer active?

...

systemctl list-timers

If not:

...

systemctl enable logrotate.timer # enables at boot time systemctl start logrotate.timer # and start it now

Should now be active:

...

systemctl list-timers (now lists logrotate.timer) ============================================

...

No idea about logs. Whatever the default is for apache 2.4 on opensuse 42.1

Paul,

I actually wanted you to run "systemctl list-timers" and confirm logrotate.timer is in the list.

There is a known bug that causes it to disappear, so defaults mean nothing.

As a consequence, my Apache server became unstable, just like yours is.

Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Jun 28, 2016 at 8:17 AM, Paul Groves wrote:

This is the output of systemctl list-timers

It does not appear that logrotate.time is running. Is there a workaround for the bug you mentioned (as in do I just have to add the timer back in)?

As stated in both my first email and my second email: === If not: systemctl enable logrotate.timer # enables at boot time systemctl start logrotate.timer # and start it now Should now be active: systemctl list-timers (now lists logrotate.timer) === Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Paul Groves wrote:

Sorry didn't see that one :)

I do not have that timer at all. It is not there.

www1:~ # systemctl enable logrotate.timer Failed to execute operation: No such file or directory

Yes, on Leap 42.1, logrotate uses plain cron, not a systemd timer. Look in /etc/cron/daily/logrotate -- Per Jessen, Zürich (21.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

I have checked and there are no such files or directories as /etc/cron /etc/cron/daily /etc/cron/daily/logrotate On 29 June 2016 at 11:08, Per Jessen wrote:

Paul Groves wrote:

...

Sorry didn't see that one :)

I do not have that timer at all. It is not there.

www1:~ # systemctl enable logrotate.timer Failed to execute operation: No such file or directory

Yes, on Leap 42.1, logrotate uses plain cron, not a systemd timer.

Look in /etc/cron/daily/logrotate

-- Per Jessen, Zürich (21.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Paul Groves wrote:

I have checked and there are no such files or directories as /etc/cron /etc/cron/daily /etc/cron/daily/logrotate

Sorry, typo - /etc/cron.daily/logrotate This thread goes back to May, remind me, what is it you're trying to debug? -- Per Jessen, Zürich (17.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Paul Groves wrote:

Hi Per, sorry for late reply. Been very busy getting set up for holidays.

I have an apache 2.4 server on opensuse 42.1 and every so often the service just stops without warning.

Hi Paul no problem, I have also been away on summer hols. If Apache just stops, that sounds like a segfault. I think that ought to be visible with "systemctl status apache". Otherwise, check the apache logs in /var/log/apache2. If it's happened recently, 'dmesg' might show something too.

I am just trying to find out why it has stopped. Starting it again works no problem.

The server is a physical machine with 8gb ram. I have another similar web server with the same software which has never had a problem.

If the software is the same, it sounds like it's a hardware issue then. Memory problem perhaps - have you run a memtest on the failing system? -- Per Jessen, Zürich (28.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org