搭建strom測試環境後，程序、ui介面一切正常，但奇怪的是，下次登入伺服器重新檢查程序發現整個storm shut down，檢視日誌如下：
nimbus.log
2017-09-15t15:06:16.690+0800o.a.s.z.clientcnxn [info] socket connection established to e3base1/172.21.8.64:11001,initiating session
2017-09-15t15:06:16.698+0800o.a.s.z.clientcnxn [info] session establishment complete on servere3base1/172.21.8.64:11001, sessionid = 0x15e5a6ab4630023, negotiated timeout =20000
2017-09-15t15:06:16.698+0800 o.a.s.c.f.s.connectionstatemanager[info] state change: connected
2017-09-15t15:06:16.726+0800 b.s.d.nimbus[info] starting nimbus server...
2017-09-15t16:43:26.548+0800 b.s.d.nimbus[info] shutting down master
2017-09-15t16:43:26.590+0800o.a.s.z.zookeeper [info] session: 0x15e5a6ab4630023 closed
2017-09-15t16:43:26.590+0800o.a.s.z.clientcnxn [info] eventthread shut down
2017-09-15t16:43:26.591+0800 b.s.d.nimbus[info] shut down master
supervisor.log
2017-09-15t15:01:22.921+0800o.a.s.z.clientcnxn [info] socket connection established toe3base1/172.21.8.64:11001, initiating session
2017-09-15t15:01:22.928+0800o.a.s.z.clientcnxn [info] session establishment complete on servere3base1/172.21.8.64:11001, sessionid = 0x15e5a6ab4630022, negotiated timeout =20000
2017-09-15t15:01:22.929+0800o.a.s.c.f.s.connectionstatemanager [info] state change: connected
2017-09-15t15:01:23.001+0800b.s.d.supervisor [info] starting supervisor with idabda54aa-1c8a-49d3-bf53-9db3d32ba5dd at host e3base3
2017-09-15t16:43:26.546+0800b.s.d.supervisor [info] shutting down supervisorabda54aa-1c8a-49d3-bf53-9db3d32ba5dd
2017-09-15t16:43:26.551+0800 b.s.event[info] event manager interrupted
2017-09-15t16:43:26.551+0800 b.s.event[info] event manager interrupted
2017-09-15t16:43:26.563+0800o.a.s.z.zookeeper [info] session: 0x15e5a6ab4630022 closed
2017-09-15t16:43:26.563+0800o.a.s.z.clientcnxn [info] eventthread shut down
分析了storm日誌、zookeeper日誌沒有發現異常資訊；
storm啟動採用如下方式：
storm nimbus > /dev/null 2>&1 &
storm supervisor > /dev/null 2>&1 &
嘗試將啟動方式修改為
nohup storm nimbus > /dev/null 2>&1 &
nohup storm supervisor > /dev/null 2>&1 &
修改為上述啟動命令後問題解決。
mysql 宕掉 問題解決
可能原因是資料過多導致。mysql 命令可以識別 但是進去後不能執行相關的mysql命令，需要 1，停掉mysql 2，在 etc my.cnf 檔案中新增innodb force recovery 6 如下示 innodb強制恢復 mysqld innodb force recovery 4 1 ...
mysql宕掉的問題解決
mysql宕掉的問題解決 可能原因是資料過多導致。mysql 命令可以識別 但是進去後不能執行相關的mysql命令，需要 www.2cto.com 1，停掉mysql 2，在 etc my.cnf 檔案中新增innodb force recovery 6 如下示 innodb強制恢復 mysqld ...
MapWindow異常問題解決
初次編譯mapwindow5，總是碰到com元件失敗的問題，如下圖所示 異常內容為 內部異常 1 comexception 檢索 com 類工廠中 clsid 為 的元件失敗，原因是出現以下錯誤 80040154 沒有註冊類 異常來自 hresult 0x80040154 regdb e class...