Question

hello i have some problem with Job for nginx.service failed. See 'systemctl status nginx.service' and 'journalc tl -xn' for details.

Posted October 30, 2016 10.7k views
Nginx Debian

nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
Active: failed (Result: exit-code) since Sun 2016-10-30 04:28:58 EDT; 13min a go
Process: 26460 ExecStop=/sbin/start-stop-daemon –quiet –stop –retry QUIT/5 –pidfile /run/nginx.pid (code=exited, status=1/FAILURE)
Process: 26395 ExecReload=/usr/sbin/nginx -g daemon on; masterprocess on; -s reload (code=exited, status=1/FAILURE)
Process: 26092 ExecStart=/usr/sbin/nginx -g daemon on; masterprocess on; (cod e=exited, status=0/SUCCESS)
Process: 26486 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
Main PID: 26095 (code=killed, signal=KILL)

Oct 30 04:28:58 bestdealstodays nginx[26486]: nginx: [emerg] could not build…4
Oct 30 04:28:58 bestdealstodays nginx[26486]: nginx: configuration file /etc…d
Oct 30 04:28:58 bestdealstodays systemd[1]: nginx.service: control process e…1
Oct 30 04:28:58 bestdealstodays systemd[1]: Failed to start A high performan....
Oct 30 04:28:58 bestdealstodays systemd[1]: Unit nginx.service entered faile....
Oct 30 04:42:05 bestdealstodays systemd[1]: Unit nginx.service cannot be rel....
Oct 30 04:42:31 bestdealstodays systemd[1]: Unit nginx.service cannot be rel....
Hint: Some lines were ellipsized, use -l to show in full.

– Logs begin at Mon 2016-10-03 17:54:02 EDT, end at Sun 2016-10-30 04:42:31 EDT. –
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyShutdown ::= { netSnmpNotifi
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in NET-SNMP-AGENT-MIB: nsNotifyRestart ::= { netSnmpNotific
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laErrMessage ::= { laEntry 101 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laLoadFloat ::= { laEntry 6 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laLoadInt ::= { laEntry 5 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laConfig ::= { laEntry 4 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laLoad ::= { laEntry 3 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laNames ::= { laEntry 2 }
Oct 30 04:42:31 bestdealstodays php5-fpm[26603]: Cannot adopt OID in UCD-SNMP-MIB: laIndex ::= { laEntry 1 }

what should i do? thx for your help

Add a comment
udikmamat
By:
udikmamat
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

4 answers
xMudrii October 30, 2016

There are probably configuration errors somewhere.
With nginx, finding these errors are easy, because it has utility that will test every configuration file.

Execute

  • sudo nginx -t

It will test nginx config and return is there error anywhere. Fix errors, test it again and try to start it:

  • sudo nginx -t

  • sudo systemctl start nginx

  • sudo systemctl status nginx # to verify is it started

If you need help fixing errors, post part of configuration with it and we will try to help you. :)

Reply Report
  • miroslavgostojic May 3, 2018

    Hello. I have the same problem:

    Setting up nginx-core (1.10.3-0ubuntu0.16.04.2) ...
Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details.
invoke-rc.d: initscript nginx, action "start" failed.
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-05-03 18:32:27 UTC; 21ms ago
  Process: 19969 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)

May 03 18:32:27 sajtovi systemd[1]: Starting A high performance web server and a reverse proxy server...
May 03 18:32:27 sajtovi nginx[19969]: [107B blob data]
May 03 18:32:27 sajtovi nginx[19969]: nginx: configuration file /etc/nginx/nginx.conf test failed
May 03 18:32:27 sajtovi systemd[1]: nginx.service: Control process exited, code=exited status=1
May 03 18:32:27 sajtovi systemd[1]: Failed to start A high performance web server and a reverse proxy server.
May 03 18:32:27 sajtovi systemd[1]: nginx.service: Unit entered failed state.
May 03 18:32:27 sajtovi systemd[1]: nginx.service: Failed with result 'exit-code'.
dpkg: error processing package nginx-core (--configure):
 subprocess installed post-installation script returned error exit status 1
    Reply Report
udikmamat October 30, 2016

i was destroy my droplet, btw thx for your answer dude.. :)

Reply Report
charannithinj November 24, 2017

[emerg] getpwnam(“ckserver”) failed in /etc/nginx/nginx.conf:1 #i am getting this error can some help me

Reply Report
BathindaHelper December 12, 2019

Nginx starts ok.
its status shows ok.
But upon droplet/ubuntu 18.04 reboot, nginx doesn’t start. Then before manual starting, its status shows an error:
root@1:~# service nginx status
● nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/nginx.service.d
└─override.conf
Active: failed (Result: signal) since Thu 2019-12-12 13:42:43 UTC; 50s ago
Docs: man:nginx(8)
Process: 982 ExecStartPost=/bin/sleep 0.1 (code=exited, status=0/SUCCESS)
Process: 969 ExecStart=/usr/sbin/nginx -g daemon on; masterprocess on; (code=exited, status=0/SUCCESS)
Process: 905 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; masterprocess on; (code=exited, status=0/SUCCESS)
Main PID: 981 (code=killed, signal=KILL)

Dec 12 13:42:43 1 systemd[1]: Starting A high performance web server and a reverse proxy server…
Dec 12 13:42:43 1 systemd[1]: Started A high performance web server and a reverse proxy server.
Dec 12 13:42:43 1 systemd[1]: nginx.service: Main process exited, code=killed, status=9/KILL
Dec 12 13:42:43 1 systemd[1]: nginx.service: Killing process 983 (nginx) with signal SIGKILL.
Dec 12 13:42:43 1 systemd[1]: nginx.service: Killing process 984 (nginx) with signal SIGKILL.
Dec 12 13:42:43 1 systemd[1]: nginx.service: Failed with result ‘signal’.

And because of this, everytime I reboot my droplet, I’ve to pay attention to starting nginx manually. Also if I create a script to run Nginx, that doesn’t work too.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help