Sorry, a problem occurred

Status
Not open for further replies.

balanga

Patron
Joined
Jul 10, 2014
Messages
271
I keep getting this msg whenever I select anything in the GUI.

How do I establish the nature of the 'problem'?

I am able to open a virtual console as well as being able to connect via ssh.

I did notice that on the operator's console there are msgs about

'smb_panic():' and

'dumping core in /var/db/system/cores'

but have no idea if this is related to the GUI problem....
 

balanga

Patron
Joined
Jul 10, 2014
Messages
271
I have just tried re-loading the FreeNAS GUI and get the following:-

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.


So I presume you mean nginx-error.log....

That has over 50 lines most of which say something like

'kevent() reported that connect() failed (61: Connection refused) while coonecting to upstream, ...
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
Samba panicking?

How about starting by posting your hardware, so we know what we're dealing with?

The logs would also be useful, the manual should say where they are.
 

balanga

Patron
Joined
Jul 10, 2014
Messages
271
Maybe bad media? Try to reinstall and restore backup of config.

Following a reboot, the preceding errors magically disappeared, so it seems unlikely that bad media was the problem...and hence no need for a reinstall or restoration of a config.
 

Noctris

Contributor
Joined
Jul 3, 2013
Messages
163

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Yeah that person doesn't have hardware that works correctly. So if op isn't meeting minimum system requirements then it's the same problem.
 

Noctris

Contributor
Joined
Jul 3, 2013
Messages
163
@SweetAndLow I meant it more in the literal way :smile:.. same guy posting the same issue twice.
 
Status
Not open for further replies.
Top