Quote:
Originally Posted by vipin_a
I am facing segfault errors in RHEL 7.2 when crons are run. Application will working fine with no issues as long as no perl/shell scripts are executed by cron job . When the cron job or with “at” command is executed , the applications coredumps. Cron is executed as normal user.
Would appreciate if anyone can help me with a solution. Is it possible that if dynamic libraries are loaded to /usr/lib64 , does OS utils misbehave. And also coredump occurs for the application accessing the shared memory and semaphores.
Dec 4 14:06:31 kernel: m3uaGW[31528]: segfault at 7f091be92f20 ip 00007f091ed971a7 sp 00007f091be92e10 error 6 in libc-2.17.so[7f091ed50000+1b8000]
Dec 6 13:03:24 kernel: vsd[18967]: segfault at 980 ip 0000000000422b1d sp 00007ffc78d1c120 error 4 in vsd[400000+58000]
Dec 6 17:28:13 kernel: cgwd[539]: segfault at 8 ip 00007f749fe176a8 sp 00007ffc6b376560 error 4 in ld-2.17.so[7f749fe0c000+21000] Dec 6 17:29:24 kernel: ipsmsd[1454]: segfault at 8 ip 00007f2ff8e166a8 sp 00007fff99d9a370 error 4 in ld-2.17.so[7f2ff8e0b000+21000]
Dec 6 21:04:47 kernel: m3uaGW[20220]: segfault at 10 ip 000000000047ac8e sp 00007f998266c610 error 4 in m3uaGW[400000+ba000]
Dec 7 17:52:37 kernel: prepaidGw[8479]: segfault at 7ffe1c006be0 ip 00007f5b7a8ec1a7 sp 00007ffe1c006ad0 error 6 in libc-2.17.so[7f5b7a8a5000+1b8000]
|
Based on what you posted, there is NOTHING anyone here is going to be able to tell you. You say "application"...but don't tell us what this application is, how it was installed, and what the connection is to perl/shell scripts. And the very small piece of dump information similarly tells us nothing.
Best thing to do would be to contact Red Hat support, since you're using RHEL 7.2. You are **PAYING FOR IT** right?? Because it is very possible that there are bugs and other fixes that are applied with your RHEL subscription that address issues you're having...and unless you pay, you WILL NOT get those. If you pay for RHEL, they will analyze your coredump, do an SOSreport, and give you suggestions on how to get things fixed. If you're not paying, then you will have to start going through each and every script, and analyze each command its running, and compare those against known bug issues, and (maybe) load an updated version.
Or you could reload your entire system with CentOS instead, and get the latest versions of everything.
