Opened 13 months ago
Closed 6 months ago
#1479 closed defect (fixed)
8.2.0-BETA3 nginx refuses connections-or doesn't start
| Reported by: | mmx | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 8.3.0-RELEASE |
| Component: | Backend | Version: | 8.2.0-RELEASE-p1 |
| Keywords: | Cc: |
Description
My config is set to 0.0.0.0 for the listening interface for the web server, and for https. Nginx is refusing connections, although I verified that it is running.
When I kill the nginx process and restart it with /etc/rc.d/ix-nginx start the same behavior occurs.
When I kill the nginx process and restart it with #nginx then I can get the web interface loading properly.
MMX
Attachments (1)
Change History (11)
comment:1 Changed 13 months ago by mmx
comment:2 Changed 12 months ago by william
- Milestone set to 8.2-RELEASE
Can you paste output of sockstat -4 on a clean startup?
And
# sqlite3 /data/freenas-v1.db "select * from system_settings"
comment:3 Changed 10 months ago by william
- Resolution set to worksforme
- Status changed from new to closed
Closing for timeout, feel free to reopen.
comment:4 Changed 9 months ago by mmx
This started happening again. :(
[root@tank] ~# sqlite3 /data/freenas-v1.db "select * from system_settings"
Asia/Bangkok||https||1|0.0.0.0||en
[root@tank] ~# sockstat -4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root sshd 4240 5 tcp4 10.2.2.11:22 10.2.2.167:50373
root sshd 2980 5 tcp4 *:22 *:*
root istgt 2811 5 tcp4 *:3260 *:*
root afpd 2741 4 tcp4 6 *:548 *:*
root cnid_metad 2738 3 tcp4 127.0.0.1:4700 *:*
avahi avahi-daem 2728 14 udp4 *:5353 *:*
avahi avahi-daem 2728 16 udp4 *:60993 *:*
root python 2433 3 tcp4 127.0.0.1:9042 *:*
root rsync 2404 5 tcp4 *:873 *:*
root nmbd 2033 9 udp4 *:137 *:*
root nmbd 2033 10 udp4 *:138 *:*
root nmbd 2033 11 udp4 10.2.2.11:137 *:*
root nmbd 2033 12 udp4 10.2.2.255:137 *:*
root nmbd 2033 13 udp4 10.2.2.11:138 *:*
root nmbd 2033 14 udp4 10.2.2.255:138 *:*
root ntpd 1852 20 udp4 *:123 *:*
root ntpd 1852 22 udp4 10.2.2.11:123 *:*
root ntpd 1852 25 udp4 127.0.0.1:123 *:*
root rpc.statd 1820 6 udp4 *:975 *:*
root rpc.statd 1820 7 tcp4 *:975 *:*
root nfsd 1803 3 tcp4 *:2049 *:*
root mountd 1785 7 udp4 *:872 *:*
root mountd 1785 8 tcp4 *:872 *:*
root rpcbind 1781 9 udp4 *:111 *:*
root rpcbind 1781 10 udp4 *:806 *:*
root rpcbind 1781 11 tcp4 *:111 *:*
root syslogd 1635 7 udp4 *:514 *:*
[root@tank] ~#
comment:5 Changed 9 months ago by mmx
- Resolution worksforme deleted
- Status changed from closed to reopened
- Summary changed from 8.2.0-BETA3 nginx refuses connections to 8.2.0-BETA3 nginx refuses connections-or doesn't start
- Version changed from 8.2.0-BETA2 to 8.2.0-RELEASE-p1
comment:6 Changed 9 months ago by william
Ok so nginx is not running...
Is this on happening right after a reboot? How much ram do you have?
Attach:
# dmesg -a
After a reboot, please.
comment:7 Changed 9 months ago by william
- Milestone 8.2.0-RELEASE deleted
Changed 9 months ago by mmx
comment:8 Changed 9 months ago by mmx
after reboot the console message says:
You may try the following URLs to access the web user interface:
https://10.2.2.11:80/
dmesg reports nginx fails to start as you can see in the attached file, but in fact the process is running:
[root@tank] ~# ps auxw | grep nginx root 2703 0.0 0.1 27688 5784 ?? Is 1:20PM 0:00.00 nginx: master process /usr/local/sbin/nginx www 2704 0.0 0.1 27688 6392 ?? I 1:20PM 0:00.01 nginx: worker process (nginx) root 4310 0.0 0.0 8976 1412 0 S+ 1:26PM 0:00.01 grep nginx [root@tank] ~#
In order to get it running I have to
- killall nginx
- /etc/rc.d/ix-nginx start (this creates the proper configuration file. If i don't do this the configuration file has the ssl certificate lines commented out
- killall nginx (usually its not running at this point, but sometimes it is.
- run "nginx" from command line.
I've also attached the nginx.conf file after a reboot:
I think something is corrupted in my configuration database. I did a clean install of 8.2.0-RELEASE on a new USB drive and swapped into the server, and then restored the config and the problem remained.
comment:9 Changed 6 months ago by mmx
This problem went away when I upgraded to 8.3.0-RELEASE. Thanks.
comment:10 Changed 6 months ago by william
- Milestone set to 8.3.0-RELEASE
- Resolution set to fixed
- Status changed from reopened to closed

I did upgrade from 8.0.3-RELEASE via GUI Upgrade. Let me know if that could cause problems. --MMX