メインコンテンツへスキップ

RSMが停止しているため、S3 API経由でStorageGRID にアクセスできません

Views:
2
Visibility:
Internal
Votes:
0
Category:
storagegrid<a>2008683264</a>
Specialty:
sgrid
Last Updated:

環境

StorageGRID 11.2.0.5以前

問題

  • S3 API経由でStorageGRID にアクセスできません。
  • SVST(Status - Replicated State Machine Service (RSM)) が原因でアラームが検出されました Not Running

例:

91d79ed3-6b1c-4120-ac58-907da8aece8e.png

  • bycast-err.log をクリックrsm: rsm panicします。

例:

<HOST> rsm: rsm panic

  • servermanager.log を表示します。Replicated State Machine(RSM)サービスが、何度も失敗して開始した結果、エラー状態になったことを示します。

例:

rsm             | start initiated
rsm             | rsm starting
rsm             | rsm ended
rsm             | rsm starting
rsm             | rsm ended
rsm             | rsm starting
rsm             | rsm ended
..
rsm             | rsm starting
rsm             | rsm ended
rsm             | Too many failed attempts, entering error state
rsm             | rsm ended

 

  • rsm.errlog RSMがパニック状態 SIGSEGVになることを示します。

例:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0xa4cf23]

goroutine 150 [running]:
storagegrid/rsm/client.(*ESClient).Execute(0xc42038a6a0, 0xd21d40, 0xc420c2c1e0, 0x0)
   /build/go/src/storagegrid/rsm/client/search.go:198 +0x603
main.requestExecutor(0xc420520360, 0xc420512000, 0xc420514200, 0xc420d43f98, 0xc420514300)
   /build/go/src/storagegrid/rsm/request_runner.go:159 +0x6e8
main.run.func5(0xc4203ba3f0, 0xc420514200, 0xc420512000, 0xc42021c000, 0xc420514300)
   /build/go/src/storagegrid/rsm/run.go:162 +0x92
created by main.run
   /build/go/src/storagegrid/rsm/run.go:160 +0x899

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

This is an internal KB article and its content should not be copy/pasted and shared with people outside of NetApp. Always seek Duty Manager authentication of caller for password reset requests. If you need further assistance post a question in Knowledge Xchange