AWS Thinkbox Discussion Forums

Deadline8, pulse crash

Deadline pulse crashed for us with the following message:

Clean Up Thread - Collecting statistics
Power Management - Thermal Shutdown: There are no temperature zones to check
Power Management - Idle Shutdown: There are no idle shutdown groups to check
Power Management - Machine Startup: There are no slaves that need to be woken up at this time
Power Management - Machine Restart: There are no machine groups to check
Repository Repair Thread - Performing repository repair
Stacktrace:


Native stacktrace:

        ./mono() [0x493565]
        ./mono() [0x4ed0da]
        ./mono() [0x41425f]
        /lib64/libpthread.so.0() [0x36ebc0f710]
        ./mono() [0x61ea6f]
        ./mono() [0x5e74f6]
        ./mono() [0x5f2794]
        ./mono() [0x5e2a89]
        ./mono() [0x5c7bc7]
        ./mono() [0x5e498b]
        ./mono() [0x5e607f]
        ./mono() [0x5d9707]
        ./mono() [0x5c921e]
        [0x418130ae]

Debug info from gdb:


=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted

Our secondary pulse did not pick up, we had to manually restart the primary.

We did fix an issue with Pulse failover in 9.0 SP4:

I’m not sure exactly when the failover broke, but it is properly monitored again.

As far as the crash, does your Linux setup store core dumps anywhere? Something like ABRT or Apport might have stashed it somewhere.

No further crash info is available sadly…

Privacy | Site terms | Cookie preferences