[Bug 1874662] Re: Corrupted installation medium
I was about to reply @guiverc to rant about how unlikely corrupt media is when you download something over TLS and the download wasn't truncated, then I read @jiitee's comment. I didn't have hyper-v enabled, but I had WSL and thus virtualization services. Turning WSL and Virtualisation Services off allowed me to install ubuntu 20.04 successfully in virtualbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874662 Title: Corrupted installation medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786675] [NEW] Apache will not start on boot if bound to a fixed IP address
Public bug reported: due to the way the systemd service file for apache2 is configured, Apache is started before the Network has been configured by the system, as a result, it fails to start if it is required to bind to a specific IP or interface. I'm not sure where is the best to fix this, so I'm reporting this on apache. One fix I can imagine is if the systemd service file is modified to wait for all network interfaces to be configured first, or wait for a specific interface. This is the way I intend to workaround this in my case (which will likely cause me to get prompted every update about overwriting). [workaround] Systemd provides an executable which will block until a specified interface is available, and this can be used to make apache wait until the desired interface is configured by using the ff directive in the unit file: ExecStartPre=/lib/systemd/systemd-networkd-wait-online -i enp4s0 In this case above, systemd will wait until interface enp4s0 is up (assigned an IP) before it attempts to start apache2. You can replace en04s0 with the relevant interface on your machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apache2 2.4.29-1ubuntu4.2 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 Apache2ConfdDirListing: False Apache2Modules: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Aug 12 09:37:54 2018 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apache2 UpgradeStatus: No upgrade log present (probably fresh install) error.log: [Sun Aug 12 06:25:02.256640 2018] [mpm_prefork:notice] [pid 26304] AH00163: Apache/2.4.29 (Ubuntu) configured -- resuming normal operations [Sun Aug 12 06:25:02.256703 2018] [core:notice] [pid 26304] AH00094: Command line: '/usr/sbin/apache2' [Sun Aug 12 09:18:11.209390 2018] [mpm_prefork:notice] [pid 26304] AH00169: caught SIGTERM, shutting down modified.conffile..etc.apache2.apache2.conf: [modified] modified.conffile..etc.apache2.ports.conf: [modified] mtime.conffile..etc.apache2.apache2.conf: 2018-05-09T00:13:58.013470 mtime.conffile..etc.apache2.ports.conf: 2018-05-08T20:15:00.040132 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786675] Re: Apache will not start on boot if bound to a fixed IP address
# systemctl status apache2 ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: failed (Result: exit-code) since Sun 2018-08-12 09:18:42 BST; 2min 0s ago Process: 978 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE) Aug 12 09:18:42 sol apachectl[978]: AH00557: apache2: apr_sockaddr_info_get() failed for sol Aug 12 09:18:42 sol apachectl[978]: AH00558: apache2: Could not reliably determine the server's fully Aug 12 09:18:42 sol apachectl[978]: (99)Cannot assign requested address: AH00072: make_sock: could not Aug 12 09:18:42 sol apachectl[978]: no listening sockets available, shutting down Aug 12 09:18:42 sol apachectl[978]: AH00015: Unable to open logs Aug 12 09:18:42 sol apachectl[978]: Action 'start' failed. Aug 12 09:18:42 sol apachectl[978]: The Apache error log may have more information. Aug 12 09:18:42 sol systemd[1]: apache2.service: Control process exited, code=exited status=1 Aug 12 09:18:42 sol systemd[1]: apache2.service: Failed with result 'exit-code'. Aug 12 09:18:42 sol systemd[1]: Failed to start The Apache HTTP Server. SystemD Unit file in /lib/systemd/system/apache2.service [Service] Type=forking Environment=APACHE_STARTED_BY_SYSTEMD=true ExecStart=/usr/sbin/apachectl start ExecStop=/usr/sbin/apachectl stop ExecReload=/usr/sbin/apachectl graceful PrivateTmp=true Restart=on-abort [Install] WantedBy=multi-user.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786675] Re: Apache will not start on boot if bound to a fixed IP address
PS, after some research, I landed on: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ The *right* Service configuration to use for Ubuntu to ensure that it starts only after the network is up is: [Unit] Description=The Apache HTTP Server After=network-online.target Wants=network-online.target [Service] Type=forking Environment=APACHE_STARTED_BY_SYSTEMD=true ExecStart=/usr/sbin/apachectl start ExecStop=/usr/sbin/apachectl stop ExecReload=/usr/sbin/apachectl graceful PrivateTmp=true Restart=on-abort [Install] WantedBy=multi-user.target The critical lines are: After=network-online.target Wants=network-online.target The implication of this configuration is that if it takes a while for the network to be up (example, slow DHCP resolution), then it will take a while for apache to boot up. I don't expect it to affect boot up time much since I don't think anything waits for apache, but i haven't tested or verified this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786675] Re: Apache will not start on boot if bound to a fixed IP address
For the record, "network-online.target" does not block indefinitely on a system that has no NICs, if that's what you were implying by breakage. I spun up a pristine Ubuntu 18.04 instance in VMWare configured apache as described above, and then shutdown the machine. I then removed the only NIC attached to the VM and booted it back up, and it booted as normal as you'd expect. >From where I stand, I see no reason why not to adopt this configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786675] Re: Apache will not start on boot if bound to a fixed IP address
to add, I believe that even when there are no physical NICs, there is always a loopback interface on every machine, and this would trigger as soon as the loopback interface is configured (127.0.0.1) . I can't think of a situation where someone would install apache on a device that has no network stack built into the kernel, so it's hard for me to think of a situation where the network-online.target will present a problem. Also, the solution to make the service to start on network-online.target works for people using the apache configuration that ubuntu ships by default (per my test with a VM). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786675] Re: Apache will not start on boot if bound to a fixed IP address
noticed you weren't on the bug's watch list, just making this comment to trigger a new notification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786675 Title: Apache will not start on boot if bound to a fixed IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1786675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
