On 7/21/2018 8:59 AM, mick crane wrote:
On 2018-07-21 05:40, メット wrote:
On 2018年7月21日 12:53:32 JST, Dave <debiantechquesti...@gmx.com> wrote:
On 07/19/2018 06:57 PM, Dave wrote:
On 7/19/18 4:27 AM, Curt wrote:
On 2018-07-19, Dave <debiantechquesti...@gmx.com> wrote:
after boot apache is not running,
if i run systemctl status apache2, i get the address bind error
shown above
at the command line after boot if i run apache2 -k restart, no
errors.
after boot if i start apache2 via /etc/init.d/apache2 start or
/usr/sbin/apache2ctl start
then - systemctl does not get the error.
/var/log/apache2 the error.log is "0" bytes
how may i start apache2 at boot with out the error.
Does this not confirm or at least support Greg W.'s hypothesis?
Did you try changing "allow-hotplug" to "auto" in your
/etc/network/interfaces file as he suggested?
Oh no - i did not change the /etc/network/interfaces file. i missed
that suggestion... I will try it.
hello .. the contents of the /etc/network/interfaces file seems to
already be set to "auto"
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
my interfaces file is identical and apache starts OK so it is probably
something else.
in /lib/systemd/system/apache2.target
do you have the "after" bit
1 [Unit]
2 Description=The Apache HTTP Server
3 After=network.target remote-fs.target nss-lookup.target
Or looking if "NetworkManager-wait-online.service" is enabled.
For systemd-networkd that is : "systemd-networkd-wait-online.service".
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
If your '/etc/network/interfaces' file is empty with the exception of
the 'lo' interface, your interfaces are probably handled by an other
"program" and you need to determine which "program" is responsible for
your interfaces.
--
John Doe
