Yes, i had the same problem. Ser didn't started at boot up, but using service ser start after logon, ser started. I think, it coud be caused by short delay between start of mysql and ser. Of course if you use mysql.

First I have moved ser to higher init start number. Ser started after apache and so on. But the same problem occurs once again. May be, that use of sleep for two seconds in ser start, could help. It works in my case.

start() { echo -e "waiting for 2 sec \n" sleep 2 echo -n $"Starting $prog: " daemon $ser $OPTIONS ...

/var/log/messages without sleep

Nov 13 10:17:15 zzz crond: crond startup succeeded Nov 13 10:17:16 zzz ser: Listening on Nov 13 10:17:16 zzz ser: ipv4:5060 Nov 13 10:17:16 zzz ser: ipv6:5060 Nov 13 10:17:16 zzz ser: Aliases: name:5060 name:5060 Nov 13 10:17:16 zzz ser: ser startup succeeded Nov 13 10:17:16 zzz anacron: anacron startup succeeded

with sleep

Nov 13 10:29:04 zzz crond: crond startup succeeded Nov 13 10:29:07 zzz ser: Listening on Nov 13 10:29:07 zzz ser: IPv4:5060 Nov 13 10:29:07 zzz ser: IPv6:5060 Nov 13 10:29:07 zzz ser: Aliases: name:5060 name:5060 Nov 13 10:29:07 zzz ser: Listening on Nov 13 10:29:07 zzz ser: IPv4:5060 Nov 13 10:29:07 zzz ser: IPv6:5060 Nov 13 10:29:07 zzz ser: Aliases: name:5060 name:5060 Nov 13 10:29:07 zzz ser: Listening on Nov 13 10:29:07 zzz ser: IPv4:5060 Nov 13 10:29:07 zzz ser: IPv6:5060 Nov 13 10:29:07 zzz ser: Aliases: name:5060 name:5060 Nov 13 10:29:07 zzz ser: ser startup succeeded Nov 13 10:29:07 zzz anacron: anacron startup succeeded Nov 13 10:29:07 zzz atd: atd startup succeeded Nov 13 10:29:07 zzz /usr/local/sbin/ser[768]: mod_init(): Database connection opened successfu Nov 13 10:29:07 zzz /usr/local/sbin/ser[768]: INFO: udp_init: SO_RCVBUF is initially 65535 Nov 13 10:29:07 zzz /usr/local/sbin/ser[768]: INFO: udp_init: SO_RCVBUF is finally 131070 Nov 13 10:29:07 zzz /usr/local/sbin/ser[768]: INFO: udp_init: SO_RCVBUF is initially 65535 Nov 13 10:29:07 zzz /usr/local/sbin/ser[768]: INFO: udp_init: SO_RCVBUF is finally 131070 Nov 13 10:29:07 zzz /usr/local/sbin/ser[807]: INFO: fifo process starting: 807 Nov 13 10:29:07 zzz /usr/local/sbin/ser[807]: SER: open_uac_fifo: fifo server up at /tmp/ser_f

Jan

On Thu, 2003-11-13 at 02:10, Andrei Pelinescu-Onciul wrote:

On Nov 12, 2003 at 16:28, Rose, John jrose@premconf.com wrote:

...

Has anyone else had problems with SER not starting on a reboot of Redhat Linux 9.0?

There were some user reporting this kind of problems, but we never encountered them (OTOH we don't use RH too much). It might be an init.d script problem. If you have problems (and it's not a broken config) just try starting & stoping ser several times from the console (/etc/init.d/ser start ; /etc/init.d/ser stop) and see if this ever fails (after starting ser check if it is running: ps ax|grep ser). If it fails send us the relevant log lines (grep for ser) and any error messages you might have got.

Andrei

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers