FreeNAS 11.1 GUI and SSH become unresponsive

Inabon

Dabbler
Joined
Dec 22, 2017
Messages
14
After heavy hard drive usage moving big files or leaving it for 8+ hours on GUI and SSh become unresponsive. Jails Work. Plex, transmission, nextcloud function properly.

Dec 22 22:19:30 freenas daemon3073: ==> Newer Consul version available: 1.0.2 (currently running: 1.0.0) <--- i think this may be an issue

have a bunch of these
2017/12/22 22:19:19 [WARN] agent: check "service:nas-health" has the 'script' field, which has been deprecated and replaced with the 'args' field. See https://www.consul.io/docs/agent/checks.html
don´t know how to fix

I was able to replicate issue with errors in consul similar to these

(da1:umass-sim1:1:0:0): WRITE. CDB: 2a 00 00 34 67 4d 00 00 80 00
(da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(da1:umass-sim1:1:0:0): Retrying command
(da1:umass-sim1:1:0:0): WRITE. CDB: 2a 00 00 34 67 4d 00 00 80 00
(da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(da1:umass-sim1:1:0:0): Error 5, Retries exhausted

It happens only when moving big files for example transmission moves a download from dir incomplete to Downloads dir

forgot to mention jails continue to work pretty normally even though ui and ssh quit responding.

ssh on jails works fine if you are logged in to jail through jexec but when you exit jail ssh to main system is frozen

hardware I had to reboot this morning.

Build FreeNAS-11.1-RELEASE
Platform Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
Memory 24537MB <---ECC
System Time Sat, 23 Dec 2017 06:21:17 -0500
Uptime 6:21AM up 4 mins, 0 users
Load Average 0.48, 0.36, 0.16
 

Inabon

Dabbler
Joined
Dec 22, 2017
Messages
14
I also have these

Dec 23 06:20:17 freenas daemon[3073]: 2017/12/23 06:20:17 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:22:23 freenas daemon[3073]: 2017/12/23 06:22:23 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:24:30 freenas daemon[3073]: 2017/12/23 06:24:30 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:26:36 freenas daemon[3073]: 2017/12/23 06:26:36 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:28:42 freenas daemon[3073]: 2017/12/23 06:28:42 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:30:49 freenas daemon[3073]: 2017/12/23 06:30:49 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:32:55 freenas daemon[3073]: 2017/12/23 06:32:55 [WARN] agent: Check 'service:nas-health' is now warning
Dec 23 06:35:02 freenas daemon[3073]: 2017/12/23 06:35:02 [WARN] agent: Check 'service:nas-health' is now warning
 

shamo316

Dabbler
Joined
Jun 21, 2016
Messages
30
im also getting that error

freenas daemon[4277]: Newer Consul version available: 1.0.2 (currently running: 1.0.0)

No issues with any drives or jails
 

majerus

Contributor
Joined
Dec 21, 2012
Messages
126
I am seeing issues where the GUI and SSH are very slow for reasons I cannot track down in 11.1 which causes me to have to reboot every 5 days or so.
 

INCSlayer

Contributor
Joined
Apr 4, 2015
Messages
197
i have been seeing similar issues and am having issues tracking down whats causing it aswell
 

styno

Patron
Joined
Apr 11, 2016
Messages
466

majerus

Contributor
Joined
Dec 21, 2012
Messages
126

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Please include details of your hardware when reporting problems. Many problems appear similar, but can be totally unrelated. Detailed descriptions of the hardware can help rule out some things.
 

windyboi

Explorer
Joined
Jan 7, 2016
Messages
79
HP Microserver Gen8. Intel(R) Xeon(R) CPU E31260L @ 2.40GHz, 16GB RAM. I haven't had any of these problems prior to 11.1 and have been using FreeNAS for 3 years or so.
 

windyboi

Explorer
Joined
Jan 7, 2016
Messages
79
Inabon, shamo316, INCSlayer, did you find a resolution for this? It keeps happening to me.
 

Shiunbird

Cadet
Joined
Feb 2, 2019
Messages
9
(da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(da1:umass-sim1:1:0:0): Retrying command
(da1:umass-sim1:1:0:0): WRITE. CDB: 2a 00 00 34 67 4d 00 00 80 00
(da1:umass-sim1:1:0:0): CAM status: CCB request completed with an error
(da1:umass-sim1:1:0:0): Error 5, Retries exhausted

Had exactly this. Fixed by moving USB boot flash from internal port to rear USB 2 port and replacing it. (Yes, had to do both things)
 

Shiunbird

Cadet
Joined
Feb 2, 2019
Messages
9
HP Microserver Gen8. Intel(R) Xeon(R) CPU E31260L @ 2.40GHz, 16GB RAM. I haven't had any of these problems prior to 11.1 and have been using FreeNAS for 3 years or so.

Dead web ui on my gen8 fixed by logging in to the console via ILO, putting interface to which web ui is bind down via ifconfig, then bringing it up via dhclient to force dhcp request. Problem isolated by connecting both NICs and binding shares to second NIC with fixed IP and binding web ui to first NIC with DHCP.

I gave up on the internal USB por on my gen8. I tried 3 flash drives and they were all giving me the errors mentioned on the first message. No errors after I started using the rear USB port. I have no idea why... I was very frustrated and came to the point of trying even illogical things.

Sorry for the weirdness of the answer. Writing from my tablet.
 

windyboi

Explorer
Joined
Jan 7, 2016
Messages
79
Dead web ui on my gen8 fixed by logging in to the console via ILO, putting interface to which web ui is bind down via ifconfig, then bringing it up via dhclient to force dhcp request. Problem isolated by connecting both NICs and binding shares to second NIC with fixed IP and binding web ui to first NIC with DHCP.

I gave up on the internal USB por on my gen8. I tried 3 flash drives and they were all giving me the errors mentioned on the first message. No errors after I started using the rear USB port. I have no idea why... I was very frustrated and came to the point of trying even illogical things.

Sorry for the weirdness of the answer. Writing from my tablet.

Thanks Shiunbird. I will try this out - perhaps I'll use one of the front USB for redundancy. Out of interest, which make/model of USB did you go for? And you are not using dual boot now?
 
Top