SOLVED Unhandled Exception

Status
Not open for further replies.

Ben King

Cadet
Joined
Sep 7, 2016
Messages
5
Hi, we have freenas 9.10 and had a disk report bad sectors, so we thought we would replace it before it completely failed, to do this i used to command line as i am familiar with zfs on linux so am used to the zpool and zfs commands, so i set the old disk as offline (mostly so i could identify which disk it was), then pulled out the disk and put the new one in and replaced the old disk with the new one.

But then went back into freenas web ui and it was saying: Unhandled Exception

django seems to be running fine i can restart it without any errors


but the problem seems to be with nginx, here is the dump of when i try and start nginx:

service nginx start
Performing sanity check on nginx configuration:
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Starting nginx.
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:443 failed (48: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:80 failed (48: Address already in use)
nginx: [emerg] bind() to [::]:80 failed (48: Address already in use)




Originally i thought this may have been a problem with me using the command line to change things and the changes were not saved in the freenas web ui database, but now it looks more like a problem with nginx not being able to bind to a port, it seems to look like the port is in use by another process but im pretty sure its not.

Thanks for any help, Ben
 

Ben King

Cadet
Joined
Sep 7, 2016
Messages
5
I have also attached the new drive to the pool using a gptid of: gptid/51546e94-7508-11e6-82a4-00238bce5630

so this should not cause any problems for the web ui i dont think.
 

Ben King

Cadet
Joined
Sep 7, 2016
Messages
5
And this is the output if i wget on the port the web ui is running on (i hope) localhost:

wget localhost:9042
--2016-09-07 16:26:42-- http://localhost:9042/
Resolving localhost (localhost)... 127.0.0.1, ::1
Connecting to localhost (localhost)|127.0.0.1|:9042... connected.
HTTP request sent, awaiting response...



It just hangs at awaiting response.
 

Sakuru

Guru
Joined
Nov 20, 2015
Messages
527
In 9.x you really should only use the command line for troubleshooting, not changing things or performing maintenance. Doing so causes inconsistencies in the middleware and strange things happen.
 

Ben King

Cadet
Joined
Sep 7, 2016
Messages
5
Ok i will do in the future but looks like everything is working now so got away with it.

Thanks for the help.
 
Status
Not open for further replies.
Top