#Rebooting gateway nodes

1 messages · Page 1 of 1 (latest)

fleet pawn
#

I have a customer that has twice in the past six months had an issue where Fabricpool files stopped getting served. They are visible but not available.

Messages indicate an issue to the storage grid.

Message: object.store.unavailable: Unable to connect to the object store "SGFabricPool" from node 3bd646cf-4fcd-11ec-b7c6-d039ea20b454. Reason: Connection unavailable

Rebooting the gateways fixes the issue.

spiral grotto
#

Strage, I suggest to open a case with Netapp to have ONTAP, StorageGrid and config checked.
I have many customers running for years without any issues.

visual aurora
#

there have been a number of similar issues fixed in recent "hotfixes" as well, so staying up-to-date is a good idea

tight mountain
#

yeah, we hit "0045115: Ensure client requests are completed in the case where the VRF default route is missing for an HA group configured as ACTIVE-ACTIVE " that was fixed in 11.7.0.3... always having the latest hotfix is a good idea

visual aurora
#

there are some serious bugs introduced around 11.7.0.4, iirc, that can really make a mess... 11.7.0.6 is the recommended release

fleet pawn
#

Yeah, will found out they steed way behind…11.5.0.5.

Working a time to get updated

spiral grotto
#

Ok, 11.5.0.5 is really old. Update to 11.5.0.11 first then directly to 11.6.0.14 (major and hotfix update at the same time!). Then you are save. Optionally update to 11.7.0.6.
Also check there ONTAP version. There was a bug in ONTAP that could cause a similar behaviour. I don’t care so much what major version you are running but you should Patch should be high. Example: It’s more save to run a 9.8P20 than a 9.13.1P1