System OpenSuSe 13.1 ISP Config latest Version System running fine sinsce weeks Did "zypper - up" today as I do evertime when ISPConfig say, updates available, now Pache wont start again. service apache2 status says apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled) Active: failed (Result: exit-code) since Sun 2015-05-24 13:17:40 CEST; 2s ago Process: 25052 ExecStop=/usr/sbin/start_apache2 -D SYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=1/FAILURE) Process: 25035 ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -DFOREGROUND -k start (code=exited, status=1/FAILURE) Main PID: 25035 (code=exited, status=1/FAILURE) Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec" May 24 13:17:39 admin systemd[1]: Starting The Apache Webserver... May 24 13:17:39 admin start_apache2[25035]: AH00526: Syntax error on line 29 of /etc/apache2/sites-enabled/000-apps.vhost: May 24 13:17:39 admin start_apache2[25035]: SuexecUserGroup configured, but suEXEC is disabled: Invalid owner or file mode for /usr/sbin/suexec2 May 24 13:17:39 admin systemd[1]: apache2.service: main process exited, code=exited, status=1/FAILURE May 24 13:17:39 admin start_apache2[25052]: AH00526: Syntax error on line 29 of /etc/apache2/sites-enabled/000-apps.vhost: May 24 13:17:39 admin start_apache2[25052]: SuexecUserGroup configured, but suEXEC is disabled: Invalid owner or file mode for /usr/sbin/suexec2 May 24 13:17:39 admin systemd[1]: apache2.service: control process exited, code=exited status=1 May 24 13:17:40 admin systemd[1]: Failed to start The Apache Webserver. May 24 13:17:40 admin systemd[1]: Unit apache2.service entered failed state. Did not change anything else since weeks. Need hint or help Thanks Rainer
Same problem on 3 other similar configured ISPConfig servers after same update today I have two quite similar ISPConfig multiserver installations with a ISPConfig Master Server and a seperate Slave server as Webserver The is also seperate Mail Server with apache for webmail None of the apaches will start, all with the same error message Rainer
If the file permission change occured on openSuSE update, you might file a bug report at SuSE, because ISPConfig is not involved when you manually update your OS. (SuSE isn't a recommended server os anyway, imho)
