S
S
Sergey Goryachev2019-01-03 22:12:28
Apache HTTP Server
Sergey Goryachev, 2019-01-03 22:12:28

Why won't apache start?

My computer refuses to start working, as it stopped on New Year's Eve, and does not leave the holiday mode.

sudo service apache2 start
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.

In journalctl -xe, to be honest, I can’t understand anything.
дек 08 13:04:05 masterhome NetworkManager[829]: <info>  [1544263445.8131] dhcp4 (enp3s0): canceled DHCP transaction, DHCP client pid 10940
дек 08 13:04:05 masterhome NetworkManager[829]: <info>  [1544263445.8132] dhcp4 (enp3s0): state changed unknown -> done
дек 08 13:04:05 masterhome NetworkManager[829]: <info>  [1544263445.8139] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
дек 08 13:04:05 masterhome NetworkManager[829]: <info>  [1544263445.8158] dhcp4 (enp3s0): dhclient started with pid 10946
дек 08 13:04:05 masterhome dhclient[10946]: DHCPREQUEST of 192.168.1.102 on enp3s0 to 255.255.255.255 port 67 (xid=0x16f0a374)
дек 08 13:04:08 masterhome dhclient[10946]: DHCPREQUEST of 192.168.1.102 on enp3s0 to 255.255.255.255 port 67 (xid=0x16f0a374)
дек 08 13:04:16 masterhome dhclient[10946]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x1204377c)
дек 08 13:04:18 masterhome kernel: r8169 0000:03:00.0 enp3s0: link down
дек 08 13:04:19 masterhome dhclient[10946]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 4 (xid=0x1204377c)
дек 08 13:04:21 masterhome NetworkManager[829]: <info>  [1544263461.1942] device (enp3s0): carrier: link connected
дек 08 13:04:21 masterhome NetworkManager[829]: <info>  [1544263461.1949] device (enp3s0): DHCPv4 lease renewal requested
дек 08 13:04:21 masterhome kernel: r8169 0000:03:00.0 enp3s0: link up
дек 08 13:04:21 masterhome NetworkManager[829]: <info>  [1544263461.2270] dhcp4 (enp3s0): canceled DHCP transaction, DHCP client pid 10946
дек 08 13:04:21 masterhome NetworkManager[829]: <info>  [1544263461.2270] dhcp4 (enp3s0): state changed unknown -> done
дек 08 13:04:21 masterhome NetworkManager[829]: <info>  [1544263461.2278] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
дек 08 13:04:21 masterhome NetworkManager[829]: <info>  [1544263461.2297] dhcp4 (enp3s0): dhclient started with pid 10951
дек 08 13:04:21 masterhome dhclient[10951]: DHCPREQUEST of 192.168.1.102 on enp3s0 to 255.255.255.255 port 67 (xid=0x1a7623dd)
дек 08 13:04:24 masterhome dhclient[10951]: DHCPREQUEST of 192.168.1.102 on enp3s0 to 255.255.255.255 port 67 (xid=0x1a7623dd)
дек 08 13:04:29 masterhome systemd[1]: Started Run anacron jobs.
-- Subject: Запуск юнита anacron.service завершен
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Процесс запуска юнита anacron.service был завершен.
-- 
-- Результат: RESULT.
дек 08 13:04:29 masterhome anacron[10958]: Anacron 2.3 started on 2018-12-08
дек 08 13:04:29 masterhome anacron[10958]: Normal exit (0 jobs run)
дек 08 13:04:32 masterhome dhclient[10951]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 3 (xid=0xd5383a0b)
дек 08 13:04:32 masterhome dhclient[10951]: DHCPREQUEST of 192.168.1.102 on enp3s0 to 255.255.255.255 port 67 (xid=0xb3a38d5)
дек 08 13:04:32 masterhome dhclient[10951]: DHCPOFFER of 192.168.1.102 from 192.168.1.1
дек 08 13:04:32 masterhome dhclient[10951]: DHCPACK of 192.168.1.102 from 192.168.1.1
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9382] dhcp4 (enp3s0):   address 192.168.1.102
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9383] dhcp4 (enp3s0):   plen 24 (255.255.255.0)
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9383] dhcp4 (enp3s0):   gateway 192.168.1.1
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9383] dhcp4 (enp3s0):   lease time 86400
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9384] dhcp4 (enp3s0):   nameserver '192.168.1.1'
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9384] dhcp4 (enp3s0):   domain name 'Home'
дек 08 13:04:32 masterhome NetworkManager[829]: <info>  [1544263472.9385] dhcp4 (enp3s0): state changed unknown -> bound
дек 08 13:04:32 masterhome dbus-daemon[822]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=829 comm="/usr/sbin/NetworkManage
дек 08 13:04:32 masterhome systemd[1]: Starting Network Manager Script Dispatcher Service...
-- Subject: Начинается запуск юнита NetworkManager-dispatcher.service
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Начат процесс запуска юнита NetworkManager-dispatcher.service.
дек 08 13:04:32 masterhome dbus-daemon[822]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
дек 08 13:04:32 masterhome systemd[1]: Started Network Manager Script Dispatcher Service.
-- Subject: Запуск юнита NetworkManager-dispatcher.service завершен
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Процесс запуска юнита NetworkManager-dispatcher.service был завершен.
-- 
-- Результат: RESULT.
дек 08 13:04:32 masterhome nm-dispatcher[10964]: req:1 'dhcp4-change' [enp3s0]: new request (1 scripts)
дек 08 13:04:32 masterhome nm-dispatcher[10964]: req:1 'dhcp4-change' [enp3s0]: start running ordered scripts...
дек 08 13:04:32 masterhome dhclient[10951]: bound to 192.168.1.102 -- renewal in 41156 seconds.
дек 08 13:04:48 masterhome systemd-resolved[786]: Using degraded feature set (UDP) for DNS server 192.168.1.1.
дек 08 13:05:03 masterhome systemd-resolved[786]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
дек 08 13:05:03 masterhome systemd-resolved[786]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

I usually solve problems always ends with a reinstallation, either Apache or mint in general.
But now I'm trying to figure out what the problem is)))

Answer the question

In order to leave comments, you need to log in

1 answer(s)
V
Vitaliy Orlov, 2019-01-03
@webirus

Try like this
and like this
And is it really the reason in Apache, judging by the logs, you have some kind of network problem, mb configuration has gone off or something like that .. Does the rest work fine?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question