Feedback
Did this article resolve your question/issue?

   

Article

Can KILL -SIGUSR1 cause a process to crash?

Information

 
TitleCan KILL -SIGUSR1 cause a process to crash?
URL NameCan-a-kill-SIGUSR1-cause-a-process-to-crash
Article Number000118299
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: UNIX / Linux
Question/Problem Description
Can kill -SIGUSR1 cause an OpenEdge process to crash with SE 49?
Can running proGetStack.sh cause a process to crash on Unix or Linux ?
Can SIGUSR1 signals sent to a client process cause a DBDOWN?
Steps to Reproduce
Clarifying Information
kill -SIGUSR1 is used on Unix/Linux systems to trigger an ABL client process to generate a protrace file
Error MessageSYSTEM ERROR: Memory violation. (49)
Defect Number
Enhancement Number
Cause
Resolution
When a process that receives a -SIGUSR1 request to dump a stack and also receives a simultaneous interrupt signal, the process can end up crashing with SYSTEM ERROR 49 which may also bring the database down as a result, or the process will hang indefinitely and no longer be responsive to further interrupt signals.

The cause has been identified in async unsafe calls in signal handling as an ongoing investigation which have been addressed in separate defects:

Upgrade to OpenEdge 11.6.4, 11.7 or later where all known issues associated with async unsafe signal handling have been addressed by implementing alternative functions, which are safe with asynchronous signal handling: Should any further incidents occur in later versions, please open a support case with technical support along with a reproducible (if possible) to be pursued as a defect. 
Workaround
Notes
Last Modified Date11/20/2020 7:18 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.