jknightcs1
24-10-2007, 21:52
Hi everyone,
I can't seem to get zabbix_agentd to run on my 64-bit Red Hat boxes. I'm able to compile it from source fine, but it always seg-faults when I try to start the agent. This happens even using the default conf file that comes with the package. Note that the same package compiles and runs fine on my 32-bit RH boxes.
One 8-CPU box with 16 gig of RAM has this:
uname -a
Linux <name removed> 2.6.9-42.0.10.0.1.ELlargesmp #1 SMP Tue Feb 27 12:34:42 PST 2007 x86_64 x86_64 x86_64 GNU/Linux
From my strace files:
fork() = 23848
fork() = 23849
fork() = 23850
fork() = 23851
fork() = 23852
rt_sigaction(SIGCHLD, {0x40cde0, [], SA_RESTORER, 0x420840}, NULL, 8) = 0
wait4(23848, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV}], 0, NULL) = 23848
--- SIGCHLD (Child exited) @ 0 (0) ---
From child 23848:
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a95557000
read(5, "cpu 298693338 2553 76045905 269"..., 1024) = 1024
read(5, " 0 158680204 0 0 0 0 0 0 0 0 0 0"..., 1024) = 574
read(5, "", 1024) = 0
close(5) = 0
munmap(0x2a95557000, 4096) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
I'm not a linux programmer, but it seems to have something to do with memory mapping. I thought this might be a bug, but I'm not seeing much else in the forums about it.
Anyone have any ideas?
I can't seem to get zabbix_agentd to run on my 64-bit Red Hat boxes. I'm able to compile it from source fine, but it always seg-faults when I try to start the agent. This happens even using the default conf file that comes with the package. Note that the same package compiles and runs fine on my 32-bit RH boxes.
One 8-CPU box with 16 gig of RAM has this:
uname -a
Linux <name removed> 2.6.9-42.0.10.0.1.ELlargesmp #1 SMP Tue Feb 27 12:34:42 PST 2007 x86_64 x86_64 x86_64 GNU/Linux
From my strace files:
fork() = 23848
fork() = 23849
fork() = 23850
fork() = 23851
fork() = 23852
rt_sigaction(SIGCHLD, {0x40cde0, [], SA_RESTORER, 0x420840}, NULL, 8) = 0
wait4(23848, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV}], 0, NULL) = 23848
--- SIGCHLD (Child exited) @ 0 (0) ---
From child 23848:
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2a95557000
read(5, "cpu 298693338 2553 76045905 269"..., 1024) = 1024
read(5, " 0 158680204 0 0 0 0 0 0 0 0 0 0"..., 1024) = 574
read(5, "", 1024) = 0
close(5) = 0
munmap(0x2a95557000, 4096) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
I'm not a linux programmer, but it seems to have something to do with memory mapping. I thought this might be a bug, but I'm not seeing much else in the forums about it.
Anyone have any ideas?