[Progress Communities] [Progress OpenEdge ABL] Forum Post: SIGUSR1 signal hung a Progress session

Status
Not open for further replies.
G

George Potemkin

Guest
Progress V11.7.5 on Linux DBA sent the SIGUSR1 signal to a Progress session. Session created a protrace file but it was filled only partially: ABL Stack Trace section was empty. Session still held a handle to the protrace file. SIGUSER1 was added to a mask of signals being blocked (SigBlk). SIGCONT was moved from the caught signal mask (SigCgt) to the ignored signal mask (SigIgn). This also means that the session did not complete the creation of the protrace file. strace shown: 14:34:16.785169 futex(0x7fe847541760, FUTEX_WAIT_PRIVATE, 2, NULL Session has ignored SIGTERM and SIGINT and finally it was killed by SIGKILL. How to debug such cases if they will happen again? Regards, George

Continue reading...
 
Status
Not open for further replies.
Top