To explain my situation, I've got a dual opteron 246 system with 1gig of
ram and 2 80gig disks in raid1 (software raid), I'm running CentOS 4.3
x86_64 with kernel 2.6.9-34.ELsmp I'm running ser 0.9.6-6 (the -6 may
just be an artifact from the fedora core rpm.. I dunno) (compiled from
ser-0.9.6_src.tar.gz)
Since no one seems to makes rpms for redhat or centOS (the same thing
obviously) I went and made my own. I grabbed a fedora core 6 src rpm,
and modified the specfile to my own liking (basically I took out the
stuff related to postgres), the compile went fine, as far as I can tell,
no errors were big enough to stop the compilation at least, and the rpms
installed just fine. All the modules are in the right place, and my
ser.cfg seems to be correct (I don't get any more errors during
startup), however, I do get a segfault :(
here's the attached output from /log/messages
Jun 23 12:20:18 sipserver ser: Listening on
Jun 23 12:20:18 sipserver ser: udp: 192.168.1.93
[192.168.1.93]:5060
Jun 23 12:20:18 sipserver ser: tcp: 192.168.1.93
[192.168.1.93]:5060
Jun 23 12:20:18 sipserver ser: Aliases:
Jun 23 12:20:18 sipserver ser: tcp: pc-00093:5060
Jun 23 12:20:18 sipserver ser: udp: pc-00093:5060
Jun 23 12:20:18 sipserver ser:
Jun 23 12:20:18 sipserver kernel: ser[3682]: segfault at
0000000000000000 rip 0000002a9589ef92 rsp 0000007fbffff850 error 4
Jun 23 12:20:18 sipserver ser: ser startup succeeded
Obviously ser isn't running, does anyone have any idea where I can start
looking to find out what dies/died/went wrong with the compile?
Thanks,
Nick