that said, it fails with upstart too
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1428796
Title:
"service stop; service start" fails with systemd
To manage notifications about th
hrm, wsgi.py depends on python-freeipa, which itself has modules that
import stuff from freeipa-server, so it's not that simple to reproduce
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/b
So it's freeipa-server apache config that causes it, not mod_nss. Turns
out it's mod_wsgi, this is enough to reproduce the failure:
WSGISocketPrefix /run/apache2/wsgi
WSGIDaemonProcess ipa processes=6 threads=1 maximum-requests=500
WSGIProcessGroup ipa
WSGIApplicationGroup ipa
WSGIImportScript /us
I'm getting a better error on Debian
maalis 06 09:43:20 ipa01 apache2[2223]: Starting web server: apache2(98)Address
already in use: AH00072: make_sock: could not bind to address [::]:443
maalis 06 09:43:20 ipa01 apache2[2223]: (98)Address already in use: AH00072:
make_sock: could not bind to ad
> maalis 05 20:32:56 ipa02.tyrell apache2[27943]: no listening sockets
> available, shutting down
> maalis 05 20:32:56 ipa02.tyrell apache2[27943]: AH00015: Unable to open logs
That's certainly a good hint where to start. What socket/log dir is
apache trying to create?
--
You received this bug
Hm, this seems to be related to mod_nss being enabled with Freeipa.
Disabling it fixes apache2 restart, though installing & enabling it
doesn't fail restart with upstart..
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubunt
That might be, but the repro rate on systemd is 100%, while I haven't
been able to reproduce it with upstart.
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bug
Your output shows that systemd is invoking the init script for apache2,
because there is no native systemd unit in the package. So this is not
a problem specific to systemd, the init script must be racy when running
under sysvinit as well. (And even under upstart, since apache2 has no
upstart job
this works with upstart and IIRC sysv (debian)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1428796
Title:
"service stop; service start" fails with systemd
To manage notification
