Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #197764 > unrolled thread

Re: apache not running at boot

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: apache not running at boot Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-18 15:40 +0200
    Re: apache not running at boot Jonathan Dowland <jmtd@debian.org> - 2018-07-18 16:20 +0200
      Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-18 22:50 +0200
        Re: apache not running at boot Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-18 23:00 +0200
        Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-19 03:00 +0200
          Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-19 08:30 +0200
          Re: apache not running at boot Joe <joe@jretrading.com> - 2018-07-19 09:00 +0200
          Re: apache not running at boot Curt <curty@free.fr> - 2018-07-19 10:30 +0200
            Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-19 11:30 +0200
              Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-20 10:40 +0200
                Re: apache not running at boot Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-25 14:40 +0200
            Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-20 01:00 +0200
              Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-21 06:00 +0200
                Re: apache not running at boot メット <mett@pmars.jp> - 2018-07-21 06:50 +0200
                  Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-21 09:00 +0200
                    Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-21 10:40 +0200
                      Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-21 11:00 +0200
                        Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-21 11:30 +0200
                          Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-21 14:10 +0200
                            Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-21 14:50 +0200
                              Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-21 15:50 +0200
                                Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-21 16:10 +0200
                                Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-21 17:40 +0200
                                  Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-21 23:30 +0200
                                    Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-22 08:20 +0200
                                      Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-22 15:00 +0200
                                        Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-22 15:20 +0200
                                          Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-22 16:10 +0200
                                            Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-22 16:40 +0200
                                              Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-22 17:00 +0200
                                                Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-22 17:00 +0200
                                                  Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-22 17:20 +0200
                                                    Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-22 17:30 +0200
                                                      Re: apache not running at boot Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-07-22 19:10 +0200
                                                        Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-23 00:20 +0200
                                                          Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-23 00:40 +0200
                                                            Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-23 01:00 +0200
                                                          Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-23 08:30 +0200
                                                            Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-23 13:20 +0200
                                                              Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-23 22:00 +0200
                                                          Re: apache not running at boot Joe <joe@jretrading.com> - 2018-07-23 09:50 +0200
                                                            Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-23 10:30 +0200
                                                    Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-22 17:40 +0200
                                                      Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-22 19:00 +0200
                                                        Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-22 20:00 +0200
                                                          Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-25 15:10 +0200
                                                            Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-25 17:00 +0200
                                                            Re: apache not running at boot mick crane <mick.crane@gmail.com> - 2018-07-25 19:20 +0200
                                                              Re: apache not running at boot john doe <johndoe65534@mail.com> - 2018-07-25 20:00 +0200
                                                    Re: apache not running at boot Curt <curty@free.fr> - 2018-07-22 17:40 +0200
                  Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-21 16:00 +0200
                    Re: apache not running at boot Curt <curty@free.fr> - 2018-07-21 17:50 +0200
                      Re: apache not running at boot Dave <debiantechquestions@gmx.com> - 2018-07-21 23:10 +0200

Page 1 of 3  [1] 2 3  Next page →

#197764 — Re: apache not running at boot

On Wed, Jul 18, 2018 at 09:29:47AM -0400, Dave wrote:
> I just installed DEB 9.4 and apache2.4 is not starting at boot.

> i can start apache with no error using apache2 -k start or
> /ect/init.d/apache2 start  or using /usr/sbin/apachectl with no errors

Sounds like the service may be disabled for some reason.  What is the
output of:

systemctl status apache2

If you see "; disabled;" on the "Loaded" line, then this should fix it,
one hopes:

systemctl enable apache2

After doing that, you should see "; enabled;" on the Loaded line.

[toc] | [next] | [standalone]

#197769

On Wed, Jul 18, 2018 at 09:36:14AM -0400, Greg Wooledge wrote:
>Sounds like the service may be disabled for some reason.  What is the
>output of:
>
>systemctl status apache2
>
>If you see "; disabled;" on the "Loaded" line, then this should fix it,
>one hopes:
>
>systemctl enable apache2
>
>After doing that, you should see "; enabled;" on the Loaded line.

The above should address having apache2 start on system boot (or restart
if killed for some reason); to start it on a running system you will
also want to issue

    systemctl start apache2

However, from what I recall, none of this should be necessary by
default, so there is likely a configuration problem. If all of the above
does not result in a running apache2, check "journalctl -u
apache2.service" for clues, and failing that, /var/log/apache2/*

-- 

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀ Please do not CC me, I am subscribed to the list.

[toc] | [prev] | [next] | [standalone]

#197781

[Multipart message — attachments visible in raw view] — view raw

On 07/18/2018 10:12 AM, Jonathan Dowland wrote:
> On Wed, Jul 18, 2018 at 09:36:14AM -0400, Greg Wooledge wrote:
>> Sounds like the service may be disabled for some reason.  What is the
>> output of:
>>
>> systemctl status apache2
>>
>> If you see "; disabled;" on the "Loaded" line, then this should fix it,
>> one hopes:
>>
>> systemctl enable apache2
>>
>> After doing that, you should see "; enabled;" on the Loaded line.
>
> The above should address having apache2 start on system boot (or restart
> if killed for some reason); to start it on a running system you will
> also want to issue
>
>    systemctl start apache2
>
> However, from what I recall, none of this should be necessary by
> default, so there is likely a configuration problem. If all of the above

hello when i run systemctl this is what i get

● apache2.service - The Apache HTTP Server
    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor 
preset: enabled)
    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 
EDT; 1min 2s ago
   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited, 
status=1/FAILURE)

Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested 
address: AH00072: make_sock: could not bind to addres
Jul 18 16:35:30 culser apachectl[614]: no listening sockets available, 
shutting down
Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have 
more information.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process 
exited, code=exited status=1
Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP Server.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered failed 
state.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result 
'exit-code'.

> does not result in a running apache2, check "journalctl -u
> apache2.service" for clues, and failing that, /var/log/apache2/*
>


hello when i run systemctl this is what i get

● apache2.service - The Apache HTTP Server
    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor 
preset: enabled)
    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 
EDT; 1min 2s ago
   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited, 
status=1/FAILURE)

Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested 
address: AH00072: make_sock: could not bind to addres
Jul 18 16:35:30 culser apachectl[614]: no listening sockets available, 
shutting down
Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have 
more information.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process 
exited, code=exited status=1
Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP Server.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered failed 
state.
Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result 
'exit-code'.

[toc] | [prev] | [next] | [standalone]

#197782

On Wed, Jul 18, 2018 at 04:41:54PM -0400, Dave wrote:
> ● apache2.service - The Apache HTTP Server
>    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor
> preset: enabled)
>    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 EDT;
> 1min 2s ago
>   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited,
> status=1/FAILURE)
> 
> Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
> Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested address:
> AH00072: make_sock: could not bind to addres
> Jul 18 16:35:30 culser apachectl[614]: no listening sockets available,
> shutting down

OK.  Here is what I think is happening:

In your /etc/network/interfaces file, where your primary network interface
is defined, you have "allow-hotplug", because that's what the Debian
installer puts there by default, because the Debian installer has been
dumbed down for laptops.

Since your interface is marked as "allow-hotplug", services that require
a functional network will not wait for this interface to be ready.

For a server or a workstation, you need to change "allow-hotplug" to "auto".

[toc] | [prev] | [next] | [standalone]

#197785

[Multipart message — attachments visible in raw view] — view raw

On 07/18/2018 04:41 PM, Dave wrote:
> On 07/18/2018 10:12 AM, Jonathan Dowland wrote:
>> On Wed, Jul 18, 2018 at 09:36:14AM -0400, Greg Wooledge wrote:
>>> Sounds like the service may be disabled for some reason.  What is the
>>> output of:
>>>
>>> systemctl status apache2
>>>
>>> If you see "; disabled;" on the "Loaded" line, then this should fix it,
>>> one hopes:
>>>
>>> systemctl enable apache2
>>>
>>> After doing that, you should see "; enabled;" on the Loaded line.
>>
>> The above should address having apache2 start on system boot (or restart
>> if killed for some reason); to start it on a running system you will
>> also want to issue
>>
>>    systemctl start apache2
>>
>> However, from what I recall, none of this should be necessary by
>> default, so there is likely a configuration problem. If all of the above
>
> hello when i run systemctl this is what i get
>
> ● apache2.service - The Apache HTTP Server
>    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; 
> vendor preset: enabled)
>    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 
> EDT; 1min 2s ago
>   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited, 
> status=1/FAILURE)
>
> Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
> Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested 
> address: AH00072: make_sock: could not bind to addres
> Jul 18 16:35:30 culser apachectl[614]: no listening sockets available, 
> shutting down
> Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
> Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
> Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have 
> more information.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process 
> exited, code=exited status=1
> Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP Server.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered 
> failed state.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result 
> 'exit-code'.
>
>> does not result in a running apache2, check "journalctl -u
>> apache2.service" for clues, and failing that, /var/log/apache2/*
>>
>
>
> hello when i run systemctl this is what i get
>
> ● apache2.service - The Apache HTTP Server
>    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; 
> vendor preset: enabled)
>    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30 
> EDT; 1min 2s ago
>   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited, 
> status=1/FAILURE)
>
> Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
> Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested 
> address: AH00072: make_sock: could not bind to addres
> Jul 18 16:35:30 culser apachectl[614]: no listening sockets available, 
> shutting down
> Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
> Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
> Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have 
> more information.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process 
> exited, code=exited status=1
> Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP Server.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered 
> failed state.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result 
> 'exit-code'. 
update:

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.

[toc] | [prev] | [next] | [standalone]

#197786

On 2018-07-19 01:57, Dave wrote:
> On 07/18/2018 04:41 PM, Dave wrote:
> 
>> On 07/18/2018 10:12 AM, Jonathan Dowland wrote:
>> On Wed, Jul 18, 2018 at 09:36:14AM -0400, Greg Wooledge wrote:
>> Sounds like the service may be disabled for some reason.  What is
>> the
>> output of:
>> 
>> systemctl status apache2
>> 
>> If you see "; disabled;" on the "Loaded" line, then this should fix
>> it,
>> one hopes:
>> 
>> systemctl enable apache2
>> 
>> After doing that, you should see "; enabled;" on the Loaded line.
>> 
>> The above should address having apache2 start on system boot (or
>> restart
>> if killed for some reason); to start it on a running system you will
>> 
>> also want to issue
>> 
>> systemctl start apache2
>> 
>> However, from what I recall, none of this should be necessary by
>> default, so there is likely a configuration problem. If all of the
>> above
> 
> hello when i run systemctl this is what i get
> 
> ● apache2.service - The Apache HTTP Server
>    Loaded: loaded (/lib/systemd/system/apache2.service; enabled;
> vendor preset: enabled)
>    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30
> EDT; 1min 2s ago
>   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited,
> status=1/FAILURE)
> 
> Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
> Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested
> address: AH00072: make_sock: could not bind to addres
> Jul 18 16:35:30 culser apachectl[614]: no listening sockets available,
> shutting down
> Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
> Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
> Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have
> more information.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process
> exited, code=exited status=1
> Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP
> Server.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered
> failed state.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result
> 'exit-code'.
> 
>> does not result in a running apache2, check "journalctl -u
>> apache2.service" for clues, and failing that, /var/log/apache2/*
> 
> hello when i run systemctl this is what i get
> 
> ● apache2.service - The Apache HTTP Server
>    Loaded: loaded (/lib/systemd/system/apache2.service; enabled;
> vendor preset: enabled)
>    Active: failed (Result: exit-code) since Wed 2018-07-18 16:35:30
> EDT; 1min 2s ago
>   Process: 614 ExecStart=/usr/sbin/apachectl start (code=exited,
> status=1/FAILURE)
> 
> Jul 18 16:35:30 culser systemd[1]: Starting The Apache HTTP Server...
> Jul 18 16:35:30 culser apachectl[614]: (99)Cannot assign requested
> address: AH00072: make_sock: could not bind to addres
> Jul 18 16:35:30 culser apachectl[614]: no listening sockets available,
> shutting down
> Jul 18 16:35:30 culser apachectl[614]: AH00015: Unable to open logs
> Jul 18 16:35:30 culser apachectl[614]: Action 'start' failed.
> Jul 18 16:35:30 culser apachectl[614]: The Apache error log may have
> more information.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Control process
> exited, code=exited status=1
> Jul 18 16:35:30 culser systemd[1]: Failed to start The Apache HTTP
> Server.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Unit entered
> failed state.
> Jul 18 16:35:30 culser systemd[1]: apache2.service: Failed with result
> 'exit-code'. update:
> 
> 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.

Seems apache is starting before network is ready.
I used to put the ip adddress to Listen to and it worked then with one 
release it stopped working so edited to Listen 127.0.0.1 in apache conf 
file or Listen * and it worked but now this release cannot find Listen 
to interface in any of the apache2 conf files only the ports in 
ports.conf

Perhaps there is some way to find what order
"systemctl enable     "
puts things in ?

mick




-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#197788

On Wed, 18 Jul 2018 20:57:18 -0400
Dave <debiantechquestions@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.
> 
> 

Is there any chance that something else has stolen port 80? Apache
doesn't like that.

I have a very dim memory of this happening to me long ago, though I
can't remember what the offending item was. Just on the offchance, check
whether 80 is in use.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#197789

On 2018-07-19, Dave <debiantechquestions@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?

-- 
Boris sober and Boris drunk are such different people, they’ve never even met. 
-- Sergei Dovlatov, Pushkin Hills

[toc] | [prev] | [next] | [standalone]

#197790

On 7/19/2018 10:27 AM, Curt wrote:
> On 2018-07-19, Dave <debiantechquestions@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?
> 

Or, how are you configuring your interface (NM, systemd-networkd, ...)?

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#197825

On 7/20/2018 12:58 AM, Dave wrote:
> 
> 
> On 7/19/18 5:24 AM, john doe wrote:
>> On 7/19/2018 10:27 AM, Curt wrote:
>>> On 2018-07-19, Dave <debiantechquestions@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?
>>>
>>
>> Or, how are you configuring your interface (NM, systemd-networkd, ...)?
>>
> I have no idea what NM is ... can you provide a path to a configuration 
> file? i will reply with it's contents.

Then this answer should be your first step:

https://lists.debian.org/debian-user/2018/07/msg00735.html

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#197984

On Fri, Jul 20, 2018 at 10:34:12AM +0200, john doe wrote:
> > I have no idea what NM is ... can you provide a path to a configuration
> > file? i will reply with it's contents.

Jeez, I go away for a few days and look what happens.

NM is "Network Manager", which is one of the optional ways to configure
a network interface in Debian.  Usually used in conjunction with a
Desktop Environment (GNOME, etc.).  Usually not used on web servers, but
it's allowed.

The typical way to learn that NM is in charge of your interfaces is by
the comment signature that it leaves at the top of /etc/resolv.conf,
which is why you were asked to examine your /etc/resolv.conf file.

I also saw something up-thread which showed Network Manager output in
the logs of some service or other.

Also you don't have your interface defined in /etc/network/interfaces
at all, which is another good indicator that you might be using Network
Manager.

Then again, your /e/n/i/ contains the "source /etc/network/interfaces.d/*"
line and you didn't tell us whether you've got your interface configured
in there.  You PROBABLY don't, but we can't be 100% certain since you
didn't bother to look there and find out.

So, it's probably NM (Network Manager) which configures your interface.

Now, I know absolutely nothing about NM (except that it leaves behind
a comment in /etc/resolv.conf), so I can't help you with that part.
You need to figure out how to ensure that Apache isn't started until
NM has brought up your interface.

(Perhaps this machine didn't start out as a web server.  Perhaps you
installed it as a desktop machine, and then added Apache to it.  That
would explain why it's got NM.)

At some point you also need to figure out the name of your interface.
It might be eth0, or it might not.  This is basic stuff.  If you don't
know the name of your interface, start with "ip link".  That should
show you all of your interfaces, and some of their current settings.

Blindly putting "auto eth0" in /e/n/i when "eth0" might not even be the
name of your interface is not productive.  My original suggestion was
to CHANGE the line "allow-hotplug whatever" to "auto whatever", which
was written under the assumption that you're using /e/n/i in the first
place, rather than NM (a reasonable guess for a web server).

If your interface isn't named in /e/n/i AT ALL, then don't touch /e/n/i.
You can't change something that's not there.

Also, someone mentioned that you might have told Apache to bind to
a specific IP address instead of binding to all addresses.  Well, that
would be pretty silly, now wouldn't it?  If you've done that, undo it.
Tell Apache to listen/bind on all interfaces, which is the default
behavior.

[toc] | [prev] | [next] | [standalone]

#197815

On 7/19/18 4:27 AM, Curt wrote:
> On 2018-07-19, Dave <debiantechquestions@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.

[toc] | [prev] | [next] | [standalone]

#197830

[Multipart message — attachments visible in raw view] — view raw

On 07/19/2018 06:57 PM, Dave wrote:
>
> On 7/19/18 4:27 AM, Curt wrote:
>> On 2018-07-19, Dave <debiantechquestions@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

[toc] | [prev] | [next] | [standalone]

#197831

On 2018年7月21日 12:53:32 JST, Dave <debiantechquestions@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 <debiantechquestions@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

Hi
only ur loopback interface is here
u need one more line and one more word:

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

hth

ps:studying a little the fine manual
wouldn't hurt 
ps2:i suppose u re under dhcp

[toc] | [prev] | [next] | [standalone]

#197833

On 2018-07-21 05:40, メット wrote:
> On 2018年7月21日 12:53:32 JST, Dave <debiantechquestions@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 <debiantechquestions@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

mick


> Hi
> only ur loopback interface is here
> u need one more line and one more word:
> 
> auto lo eth0
> iface lo inet loopback
> iface eth0 inet dhcp
> 
> hth
> 
> ps:studying a little the fine manual
> wouldn't hurt
> ps2:i suppose u re under dhcp

-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#197834

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 <debiantechquestions@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 <debiantechquestions@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

[toc] | [prev] | [next] | [standalone]

#197835

On 2018-07-21 09:39, john doe wrote:

>> 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.

I'm quite cheerful as everything seems to be working but it wouldn't 
hurt to find out and may assist OP.
Can you give clue where to look ?
Not knowing much about systemd

mick



-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#197836

On 2018-07-21 09:56, mick crane wrote:
> On 2018-07-21 09:39, john doe wrote:
> 
>>> 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.
> 
> I'm quite cheerful as everything seems to be working but it wouldn't
> hurt to find out and may assist OP.
> Can you give clue where to look ?
> Not knowing much about systemd

just quickly looking

/etc/default/networking
seems that the default is to wait for all interfaces ?

      21 # Which interface to wait for.
      22 # If none given, wait for all auto interfaces, or if there are 
none,
      23 # wait for at least one hotplug interface.
      24 #WAIT_ONLINE_IFACE=


mick




-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

#197837

On 7/21/2018 11:21 AM, mick crane wrote:
> On 2018-07-21 09:56, mick crane wrote:
>> On 2018-07-21 09:39, john doe wrote:
>>
>>>> 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.
>>
>> I'm quite cheerful as everything seems to be working but it wouldn't
>> hurt to find out and may assist OP.

Appologies for the confusion, I read your answer and think I could add 
to it but was not in anycase directed towards you! :)

Yes, my comment was for the OP (taking into account other answers he has 
sent to the list).

>> Can you give clue where to look ?
>> Not knowing much about systemd
> 

The service 'systemd-networkd' looks among other directories in 
'/etc/systemd/network'.

https://www.freedesktop.org/software/systemd/man/systemd-networkd.service.html


One hint to determine how your interfaces are configured could be to 
look at the top of the file '/etc/resolv.conf'. If you have some comment 
lines there, those comments might indicate which "PRG" is handeling your 
INTs.
Also, has said above, if your '/etc/network/interfaces' only contains 
the 'lo' interface you can probably eliminate dhclient for configuring 
your DHCP interface.

> just quickly looking
> 
> /etc/default/networking
> seems that the default is to wait for all interfaces ?
> 

As far as I understand it, '/etc/default/networking' is only useful at 
boot or when executing '/etc/init.d/networking' (systemd way: $ 
systemctl ... networking.service).

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#197838

On 2018-07-21 13:00, john doe wrote:
> On 7/21/2018 11:21 AM, mick crane wrote:
>> On 2018-07-21 09:56, mick crane wrote:
>>> On 2018-07-21 09:39, john doe wrote:
>>> 
>>>>> 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.
>>> 
>>> I'm quite cheerful as everything seems to be working but it wouldn't
>>> hurt to find out and may assist OP.
> 
> Appologies for the confusion, I read your answer and think I could add
> to it but was not in anycase directed towards you! :)
> 
> Yes, my comment was for the OP (taking into account other answers he
> has sent to the list).

looking at links you posted if I was OP I would probably try adding

After=network-online.target
Wants=network-online.target

to  /lib/systemd/system/apache2.target

and see if apache starts at boot

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web