Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #197764 > unrolled thread
| Started by | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| First post | 2018-07-18 15:40 +0200 |
| Last post | 2018-07-21 23:10 +0200 |
| Articles | 13 on this page of 53 — 9 participants |
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.
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 3 of 3 — ← Prev page 1 2 [3]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2018-07-23 09:50 +0200 |
| Message-ID | <weDLr-4UZ-7@gated-at.bofh.it> |
| In reply to | #197923 |
On Sun, 22 Jul 2018 18:14:04 -0400 Dave <debiantechquestions@gmx.com> wrote: > > I think i should explain something i did not explain before - > > I have an old server that is currently running, it is old and running > Deb 4 , and completely configured to run with our 1 router, server > IP, dhcp, all ports 80, 443, 22, 21 ect ... > > The Apache2 issue is on my new server Deb 9.4 which will replace the > old server once it is all configured. At this time the new server is > not configured with the router as i do not believe i can run 2 > servers at the same time on the same network ( or can i ). and i do > not want any interruption with the old server running as it is > serving the many websites and network services needed for my business. > > In short i am trying to make a smooth transition. > > So perhaps Apache is not starting because my new server is not > configured with our 1 router .. ? maybe ? > > I have 1 internet line, and 1 router. > No, there shouldn't be a problem. There can't be two DHCP servers in one network without a lot of faffing about, but it appears neither of your servers is providing DHCP. The issue appears to be one of slow network startup. It's still not completely clear what software is actually setting the IP address on your server. Being a server, the IP address should be statically set, not picking up DHCP, and there should be no real need for Network Manager, if you have that installed. Until we get to the bottom of this, there will be no progress. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2018-07-23 10:30 +0200 |
| Message-ID | <weEoa-5ps-1@gated-at.bofh.it> |
| In reply to | #197933 |
On 7/23/2018 9:42 AM, Joe wrote: > On Sun, 22 Jul 2018 18:14:04 -0400 > Dave <debiantechquestions@gmx.com> wrote: > > >> >> I think i should explain something i did not explain before - >> >> I have an old server that is currently running, it is old and running >> Deb 4 , and completely configured to run with our 1 router, server >> IP, dhcp, all ports 80, 443, 22, 21 ect ... >> >> The Apache2 issue is on my new server Deb 9.4 which will replace the >> old server once it is all configured. At this time the new server is >> not configured with the router as i do not believe i can run 2 >> servers at the same time on the same network ( or can i ). and i do >> not want any interruption with the old server running as it is >> serving the many websites and network services needed for my business. >> >> In short i am trying to make a smooth transition. >> >> So perhaps Apache is not starting because my new server is not >> configured with our 1 router .. ? maybe ? >> >> I have 1 internet line, and 1 router. >> > > No, there shouldn't be a problem. There can't be two DHCP servers in > one network without a lot of faffing about, but it appears neither of > your servers is providing DHCP. > > The issue appears to be one of slow network startup. It's still not > completely clear what software is actually setting the IP address on > your server. Being a server, the IP address should be statically set, > not picking up DHCP, and there should be no real need for Network > Manager, if you have that installed. Until we get to the bottom of > this, there will be no progress. > Looks like NM is used: https://lists.debian.org/debian-user/2018/07/msg00848.html -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2018-07-22 17:40 +0200 |
| Message-ID | <weoCK-3cV-9@gated-at.bofh.it> |
| In reply to | #197896 |
On 7/22/2018 5:13 PM, Dave wrote: > > > On 07/22/2018 10:59 AM, john doe wrote: >> On 7/22/2018 4:48 PM, Dave wrote: >>> On 07/22/2018 10:39 AM, john doe wrote: >>>> On 7/22/2018 4:08 PM, Dave wrote: >>>>> >>>>> >>>>> On 07/22/2018 09:17 AM, john doe wrote: >>>>>> On 7/22/2018 2:57 PM, Dave wrote: >>>>>>> >>>>>>> >>>>>>> On 07/22/2018 02:14 AM, john doe wrote: >>>>>>>> On 7/21/2018 11:22 PM, Dave wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> On 07/21/2018 11:38 AM, john doe wrote: >>>>>>>>>> On 7/21/2018 3:46 PM, Dave wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 07/21/2018 08:42 AM, mick crane wrote: >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> hello - my Deb 9.4 / Apache 2.4 has no file called >>>>>>>>>>> apache2.target, however there is a >>>>>>>>>>> /lib/systemd/system/apache2.service file:: the contents as >>>>>>>>>>> follows >>>>>>>>>>> Description=The Apache HTTP Server >>>>>>>>>>> After=network.target remote-fs.target nss-lookup.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 >>>>>>>>>>> root@culser:/lib/systemd/system# >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Ok -- lets try: >>>>>>>>>> >>>>>>>>>> Undo any changes in '/etc/network/interfaces'. >>>>>>>>>> >>>>>>>>>> As root: >>>>>>>>>> >>>>>>>>>> $ mkdir -p /etc/systemd/apache2.d >>>>>>>>>> $ printf "%s\n%s\n" "After=network-online.target" >>>>>>>>>> "Wants=network-online.target" > >>>>>>>>>> /etc/systemd/apache2.d/boot-args.conf >>>>>>>>>> >>>>>>>>>> Then try: >>>>>>>>>> >>>>>>>>>> $ systemctl enable NetworkManager-wait-online >>>>>>>>>> $ systemctl reboot >>>>>>>>>> >>>>>>>>>> If it is not working: >>>>>>>>>> >>>>>>>>>> $ systemctl disable NetworkManager-wait-online.service >>>>>>>>>> $ systemctl enable systemd-networkd-wait-online.service >>>>>>>>>> $ systemctl reboot >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Note that the lines starting with a '$' are commands and >>>>>>>>>> should be entered on one line. >>>>>>>>>> >>>>>>>>>> https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ >>>>>>>>>> https://www.freedesktop.org/software/systemd/man/systemd.unit.html >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> I tried both those options, apache2 does not start at boot. >>>>>>>>> the contents of /boot-args.conf is as follows: >>>>>>>>> >>>>>>>>> After=network-online.target >>>>>>>>> Wants=network-online.target >>>>>>>>> >>>>>>>>> To check if apache is running after boot i check the >>>>>>>>> /var/run/apache2.pid file is present. it is not present. >>>>>>>>> I also use ps -e | grep apache and nothing is returned. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> After a reboot what output do you get: >>>>>>>> >>>>>>>> $ systemctl status apache2 >>>>>>>> >>>>>>> >>>>>>> after boot or reboot the systemctl cmd prints the following: >>>>>>> >>>>>>> ● apache2.service - The Apache HTTP Server >>>>>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; >>>>>>> vendor preset: enabled) >>>>>>> Active: failed (Result: exit-code) since Sun 2018-07-22 >>>>>>> 08:55:17 EDT; 51s ago >>>>>>> Process: 588 ExecStart=/usr/sbin/apachectl start (code=exited, >>>>>>> status=1/FAILURE) >>>>>>> >>>>>>> Jul 22 08:55:17 culser systemd[1]: Starting The Apache HTTP >>>>>>> Server... >>>>>>> Jul 22 08:55:17 culser apachectl[588]: (99)Cannot assign >>>>>>> requested address: AH00072: make_sock: coul >>>>>>> Jul 22 08:55:17 culser apachectl[588]: no listening sockets >>>>>>> available, shutting down >>>>>>> Jul 22 08:55:17 culser apachectl[588]: AH00015: Unable to open logs >>>>>>> Jul 22 08:55:17 culser apachectl[588]: Action 'start' failed. >>>>>>> Jul 22 08:55:17 culser apachectl[588]: The Apache error log may >>>>>>> have more information. >>>>>>> Jul 22 08:55:17 culser systemd[1]: apache2.service: Control >>>>>>> process exited, code=exited status=1 >>>>>>> Jul 22 08:55:17 culser systemd[1]: Failed to start The Apache >>>>>>> HTTP Server. >>>>>>> Jul 22 08:55:17 culser systemd[1]: apache2.service: Unit entered >>>>>>> failed state. >>>>>>> Jul 22 08:55:17 culser systemd[1]: apache2.service: Failed with >>>>>>> result 'exit-code'. >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> Is it properly starting if you do?: >>>>>> >>>>>> $ systemctl start apache2 >>>>>> $/usr/sbin/apachectl start >>>>>> >>>>>> If you get any errors it is most likely that the issue lies in >>>>>> Apache's configuration. >>>>>> >>>>> John, >>>>> >>>>> After boot - systemctl start apache2, gets no errors. >>>>> ps -e shows apache2 is running. >>>>> /var/run/apache.pid is present. >>>>> >>>>> systemctl status apache2 produces the following: >>>>> >>>>> ● apache2.service - The Apache HTTP Server >>>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; >>>>> vendor preset: enabled) >>>>> Active: active (running) since Sun 2018-07-22 10:02:57 EDT; 47s >>>>> ago >>>>> Process: 1518 ExecStart=/usr/sbin/apachectl start (code=exited, >>>>> status=0/SUCCESS) >>>>> Main PID: 1522 (apache2) >>>>> Tasks: 6 (limit: 4915) >>>>> CGroup: /system.slice/apache2.service >>>>> ├─1522 /usr/sbin/apache2 -k start >>>>> ├─1523 /usr/sbin/apache2 -k start >>>>> ├─1524 /usr/sbin/apache2 -k start >>>>> ├─1525 /usr/sbin/apache2 -k start >>>>> ├─1526 /usr/sbin/apache2 -k start >>>>> └─1527 /usr/sbin/apache2 -k start >>>>> >>>>> Jul 22 10:02:57 culser systemd[1]: Starting The Apache HTTP Server... >>>>> Jul 22 10:02:57 culser systemd[1]: Started The Apache HTTP Server. >>>>> >>>>> I am still baffled as to why apache2 will not start automatically >>>>> when booting. >>>>> >>>>> I can run apache2 -k start/restart systemctl start apache2 >>>>> manually after boot, but i may forget to do this. many >>>>> installations such as php, mysql depend on seeing the apache2.pid >>>>> file. >>>>> >>>>> >>>> >>>> A poorly and temporary work around could be to add in >>>> '/etc/rc.local' the command: >>>> >>>> $ systemctl restart apache2 >>>> >>>> What is the output of: >>>> >>>> $ systemctl status systemd-networkd >>>> $ systemctl status NetworkManager >>>> >>>> In the apache configuration, as pointed out by others on this list, >>>> you use some options to bind to a specific address. >>>> It would be interesting to remove those options and see how it goes; >>>> that is clearly the issue at hand. >>>> >>>> Some hints (look at what the command does and the inplication of >>>> executing that command): >>>> >>>> - $ dpkg-reconfigure apache2 >>>> - Understanding what is configuring your interfaces (which "prg") is >>>> paramount. >>>> >>>> Hopefully others on the list will jump in because I'm running out of >>>> ideas. >>>> >>> the output of: >>> systemctl status systemd-networkd >>> ● systemd-networkd.service - Network Service >>> Loaded: loaded (/lib/systemd/system/systemd-networkd.service; >>> disabled; vendor preset: enabled) >>> Active: inactive (dead) >>> Docs: man:systemd-networkd.service(8) >>> >>> The output of: >>> systemctl status NetworkManager >>> ● NetworkManager.service - Network Manager >>> Loaded: loaded (/lib/systemd/system/NetworkManager.service; >>> enabled; vendor preset: enabled) >>> Active: active (running) since Sun 2018-07-22 10:42:56 EDT; 2min >>> 51s ago >>> Docs: man:NetworkManager(8) >>> Main PID: 574 (NetworkManager) >>> Tasks: 4 (limit: 4915) >>> CGroup: /system.slice/NetworkManager.service >>> ├─574 /usr/sbin/NetworkManager --no-daemon >>> └─818 /sbin/dhclient -d -q -sf >>> /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclie >>> >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0341] >>> dhcp4 (enp5s0): domain name >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0341] >>> dhcp4 (enp5s0): state changed >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0359] >>> device (enp5s0): state change: >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0372] >>> device (enp5s0): state change: >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0377] >>> device (enp5s0): state change: >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0378] >>> manager: NetworkManager state >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0397] >>> manager: NetworkManager state >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0398] >>> policy: set 'Wired connection >>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0418] >>> device (enp5s0): Activation: s >>> Jul 22 10:43:03 culser NetworkManager[574]: <info> [1532270583.9253] >>> manager: startup complete >>> >>> >> >> For now do: >> $ systemctl disable systemd-networkd-wait-online >> $ systemctl disable NetworkManager-wait-online >> $ rm -r /etc/systemd/apache2.d >> Only the lo interface should be listed in /etc/network/interfaces or >> associated files (empty directory /etc/network/interfaces.d) >> $ systemctl enable NetworkManager-wait-online >> $ systemctl reboot >> >> Finger crossed! :-p >> > > you running out of ideas ? never, your a linux expert compared to me. > > I have been coping as many as i can who previously contributed to see if > maybe someone will have the answer. > > Unfortunately, the systemctl disable collection of commands did not work What let you think that didn't work (any error) or you mean that it didn't solve your issue? > after reboot. Ok -- If you don't mind doing those 2 followed by a reboot: $ mkdir -p /etc/systemd/apache2.d $ printf "%s\n%s\n" "After=network-online.target" "Wants=network-online.target" > /etc/systemd/apache2.d/boot-args.conf > the /etc/network/interfaces.d is empty. > > i can't imagine why Deb, is not automatically configuring apache2 to > auto start, a well know server for 10+ years and yet it seems in my case > it was not configured properly. > The service is properly starting at boot, you ask your apache server to bind to an Ip address that is not configured when the service starts. Lets say that your dhcp server is giving you the IP 172.19.234.253, you tell apache to only listen on that IP but at boot that IP is not yet assigned to your interface. Basically, you have two option: 1) Do not bind to a specific IP in apache config 2) Insure that the interface is configured before starting apache (NetworkManager-wait-online should do that) That is my understanding of your issue. -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2018-07-22 19:00 +0200 |
| Message-ID | <wepSa-3XU-5@gated-at.bofh.it> |
| In reply to | #197903 |
On 7/22/2018 5:32 PM, john doe wrote: > On 7/22/2018 5:13 PM, Dave wrote: >> >> >> On 07/22/2018 10:59 AM, john doe wrote: >>> On 7/22/2018 4:48 PM, Dave wrote: >>>> On 07/22/2018 10:39 AM, john doe wrote: >>>>> On 7/22/2018 4:08 PM, Dave wrote: >>>>>> >>>>>> >>>>>> On 07/22/2018 09:17 AM, john doe wrote: >>>>>>> On 7/22/2018 2:57 PM, Dave wrote: >>>>>>>> >>>>>>>> >>>>>>>> On 07/22/2018 02:14 AM, john doe wrote: >>>>>>>>> On 7/21/2018 11:22 PM, Dave wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 07/21/2018 11:38 AM, john doe wrote: >>>>>>>>>>> On 7/21/2018 3:46 PM, Dave wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 07/21/2018 08:42 AM, mick crane wrote: >>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> hello - my Deb 9.4 / Apache 2.4 has no file called >>>>>>>>>>>> apache2.target, however there is a >>>>>>>>>>>> /lib/systemd/system/apache2.service file:: the contents as >>>>>>>>>>>> follows >>>>>>>>>>>> Description=The Apache HTTP Server >>>>>>>>>>>> After=network.target remote-fs.target nss-lookup.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 >>>>>>>>>>>> root@culser:/lib/systemd/system# >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Ok -- lets try: >>>>>>>>>>> >>>>>>>>>>> Undo any changes in '/etc/network/interfaces'. >>>>>>>>>>> >>>>>>>>>>> As root: >>>>>>>>>>> >>>>>>>>>>> $ mkdir -p /etc/systemd/apache2.d >>>>>>>>>>> $ printf "%s\n%s\n" "After=network-online.target" >>>>>>>>>>> "Wants=network-online.target" > >>>>>>>>>>> /etc/systemd/apache2.d/boot-args.conf >>>>>>>>>>> >>>>>>>>>>> Then try: >>>>>>>>>>> >>>>>>>>>>> $ systemctl enable NetworkManager-wait-online >>>>>>>>>>> $ systemctl reboot >>>>>>>>>>> >>>>>>>>>>> If it is not working: >>>>>>>>>>> >>>>>>>>>>> $ systemctl disable NetworkManager-wait-online.service >>>>>>>>>>> $ systemctl enable systemd-networkd-wait-online.service >>>>>>>>>>> $ systemctl reboot >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Note that the lines starting with a '$' are commands and >>>>>>>>>>> should be entered on one line. >>>>>>>>>>> >>>>>>>>>>> https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ >>>>>>>>>>> https://www.freedesktop.org/software/systemd/man/systemd.unit.html >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I tried both those options, apache2 does not start at boot. >>>>>>>>>> the contents of /boot-args.conf is as follows: >>>>>>>>>> >>>>>>>>>> After=network-online.target >>>>>>>>>> Wants=network-online.target >>>>>>>>>> >>>>>>>>>> To check if apache is running after boot i check the >>>>>>>>>> /var/run/apache2.pid file is present. it is not present. >>>>>>>>>> I also use ps -e | grep apache and nothing is returned. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> After a reboot what output do you get: >>>>>>>>> >>>>>>>>> $ systemctl status apache2 >>>>>>>>> >>>>>>>> >>>>>>>> after boot or reboot the systemctl cmd prints the following: >>>>>>>> >>>>>>>> ● apache2.service - The Apache HTTP Server >>>>>>>> Loaded: loaded (/lib/systemd/system/apache2.service; >>>>>>>> enabled; vendor preset: enabled) >>>>>>>> Active: failed (Result: exit-code) since Sun 2018-07-22 >>>>>>>> 08:55:17 EDT; 51s ago >>>>>>>> Process: 588 ExecStart=/usr/sbin/apachectl start >>>>>>>> (code=exited, status=1/FAILURE) >>>>>>>> >>>>>>>> Jul 22 08:55:17 culser systemd[1]: Starting The Apache HTTP >>>>>>>> Server... >>>>>>>> Jul 22 08:55:17 culser apachectl[588]: (99)Cannot assign >>>>>>>> requested address: AH00072: make_sock: coul >>>>>>>> Jul 22 08:55:17 culser apachectl[588]: no listening sockets >>>>>>>> available, shutting down >>>>>>>> Jul 22 08:55:17 culser apachectl[588]: AH00015: Unable to open logs >>>>>>>> Jul 22 08:55:17 culser apachectl[588]: Action 'start' failed. >>>>>>>> Jul 22 08:55:17 culser apachectl[588]: The Apache error log may >>>>>>>> have more information. >>>>>>>> Jul 22 08:55:17 culser systemd[1]: apache2.service: Control >>>>>>>> process exited, code=exited status=1 >>>>>>>> Jul 22 08:55:17 culser systemd[1]: Failed to start The Apache >>>>>>>> HTTP Server. >>>>>>>> Jul 22 08:55:17 culser systemd[1]: apache2.service: Unit entered >>>>>>>> failed state. >>>>>>>> Jul 22 08:55:17 culser systemd[1]: apache2.service: Failed with >>>>>>>> result 'exit-code'. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> Is it properly starting if you do?: >>>>>>> >>>>>>> $ systemctl start apache2 >>>>>>> $/usr/sbin/apachectl start >>>>>>> >>>>>>> If you get any errors it is most likely that the issue lies in >>>>>>> Apache's configuration. >>>>>>> >>>>>> John, >>>>>> >>>>>> After boot - systemctl start apache2, gets no errors. >>>>>> ps -e shows apache2 is running. >>>>>> /var/run/apache.pid is present. >>>>>> >>>>>> systemctl status apache2 produces the following: >>>>>> >>>>>> ● apache2.service - The Apache HTTP Server >>>>>> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; >>>>>> vendor preset: enabled) >>>>>> Active: active (running) since Sun 2018-07-22 10:02:57 EDT; >>>>>> 47s ago >>>>>> Process: 1518 ExecStart=/usr/sbin/apachectl start (code=exited, >>>>>> status=0/SUCCESS) >>>>>> Main PID: 1522 (apache2) >>>>>> Tasks: 6 (limit: 4915) >>>>>> CGroup: /system.slice/apache2.service >>>>>> ├─1522 /usr/sbin/apache2 -k start >>>>>> ├─1523 /usr/sbin/apache2 -k start >>>>>> ├─1524 /usr/sbin/apache2 -k start >>>>>> ├─1525 /usr/sbin/apache2 -k start >>>>>> ├─1526 /usr/sbin/apache2 -k start >>>>>> └─1527 /usr/sbin/apache2 -k start >>>>>> >>>>>> Jul 22 10:02:57 culser systemd[1]: Starting The Apache HTTP Server... >>>>>> Jul 22 10:02:57 culser systemd[1]: Started The Apache HTTP Server. >>>>>> >>>>>> I am still baffled as to why apache2 will not start automatically >>>>>> when booting. >>>>>> >>>>>> I can run apache2 -k start/restart systemctl start apache2 >>>>>> manually after boot, but i may forget to do this. many >>>>>> installations such as php, mysql depend on seeing the apache2.pid >>>>>> file. >>>>>> >>>>>> >>>>> >>>>> A poorly and temporary work around could be to add in >>>>> '/etc/rc.local' the command: >>>>> >>>>> $ systemctl restart apache2 >>>>> >>>>> What is the output of: >>>>> >>>>> $ systemctl status systemd-networkd >>>>> $ systemctl status NetworkManager >>>>> >>>>> In the apache configuration, as pointed out by others on this list, >>>>> you use some options to bind to a specific address. >>>>> It would be interesting to remove those options and see how it >>>>> goes; that is clearly the issue at hand. >>>>> >>>>> Some hints (look at what the command does and the inplication of >>>>> executing that command): >>>>> >>>>> - $ dpkg-reconfigure apache2 >>>>> - Understanding what is configuring your interfaces (which "prg") >>>>> is paramount. >>>>> >>>>> Hopefully others on the list will jump in because I'm running out >>>>> of ideas. >>>>> >>>> the output of: >>>> systemctl status systemd-networkd >>>> ● systemd-networkd.service - Network Service >>>> Loaded: loaded (/lib/systemd/system/systemd-networkd.service; >>>> disabled; vendor preset: enabled) >>>> Active: inactive (dead) >>>> Docs: man:systemd-networkd.service(8) >>>> >>>> The output of: >>>> systemctl status NetworkManager >>>> ● NetworkManager.service - Network Manager >>>> Loaded: loaded (/lib/systemd/system/NetworkManager.service; >>>> enabled; vendor preset: enabled) >>>> Active: active (running) since Sun 2018-07-22 10:42:56 EDT; 2min >>>> 51s ago >>>> Docs: man:NetworkManager(8) >>>> Main PID: 574 (NetworkManager) >>>> Tasks: 4 (limit: 4915) >>>> CGroup: /system.slice/NetworkManager.service >>>> ├─574 /usr/sbin/NetworkManager --no-daemon >>>> └─818 /sbin/dhclient -d -q -sf >>>> /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclie >>>> >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0341] >>>> dhcp4 (enp5s0): domain name >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0341] >>>> dhcp4 (enp5s0): state changed >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0359] >>>> device (enp5s0): state change: >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0372] >>>> device (enp5s0): state change: >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0377] >>>> device (enp5s0): state change: >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0378] >>>> manager: NetworkManager state >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0397] >>>> manager: NetworkManager state >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0398] >>>> policy: set 'Wired connection >>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0418] >>>> device (enp5s0): Activation: s >>>> Jul 22 10:43:03 culser NetworkManager[574]: <info> [1532270583.9253] >>>> manager: startup complete >>>> >>>> >>> >>> For now do: >>> $ systemctl disable systemd-networkd-wait-online >>> $ systemctl disable NetworkManager-wait-online >>> $ rm -r /etc/systemd/apache2.d >>> Only the lo interface should be listed in /etc/network/interfaces or >>> associated files (empty directory /etc/network/interfaces.d) >>> $ systemctl enable NetworkManager-wait-online >>> $ systemctl reboot >>> >>> Finger crossed! :-p >>> >> >> you running out of ideas ? never, your a linux expert compared to me. >> >> I have been coping as many as i can who previously contributed to see >> if maybe someone will have the answer. >> >> Unfortunately, the systemctl disable collection of commands did not work > > What let you think that didn't work (any error) or you mean that it > didn't solve your issue? > >> after reboot. > > Ok -- If you don't mind doing those 2 followed by a reboot: > > $ mkdir -p /etc/systemd/apache2.d > $ printf "%s\n%s\n" "After=network-online.target" > "Wants=network-online.target" > /etc/systemd/apache2.d/boot-args.conf > >> the /etc/network/interfaces.d is empty. >> >> i can't imagine why Deb, is not automatically configuring apache2 to >> auto start, a well know server for 10+ years and yet it seems in my >> case it was not configured properly. >> > > The service is properly starting at boot, you ask your apache server to > bind to an Ip address that is not configured when the service starts. > > Lets say that your dhcp server is giving you the IP 172.19.234.253, you > tell apache to only listen on that IP but at boot that IP is not yet > assigned to your interface. > > Basically, you have two option: > > 1) Do not bind to a specific IP in apache config > 2) Insure that the interface is configured before starting apache > (NetworkManager-wait-online should do that) > > That is my understanding of your issue. > Also what is the output of: $ systemctl status NetworkManager-wait-online -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | mick crane <mick.crane@gmail.com> |
|---|---|
| Date | 2018-07-22 20:00 +0200 |
| Message-ID | <weqOd-4Ba-5@gated-at.bofh.it> |
| In reply to | #197910 |
On 2018-07-22 17:52, john doe wrote: <snipped> > > Also what is the output of: > > $ systemctl status NetworkManager-wait-online what would be handy is a way to get a verbose output to the apache2 log on boot. mick -- Key ID 4BFEBB31
[toc] | [prev] | [next] | [standalone]
| From | Dave <debiantechquestions@gmx.com> |
|---|---|
| Date | 2018-07-25 15:10 +0200 |
| Message-ID | <wfrIg-5zM-63@gated-at.bofh.it> |
| In reply to | #197912 |
[Multipart message — attachments visible in raw view] — view raw
On 07/22/2018 01:55 PM, mick crane wrote: > On 2018-07-22 17:52, john doe wrote: > <snipped> >> >> Also what is the output of: >> >> $ systemctl status NetworkManager-wait-online > > what would be handy is a way to get a verbose output to the apache2 > log on boot. > > mick > ah - i found this in the syslog after boot, previously i did not see this. Jul 25 08:57:52 www apachectl[600]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 192.168.1.139:80 Jul 25 08:57:52 www apachectl[600]: no listening sockets available, shutting down Jul 25 08:57:52 www apachectl[600]: AH00015: Unable to open logs I think i need a test enviroment to provide open ports.
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2018-07-25 17:00 +0200 |
| Message-ID | <wftqF-6u8-5@gated-at.bofh.it> |
| In reply to | #197985 |
On 7/25/2018 3:05 PM, Dave wrote: > > > On 07/22/2018 01:55 PM, mick crane wrote: >> On 2018-07-22 17:52, john doe wrote: >> <snipped> >>> >>> Also what is the output of: >>> >>> $ systemctl status NetworkManager-wait-online >> >> what would be handy is a way to get a verbose output to the apache2 >> log on boot. >> >> mick >> > > ah - i found this in the syslog after boot, previously i did not see this. > > Jul 25 08:57:52 www apachectl[600]: (99)Cannot assign requested address: > AH00072: make_sock: could not bind to address 192.168.1.139:80 > Jul 25 08:57:52 www apachectl[600]: no listening sockets available, > shutting down > Jul 25 08:57:52 www apachectl[600]: AH00015: Unable to open logs > > I think i need a test enviroment to provide open ports. > > Or changing the line in your *.conf file from: listen 192.168.1.139:80 to: listen port Use port 80 only when everything is working properly. It won't hurt to have a test env. If you only have one interface on the "new server" specifying the Ip is probably not necessary. 1) read the rest of the e-mails. 2) The log file can't be open, that need to be fixed. -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | mick crane <mick.crane@gmail.com> |
|---|---|
| Date | 2018-07-25 19:20 +0200 |
| Message-ID | <wfvC9-872-1@gated-at.bofh.it> |
| In reply to | #197985 |
On 2018-07-25 14:05, Dave wrote: > On 07/22/2018 01:55 PM, mick crane wrote: > >> On 2018-07-22 17:52, john doe wrote: >> <snipped> >> >>> Also what is the output of: >>> >>> $ systemctl status NetworkManager-wait-online >> >> what would be handy is a way to get a verbose output to the apache2 >> log on boot. >> >> mick > > ah - i found this in the syslog after boot, previously i did not see > this. > > Jul 25 08:57:52 www apachectl[600]: (99)Cannot assign requested > address: AH00072: make_sock: could not bind to address > 192.168.1.139:80 > Jul 25 08:57:52 www apachectl[600]: no listening sockets available, > shutting down > Jul 25 08:57:52 www apachectl[600]: AH00015: Unable to open logs > > I think i need a test enviroment to provide open ports. It seems like an unusual address for DHCP to be giving out. If it is just webpages. give new server fixed ipaddress in same range as network 192.168.1.x you know to be unused. You used to be able to do that with ifconfig but these days I don't know. get ssh working and copy (scp )over /var/www/html from old server to new server, or just copy over via a usb stick. You may have problems depending how webpages are linked, by ipaddress or name. I've fixed something like that before with sed on all the html pages. mick -- Key ID 4BFEBB31
[toc] | [prev] | [next] | [standalone]
| From | john doe <johndoe65534@mail.com> |
|---|---|
| Date | 2018-07-25 20:00 +0200 |
| Message-ID | <wfweR-8n2-1@gated-at.bofh.it> |
| In reply to | #197991 |
On 7/25/2018 7:10 PM, mick crane wrote: > On 2018-07-25 14:05, Dave wrote: >> On 07/22/2018 01:55 PM, mick crane wrote: >> >>> On 2018-07-22 17:52, john doe wrote: >>> <snipped> >>> >>>> Also what is the output of: >>>> >>>> $ systemctl status NetworkManager-wait-online >>> >>> what would be handy is a way to get a verbose output to the apache2 >>> log on boot. >>> >>> mick >> >> ah - i found this in the syslog after boot, previously i did not see >> this. >> >> Jul 25 08:57:52 www apachectl[600]: (99)Cannot assign requested >> address: AH00072: make_sock: could not bind to address >> 192.168.1.139:80 >> Jul 25 08:57:52 www apachectl[600]: no listening sockets available, >> shutting down >> Jul 25 08:57:52 www apachectl[600]: AH00015: Unable to open logs >> >> I think i need a test enviroment to provide open ports. > > It seems like an unusual address for DHCP to be giving out. > If it is just webpages. Looks correct to me, assuming that the OP is behind some kind of 'NAT'. > give new server fixed ipaddress in same range as network 192.168.1.x you > know to be unused. > You used to be able to do that with ifconfig but these days I don't know. > The OP will need to use NetworkManager (NM) to do that. > get ssh working and copy (scp )over /var/www/html from old server to new > server, or just copy over via a usb stick. > You may have problems depending how webpages are linked, by ipaddress or > name. If all the 'pages' are in the same directory I guess the OP could use relative path. -- John Doe
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2018-07-22 17:40 +0200 |
| Message-ID | <weoCK-3cV-11@gated-at.bofh.it> |
| In reply to | #197896 |
On 2018-07-22, Dave <debiantechquestions@gmx.com> wrote:
>
>
>>>
>>> Jul 22 10:42:59 culser NetworkManager[574]: <info> [1532270579.0341]
>>> dhcp4 (enp5s0): domain name
******
I don't know anything about this. I do notice your network device
doesn't seem to be called 'eth0', so using that designation in your
/e/n/i probably does exactly zero.
Maybe I'm wrong and/or this has nothing to do with the price of tea in
China.
Good luck.
--
Boris sober and Boris drunk are such different people, they’ve never even met.
-- Sergei Dovlatov, Pushkin Hills
[toc] | [prev] | [next] | [standalone]
| From | Dave <debiantechquestions@gmx.com> |
|---|---|
| Date | 2018-07-21 16:00 +0200 |
| Message-ID | <we0Ap-4mG-5@gated-at.bofh.it> |
| In reply to | #197831 |
On 07/21/2018 12:40 AM, メット 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 > 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 > > i added "eth0" i added the "iface eth0 inet dhcp" rebooted and apache2 is still not starting on boot.
[toc] | [prev] | [next] | [standalone]
| From | Curt <curty@free.fr> |
|---|---|
| Date | 2018-07-21 17:50 +0200 |
| Message-ID | <we2iR-5tQ-1@gated-at.bofh.it> |
| In reply to | #197840 |
On 2018-07-21, Dave <debiantechquestions@gmx.com> wrote: > > > i added "eth0" > i added the "iface eth0 inet dhcp" > rebooted > and apache2 is still not starting on boot. > > What about Otto (I mean auto)? Or is this an inadvertent omission in your post and not in your /e/n/i? auto eth0 iface eth0 inet dhcp would correspond to the man page (but not exactly the wiki--https://wiki.debian.org/NetworkConfiguration--which appears to suggest *both* 'auto eth0' and 'allow-hotplug eth0' for those 'just' using DHCP but whatever, nothing is ever clear, and the cats get skinned all over the place and any which way). But then I thought the conclusion was your network was being brought up/configured by other means than /e/n/i (yet to be discovered or divulged). -- Boris sober and Boris drunk are such different people, they’ve never even met. -- Sergei Dovlatov, Pushkin Hills
[toc] | [prev] | [next] | [standalone]
| From | Dave <debiantechquestions@gmx.com> |
|---|---|
| Date | 2018-07-21 23:10 +0200 |
| Message-ID | <we7ix-kp-1@gated-at.bofh.it> |
| In reply to | #197847 |
[Multipart message — attachments visible in raw view] — view raw
On 07/21/2018 11:43 AM, Curt wrote: > On 2018-07-21, Dave <debiantechquestions@gmx.com> wrote: >> >> i added "eth0" >> i added the "iface eth0 inet dhcp" >> rebooted >> and apache2 is still not starting on boot. >> >> > What about Otto (I mean auto)? Or is this an inadvertent omission in > your post and not in your /e/n/i? > > auto eth0 > iface eth0 inet dhcp > > would correspond to the man page (but not exactly the > wiki--https://wiki.debian.org/NetworkConfiguration--which appears > to suggest *both* 'auto eth0' and 'allow-hotplug eth0' for those 'just' > using DHCP but whatever, nothing is ever clear, and the cats get skinned > all over the place and any which way). > > But then I thought the conclusion was your network was being brought > up/configured by other means than /e/n/i (yet to be discovered or > divulged). > /etc/network/interfaces the current and default installed is as follows: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo eth0 iface lo inet loopback iface eth0 inet dhcp
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | linux.debian.user
csiph-web