Nginx not running with no error message

Nginx not running with no error message

#!/bin/sh
echo "start"
rm /etc/nginx/sites-enabled/default
ln -s /primerbean/nginx_conf/healthbean_nginx.conf /etc/nginx/sites-enabled/
/etc/init.d/nginx start
echo `service nginx status`
echo `service apache2 status`
service nginx restart
echo `service nginx status`
cat /var/log/nginx/error.log
uwsgi --ini /primerbean/nginx_conf/healthbean_uwsgi.ini
# migrate db, so we have the latest db schema
# python manage.py migrate
# start development server on public ip interface, on port 8000
# python manage.py runserver 0.0.0.0:8000

Ask Question

up vote56down votefavorite

19

I am trying to start my nginx server. When I type "$> /etc/init.d/nginx start", I have a message appearing "Starting nginx:", and then nothing happens. There is no error message, and when I check the status of nginx I see that it is not running.

Here is my /etc/nginx/nginx.conf file:

worker_processes  4;
daemon off;

error_log  /home/vincent/tmp/nginx.log;

pid        /home/vincent/tmp/nginx.pid;

events {
    worker_connections  1024;
}

http {
default_type  application/octet-stream;

log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                  '$status $body_bytes_sent "$http_referer" '
                  '"$http_user_agent" "$http_x_forwarded_for"';

access_log  /home/vincent/tmp/access.log  main;

sendfile        on;

keepalive_timeout  65;

include /etc/nginx/site-enabled/*;

}

And here is my /etc/nginx/sites-available/default file :

server {
  listen       80;
  server_name technical-test.neo9.lan; 

  access_log  /var/log/nginx/technical-test.neo9.lan.log main;

  set $home /home/vincent;

  location / {
    alias $home/neo9/web/app/;
    index  index.html;
  }

  location /api/ {
    rewrite  ^/api/(.*)$  /$1 break;
    proxy_pass http://localhost:1234;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
  }
}

nginx

shareimprove this question

edited Jul 25 '13 at 15:42 Charles 43.1k1180118

asked Jul 25 '13 at 13:38 user2618928 281134

3

Did you try service nginx configtest ? – Tim Baas Jul 25 '13 at 13:40

Using this command give me this answer : "Testing nginx configuration: nginx." – user2618928 Jul 25 '13 at 13:44 

3

And "sudo nginx -t" gives me : nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful – user2618928 Jul 25 '13 at 13:46

1

Did you also try starting nginx with sudo? – Tim Baas Jul 25 '13 at 13:47

I am always starting it with sudo, otherwise I get an error of permission denied when it tries to acces the error.log file – user2618928 Jul 25 '13 at 13:49

show 2 more comments

8 Answers

activeoldestvotes

up vote174down vote

First, always sudo nginx -t to verify your config files are good.

I ran into the same problem. The reason I had the issue was twofold. First, I had accidentally copied a log file into my site-enabled folder. I deleted the log file and made sure that all the files in sites-enabled were proper nginx site configs. I also noticed two of my virtual hosts were listening for the same domain. So I made sure that each of my virtual hosts had unique domain names.

sudo service nginx restart

Then it worked.

shareimprove this answer

edited Dec 21 '13 at 8:38 Jay Mayu 9,4842595133

answered Oct 29 '13 at 20:21 badmadrad 1,953176

53

sudo nginx -t is an awesome tip :) – Jay Mayu Dec 21 '13 at 8:38

1

As you(@badmadrad) said I got the following by running sudo nginx -t.but still when I try to restart it fail. ferdinand@ferdinand-desktop:~$ sudo nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful ferdinand@ferdinand-desktop:~$ sudo service nginx restart * Restarting nginx nginx [fail] – Ferdinand Rosario Aug 4 '14 at 11:36 

make sure your site-enabled only has nginx conf files in there. Also make sure there is no port conflict when starting nginx. – badmadrad Sep 23 '14 at 17:15

add a comment

up vote8down vote

You should probably check for errors in /var/log/nginx/error.log.

In my case I did no add the port for ipv6. You should also do this (in case you are running nginx on a port other than 80): listen [::]:8000 default_server ipv6only=on;

shareimprove this answer

answered Sep 29 '15 at 4:19 Arvind Bhardwaj 3,94822337

add a comment

up vote4down vote

In your /etc/nginx/nginx.conf file you have:

include /etc/nginx/site-enabled/*;

And probably the path you are using is:

/etc/nginx/sites-enabled/default

Notice the missing s in site.

shareimprove this answer

edited Apr 9 '14 at 17:07

answered Mar 28 '14 at 15:44 DanielBlanco 513

add a comment

up vote3down vote

Check the daemon option in nginx.conf file. It has to be ON. Or you can simply rip out this line from config file. This option is fully described here http://nginx.org/en/docs/ngx_core_module.html#daemon

shareimprove this answer

answered Aug 8 '13 at 11:33 zloboid 313

This was it. Thank you! – Alex Jul 5 '14 at 9:05

add a comment

up vote1down vote

1. Check for your configuration files by running the aforementioned command: sudo nginx -t.

2. Check for port conflicts. For instance, if apache2 (ps waux | grep apache2) or any other service is using the same ports configured for nginx (say port 80) the service will not start and will fail silently (err... the cousin of my friend had this problem...)

shareimprove this answer

answered Mar 18 '16 at 10:14 gtamorim 508

add a comment

up vote1down vote

One case you check that nginx hold on 80 number port in system by default , check if you have any server like as apache or anything exist on system that block 80 number port thats the problem occurred.

1 .You change port number on nginx by this way,

sudo vim /etc/nginx/sites-available/default

Change 80 to 81 or anything,

1. Check everything is ok by ,

sudo nginx -t

1. Restart server

sudo service nginx start

1. Check the status of nginx:

sudo service nginx status

Hope that will work

shareimprove this answer

answered Feb 15 at 5:37 Zahid Rahman 6691617

add a comment

up vote0down vote

I had the exact same problem with my instance. My problem was that I forgot to allow port 80 access to the server. Maybe that's your issue as well?

Check with your WHM and make sure that port is open for the IP address of your site,

shareimprove this answer

answered Jul 21 '14 at 19:40 Kousha 5,078854105

add a comment

up vote0down vote

For what it's worth: I just had the same problem, after editing the nginx.conf file. I tried and tried restarting it by commanding sudo nginx restart and various other commands. None of them produced any output. Commanding sudo nginx -t to check the configuration file gave the output sudo: nginx: command not found, which was puzzling. I was starting to think there were problems with the path.

Finally, I logged in as root (sudo su) and commanded sudo nginx restart. Now, the command displayed an error message concerning the configuration file. After fixing that, it restarted successfully.

shareimprove this answer

answered Nov 21 '14 at 17:22 Teemu Leisti 3,38622032

add a comment