Homer still not working after an update this morning -- see action
snippets below.

It shows every indication it is not running, but I can log into the
interface and call up data from 7/30 (the last time it was running).

jim

---------------------------------------------------------------

Ran update this morning:

 sipxhomer                               i686
4.6.0-26.ge5184ee                   sipXecs                   143 k
 sipxhomer-config                        i686
4.6.0-26.ge5184ee                   sipXecs                    14 k
 sipxhomer-proxyplugin                   i686
4.6.0-26.ge5184ee                   sipXecs                   117 k

Rebooted.

var/log/messages:

Aug  2 04:40:24 sipx kernel: sipxhomer[2652]: segfault at fff5 ip
0807a027 sp bfd27dc0 error 4 in sipxhomer[8048000+6a000]

/var/log/sipxpbx/sipxhomer.log

*** No new entries

------------------------------------

Attempted restart of homer:

etc/init.d/sipxhomer status
sipxhomer dead but pid file exists

/etc/init.d/sipxhomer restart
Stopping sipxhomer:                                        [FAILED]
Starting sipxhomer: 
sipxhomer version 1.0 - All Rights Reserved.

[root@sipx sipxpbx]#                                       [  OK  ]

/etc/init.d/sipxhomer status
sipxhomer dead but pid file exists


------------------------------------

/etc/init.d/sipxhomer nofork

sipxhomer version 1.0 - All Rights Reserved.

terminate called after throwing an instance of 'HEPDaoException'
  what():  [MySQL][ODBC 5.1 Driver]Failed to parse the incoming connect
string.

/var/log/sipxpbx/sipxhomer.log

*** No new entries

------------------------------------

/var/log/mysqld.log:

120802 04:39:11 mysqld_safe mysqld from pid
file /var/run/mysqld/mysqld.pid ended
120802 04:40:03 mysqld_safe Starting mysqld daemon with databases
from /var/lib/mysql
120802  4:40:03  InnoDB: Initializing buffer pool, size = 8.0M
120802  4:40:03  InnoDB: Completed initialization of buffer pool
120802  4:40:03  InnoDB: Started; log sequence number 0 44233
120802  4:40:03 [Note] Event Scheduler: Loaded 0 events
120802  4:40:03 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.1.61'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
Source distribution

------------------------------------
rpm -qa | grep sipx

sipxsupervisor-4.6.0-261.gbbdad.i686
sipxmongo-server-4.6.0-261.gbbdad.i686
sipxcdr-client-4.6.0-261.gbbdad.i686
sipxcommserverlib-4.6.0-261.gbbdad.i686
sipxrelay-4.6.0-261.gbbdad.i686
sipxaudiocodes-4.6.0-261.gbbdad.noarch
sipxconfig-tftp-4.6.0-265.g4ba15.i686
sipxfreeswitch-4.6.0-261.gbbdad.i686
sipxrls-4.6.0-261.gbbdad.i686
sipxregistry-4.6.0-261.gbbdad.i686
sipxhomer-proxyplugin-4.6.0-26.ge5184ee.i686
sipximbot-4.6.0-5.gf9087.i686
sipxaastra-4.6.0-5.gf9087.i686
sipxmitel-4.6.0-5.gf9087.i686
sipxnortel-4.6.0-5.gf9087.i686
sipxgtek-4.6.0-5.gf9087.i686
sipxhitachi-4.6.0-5.gf9087.i686
sipxprovision-4.6.0-5.gf9087.i686
sipxportlib-4.6.0-261.gbbdad.i686
sipxhomer-config-4.6.0-26.ge5184ee.i686
sipxhomer-4.6.0-26.ge5184ee.i686
sipxtacklib-4.6.0-265.g4ba15.i686
sipxmongo-4.6.0-261.gbbdad.i686
sipxpostgres-4.6.0-261.gbbdad.i686
sipxacdstatistics-client-4.6.0-261.gbbdad.i686
sipxdns-4.6.0-265.g4ba15.i686
sipxsnmp-4.6.0-261.gbbdad.i686
sipxmedialib-4.6.0-261.gbbdad.i686
sipxconfig-4.6.0-265.g4ba15.i686
sipxmediaadapterlib-4.6.0-261.gbbdad.i686
sipxsqa-4.6.0-261.gbbdad.i686
sipxconfig-ftp-4.6.0-265.g4ba15.i686
sipxcounterpath-4.6.0-261.gbbdad.i686
sipxcdr-4.6.0-261.gbbdad.i686
sipxivr-4.6.0-261.gbbdad.i686
sipxopenfire-4.6.0-261.gbbdad.i686
sipxsqa-server-4.6.0-261.gbbdad.i686
sipxpark-4.6.0-261.gbbdad.i686
sipxproxy-4.6.0-261.gbbdad.i686
sipxpublisher-4.6.0-261.gbbdad.i686
sipxrest-4.6.0-5.gf9087.i686
sipx-openfire-3.6.4-3.noarch
sipxcdrlog-4.6.0-5.gf9087.i686
sipxlg-nortel-4.6.0-5.gf9087.i686
sipxgrandstream-4.6.0-5.gf9087.i686
sipxipdialog-4.6.0-5.gf9087.i686
sipxisphone-4.6.0-5.gf9087.i686
sipxclearone-4.6.0-5.gf9087.i686
sipxcisco-4.6.0-5.gf9087.i686
sipxunidata-4.6.0-5.gf9087.i686
sipxacccode-4.6.0-5.gf9087.i686
sipxrecording-4.6.0-84.g2b8f3.i686
sipxcommons-4.6.0-261.gbbdad.i686
sipxprompts-4.6.0-261.gbbdad.i686
sipxtunnel-4.6.0-261.gbbdad.i686
sipxhttpd-4.6.0-261.gbbdad.i686
sipxcalllib-4.6.0-261.gbbdad.i686
sipxpolycom-4.6.0-261.gbbdad.i686
sipxbridge-4.6.0-261.gbbdad.i686
sipxpage-4.6.0-261.gbbdad.i686
sipxsaa-4.6.0-261.gbbdad.i686
sipxcallcontroller-4.6.0-5.gf9087.i686
sipxsnom-4.6.0-109.gd2c8b.i686
sipxevent-4.6.0-5.gf9087.i686
sipxopenacd-4.6.0-51.g717ed.i686


> On Thu, Aug 2, 2012 at 5:31 AM, Tony Graziano
> <[email protected]> wrote:
>         the pid file does exist (var/run/sipxpbx/sipxhomer.pid) and
>         manually removing it and restarting sipxhomer results in the
>         same error. the pid file does get removed when stopping
>         service too. 
> 
> 
> I was able to reproduce this and I spent some time trying to diagnose.
> Joegen is taking a look at it more in depth so stay tuned.
> 
> 
> If you're eager to test, this did work for me.  Run homer in
> foreground. As root, run
> 
> 
>   /etc/init.d/sipxhomer nofork
> 
> 
> Although that didn't work for jnolan, it worked for me.  We're waiting
> to hear back from Jim, maybe he hadn't enabled the features, not sure.
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to