ppumkin
Dabbler
- Joined
- Aug 16, 2012
- Messages
- 11
I upgraded a remote box that was on 9.2 to 9.10 - saw 9.x is in maintenance mode, so...
Any way I have other boxes running 11.x and was all good so I decided to upgrade this remote box to 11.3 .. STABLE - right?
Error:
Connecting to FreeNAS ... Make sure the FreeNAS system is powered on and connected to the network..
I had a search on the forums here and this issue was reported in 11.2 like some thread was going on for a while and ended in December 2018 so not sure why this happening in 11.3-STABLE?
I tried all sorts of things suggests as I outline below. Does any body have a work around, please?!
I first thought it was because I was initially on Server 2012 and I don't think that supports web sockets.. or maybe some restrictive policy, so I RDP onto a Win10 machine and the same issue. Getting hundred of web sockets errors 502 like in the tens of other threads found here from 2018, early 2019ish for 11.2-BETA
I cleared browser caches, I disabled internet security scanners, incognito mode, /IP/legacy takes me back to the non legacy URL, and the IP/legacy?
Interestingly on the /legacy/account/login?/next=/legacy/ I get stack trace
Request Method: GET
Request URL: http://192.168.1.100/legacy/account/login?/next=/legacy/
Software Version: FreeNAS-11.3-U1 (34d6357440)
Exception Type: OperationalError
Exception Value: no such column: system_settings.stg_crash_reporting
no such column: system_settings.stg_crash_reporting
Exception Location: ./freenasUI/freeadmin/sqlite3_ha/base.py in execute, line 381
Server time: Thu, 5 Mar 2020 08:56:31 +0000
Which points to a sqlite database problem?? is it valid?
What makes it worse is that SMB, or my iSCSCI does NOT work! And SSH root login does not work either and this is a remote box so I basically f****d my life now.
Have to take a day off and go there now. You do these things so often and it just works and then the least expected time and worst case scenario it bites you. That is my fault I am an idiot.. should have known better.
Any way I have other boxes running 11.x and was all good so I decided to upgrade this remote box to 11.3 .. STABLE - right?
Error:
Connecting to FreeNAS ... Make sure the FreeNAS system is powered on and connected to the network..
I had a search on the forums here and this issue was reported in 11.2 like some thread was going on for a while and ended in December 2018 so not sure why this happening in 11.3-STABLE?
I tried all sorts of things suggests as I outline below. Does any body have a work around, please?!
I first thought it was because I was initially on Server 2012 and I don't think that supports web sockets.. or maybe some restrictive policy, so I RDP onto a Win10 machine and the same issue. Getting hundred of web sockets errors 502 like in the tens of other threads found here from 2018, early 2019ish for 11.2-BETA
I cleared browser caches, I disabled internet security scanners, incognito mode, /IP/legacy takes me back to the non legacy URL, and the IP/legacy?
Interestingly on the /legacy/account/login?/next=/legacy/ I get stack trace
Request Method: GET
Request URL: http://192.168.1.100/legacy/account/login?/next=/legacy/
Software Version: FreeNAS-11.3-U1 (34d6357440)
Exception Type: OperationalError
Exception Value: no such column: system_settings.stg_crash_reporting
no such column: system_settings.stg_crash_reporting
Exception Location: ./freenasUI/freeadmin/sqlite3_ha/base.py in execute, line 381
Server time: Thu, 5 Mar 2020 08:56:31 +0000
Which points to a sqlite database problem?? is it valid?
What makes it worse is that SMB, or my iSCSCI does NOT work! And SSH root login does not work either and this is a remote box so I basically f****d my life now.
Have to take a day off and go there now. You do these things so often and it just works and then the least expected time and worst case scenario it bites you. That is my fault I am an idiot.. should have known better.
Last edited: