FreeNAS-9.3-STABLE-201509282017 Can't Launch Shell from GUI

[FreeNASBob]

When I try to launch a shell from the GUI I just get a window that says "Loading..." and then disappears after a few seconds. After trying several times I get the following in the log:

Oct 22 19:00:32 freenas kernel: sonewconn: pcb 0xfffff8002497d0f0: Listen queue overflow: 8 already in queue awaiting acceptance (1 occurrences)

 

[FreeNASBob]

I have a feeling this is due to a script that I ran in the shell window. I closed the window without closing the script. My best guess is that shell is still active, but hidden from the GUI. I would have thought closing the shell would kill any process running in that window.

 

[FreeNASBob]

Tried looking at the console through IPMI, but top doesn't show anything that looks like my script still running. Sure hate to reboot.

 

[FreeNASBob]

Rebooted and tried to re-create the issue, but not having any success so far.

 

[FreeNASBob]

According to the BSD mailing lists this error is network related and is supposed to be when there are too many connection requests. The problem is there were no connection requests other than my Web GUI session. There's no way a gigabit card was saturated trying to load the shell window.

Edit - Looks like it might be a SAMBA issue

 

[cyberjock]

I have a feeling this is due to a script that I ran in the shell window. I closed the window without closing the script. My best guess is that shell is still active, but hidden from the GUI. I would have thought closing the shell would kill any process running in that window.

This is very possible, and I can reproduce this easily. It's also one of the reasons why I abhor the WebGUI's shell. :P

 

[Ericloewe]

This is very possible, and I can reproduce this easily. It's also one of the reasons why I abhor the WebGUI's shell. :p

My favorite quirk is how it responds extremely poorly to lag. My main workstation (I get to call it that because it uses ECC, too. :p Sounds cooler than "desktop".) has to be connected over Wi-Fi, and it's damn close to working like an Ethernet connection (a not very good one) would - except for the WebGUI shell, which is almost impossible to use. SSH is really the best way of doing these things.

 

[cyberjock]

I, personally, log into my servers via SSH key exchange. I use putty and saved all my server's info, so I double click on putty's icon, double click on the server I want, and I have an instant command line. :)

Almost as fast as the WebGUI shell, but fast enough to make it worthwhile. :P

 

[Ericloewe]

I, personally, log into my servers via SSH key exchange. I use putty and saved all my server's info, so I double click on putty's icon, double click on the server I want, and I have an instant command line. :)

Almost as fast as the WebGUI shell, but fast enough to make it worthwhile. :p

Same here, but I do have to insert the key's passphrase.