segmentation fault error

E

ephdia

Verified User
Joined
Feb 5, 2008
Messages
7
Hello,
I am using RHEL4.Unfortunately 2 days before all the cronjob was stoppedand i am getting segmentation fault error,while find status of the service.
ERROR: service crond status
/sbin/service: line 68: 28349 Segmentation fault env -i LANG=$LANG PATH=$PATH TERM=$TERM "${SERVICEDIR}/${SERVICE}" ${OPTIONS}

Could anyone explain about this error?
I searched on this error and found it may be hardware error due to bad RAM memory.so now i have to run some diagnostic test to figure out the exact cause of problem.I am heard of memtest,but don't know how to run that in linux....:( .Please help me...to find out some easy linux package or tool to test RAM.
I also tried a script in this link http://people.redhat.com/dledford/memtest.html.It took long time for me and also it make my server load to exceed threshold limit.So i gave off this script.Is there anyone get positive result using this script? Please help me to sort out the problem and to overcome that.
 
Is it generating a .core file? If so you will want to use a program like strace to figure out what is happening to cause the core dump.

Have you restarted the crond service and see if the same error happens?
 
chatwizrd, i am not known about the .core file.please explain, me where i have to see is the .core file generated or not?
No. i din't restart crond.As i couldn't find status of none of the service.
for service --status-all also,
i am getting repeatative lines of error states,
/sbin/service: line 34: 28610 Segmentation fault env -i LANG=$LANG PATH=$PATH TERM=$TERM "${SERVICEDIR}/${SERVICE}" status

so i am afraid to do restart service.Please advice me..
 
I tried restarting crond service,no response that also showing the same error.
service crond restart
/sbin/service: line 68: 29015 Segmentation fault env -i LANG=$LANG PATH=$PATH TERM=$TERM "${SERVICEDIR}/${SERVICE}" ${OPTIONS}


Please help me to solve this problem...
 
You boot up with memtest, you don't actually run it in linux (or any OS for that matter).
 
Try the following. I assume since you have EL4 you have up2date.

Code: 
up2date --get initscripts --tmpdir=/root/
rpm -Uvh --force /root/init*rpm
 
Last edited:
Thanks for your replies,
I got as follows for,
rpm -qa initscripts
initscripts-8.45.14.EL-1
 
Thanks for your replies,
I got as follows for,
rpm -qa initscripts
initscripts-8.45.14.EL-1

I tried http://people.redhat.com/dledford/memtest.html this script it took long time and system load exceeds threshold level so i stopped this script.

for, up2date --get initscripts --tmpdir=/root/
I am asked to select a number to edit.,
0. isatty Yes
1. rhnuuid 190d611c-7802-11db-989a-27baa520882c
2. debug No
3. useRhn No
4. showAvailablePacka No
5. storageDir /root/
6. useNoSSLForPackage No
7. pkgSkipList ['kernel*']
8. retrieveOnly No
9. noSSLServerURL http://xmlrpc.rhn.redhat.com/XMLRPC
10. networkRetries 5
11. pkgsToInstallNotUp ['kernel', 'kernel-modules', 'kernel-devel']
12. enableProxy No
13. noBootLoader No
14. proxyPassword
15. updateUp2date Yes
16. keepAfterInstall No
17. useGPG Yes
18. headerCacheSize 40
19. forceInstall No
20. systemIdPath /etc/sysconfig/rhn/systemid
21. retrieveSource No
22. enableRollbacks No
23. gpgKeyRing /etc/sysconfig/rhn/up2date-keyring.gpg
24. adminAddress ['root@localhost']
25. serverURL https://xmlrpc.rhn.redhat.com/XMLRPC
26. fileSkipList []
27. versionOverride
28. sslCACert /usr/share/rhn/RHNS-CA-CERT
29. noReplaceConfig Yes
30. enableProxyAuth No
31. disallowConfChange ['noReboot', 'sslCACert', 'useNoSSLForPackages', 'noSSLSe
32. headerFetchCount 10
33. proxyUser
34. removeSkipList ['kernel*']
35. httpProxy
36. noReboot No

Please help me how can i proceed more.....

if it is RAM problem, shall i change RAM to make my service run as normal? Did anyone solved this error?
 
Chatwizrd, thanks for your reply.But, won't it be a problem if i update my package? as it is a running server,i am thinking twice about doing any updation of package..doesn't it reflect on any other process?
 
Generally RedHat is fairly safe about updates; it will save files and even refuse to install files, if it can detect a problem. That said, I almost didn't respond to this thread; I really don't want you blaming me if your server stops completely.

I'd recommend finding out what files are included in that particular RPM, and then save backups of those files somewhere safe first.

Jeff
 
You must log in or register to reply here.
Back
Top