On 05/15/2017 03:16 PM, Sung Hsin Lei wrote:
> Hello,
>
> Thanks for the response. Attached in the data in the command prompt when
> I run slon from the command prompt. The last things that slon seems to
> be doing is:
>
> 2017-05-14 00:37:31 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008808 done in 0.000 seconds
> 2017-05-14 00:37:49 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008809 done in 0.000 seconds
> 2017-05-14 00:37:51 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008810 done in 0.000 seconds
> 2017-05-14 00:38:09 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008811 done in 0.000 seconds
> 2017-05-14 00:38:11 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008812 done in 0.000 seconds
> 2017-05-14 00:38:29 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008813 done in 0.000 seconds
> 2017-05-14 00:38:31 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008814 done in 0.000 seconds
> 2017-05-14 00:38:49 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008815 done in 0.000 seconds
> 2017-05-14 00:38:51 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008816 done in 0.000 seconds
> NOTICE:  Slony-I: log switch to sl_log_2 complete - truncate sl_log_1
> CONTEXT:  PL/pgSQL function _slony_securithor2.cleanupevent(interval)
> line 95 at assignment
> 2017-05-14 00:39:09 Eastern Daylight Time INFO   cleanupThread:    0.060
> seconds for cleanupEvent()
> 2017-05-14 00:39:09 Eastern Daylight Time INFO   cleanupThread:    0.010
> seconds for vacuuming
> 2017-05-14 00:39:09 Eastern Daylight Time INFO   remoteWorkerThread_2:
> SYNC 5000008817 done in 0.000 seconds
>
>
> Does Slony has any other types of logs? If yes, how do I access it?
>
>

No that is the type of stuff slon logs. You can turn the debug level up 
to debug and it will log a bit more at the same place.
Can you tell how close the timestamp of the crash/error message is to 
those messages?

Those messages are all normal and don't show any sign of a problem



> Thanks.
>
>
>
>
>
>
> On Mon, May 15, 2017 at 2:35 PM, Steve Singer <ssinger at ca.afilias.info
> <mailto:ssinger at ca.afilias.info>> wrote:
>
>     On 05/14/2017 12:22 AM, Sung Hsin Lei wrote:
>
>         Hello,
>
>         I was wondering if someone had a similar error or know what this
>         error
>         means?
>
>         I compiled my Slony 2.2.5 64-bit with Postgres 9.3. On one of my
>         VM's,
>         replication would run fine for about 2 days and then it would
>         just stop.
>         When it stops, I need to restart the slon service for
>         replication to resume.
>
>         looking at the windows logs, I get the following:
>
>
>         Faulting application name: slon.exe, version: 0.0.0.0, time stamp:
>         0x57be7ff1
>         Faulting module name: ntdll.dll, version: 6.1.7601.23796, time
>         stamp:
>         0x590296ce
>         Exception code: 0xc0000374
>         Fault offset: 0x00000000000bf3e2
>         Faulting process id: 0x1464
>         Faulting application start time: 0x01d2cc57301577a0
>         Faulting application path: C:\Program
>         Files\PostgreSQL\9.3\bin\slon.exe
>         Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
>         Report Id: 9fcc9980-384e-11e7-9cd3-7ab625288ae1
>
>
>     Any idea what slon was doing at this time? Did slon log anything
>     about its activities?
>
>
>         Has anyone experience such problem or know what this means?
>
>
>         Thank you.
>
>
>
>
>         _______________________________________________
>         Slony1-general mailing list
>         Slony1-general at lists.slony.info
>         <mailto:Slony1-general at lists.slony.info>
>         http://lists.slony.info/mailman/listinfo/slony1-general
>         <http://lists.slony.info/mailman/listinfo/slony1-general>
>
>
>