Are you sure that all processes of the old openser process are killed? This looks indeed very strange.
klaus
Benko schrieb:
Hello!
I wanted to upgrade a server from 1.1.0 to 1.2.2 today but despite extensive testing beforehand i have some trouble: After starting with the new openser-binary, it didn't allow any registrations and answered with "500 server error occured". Logging said:
Sep 18 17:23:12 [/sbin/openser] ERROR: sip_msg_cloner: cannot allocate \ memory_ Sep 18 17:23:12 [/sbin/openser] ERROR: new_t: out of mem:_ Sep 18 17:23:12 [/sbin/openser] ERROR: t_newtran: new_t failed_Sep 18
and
17:23:12 [/sbin/openser] ERROR: sip_msg_cloner: cannot allocate memory_ Sep 18 17:23:12 [/sbin/openser] ERROR: store_reply: can't alloc' clone \ memory_
after restarting it with "-m 128"(according to the faq) these errors are gone, but it still doesn't accept registrations and prints: Sep 18 17:24:16 [/sbin/openser] ERROR:tm:print_uac_request: no shmem_ Sep 18 17:24:16 [/sbin/openser] ERROR:tm:t_forward_nonack: failure to \ add branches_ Sep 18 17:24:16 [/sbin/openser] ERROR:tm:w_t_relay: t_forward_nonack \ failed_
[update] - after several restarts, the first error-messages appeared again.
When i run the new version on port 5061(old production server 1.1.0 is running parallel on port 5060) i can register with the new server(on port 5061) without problems.
I have the vague impression that the new instance can't free memory, but why does it work when i run it on a different port? Any clues?
Regards Christian
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users