Looking deeper into a link from one of the links I posted below :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151262 shows it to be a registered bug.
An excerpt suggests the following :
ntpd randomly segfaults, compiled with the default RPM_OPT_FLAGS... turning off exec-shield-randomize cures the segfaults
can do this by doing the following as root :
echo 0 > /proc/sys/kernel/exec-shield-randomize
or to make it permanent : add /"kernel.exec-shield-randomize = /0" to //etc/sysctl.conf
/Might be worth a try - although you should note that by turning off the randomisation of Linux memory, it is making the system less secure - although with SELinux turned off already it's probably not that much of an issue for that box.
HTH, Paul
Howard Lowndes wrote:
I also have SELinux disabled on this particular box :(
Paul Robinson wrote:
I suffered similar problems with a vanilla install of FC3 with MySQL's socket. Turned out to be due to SELINUX which is enabled by default on FC3 however I don't believe that ntpd is affected by SELINUX.
Seems like you aren't the only one with this problem though:
http://www.redhat.com/archives/fedora-test-list/2005-April/msg00962.html
and
http://64.233.179.104/search?q=cache:alJvtG_zJbAJ:fcp.homelinux.org/modules/newbb/viewtopic.php%3Ftopic_id%3D14951%26forum%3D12%26post_id%3D60142+EACCES+(Permission+denied)+SELINUX&hl=en&start=3
if they help point you in the right direction.
HTH Paul
Howard Lowndes wrote:
I've tried running it with strace and it seems to be reasonably consistent about crapping out about the nscd socket, but not every time:
socket(PF_FILE, SOCK_STREAM, 0) = 13
fcntl64(13, F_GETFL) = 0x2 (flags O_RDWR)
fcntl64(13, F_SETFL, O_RDWR|O_NONBLOCK) = 0
connect(13, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 EACCES (Permission denied)
close(13) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
The socket is mode 666
Howard Lowndes wrote:
FC3 with everything up to date, but now the ntpd daemon refuses to start.
Hand cranking it in the foreground gives a seg fault, but nothing in the logs.
The weird thing is that it was working fine until I had to do a power cycle a couple of days ago to free up a locked serial port.
Any ideas?
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
