New Install - Stumped. Components not registering..
  • Vote Up0Vote Down John ChewterJohn Chewter
    Posts: 899Member
    Airtime server says its running
    But its not registering components

    The other servers say PID Failed but the processes are running and I can see their PIDs
    I have have hunted high and low in the forum but cannot see anything exactlty like this.

    Any ideas?


    AIRTIME_STATUS_URL             = http://server.trt003.tk:80/api/status/format/json/api_key/%%api_key%%
    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 3.8.13-xxxx-grs-ipv6-64
    MACHINE_ARCHITECTURE           = x86_64
    TOTAL_MEMORY_MBYTES            = 16333020
    TOTAL_SWAP_MBYTES              = 33552376
    AIRTIME_VERSION                = 2.4.0
    OS                             = Ubuntu 12.04.2 LTS x86_64
    CPU                            = Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
    WEB_SERVER                     = Apache/2.2.22 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = FAILED
    PLAYOUT_ENGINE_RUNNING_SECONDS = 0
    PLAYOUT_ENGINE_MEM_PERC        = 0%
    PLAYOUT_ENGINE_CPU_PERC        = 0%
    -- Displaying log file /var/log/airtime/pypo/pypo.log
    -- 2013-06-29 19:06:47,616 ERROR - [pypocli.py : <module>() : line 239] -
    -- 2013-06-29 19:06:57,626 DEBUG - [api_client.py : __call__() : line 134] - http://server.trt003.tk:80/api/register-component/format/json/api_key/S1GF7UW271GAF1HVOSWQ/component/pypo
    -- 2013-06-29 19:06:57,714 ERROR - [pypocli.py : <module>() : line 239] -
    -- 2013-06-29 19:07:07,724 DEBUG - [api_client.py : __call__() : line 134] - http://server.trt003.tk:80/api/register-component/format/json/api_key/S1GF7UW271GAF1HVOSWQ/component/pypo
    -- 2013-06-29 19:07:07,775 ERROR - [pypocli.py : <module>() : line 239] -
    --
    --
    LIQUIDSOAP_PROCESS_ID          = FAILED
    LIQUIDSOAP_RUNNING_SECONDS     = 0
    LIQUIDSOAP_MEM_PERC            = 0%
    LIQUIDSOAP_CPU_PERC            = 0%
    -- Displaying log file /var/log/airtime/pypo-liquidsoap/ls_script.log
    -- 2013/06/29 19:06:45 [server:3] Client localhost.localdomain disconnected.
    -- 2013/06/29 19:06:55 [server:3] New client: localhost.localdomain.
    -- 2013/06/29 19:06:55 [server:3] Client localhost.localdomain disconnected.
    -- 2013/06/29 19:07:05 [server:3] New client: localhost.localdomain.
    -- 2013/06/29 19:07:05 [server:3] Client localhost.localdomain disconnected.
    --
    --
    MEDIA_MONITOR_PROCESS_ID       = FAILED
    MEDIA_MONITOR_RUNNING_SECONDS  = 0
    MEDIA_MONITOR_MEM_PERC         = 0%
    MEDIA_MONITOR_CPU_PERC         = 0%
    -- Displaying log file /var/log/airtime/media-monitor/media-monitor.log
    -- 2013-06-29 19:06:47,837 ERROR - [Thread-1] [launcher.py : run()] : LINE 94 -
    -- 2013-06-29 19:06:57,846 DEBUG - [Thread-1] [api_client.py : __call__()] : LINE 134 - http://server.trt003.tk:80/api/register-component/format/json/api_key/S1GF7UW271GAF1HVOSWQ/component/media-monitor
    -- 2013-06-29 19:06:57,897 ERROR - [Thread-1] [launcher.py : run()] : LINE 94 -
    -- 2013-06-29 19:07:07,907 DEBUG - [Thread-1] [api_client.py : __call__()] : LINE 134 - http://server.trt003.tk:80/api/register-component/format/json/api_key/S1GF7UW271GAF1HVOSWQ/component/media-monitor
    -- 2013-06-29 19:07:07,957 ERROR - [Thread-1] [launcher.py : run()] : LINE 94 -
    --
    --
    -- There appears to be a problem with your Airtime installation.
    -- Please visit http://wiki.sourcefabric.org/x/HABQ
    invoke-rc.d: initscript airtime-playout, action "status" failed.

    No longer using Airtime or Libretime.
  • 4 Comments sorted by
  • Vote Up0Vote Down John ChewterJohn Chewter
    Posts: 899Member
    After some digging.. I found this seems to be causing the problem:
    INSERT
    statement [INSERT INTO cc_service_register (NAME,IP) VALUES (:p1,:p2)]
    [wrapped: SQLSTATE[22001]: String data, right truncated: 7 ERROR:  value
    too long for type character varying(18)] - See more at:
    http://forum.sourcefabric.org/discussion/15603/new-install-stumped-components-not-registering-#sthash.h7NoOzqr.dpuf

    [index.php : () : line 71] - Unable to execute INSERT statement [INSERT INTO cc_service_register (NAME,IP) VALUES (:p1,:p2)] [wrapped: SQLSTATE[22001]: String data, right truncated: 7 ERROR:  value too long for type character varying(18)]

    INSERT
    statement [INSERT INTO cc_service_register (NAME,IP) VALUES (:p1,:p2)]
    [wrapped: SQLSTATE[22001]: String data, right truncated: 7 ERROR:  value
    too long for type character varying(18)] - See more at:
    http://forum.sourcefabric.org/discussion/15603/new-install-stumped-components-not-registering-#sthash.h7NoOzqr.dpuf
    zendphp.log

    2013-06-30T08:45:06+02:00 INFO (6): [ApiController.php : registerComponentAction() : line 721] - Registered Component: media-monitor@2001:41d0:8:52df::1
    2013-06-30T08:45:06+02:00 INFO (6): [index.php : () : line 71] - Unable to execute INSERT statement [INSERT INTO cc_service_register (NAME,IP) VALUES (:p1,:p2)] [wrapped: SQLSTATE[22001]: String data, right truncated: 7 ERROR:  value too long for type character varying(18)]
    2013-06-30T08:45:06+02:00 INFO (6): [index.php : () : line 73] - #0 /usr/share/airtime/application/models/airtime/om/BaseCcServiceRegister.php(333): BasePeer::doInsert(Object(Criteria), Object(PropelPDO))
    #1 /usr/share/airtime/application/models/airtime/om/BaseCcServiceRegister.php(291): BaseCcServiceRegister->doSave(Object(PropelPDO))
    #2 /usr/share/airtime/application/models/ServiceRegister.php(37): BaseCcServiceRegister->save()
    #3 /usr/share/airtime/application/controllers/ApiController.php(723): Application_Model_ServiceRegister::Register('media-monitor', '2001:41d0:8:52d...')
    #4 /usr/share/php/libzend-framework-php/Zend/Controller/Action.php(516): ApiController->registerComponentAction()
    #5 /usr/share/php/libzend-framework-php/Zend/Controller/Dispatcher/Standard.php(295): Zend_Controller_Action->dispatch('registerCompone...')
    #6 /usr/share/php/libzend-framework-php/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
    #7 /usr/share/php/libzend-framework-php/Zend/Application/Bootstrap/Bootstrap.php(97): Zend_Controller_Front->dispatch()
    #8 /usr/share/php/libzend-framework-php/Zend/Application.php(366): Zend_Application_Bootstrap_Bootstrap->run()
    #9 /usr/share/airtime/public/index.php(64): Zend_Application->run()
    Post edited by John Chewter at 2013-06-30 02:48:41
    No longer using Airtime or Libretime.
  • Vote Up0Vote Down John ChewterJohn Chewter
    Posts: 899Member
    Hmmmm Its getting the ip wrong. Its trying to use like a mangled mac address intead of ip address - anybody seen this?
    No longer using Airtime or Libretime.
  • Vote Up0Vote Down Bernard ToplakBernard Toplak
    Posts: 1Member
    Hi @all,

    I know I'm bumping an old thread, but I think it could be interesting to other users too.

    I spent whole day trying to reinstall/debug AirTime 2.5, with the same problems as original poster.
    Cryptic errors outputed (from logs) when running "airtime-check-system" didn't help at all...

    At last I took a closer look at zendphp.log file, and I noticed that pypo, media-monitor and other services are trying to bind on IPv6 addresses (mistakenly interpreted as MAC addr by original poster), which fails dramatically. 
    After a quick sweep of AirTime conf files I concluded that no file contains IPv6 addresses. That left only one option - /etc/hosts file. I commented out the line with hostname mapped to IPv6 and - voila! It works

    I hope this will help anyone else not to loose hours and grayhair... maybe add it to manual/wiki?
  • Vote Up0Vote Down Roger WilcoRoger Wilco
    Posts: 784Banned
    Yeah, that's exactly it. Airtime and Liquidsoap aren't IPv6 enabled nor will they be anytime soon. :-B
Add a Comment