|
Sometimes database server SA16 crash (build 16.0.0.2344), no outupt log specified init switchs: -c 77p -ch 80p -ti 600 -gt 4 -gtc 4 -o E:\LogsSQL16\srvmessages.log -oe E:\LogsSQL16\srverrors.log -dt E:\TmpSQL16 -gna 0 -gn 20 -gnl 10 -gnh 100 -gns (...) (...) (...) Is there anything that i can do to identify the problem? |
|
The server did not stop, it kept running (see all the normal checkpoint messages). The server did write several messages that exactly identify the connection that terminated (see the detailed messages starting with "Connection terminated abnormally"). If a client application crashes, that is a completely separate event from the server. The server cannot be expected to know what happened on some other computer somewhere else on the network. Here is where you should be looking for the problem; i.e., the FCore.exe program running on IP=192.168.69.96: IP=192.168.69.96; HOST=pccom707; OSUSER=mgois; OS='Windows 7 Build 7601 Service Pack 1'; EXE='\Ns-uf01\app$\Fapricela\CRMSALES\Versão 2\FCore.exe'; PID=0x15dc; THREAD=0x1420; VERSION=16.0.0.2283; API=OLEDB; TIMEZONEADJUSTMENT=0; APPINFO=FCORE |
|
Nothing in these messages suggests that the server crashed. I see some messages that client apps either crashed or, possibly, terminated normally without disconnecting first. the problem is that the server don't write anything in the log when stops unexpectedly. the OS Event Viewer is not illustrative (05-12-2016 12:53:49): The SQL Anywhere - SA16 service terminated unexpectedly. It has done this 4 time(s).
(05 Dec '16, 09:58)
SamuelCosta
Replies hidden
1
What makes you think the "SA16 service terminated unexpectedly"? The message says the Fcore.exe program on IP=192.168.69.96 terminated... that's not the SA16 service, is it?
(07 Dec '16, 06:59)
Breck Carter
|
That seems contradictory to me. So do you use a console log, and if so, what does it contain before/after a crash?
no error log is created, only the message log (with the last messages before the crash) that i extracted in the post.
Well, even if the log does not contain anything when the server crashes, it should certainly contain some lines when the server is restarted (say, the product name and version number) and when the database is started (database name, recovery steps and the like). It would help us if you show these lines...
shure, but i create a new log file everytime the service is manually started. Those are the last lines before crash.
I found two files: SA16_20161205_125344_3092.CRASH_LOG_FILE and SA16_20161205_125344_3092.DMP in the SQL Anywhere 16 diagnostics folder, how can i send it?
You can send those to Product Support if you open up an incident.
Alternatively you can submit those using
dbsupport -saand let us know the submission numbers (if you didn't catch those when submitted you can list them usingdbsupport -ls)