22 Oct
2015
22 Oct
'15
9:21 a.m.
Hi,
I have been trying to setup Kamailio v4.3.3 rev. e275bc on RHEL 7.1 64bit.
It has been very difficult to resolve all dependencies initially due to
RHEL's extremely limited repositories and libraries support, but
nevertheless I am finally able to successfully compile kamailio with all
essential modules on it.
However, now kamailio fails to start up and gives this strange error,
--
36(3335) CRITICAL: <core> [io_wait.c:526]: init_io_wait(): could not alloc
epoll array
36(3335) CRITICAL: <core> [tcp_main.c:4523]: tcp_main_loop(): exiting...
0(3250) ALERT: <core> [main.c:725]: handle_sigs(): child process 3335
exited normally, status=255
0(3250) INFO: <core> [main.c:743]: handle_sigs(): terminating due to
SIGCHLD
--
I have never seem this error before nor i can find any info related to it
anywhere on internet. So, i doubt it is due to any missing dependency.
Any idea what may be the cause of this?
Thank you.
22 Oct
22 Oct
11:56 a.m.
Hello,
first -- do not cross-post to many mailing lists, it makes hard to track
and each mailing lists has its own purpose. Crossposting should be done
only for announcements concerning both development as well as usage.
This is about use of a kamailio stable version, so it is for sr-users.
Do you have selinux enabled? Are there any particular limits set on the
system?
Also, you should run with debug=3 in kamailio.cfg and see if you get
more hints from the debug messages printed before the CRITICAL logs. You
can send them here if you want us to take a look.
Cheers,
Daniel
On 22/10/15 08:21, M S wrote:
Hi,
I have been trying to setup Kamailio v4.3.3 rev. e275bc on RHEL 7.1
64bit.
It has been very difficult to resolve all dependencies initially due
to RHEL's extremely limited repositories and libraries support, but
nevertheless I am finally able to successfully compile kamailio with
all essential modules on it.
However, now kamailio fails to start up and gives this strange error,
--
36(3335) CRITICAL: <core> [io_wait.c:526]: init_io_wait(): could not
alloc epoll array
36(3335) CRITICAL: <core> [tcp_main.c:4523]: tcp_main_loop():
exiting... 0(3250) ALERT: <core> [main.c:725]: handle_sigs(): child
process 3335 exited normally, status=255
0(3250) INFO: <core> [main.c:743]: handle_sigs(): terminating due to
SIGCHLD
--
I have never seem this error before nor i can find any info related to
it anywhere on internet. So, i doubt it is due to any missing dependency.
Any idea what may be the cause of this?
Thank you.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
5:28 p.m.
New subject: Kamailio start up fails with strange IO Error on RHEL 7.1
I am sorry for inconvenience, I was a bit confused whether it is a related
to dev or user mailing list since kamailio was giving segmentation fault
(which i guess was expected in this case), so i post it on both. Anyways, i
will try to be careful next time.
Initially selinux was enabled, but then i disabled to see if that helps but
didn't find any change in behavior.
Here is BT Full of sigfault,the full kamailio debug level 3 logs are also
attached herewith.
--
#0 0x00007fda5dd5c811 in __strlen_sse2 () from /lib64/libc.so.6
No symbol table info available.
#1 0x00007fda5dd4c5bf in fputs_unlocked () from /lib64/libc.so.6
No symbol table info available.
#2 0x00007fda5ddc6208 in __vsyslog_chk () from /lib64/libc.so.6
No symbol table info available.
#3 0x00007fda5ddc66df in syslog () from /lib64/libc.so.6
No symbol table info available.
#4 0x000000000050c4f3 in handle_sigs () at main.c:747
__llevel = 3
chld = 0
chld_status = 65280
memlog = 0
__FUNCTION__ = "handle_sigs"
#5 0x00000000005141b4 in main_loop () at main.c:1701
i = 2
pid = 2995
si = 0x0
si_desc = "udp receiver child=1
sock=192.168.233.129:5060\000\000\220Q\024W\377\177",
'\000' <repeats 18 times>,
"\337f\334]\332\177\000\000PN\024W\001\000\000\000h\035\216]\332\177\000\000\360N\024W\377\177\000\000\060N\024W\377\177\000\000\"\036\006k\000\000\000\000(\365\207N\332\177\000"
nrprocs = 2
__FUNCTION__ = "main_loop"
#6 0x0000000000519258 in main (argc=2, argv=0x7fff57145198) at main.c:2547
cfg_stream = 0xf4d010
c = -1
r = 0
tmp = 0x7fda5e6d8560 "\300\204m^\332\177"
tmp_len = 0
port = 0
proto = 32730
options = 0x725120
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:"
ret = -1
seed = 2893849513
rfd = 4
debug_save = 0
debug_flag = 0
dont_fork_cnt = 0
n_lst = 0x7fff57145060
p = 0x7fda5dd75646 <intel_check_word+166>
"H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete
sequence \305>
st = {st_dev = 18, st_ino = 22284, st_nlink = 2, st_mode = 16832,
st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize =
4096, st_blocks = 0, st_atim = {tv_sec = 1445526750, tv_nsec = 59990608},
st_mtim = {
tv_sec = 1445526751, tv_nsec = 158990545}, st_ctim = {tv_sec =
1445526751, tv_nsec = 158990545}, __unused = {0, 0, 0}}
__FUNCTION__ = "main"
--
Thank you.
On Thu, Oct 22, 2015 at 9:56 AM, Daniel-Constantin Mierla <miconda(a)gmail.com
wrote:
Hello,
first -- do not cross-post to many mailing lists, it makes hard to track
and each mailing lists has its own purpose. Crossposting should be done
only for announcements concerning both development as well as usage. This
is about use of a kamailio stable version, so it is for sr-users.
Do you have selinux enabled? Are there any particular limits set on the
system?
Also, you should run with debug=3 in kamailio.cfg and see if you get more
hints from the debug messages printed before the CRITICAL logs. You can
send them here if you want us to take a look.
Cheers,
Daniel
On 22/10/15 08:21, M S wrote:
Hi,
I have been trying to setup Kamailio v4.3.3 rev. e275bc on RHEL 7.1 64bit.
It has been very difficult to resolve all dependencies initially due to
RHEL's extremely limited repositories and libraries support, but
nevertheless I am finally able to successfully compile kamailio with all
essential modules on it.
However, now kamailio fails to start up and gives this strange error,
--
36(3335) CRITICAL: <core> [io_wait.c:526]: init_io_wait(): could not alloc
epoll array
36(3335) CRITICAL: <core> [tcp_main.c:4523]: tcp_main_loop(): exiting...
0(3250) ALERT: <core> [main.c:725]: handle_sigs(): child process 3335
exited normally, status=255
0(3250) INFO: <core> [main.c:743]: handle_sigs(): terminating due to
SIGCHLD
--
I have never seem this error before nor i can find any info related to it
anywhere on internet. So, i doubt it is due to any missing dependency.
Any idea what may be the cause of this?
Thank you.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
23 Oct
23 Oct
12:22 p.m.
The brancktrace leads to a log message during shutdown, so that is not
an issue at all.
Looking at log messages, it appears you don't have sufficient private
memory. What is your -M parameter? If you haven't provided it, then try
with -M 12
Cheers,
Daniel
On 22/10/15 16:28, M S wrote:
I am sorry for inconvenience, I was a bit confused
whether it is a
related to dev or user mailing list since kamailio was giving
segmentation fault (which i guess was expected in this case), so i
post it on both. Anyways, i will try to be careful next time.
Initially selinux was enabled, but then i disabled to see if that
helps but didn't find any change in behavior.
Here is BT Full of sigfault,the full kamailio debug level 3 logs are
also attached herewith.
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
6:34 p.m.
New subject: Kamailio start up fails with strange IO Error on RHEL 7.1
Since I don't have systemd compatible start script for RHEL, so i was
starting kamailio through commandline, e.g. /usr/local/sbin/kamailio start
Anyways, manually specifying the private memory parameter did indeed solved
the problem. Thank you so much for help.
Let me now write up a systemd service script for RHEL.
Thank you.
On Fri, Oct 23, 2015 at 10:22 AM, Daniel-Constantin Mierla <
miconda(a)gmail.com> wrote:
The brancktrace leads to a log message during
shutdown, so that is not
an issue at all.
Looking at log messages, it appears you don't have sufficient private
memory. What is your -M parameter? If you haven't provided it, then try
with -M 12
Cheers,
Daniel
On 22/10/15 16:28, M S wrote:
I am sorry for inconvenience, I was a bit
confused whether it is a
related to dev or user mailing list since kamailio was giving
segmentation fault (which i guess was expected in this case), so i
post it on both. Anyways, i will try to be careful next time.
Initially selinux was enabled, but then i disabled to see if that
helps but didn't find any change in behavior.
Here is BT Full of sigfault,the full kamailio debug level 3 logs are
also attached herewith.
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
26 Oct
26 Oct
10:58 a.m.
On 23/10/15 17:34, M S wrote:
Since I don't have systemd compatible start script
for RHEL, so i was
starting kamailio through commandline, e.g. /usr/local/sbin/kamailio start
A side note: be aware that /usr/local/sbin/kamailio does not take the
'start' parameter. The 'start' parameter is specific to init.d scripts,
so that would be /etc/init.d/kamailio.
Then, afaik, you can still use /etc/init.d/kamailio to start/stop
kamailio, on redhat you can install it with:
make install-initd-centos
Cheers,
Daniel
Anyways, manually specifying the private memory parameter did indeed
solved the problem. Thank you so much for help.
Let me now write up a systemd service script for RHEL.
Thank you.
On Fri, Oct 23, 2015 at 10:22 AM, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
The brancktrace leads to a log message during shutdown, so that is not
an issue at all.
Looking at log messages, it appears you don't have sufficient private
memory. What is your -M parameter? If you haven't provided it,
then try
with -M 12
Cheers,
Daniel
On 22/10/15 16:28, M S wrote:
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
I am sorry for inconvenience, I was a bit
confused whether it is a
related to dev or user mailing list since kamailio was giving
segmentation fault (which i guess was expected in this case), so i
post it on both. Anyways, i will try to be careful next time.
Initially selinux was enabled, but then i disabled to see if that
helps but didn't find any change in behavior.
Here is BT Full of sigfault,the full kamailio debug level 3 logs are
also attached herewith.
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -
http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
5:26 p.m.
New subject: Kamailio start up fails with strange IO Error on RHEL 7.1
Great.
Thank you so much for your help.
On Mon, Oct 26, 2015 at 8:58 AM, Daniel-Constantin Mierla <miconda(a)gmail.com
wrote:
>
>
> On 23/10/15 17:34, M S wrote:
>
> Since I don't have systemd compatible start script for RHEL, so i was
> starting kamailio through commandline, e.g. /usr/local/sbin/kamailio start
>
>
> A side note: be aware that /usr/local/sbin/kamailio does not take the
> 'start' parameter. The 'start' parameter is specific to init.d
scripts, so
> that would be /etc/init.d/kamailio.
>
> Then, afaik, you can still use /etc/init.d/kamailio to start/stop
> kamailio, on redhat you can install it with:
>
> make install-initd-centos
>
> Cheers,
> Daniel
>
>
>
> Anyways, manually specifying the private memory parameter did indeed
> solved the problem. Thank you so much for help.
>
> Let me now write up a systemd service script for RHEL.
>
> Thank you.
>
>
>
> On Fri, Oct 23, 2015 at 10:22 AM, Daniel-Constantin Mierla <
> <miconda@gmail.com>miconda@gmail.com
wrote:
>
>> The brancktrace leads to a log message during shutdown, so that is not
>> an issue at all.
>>
>> Looking at log messages, it appears you don't have sufficient private
>> memory. What is your -M parameter? If you haven't provided it, then try
>> with -M 12
>>
>> Cheers,
>> Daniel
>>
>> On 22/10/15 16:28, M S wrote:
>> > I am sorry for inconvenience, I was a bit confused whether it is a
>> > related to dev or user mailing list since kamailio was giving
>> > segmentation fault (which i guess was expected in this case), so i
>> > post it on both. Anyways, i will try to be careful next time.
>> >
>> > Initially selinux was enabled, but then i disabled to see if that
>> > helps but didn't find any change in behavior.
>> >
>> > Here is BT Full of sigfault,the full kamailio debug level 3 logs are
>> > also attached herewith.
>>
>> --
>> Daniel-Constantin Mierla
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>> Book: SIP Routing With Kamailio - <http://www.asipto.com>
>> http://www.asipto.com
>>
>>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
>
>
3315
days inactive
3319
days old
6 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
M S