[Spce-user] Call Data display & Odd behavior

Mon Feb 20 14:16:59 EST 2012

Hi,

 So I did another reboot and now see sems is failing due to mysql
connection. Could sems be starting up before mysql?

Here is what I'm seeing:

root at dev3:~# /etc/init.d/sems status
sems is not running ... failed!
root at dev3:~# tail /var/log/ngcp/sems.log
Feb 20 19:13:48 dev3 sems[861]: [#7f44d45c7720] [dump_Ifs,
AmConfig.cpp:812] INFO: #011LocalSIPPort=5080
Feb 20 19:13:48 dev3 sems[861]: [#7f44d45c7720] [dump_Ifs,
AmConfig.cpp:813] INFO: #011RtpLowPort=40001
Feb 20 19:13:48 dev3 sems[861]: [#7f44d45c7720] [dump_Ifs,
AmConfig.cpp:814] INFO: #011RtpHighPort=50000
Feb 20 19:13:48 dev3 sems[861]: [#7f44d45c7720] [dump_Ifs,
AmConfig.cpp:817] INFO: Signaling address map:
Feb 20 19:13:48 dev3 sems[861]: [#7f44d45c7720] [dump_Ifs,
AmConfig.cpp:822] INFO: #011127.0.0.1 -> default
Feb 20 19:13:48 dev3 sems[886]: [#7f44d45c7720] [main, sems.cpp:463] INFO:
Loading plug-ins
Feb 20 19:13:48 dev3 sems[886]: [#7f44d45c7720] [load, AmPlugIn.cpp:216]
INFO: AmPlugIn: loading modules:
'wav;gsm;xmlrpc2di;di_dial;stats;uac_auth;session_timer;click2dial;sw_vsc;conference;sbc;registrar_client;reg_agent;db_reg_agent'
Feb 20 19:13:48 dev3 sems[886]: [#7f44d45c7720] [onLoad,
DBRegAgent.cpp:203] ERROR: MySQL++ error: Can't connect to local MySQL
server through socket '/var/run/mysqld/mysqld.sock' (2)
Feb 20 19:13:48 dev3 sems[886]: [#7f44d45c7720] [main, sems.cpp:509] INFO:
Disposing plug-ins
Feb 20 19:13:48 dev3 sems[886]: [#7f44d45c7720] [main, sems.cpp:520] INFO:
Exiting (failure)
root at dev3:~# /etc/init.d/mysql status
/usr/bin/mysqladmin  Ver 8.42 Distrib 5.1.60, for debian-linux-gnu on x86_64
Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Server version 5.1.60-rel13.1-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/run/mysqld/mysqld.sock
Uptime: 1 min 38 sec

Threads: 4  Questions: 337  Slow queries: 0  Opens: 600  Flush tables: 1
 Open tables: 149  Queries per second avg: 3.438.

--skyler

On Mon, Feb 20, 2012 at 10:06 AM, Skyler <skchopperguy at gmail.com> wrote:

> Hi Andrew,
>
> On Mon, Feb 20, 2012 at 9:11 AM, Andrew Pogrebennyk <
> apogrebennyk at sipwise.com> wrote:
>
>> Hi Skyler,
>> maybe others will correct me, but the destination is only normalized in
>> the csc panel's CDR list. If you go to csc you should really see
>> "Voicebox", at least that's what it looks like for me. We do not have
>> normalization in the admin panel.
>>
>> Yes, in csc this is normalized. Actually, now that I think about it the
> admin panel should NOT be normalized for quick debug reasons. Makes sense.
>
>
>
>> As for the issue with missing CDRs please check /var/log/ngcp/cdr.log
>> (mediator) and /var/log/ngcp/rate-o-mat.log (rate-o-mat).
>>
>
>  Ok, will look there when this occurs again. Thanks.
>
>
>> And I don't have a problem with sems start on boot in version 2.4, could
>> you please show me the output from ls -l /etc/rc2.d?
>>
>>
>  It appears to be in startup sequence but when trying to make a call after
> reboot no calls connect. When I do /etc/init.d/sems status after a reboot
> it shows 'failed'. No errors in /var/log/ngcp/sems.log to indicate a
> problem. I'll just keep this in mind as a first check after any reboots.
>
> root at dev3:~# ls -l /etc/rc2.d
> total 4
> -rw-r--r-- 1 root root 677 Jan  1  2011 README
> lrwxrwxrwx 1 root root  20 Feb  1 11:40 S01fancontrol ->
> ../init.d/fancontrol
> lrwxrwxrwx 1 root root  17 Feb  1 11:40 S01rsyslog -> ../init.d/rsyslog
> lrwxrwxrwx 1 root root  14 Feb  1 12:18 S01sudo -> ../init.d/sudo
> lrwxrwxrwx 1 root root  17 Feb  2 10:05 S02apache2 -> ../init.d/apache2
> lrwxrwxrwx 1 root root  15 Feb  2 10:05 S03acpid -> ../init.d/acpid
> lrwxrwxrwx 1 root root  18 Feb  2 10:05 S03collectd -> ../init.d/collectd
> lrwxrwxrwx 1 root root  14 Feb  2 10:05 S03cron -> ../init.d/cron
> lrwxrwxrwx 1 root root  20 Feb  2 10:06 S03irqbalance ->
> ../init.d/irqbalance
> lrwxrwxrwx 1 root root  21 Feb  2 10:06 S03kamailio-lb ->
> ../init.d/kamailio-lb
> lrwxrwxrwx 1 root root  15 Feb  2 10:05 S03mysql -> ../init.d/mysql
> lrwxrwxrwx 1 root root  35 Feb  2 10:05 S03ngcp-mediaproxy-ng-daemon ->
> ../init.d/ngcp-mediaproxy-ng-daemon
> lrwxrwxrwx 1 root root  25 Feb  2 10:06 S03ngcp-rate-o-mat ->
> ../init.d/ngcp-rate-o-mat
> lrwxrwxrwx 1 root root  13 Feb  2 10:05 S03ntp -> ../init.d/ntp
> lrwxrwxrwx 1 root root  15 Feb  2 10:06 S03rsync -> ../init.d/rsync
> lrwxrwxrwx 1 root root  14 Feb  2 10:06 S03sems -> ../init.d/sems
> lrwxrwxrwx 1 root root  15 Feb  2 10:05 S03snmpd -> ../init.d/snmpd
> lrwxrwxrwx 1 root root  13 Feb  2 10:05 S03ssh -> ../init.d/ssh
> lrwxrwxrwx 1 root root  17 Feb  2 10:06 S03sysstat -> ../init.d/sysstat
> lrwxrwxrwx 1 root root  18 Feb  2 10:06 S04asterisk -> ../init.d/asterisk
> lrwxrwxrwx 1 root root  15 Feb  2 10:05 S04exim4 -> ../init.d/exim4
> lrwxrwxrwx 1 root root  18 Feb  2 10:05 S04kamailio -> ../init.d/kamailio
> lrwxrwxrwx 1 root root  24 Feb  2 10:06 S04kamailio-proxy ->
> ../init.d/kamailio-proxy
> lrwxrwxrwx 1 root root  18 Feb  2 10:06 S04mediator -> ../init.d/mediator
> lrwxrwxrwx 1 root root  18 Feb  2 10:05 S05bootlogs -> ../init.d/bootlogs
> lrwxrwxrwx 1 root root  18 Feb  2 10:05 S06rc.local -> ../init.d/rc.local
> lrwxrwxrwx 1 root root  19 Feb  2 10:05 S06rmnologin -> ../init.d/rmnologin
> lrwxrwxrwx 1 root root  23 Feb  2 10:05 S06stop-bootlogd ->
> ../init.d/stop-bootlogd
>
>
> Thanks!
>
> On 02/19/2012 11:02 PM, Skyler wrote:
>> > Hi,
>> >
>> >  When I look at Call Data for a subscriber from within the admin panel,
>> > I see calls to voicemail showing like "abc17778884545 at voicebox.local"
>> or
>> > "vmu17778884545 at voicebox.local". I'm sure that back in 2.2 all calls
>> > used to show like "voicebox" or "voicemail".
>> >
>> >  How would I change this so calls to voicebox show "voicebox" in the
>> > Call Data display? I don't mind hacking around if you can point me in
>> > the direction ;)
>> >
>> >  I've also noticed that CDR's sometimes don't display at all until
>> > server is rebooted. Which service is responsible for this so I can
>> > monitor it? doesn't affect calls so I haven't noticed before today.
>> > Also, I have to manually start SEMS after reboots it
>> > seems. /var/log/ngcp/sems.log is empty so I have no idea what might be
>> > the problem there.
>> >
>> > - Skyler
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20120220/0bfc0739/attachment-0001.html>