[Spce-user] kamailio-proxy does not start after reboot
Andy Clark
andyclark05251978 at gmail.com
Thu Mar 21 13:05:03 EDT 2019
basically here is the situation
homer -> enable -> yes (ngcp-rtpengine-daemon.service fails on reboot) -
sends no packets to homer 9060
homer -> enable -> no (ngcp-rtpengine-daemon.service works)
I confirmed homer is working by generating fake messages using hepgen
security -> firewall -> enable -> yes
1. kamailio-proxy.service might or might not fail.
if fail and restart the service, extra sockets does NOT work
if "netfilter-persistent.service" fails then proxy has no issues, extra
sockets no issues
if "netfilter-persistent.service" does not fail, extra sockets does NOT
work but 5060/5061 works
I really need some help here
On Thu, Mar 21, 2019 at 4:16 AM Andy Clark <andyclark05251978 at gmail.com>
wrote:
> root at spce:~# sudo systemd-analyze critical-chain kamailio-proxy.service
> The time after the unit is active or started is printed after the "@"
> character.
> The time the unit takes to start is printed after the "+" character.
>
> kamailio-proxy.service +528ms
> └─network-online.target @2.653s
> └─network.target @2.639s
> └─network-pre.target @2.345s
>
>
> On Thu, Mar 21, 2019 at 4:00 AM Andy Clark <andyclark05251978 at gmail.com>
> wrote:
>
>> portion of the logs
>>
>> Mar 21 03:28:34 spce proxy[18720]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18720]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18718]: NOTICE: <spce> [main.c:692]:
>> handle_sigs(): Thank you for flying kamailio!!!
>> Mar 21 03:28:34 spce proxy[18719]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18721]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18721]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18719]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18722]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18722]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18723]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18723]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18725]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18725]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18724]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18727]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18724]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18727]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18726]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18726]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18732]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18732]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18730]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18728]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18730]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18728]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18737]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18729]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18731]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18736]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18737]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18731]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18736]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18729]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18734]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18733]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18734]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18733]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18738]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18738]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18735]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:28:34 spce proxy[18735]: NOTICE: qm_sums: summarizing all
>> alloc'ed. fragments:
>> Mar 21 03:28:34 spce proxy[18740]: NOTICE: <spce> [main.c:835]:
>> sig_usr(): Memory still-in-use summary (pkg):
>> Mar 21 03:29:49 spce proxy[1648]: WARNING: db_redis [redis_dbase.c:1084]:
>> db_redis_perform_query(): performing full table scan on table 'dialog'
>> while performing query
>> Mar 21 03:29:49 spce proxy[1648]: WARNING: db_redis [redis_dbase.c:1084]:
>> db_redis_perform_query(): performing full table scan on table 'dialog_vars'
>> while performing query
>> Mar 21 03:29:49 spce proxy[1670]: WARNING: db_redis [redis_dbase.c:1084]:
>> db_redis_perform_query(): performing full table scan on table 'location'
>> while performing query
>> Mar 21 03:29:49 spce proxy[1670]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1670]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1671]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1671]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1674]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1674]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1681]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1681]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1673]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1673]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1684]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1684]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1678]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1678]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1675]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1675]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1690]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1690]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1688]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1688]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1701]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1701]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1687]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1687]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1696]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1696]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1694]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1694]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1703]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1703]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1707]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1707]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1702]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1702]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1709]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1709]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1697]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1697]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1708]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1708]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1733]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1733]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1713]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1713]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1726]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1726]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1712]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1712]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1725]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1725]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1728]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1728]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>> Mar 21 03:29:49 spce proxy[1730]: ERROR: rtpengine [rtpengine.c:2605]:
>> send_rtpp_command(): can't send command "ping" to RTP proxy <udp:
>> 127.0.0.1:2223>
>> Mar 21 03:29:49 spce proxy[1730]: ERROR: rtpengine [rtpengine.c:2506]:
>> rtpp_test(): proxy did not respond to ping
>>
>>
>> root at spce:~# sudo ngcp-service summary | grep proxy
>> proxy managed on-boot active
>>
>>
>> root at spce:~# sudo systemctl is-enabled kamailio-proxy
>> enabled
>>
>> Startup finished in 1.552s (kernel) + 39.015s (userspace) = 40.567s
>> graphical.target reached after 39.008s in userspace
>>
>>
>> *Also i would like to add - it will randomly start but other services
>> will fail on boot*
>>
>> ● netfilter-persistent.service
>> loaded failed failed netfilter persistent
>> configuration
>> ● ngcp-rtpengine-daemon.service
>> loaded failed failed NGCP RTP/media Proxy
>> Daemon
>>
>> *-- Lastly my extra socket are not working*
>>
>>
>> more info
>>
>> root at spce:~# systemctl status
>> ● spce.mydomain.com
>> State: degraded
>> Jobs: 0 queued
>> Failed: 2 units
>> Since: Thu 2019-03-21 03:29:43 PDT; 26min ago
>> CGroup: /
>> ├─user.slice
>> │ └─user-0.slice
>> │ ├─session-5.scope
>> │ │ ├─ 3461 sshd: root at pts/0
>> │ │ ├─ 3596 -bash
>> │ │ ├─17286 systemctl status
>> │ │ └─17287 pager
>> │ └─user at 0.service
>> │ └─init.scope
>> │ ├─3562 /lib/systemd/systemd --user
>> │ └─3563 (sd-pam)
>> ├─init.scope
>> │ └─1 /sbin/init
>> └─system.slice
>> ├─irqbalance.service
>> │ └─482 /usr/sbin/irqbalance --foreground
>> ├─lvm2-lvmetad.service
>> │ └─342 /sbin/lvmetad -f
>> ├─fail2ban.service
>> │ └─1091 /usr/bin/python3 /usr/bin/fail2ban-server -s
>> /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
>> ├─grafana-server.service
>> │ └─764 /usr/sbin/grafana-server
>> --config=/etc/grafana/grafana.ini --pidfile=/run/grafana/grafana.pid
>> cfg:default.paths.logs=/var/log/grafana
>> cfg:default.paths.data=/var/lib/grafana
>> cfg:default.paths.plugins=/var/lib/grafana
>> ├─ngcp-rate-o-mat.service
>> │ └─1276 rate-o-mat
>> ├─influxdb.service
>> │ └─767 /usr/bin/influxd -config /etc/influxdb/influxdb.conf
>> -pidfile /run/influxdb/influxd.pid
>> ├─prosody.service
>> │ └─1261 lua5.1 /usr/bin/prosody
>> ├─nginx.service
>> │ ├─1061 nginx: master process /usr/sbin/nginx -g daemon on;
>> master_process on;
>> │ ├─1062 nginx: worker process
>> │ ├─1063 nginx: worker process
>> │ ├─1064 nginx: worker process
>> │ └─1065 nginx: worker process
>> ├─ngcp-sems.service
>> │ └─1258 /usr/sbin/ngcp-sems -E -u sems -g sems -P
>> /run/ngcp-sems/ngcp-sems.pid -f /etc/ngcp-sems/sems.conf
>> ├─dbus.service
>> │ └─458 /usr/bin/dbus-daemon --system --address=systemd:
>> --nofork --nopidfile --systemd-activation
>> ├─asterisk.service
>> │ └─763 /usr/sbin/asterisk -g -f -U asterisk
>> ├─ngcp-witnessd.service
>> │ ├─ 769 ngcp-witnessd
>> │ ├─17217 sleep 10
>> │ └─17254 sleep 10
>> ├─ngcp-mediator.service
>> │ └─1260 /usr/bin/mediator
>> ├─ssh.service
>> │ └─934 /usr/sbin/sshd -D
>> ├─ntp.service
>> │ └─812 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 115:118
>> ├─system-getty.slice
>> │ └─getty at tty1.service
>> │ └─773 /sbin/agetty -o -p -- \u --noclear tty1 linux
>> ├─open-vm-tools.service
>> │ └─324 /usr/bin/vmtoolsd
>> ├─systemd-logind.service
>> │ └─484 /lib/systemd/systemd-logind
>> ├─ngcp-license-client.service
>> │ └─1438 /usr/sbin/ngcp-licensed
>> ├─telegraf.service
>> │ └─456 /usr/bin/telegraf -pidfile
>> /run/telegraf/telegraf.pid -config /etc/telegraf/telegraf.conf
>> -config-directory /etc/telegraf/telegraf.d
>> ├─cron.service
>> │ └─485 /usr/sbin/cron -f
>> ├─kamailio-lb.service
>> │ ├─1109 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1133 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1134 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1135 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1136 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1137 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1138 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1139 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1141 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1142 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1143 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1144 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1145 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1146 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1147 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1148 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1149 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1150 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1151 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1152 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1153 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1154 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1155 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1156 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1157 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1158 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1159 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1160 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1161 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1162 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1163 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1164 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1165 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1166 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1167 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1168 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1169 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ ├─1170 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> │ └─1171 /usr/sbin/kamailio -P /run/kamailio/kamailio.lb.pid
>> -f /etc/kamailio/lb/kamailio.cfg -m 64 -M 16 -DD
>> ├─systemd-udevd.service
>> │ └─349 /lib/systemd/systemd-udevd
>> ├─acpid.service
>> │ └─457 /usr/sbin/acpid
>> ├─rsyslog.service
>> │ └─486 /usr/sbin/rsyslogd -n
>> ├─systemd-journald.service
>> │ └─330 /lib/systemd/systemd-journald
>> ├─mariadb.service
>> │ └─1059 /usr/sbin/mysqld
>> ├─haveged.service
>> │ └─356 /usr/sbin/haveged --Foreground --verbose=1 -w 1024
>> ├─redis-server.service
>> │ └─1066 /usr/bin/redis-server 127.0.0.1:6379
>> ├─kamailio-proxy.service
>> │ ├─1648 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1670 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1671 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1673 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1674 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1675 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1678 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1681 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1684 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1687 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1688 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1690 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1694 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1696 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1697 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1701 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1702 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1703 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1707 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1708 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1709 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1712 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1713 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1725 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1726 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1728 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ ├─1730 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> │ └─1733 /usr/sbin/kamailio -P
>> /run/kamailio/kamailio.proxy.pid -f /etc/kamailio/proxy/kamailio.cfg -m 499
>> -M 192 -DD
>> ├─ngcp-panel.service
>> │ ├─1262 perl-fcgi-pm [NGCP::Panel]
>> │ ├─1916 perl-fcgi
>> │ ├─1917 perl-fcgi
>> │ ├─1918 perl-fcgi
>> │ ├─1919 perl-fcgi
>> │ ├─1920 perl-fcgi
>> │ ├─1921 perl-fcgi
>> │ ├─1922 perl-fcgi
>> │ ├─1923 perl-fcgi
>> │ ├─1924 perl-fcgi
>> │ └─1925 perl-fcgi
>> └─exim4.service
>> └─1549 /usr/sbin/exim4 -bdf -q30m
>>
>>
>>
>>
>>
>> On Thu, Mar 21, 2019 at 2:50 AM Alex Lutay <alutay at sipwise.com> wrote:
>>
>>> Hi,
>>>
>>> please check:
>>>
>>> 0) check kamailio proxy log, I believe there is the answer...
>>>
>>> > less /var/log/ngcp/kamailio-proxy.log
>>>
>>> 1) If logs are empty, is it supposed to start?
>>>
>>> > [sipwise-lab-trunk] sipwise at spce:~$ sudo ngcp-service summary | grep
>>> proxy
>>> > proxy managed on-boot ...
>>>
>>> So, 'managed' mean ngcpcfg should start it on boot.
>>>
>>> 2) check is systemd is aware about kamailio (we use preset here):
>>>
>>> > [sipwise-lab-trunk] sipwise at spce:~$ sudo systemctl is-enabled
>>> kamailio-proxy
>>> > enabled
>>>
>>> 3) check your systemd "dependencies" for kamailio (some might failed to
>>> start -> blocked kamailio start):
>>>
>>> > [sipwise-lab-trunk] sipwise at spce:~$ sudo systemd-analyze
>>> critical-chain kamailio-proxy.service
>>> > kamailio-proxy.service +9.557s
>>> > └─mariadb.service @2.967s +6.221s
>>> > └─network.target @2.872s
>>> > └─networking.service @2.030s +841ms
>>> > └─local-fs.target @2.027s
>>> > └─vagrant.mount @38.396s
>>> > └─local-fs-pre.target @796ms
>>> > └─lvm2-monitor.service @520ms +275ms
>>> > └─lvm2-lvmetad.service @759ms
>>> > └─systemd-journald.socket @512ms
>>> > └─-.mount @393ms
>>> > └─system.slice @393ms
>>> > └─-.slice @393ms
>>>
>>> Have fun!
>>>
>>> On 3/21/19 2:07 AM, Andy Clark wrote:
>>> > Kamailio proxy does not start after reboot - must start manually
>>>
>>> --
>>> Alex Lutay
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20190321/41310a78/attachment-0001.html>
More information about the Spce-user
mailing list