Freenas Web Acces error

[informatica chk]

hello
i´m using freenas 9.3 relaesed version.
it was working fin till today i couldnt acces to Web GUI.
i updated nothing, so i was rebooting the server, but still, no web acces,
i could acces via ssh, the server is working fine, but just the web access no.
heere the error
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check theerror log for details.

Faithfully yours, nginx.

cat /var/log/nginx-error.log
2015/12/16 12:25:27 [error] 10044#0: *1 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 12:25:27 [error] 10044#0: *1 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:26:15 [error] 10044#0: *1 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 12:26:15 [error] 10044#0: *1 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:28:38 [error] 10044#0: *8 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450279793316 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:30:42 [error] 10044#0: *10 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 12:30:42 [error] 10044#0: *10 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:33:38 [error] 10044#0: *14 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450280093295 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:34:18 [error] 10044#0: *18 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 12:34:18 [error] 10044#0: *18 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:34:23 [error] 10044#0: *21 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 12:38:38 [error] 10044#0: *23 connect() to 127.0.0.1:9042 failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450280393287 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:43:38 [error] 10044#0: *25 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450280693264 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:48:37 [error] 10044#0: *27 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450280993270 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:53:37 [error] 10044#0: *29 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450281293260 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 12:58:37 [error] 10044#0: *31 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450281593227 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 13:02:19 [error] 10044#0: *33 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 13:02:19 [error] 10044#0: *33 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 13:03:37 [error] 10044#0: *37 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450281893223 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 13:08:37 [error] 10044#0: *39 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450282193215 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 13:11:30 [error] 10044#0: *41 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3"
2015/12/16 13:11:30 [error] 10044#0: *41 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.3.151, server: localhost, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
2015/12/16 13:13:37 [error] 10044#0: *45 kevent() reported that connect() failed (61: Connection refused) while connecting to upstream, client: 192.168.1.16, server: localhost, request: "GET /admin/alert/status/?1450282493181 HTTP/1.1", upstream: "fastcgi://127.0.0.1:9042", host: "192.168.3.3", referrer: "http://192.168.3.3/"
[root@com-chlp-3003] ~#

 

[informatica chk]

my server ip is 192.168.3.3
my pc ip is 192.168.3.151

i tried to acces with diferent pc´s , but nothing different

 

[hugovsky]

Try to install freenas again and startover.

 

[informatica chk]

if there is no other soluccion i have to do it,
got over 200 users on my server.
and my backup config to, but i would love to try a different soluccion, so that i could use if it happends again

 

[SweetAndLow]

Try restarting nginx

 

[informatica chk]

dosnt work neither

 

[mhampton]

I had the same problem this morning (9.3-STABLE). No idea what broke the gui, but running "service django start" fixed it temporarily. Not a real "fix" but perhaps a workaround.

 

[informatica chk]

hello
thanks for the answer.. i tried , but i got this error starting the services
[root@com-chlp-3003] ~# service django start
Traceback (most recent call last):
File "/usr/local/lib/python2.7/encodings/__init__.py", line 44, in <module>
_aliases = aliases.aliases
AttributeError: 'module' object has no attribute 'aliases'

 

[mhampton]

I had the same problem this morning (9.3-STABLE). No idea what broke the gui, but running "service django start" fixed it temporarily. Not a real "fix" but perhaps a workaround.

Reviewing /var/log/messages, in my case some processes were killed by the kernel Sunday afternoon due to lack of swap space, including python2.7 which is the gui:

Code:

Dec 20 14:06:55 nas01 kernel: pid 6393 (python2.7), uid 0, was killed: out of swap space
Dec 20 14:06:55 nas01 kernel: pid 6393 (python2.7), uid 0, was killed: out of swap space
Dec 20 14:07:04 nas01 kernel: pid 6464 (collectd), uid 0, was killed: out of swap space
Dec 20 14:07:04 nas01 kernel: pid 6464 (collectd), uid 0, was killed: out of swap space
Dec 20 14:07:07 nas01 kernel: pid 6389 (python2.7), uid 0, was killed: out of swap space
Dec 20 14:07:07 nas01 kernel: pid 6389 (python2.7), uid 0, was killed: out of swap space
Dec 20 14:07:08 nas01 kernel: pid 6111 (smbd), uid 0, was killed: out of swap space
Dec 20 14:07:08 nas01 kernel: pid 6111 (smbd), uid 0, was killed: out of swap space

So apparently my CIFS service (which fortunately no one is currently using) and the system stats collection daemon were also killed.

The python2.7 daemons consume a lot of memory; In my case python2.7 processes currently consume ~1GB.

My server has 32GB of ram, so the above errors are a bit disconcerting. I also found it odd that no swap is configured on the server by the FreeNAS installer. I get it that swapping is undesirable, but killing processes is more undesirable IMHO.

 

[rsquared]

Swap has to go to a drive, and you don't want it on your boot drive, so it gets set up when you create your pool. It should default to 2 GB/drive I believe.

 

[mhampton]

Swap has to go to a drive, and you don't want it on your boot drive, so it gets set up when you create your pool. It should default to 2 GB/drive I believe.

I just manually added a 64GB swap device on a spare 180GB SSD. I'm just surprised that the installer didn't do this.

 

[gpsguy]

By default, FreeNAS creates a 2GB swap partition on each drive when using the web gui to create the pool.

Did you create your pool using the web gui? If so, if you do a "gpart show" without the quotes from the shell, do you see the swap partitions on each drive?


Sent from my phone

 

[mhampton]

By default, FreeNAS creates a 2GB swap partition on each drive when using the web gui to create the pool.

Did you create your pool using the web gui? If so, if you do a "gpart show" without the quotes from the shell, do you see the swap partitions on each drive?

Sent from my phone

Well that explains it. I didn't use the gui to create my pool. I had 48 disks, and initially I didn't see a way to create 1 pool with multiple vdevs using the gui, so I created the pool via the command line. Then I exported it via the command line, and imported it via the gui.

So now I'm curious: Since I didn't use the gui to create the pool, what else is missing?

 

[pirateghost]

Well that explains it. I didn't use the gui to create my pool. I had 48 disks, and initially I didn't see a way to create 1 pool with multiple vdevs using the gui, so I created the pool via the command line. Then I exported it via the command line, and imported it via the gui.

So now I'm curious: Since I didn't use the gui to create the pool, what else is missing?

I don't know what you're missing but you can indeed create a pool with multiple vdevs.

Create vdev and pool
Create new vdev out of next set of disks,and select to extend the pool (its a drop down in the volume manager)
Rinse.
Repeat.

 

[gpsguy]

One of the reasons for putting a swap partition on each drive is to facilitate disk swaps. Should a drive fail and you need to replace it, sometimes the replacement might be a few bytes smaller than the original one. With the swap partition in place, FreeNAS can resize that partition so you can use the drive.

Since you say that you have 48 disks and 32GB RAM - how big is your pool. It appears that you need to add RAM.

While you would have had swap space had you let it partition the drives, it should have sufficient RAM so it doesn't have to use the swap space.


Sent from my phone

 

[mhampton]

One of the reasons for putting a swap partition on each drive is to facilitate disk swaps. Should a drive fail and you need to replace it, sometimes the replacement might be a few bytes smaller than the original one. With the swap partition in place, FreeNAS can resize that partition so you can use the drive.

Since you say that you have 48 disks and 32GB RAM - how big is your pool. It appears that you need to add RAM.

While you would have had swap space had you let it partition the drives, it should have sufficient RAM so it doesn't have to use the swap space.

Sent from my phone

The disks are 600GB disks; the pool is ~30TB. I read here that 1GB of memory per TB was sufficient, and I am satisfied with performance so far. For now, adding swap will do the trick I think.

At some point I'm going to rebuild this pool, and I'll use the GUI (among other changes) which will solve this problem as well as the problem of slightly different disk sizing (which has already bit me).

 

[informatica chk]

[root@com-chlp-3003] ~# nginx
nginx: [emerg] bind() to 192.168.3.3:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 192.168.3.3:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 192.168.3.3:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 192.168.3.3:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 192.168.3.3:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] still could not bind()

is that the problem?
i still dont get to fix it