SQL Anywhere for Linux - Re: ASA 9.0.1 (1989) Message Unable to synchronize due to external

Author

Re: ASA 9.0.1 (1989) Message Unable to synchronize due to external

Mark Culp

2005-04-05, 8:03 pm

Ok, I missed the fact that the "last line" was the subject of your posting.

What this message means is that the SYSV semaphore that the engine uses
internally (and externally as part of communications) was deleted, and therefore
it could not function properly, and therefore it decided to shutdown.

This can happen for a number of reasons, including someone using ipcrm to
delete the semaphore. But we've seen this a number of times now... and
it could be caused by the engine crashing somewhere, at which point the sig
handle catches it and attempts to cleanup the resources (including the
semaphore)
before it calls abort() - the issue that we have seen is that one of the threads
in the engine detects that the semaphore is gone and spits out this message
(before the other thread has got to the point of calling abort()).

What was the line(s) prior to this in the console output? This information
may provide some insight on the true reason for the shutdown.

Can you repro the problem?
--
Mark Culp
ASA Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------

José Henrique wrote:
>
> Hi,
>
> my ASA database is crashing e I see this message in last line of output
> file (-o param at dbsrv9).
>
> What's this message?
>
> Regards,
>
> José Henrique

José Henrique

2005-04-05, 8:03 pm

Mark, the output logs of day 03/24/2005

1º Shutdown

I. 03/24 10:26:46. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 10:26
I. 03/24 10:26:46. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 10:26
I. 03/24 10:26:46. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 10:26
I. 03/24 10:26:59. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 10:26
I. 03/24 10:26:59. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 10:26
I. 03/24 10:34:05. Disconnecting Client - No activity for 10 minutes
I. 03/24 10:34:05. Disconnected TCPIP client's AppInfo:
HOST=JONE0;OS=Window
s XP Build 2600
;PID=0x6c8;THREAD=0x
3ac;EXE=C:\Program Files\Sybase\Shared\
Sybase
Central
4.3\win32\scjview.exe;VERSION=9.0.2. 2542;API=ODBC;TIMEZO
NEADJUSTMENT=-180
I. 03/24 11:12:54. Disconnecting Client - No activity for 4 minutes
I. 03/24 11:12:54. Disconnected TCPIP client's AppInfo:
HOST=PROG1;OS=Window
s XP Build 2600 Service Pack
2;PID=0xbf0;THREAD=0
xb4c;EXE=C:\Arquivos
de programas\Sybase\SQL

Anywhere
9\win32\dbisql.exe;VERSION=9.0.2. 3044;API=ODBC;TIMEZO
NEADJUSTMENT=-180
I. 03/24 11:14:30. Unable to synchronize due to external event - engine
shutting down

2º Shutdown

I. 03/24 13:19:05. Disconnecting Client - No activity for 4 minutes
I. 03/24 13:19:05. Disconnected TCPIP client's AppInfo:
HOST=HERA;OS=Windows
2003 Build 3790
;PID=0xb58;THREAD=0x
a60;EXE=C:\creditran
\servicos\iBanking.exe;VERSION=9.0.2. 3044;API=DBLIB;TIMEZ
ONEADJUSTMENT=-180
I. 03/24 13:25:59. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 13:25
I. 03/24 13:25:59. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 13:25
I. 03/24 13:27:13. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 13:27
I. 03/24 13:27:14. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 13:27
I. 03/24 13:41:27. Disconnecting Client - No activity for 10 minutes
I. 03/24 13:41:27. Disconnected TCPIP client's AppInfo:
HOST=PROG1;OS=Window
s XP Build 2600 Service Pack
2;PID=0x9a0;THREAD=0
xa40;EXE=C:\Arquivos
de
programas\Sybase\Sha
red\Sybase Central
4.3\win32\scjview.exe;VERSION=9.0.2. 3044;API=ODBC;TIMEZO
NEADJUSTMENT=-180
I. 03/24 13:47:39. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 13:47
I. 03/24 13:47:39. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 13:47
I. 03/24 13:48:14. Unable to synchronize due to external event - engine
shutting down

3º Shutdown

I. 03/24 16:12:43. Disconnected TCPIP client's AppInfo:
HOST=PROG1;OS=Window
s XP Build 2600 Service Pack
2;PID=0x8f4;THREAD=0
xd24;EXE=C:\Arquivos
de programas\Sybase\SQL

Anywhere
9\win32\dbisql.exe;VERSION=9.0.2. 3044;API=ODBC;TIMEZO
NEADJUSTMENT=-180
I. 03/24 16:15:47. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 16:15
I. 03/24 16:15:47. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 16:15
I. 03/24 16:21:08. Disconnecting Client - No activity for 4 minutes
I. 03/24 16:21:08. Disconnected TCPIP client's AppInfo:
HOST=PROG1;OS=Window
s XP Build 2600 Service Pack
2;PID=0x22c;THREAD=0
x6f0;EXE=C:\Arquivos
de programas\Sybase\SQL

Anywhere
9\win32\dbisql.exe;VERSION=9.0.2. 3044;API=ODBC;TIMEZO
NEADJUSTMENT=-180
I. 03/24 16:30:47. Disconnecting Client - No activity for 10 minutes
I. 03/24 16:30:47. Disconnected TCPIP client's AppInfo:
HOST=JONE0;OS=Window
s XP Build 2600
;PID=0x7f8;THREAD=0x
a74;EXE=C:\Program Files\Sybase\Shared\
Sybase
Central
4.3\win32\scjview.exe;VERSION=9.0.2. 2542;API=ODBC;TIMEZO
NEADJUSTMENT=-180
I. 03/24 16:46:46. Starting checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 16:46
I. 03/24 16:46:46. Finished checkpoint of "credinet9" (credinet.db) at
Thu Mar 24 2005 16:46
I. 03/24 17:09:38. Unable to synchronize due to external event - engine
shutting down

José Henrique

Em, 25/03/2005 01:31, Mark Culp escreveu[color=darkr
ed]
> Ok, I missed the fact that the "last line" was the subject of your posting.
>
> What this message means is that the SYSV semaphore that the engine uses
> internally (and externally as part of communications) was deleted, and therefore
> it could not function properly, and therefore it decided to shutdown.
>
> This can happen for a number of reasons, including someone using ipcrm to
> delete the semaphore. But we've seen this a number of times now... and
> it could be caused by the engine crashing somewhere, at which point the sig
> handle catches it and attempts to cleanup the resources (including the
> semaphore)
> before it calls abort() - the issue that we have seen is that one of the threads
> in the engine detects that the semaphore is gone and spits out this message
> (before the other thread has got to the point of calling abort()).
>
> What was the line(s) prior to this in the console output? This information
> may provide some insight on the true reason for the shutdown.
>
> Can you repro the problem?
> --
> Mark Culp
> ASA Research and Development
> -------------------------------------------------------------------------
> ** Whitepapers, TechDocs, bug fixes are all available through the **
> ** iAnywhere Developer Community at http://www.ianywhere.com/developer **
> -------------------------------------------------------------------------
>
> José Henrique wrote:
>

Sponsored Links