15 Dec
2010
15 Dec
'10
4:51 p.m.
Hi!
When updating binaries of Kamailio (e.g. replacing a module) Kamailio
immediately shuts down, e.g.:
: <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 14
ALERT: <core> [main.c:741]: child process 15490 exited by a signal 11
When I update Asterisk I can replace the binaries and Asterisk keeps
still running. This is very convenient as the service disruption is much
shorter.
I wonder how Kamailio detects that the binaries were replaced. I suspect
it has something to do how the modules are loaded (seems like the fd is
still open). Is this a feature? Is it possible to change it (to be
similar to Asterisk)?
regards
Klaus
16 Dec
16 Dec
2:36 p.m.
On Wednesday 15 December 2010, Klaus Darilion wrote:
When updating binaries of Kamailio (e.g. replacing a
module) Kamailio
immediately shuts down, e.g.:
: <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 14
ALERT: <core> [main.c:741]: child process 15490 exited by a signal 11
When I update Asterisk I can replace the binaries and Asterisk keeps
still running. This is very convenient as the service disruption is much
shorter.
I wonder how Kamailio detects that the binaries were replaced. I suspect
it has something to do how the modules are loaded (seems like the fd is
still open). Is this a feature? Is it possible to change it (to be
similar to Asterisk)?
Hi Klaus,
do you observe this issue with different versions (e.g. also with old 1.5
kamailio) as well? I don't remember that i saw something like this here.
Cheers,
Henning
5:40 p.m.
Am 16.12.2010 13:36, schrieb Henning Westerholt:
On Wednesday 15 December 2010, Klaus Darilion wrote:
I have not tested with 1.5. But I think it happened also with old versions.
regards
klaus
When updating binaries of Kamailio (e.g.
replacing a module) Kamailio
immediately shuts down, e.g.:
:<core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 14
ALERT:<core> [main.c:741]: child process 15490 exited by a signal 11
When I update Asterisk I can replace the binaries and Asterisk keeps
still running. This is very convenient as the service disruption is much
shorter.
I wonder how Kamailio detects that the binaries were replaced. I suspect
it has something to do how the modules are loaded (seems like the fd is
still open). Is this a feature? Is it possible to change it (to be
similar to Asterisk)?
Hi Klaus,
do you observe this issue with different versions (e.g. also with old 1.5
kamailio) as well? I don't remember that i saw something like this here.
7:57 p.m.
On Thursday 16 December 2010, Klaus Darilion wrote:
Hi Klaus,
this is then really strange. Because we update regularly our server binaries,
without observing this, i think. Just a stupid idea, maybe there is some
packaging magic (e.g. debian) in place that restarts the server after the
update?
Viele Grüße,
Henning
do you observe
this issue with different versions (e.g. also with old 1.5
kamailio) as well? I don't remember that i saw something like this here.
I have not tested with 1.5. But I think it happened also with old versions.
21 Dec
21 Dec
11:23 a.m.
Am 16.12.2010 18:57, schrieb Henning Westerholt:
On Thursday 16 December 2010, Klaus Darilion wrote:
Hi Klaus,
this is then really strange. Because we update regularly our server binaries,
without observing this, i think. Just a stupid idea, maybe there is some
packaging magic (e.g. debian) in place that restarts the server after the
update?
Guess I should verify that maybe I'm wrong
regards
klaus
do you
observe this issue with different versions (e.g. also with old 1.5
kamailio) as well? I don't remember that i saw something like this here.
I have not tested with 1.5. But I think it happened also with old versions.
5088
days inactive
5094
days old
4 comments
2 participants
participants (2)
-
Henning Westerholt -
Klaus Darilion