Posted by Barbara Brazil on May 31, 2017 at 11:48:30:
In Reply to: Comet Database server crash...> posted by Tom Fulton on May 31, 2017 at 10:06:07:
One log that you didn't send that might help is a Comet.log from one of the nodes. It certainly seems like something went wrong and if it happens again here are some things to try.
Just because you see the red slash thru the UI tray icon doesn't necessarily mean the server has stopped. There are times when the UI can lose it's connection to the server. You can verify if the server is still running by checking the Task Manager (be sure to show processes from all users). The file server is CFileSrv.exe. The Security Server is CSecSrv.exe. If the server you think has stopped is still running you can reconnect the UI by shutting down the UI window (File->Exit) then restarting the UI. This will not affect any users. The UIs are FileSrvUI.ex and SecSrvUI.exe.
If you do suspect a crash you might review the Windows Event log to verify. There may be some useful info there.
BTW the error 57 you see in CometNTService.log can be eliminated by changing a setting in the CometNTService.ini file. Open it in a text editor and change ProcCount=4 to ProcCount=3. This error is not harmful, just causes confusion in the log. It's trying to start one too many programs and failing on the 4th one which is not named.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.