Answer the question
In order to leave comments, you need to log in
Nginx does not start on Ubuntu, what could be the matter?
nginx does not start on ubuntu 15.04 (x64), the log has already broken my head:
[email protected]:~$ sudo /etc/init.d/nginx start
[....] Starting nginx (via systemctl): nginx.serviceJob for nginx.service failed. See "systemctl status nginx.service" and "journalctl -xe" for details.
failed!
[email protected]:~$ systemctl status nginx.service
● nginx.service - LSB: Stop/start nginx
Loaded: loaded (/etc/init.d/nginx)
Active: failed (Result: exit-code) since Срд 2015-07-15 13:05:55 EEST; 49s ago
Docs: man:systemd-sysv-generator(8)
Process: 5271 ExecStart=/etc/init.d/nginx start (code=exited, status=1/FAILURE)
[email protected]:~$ sudo journalctl -xe
Июл 15 13:46:37 nikita-roshchenko dbus[687]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Июл 15 13:46:37 nikita-roshchenko systemd[1]: Started Network Manager Script Dispatcher Service.
-- Subject: Запуск юнита NetworkManager-dispatcher.service завершен
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Процесс запуска юнита NetworkManager-dispatcher.service был завершен.
--
-- Результат: done.
Июл 15 13:46:37 nikita-roshchenko nm-dispatcher[6287]: Dispatching action 'dhcp4-change' for wlan0
Июл 15 13:46:37 nikita-roshchenko dhclient[1271]: bound to 172.16.50.110 -- renewal in 860 seconds.
Июл 15 13:47:49 nikita-roshchenko avahi-daemon[637]: server.c: Packet too short or invalid while reading response record. (Maybe
Июл 15 13:48:01 nikita-roshchenko wpa_supplicant[848]: wlan0: WPA: Group rekeying completed with 24:a0:74:78:b0:83 [GTK=TKIP]
Июл 15 13:56:33 nikita-roshchenko sudo[6330]: nikita : TTY=pts/0 ; PWD=/home/nikita ; USER=root ; COMMAND=/bin/journalctl -xe
Июл 15 13:56:33 nikita-roshchenko sudo[6330]: pam_unix(sudo:session): session opened for user root by (uid=0)
Answer the question
In order to leave comments, you need to log in
In the fact that you found an article ten years ago and run nginx as it says there, or you yourself got used to it crookedly.
1) sudo service nginx start
instead of masturbation, what did you write
2) Look /var/log/nginx/error.log
, everything is written there
try nginx -t , possibly via sudo (depends on file permissions settings)
look towards /var/log/* or in the log, which is indicated in the config
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question