Activity log for bug #1899852

Date Who What changed Old value New value Message
2020-10-14 23:15:51 Benjamin Allot bug added bug
2020-10-15 06:46:26 Benjamin Allot bug added subscriber The Canonical Sysadmins
2020-10-15 06:48:28 Benjamin Allot description Hello, Let's first list my configuration items: * apache2 2.4.29-1ubuntu4.14 * release: Ubuntu 18.04.5 LTS Upon reboot, the following message is seen in apache2.service logs: -- Unit apache2.service has begun starting up. Oct 14 12:18:32 SERVER apachectl[3833]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address [REDACTED IPV6.33]:443 Oct 14 12:18:32 SERVER apachectl[3833]: no listening sockets available, shutting down Oct 14 12:18:32 SERVER apachectl[3833]: AH00015: Unable to open logs Oct 14 12:18:32 SERVER apachectl[3833]: Action 'start' failed. Oct 14 12:18:32 SERVER apachectl[3833]: The Apache error log may have more information. Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Failed with result 'exit-code'. Oct 14 12:18:33 SERVER systemd[1]: Failed to start The Apache HTTP Server. The apache2 configuration is using the ipv4 and ipv6 present on the server: /etc/apache2/ports.conf:Listen <REDACTED ipv4.245>:443 /etc/apache2/ports.conf:Listen <REDACTED ipv4.247>:443 /etc/apache2/ports.conf:Listen [REDACTED IPV6::33]:443 /etc/apache2/ports.conf:Listen [REDACTED IPV6::35]:443 and the /etc/network/interfaces look as this (no netplan): # Additional IPs that are used to serve https traffic for # releases.ubuntu.com so that archive doesn't respond on 443. auto bond0:1 iface bond0:1 inet static address <REDACTED IPV4>.247/32 # Using up/down to avoid LP:1347246. up /sbin/ip addr add REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 down /bin/ip addr del REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 # Additional IPs that are used to serve *.clouds.archive.ubuntu.com # with HTTPProtocolOptions unsafe, which is needed to work around # cloud-init bug LP:1868232 (cRT#125271). auto bond0:2 iface bond0:2 inet static address <REDACTED IPV4>.245/32 # Using up/down to avoid LP:1347246. up /sbin/ip addr add REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 down /bin/ip addr del REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 I was surprised that the apache2.service does not contain a After=network-online.target $ systemctl show apache2.service | grep -E '(Wants|Require|After|Before)' RemainAfterExit=no Requires=system.slice sysinit.target -.mount Before=multi-user.target shutdown.target After=basic.target sysinit.target systemd-journald.socket system.slice network.target nss-lookup.target systemd-tmpfiles-setup.service remote-fs.target -.mount RequiresMountsFor=/var/tmp /tmp $ systemctl show network.target | grep "^After" After=network-pre.target ifup@bond0.service ifup@ens2f0.service ifup@ens2f1.service systemd-resolved.service ufw.service networking.service systemd-networkd.service So I was wondering if the "ifup@bond0" was enough as a dependency here, to be sure to have the ipv6 up and running or if we would need something like "ifup@bond0:2" and "ifup@bond0:1" as part of the list of the services in the network.target "After" list. Hello, Let's first list my configuration items: * apache2 2.4.29-1ubuntu4.14 * release: Ubuntu 18.04.5 LTS Upon reboot, the following message is seen in apache2.service logs: -- Unit apache2.service has begun starting up. Oct 14 12:18:32 SERVER apachectl[3833]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address [REDACTED IPV6.33]:443 Oct 14 12:18:32 SERVER apachectl[3833]: no listening sockets available, shutting down Oct 14 12:18:32 SERVER apachectl[3833]: AH00015: Unable to open logs Oct 14 12:18:32 SERVER apachectl[3833]: Action 'start' failed. Oct 14 12:18:32 SERVER apachectl[3833]: The Apache error log may have more information. Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 14 12:18:33 SERVER systemd[1]: apache2.service: Failed with result 'exit-code'. Oct 14 12:18:33 SERVER systemd[1]: Failed to start The Apache HTTP Server. The apache2 configuration is using the ipv4 and ipv6 present on the server: /etc/apache2/ports.conf:Listen <REDACTED ipv4.245>:443 /etc/apache2/ports.conf:Listen <REDACTED ipv4.247>:443 /etc/apache2/ports.conf:Listen [REDACTED IPV6::33]:443 /etc/apache2/ports.conf:Listen [REDACTED IPV6::35]:443 and the /etc/network/interfaces looks like this (no netplan): # Additional IPs that are used to serve https traffic for # releases.ubuntu.com so that archive doesn't respond on 443. auto bond0:1 iface bond0:1 inet static     address <REDACTED IPV4>.247/32     # Using up/down to avoid LP:1347246.     up /sbin/ip addr add REDACTED IPV6::33/128 dev $IFACE preferred_lft 0     down /bin/ip addr del REDACTED IPV6::33/128 dev $IFACE preferred_lft 0 # Additional IPs that are used to serve *.clouds.archive.ubuntu.com # with HTTPProtocolOptions unsafe, which is needed to work around # cloud-init bug LP:1868232 (cRT#125271). auto bond0:2 iface bond0:2 inet static     address <REDACTED IPV4>.245/32     # Using up/down to avoid LP:1347246.     up /sbin/ip addr add REDACTED IPV6::35/128 dev $IFACE preferred_lft 0     down /bin/ip addr del REDACTED IPV6::35/128 dev $IFACE preferred_lft 0 I was surprised that the apache2.service does not contain a After=network-online.target $ systemctl show apache2.service | grep -E '(Wants|Require|After|Before)' RemainAfterExit=no Requires=system.slice sysinit.target -.mount Before=multi-user.target shutdown.target After=basic.target sysinit.target systemd-journald.socket system.slice network.target nss-lookup.target systemd-tmpfiles-setup.service remote-fs.target -.mount RequiresMountsFor=/var/tmp /tmp $ systemctl show network.target | grep "^After" After=network-pre.target ifup@bond0.service ifup@ens2f0.service ifup@ens2f1.service systemd-resolved.service ufw.service networking.service systemd-networkd.service So I was wondering if the "ifup@bond0" was enough as a dependency here, to be sure to have the ipv6 up and running or if we would need something like "ifup@bond0:2" and "ifup@bond0:1" as part of the list of the services in the network.target "After" list.
2020-10-19 14:48:27 Christian Ehrhardt  bug task added systemd (Ubuntu)
2020-10-19 14:48:32 Christian Ehrhardt  apache2 (Ubuntu): status New Invalid
2020-10-19 14:48:34 Christian Ehrhardt  systemd (Ubuntu): status New Invalid