No airtime-playout or liquidsoap start
  • Vote Up0Vote Down Ryan RidenourRyan Ridenour
    Posts: 3Member
    I just dont get it. I've successfully installed Airtime 2.5 on 3 machines here at home and not had any problems. But when I try it on a vps everything goes wrong. To make a long story short I finally got it to connect to icecast but cant get airtime-playout or liquidsoap to start. I've tried going through all the sudo invokerc.d start and restart commands. But they will start for a second or two then stop. The "on air" light comes on and off intermittently.

    What should I dig into next?

    Below is the output of the airtime-system-check.

    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 2.6.32-042stab081.8
    MACHINE_ARCHITECTURE           = i686
    TOTAL_MEMORY_MBYTES            = 2097152
    TOTAL_SWAP_MBYTES              = 2097152
    AIRTIME_VERSION                = 2.5.0
    OS                             = Ubuntu 12.04.3 LTS i686
    CPU                            = Intel(R) Xeon(R) CPU           L5520  @ 2.27GHz
    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-11-11 17:05:20,306 ERROR - [LogWriter.py : write() : line 8] - Error
    -- 2013-11-11 17:05:20,306 ERROR - [LogWriter.py : write() : line 8] - :
    -- 2013-11-11 17:05:20,306 ERROR - [LogWriter.py : write() : line 8] - unsupported locale setting
    -- 2013-11-11 17:05:20,307 ERROR - [LogWriter.py : write() : line 8] -
    -- 
    -- 
    -- 
    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/11/11 17:04:59 [server:3] Client localhost.localdomain disconnected.
    -- 2013/11/11 17:05:10 [server:3] New client: localhost.localdomain.
    -- 2013/11/11 17:05:10 [server:3] Client localhost.localdomain disconnected.
    -- 2013/11/11 17:05:20 [server:3] New client: localhost.localdomain.
    -- 2013/11/11 17:05:20 [server:3] Client localhost.localdomain disconnected.
    -- 
    -- 
    MEDIA_MONITOR_PROCESS_ID       = 454
    MEDIA_MONITOR_RUNNING_SECONDS  = 2605
    MEDIA_MONITOR_MEM_PERC         = 0.4%
    MEDIA_MONITOR_CPU_PERC         = 0.0%
    -- There appears to be a problem with your Airtime installation.

  • 5 Comments sorted by
  • Vote Up0Vote Down Tarkan KayaTarkan Kaya
    Posts: 52Member
    It might be problem I had just a week ago when I decided to try Airtime a couple of years later again.

    I am running Airtime on a VPS right now and the first thing I did which I saw in your logfile here is trying to install it on Ubuntu 12.04.3 LTS i686. I got exactly the same failing process id's as yours except the media id seems to be ok with yours. Since I couldn't find any solution after hours of search for 12.04.3 I decided to give it a final try on Ubuntu 12.04 x64 and it installed without any problem and runs fine (even right now).

    This might not be a way for you to deal with the problem. But here that was my experience.


    eastanbul.com
  • Vote Up0Vote Down Ryan RidenourRyan Ridenour
    Posts: 3Member
    Come to think of it all the machines I installed on at home are running 64 bit Ubuntu and Ubuntu based distros. I'll reinstall the vps and see how it goes. 
    I'll let you know if I have success or not. 
    Thank you for the idea.

  • Vote Up0Vote Down NaomiNaomi
    Posts: 228Member
    It seems to say there is a problem with your locale. Is it not UTF-8?
    On Nov 11, 2013 7:52 PM, "Ryan Ridenour" <<br />airtime-support@lists.sourcefabric.org> wrote:

    > Come to think of it all the machines I installed on at home are running 64
    > bit Ubuntu and Ubuntu based distros. I'll reinstall the vps and see how it
    > goes.
    > I'll let you know if I have success or not.
    > Thank you for the idea.
    >
    >
  • Vote Up0Vote Down Ryan RidenourRyan Ridenour
    Posts: 3Member
    It must've been the 32 bit. I reinstalled the vps with 64 bit Ubuntu 12.04.32 and installed Airtime and it is running nice and smooth now. 

    @Namoi Good Eye! I did reinstall and update the locales and that didn't work either. It must be that Airtime doesn't like 32 bit for some reason.
  • Vote Up0Vote Down Felix AnzolaFelix Anzola
    Posts: 1Member
    I´ve been able to sucessfully install and broadcast on my home network using airtime and is great, however once i reboot my system i get similar errors to this post, and the only way to make airtime work again is to completely remove it and remove postgresql and reinstall from scratch... which i suppose is not the way it is supposed to be, can somebody help me out?

    I´ve tried in two different machines running 12.04.3 DreamStudio 64bit, both with exact same results.

    I´m very sorry i´m very new to this as i´m willing to get a web station running for my studio and have never done it before, although i´ve been working for 5 years with Ubuntu (studio, dreamstudio) and Debian (avlinux).

    Also i notice the "AIRTIME_STATUS_URL" displayed by the airtime check doesn´t correspond to what i entered as host, and it doesn´t matter if i try to change that manually in the conf files of airtime, it can change what the status url displays but won´t fix airtime.

    This is the check output:

    AIRTIME_STATUS_URL             = http://felixer-laptop:80/api/status/format/json/api_key/%%api_key%%
    AIRTIME_SERVER_RESPONDING      = OK

    KERNEL_VERSION                 = UNKNOWN
    MACHINE_ARCHITECTURE           = UNKNOWN
    TOTAL_MEMORY_MBYTES            = UNKNOWN
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = UNKNOWN
    OS                             = DreamStudio 12.04.3 LTS x86_64

    CPU                            = Intel(R) Core(TM)2 Duo CPU     T6400  @ 2.00GHz
    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
    -- 2014-04-04 18:14:01,589 INFO - [api_client.py : is_server_compatible() : line 220] - Unable to get Airtime version number.

    --
    -- 2014-04-04 18:14:06,594 DEBUG - [api_client.py : __call__() : line 134] - http://felixer-laptop:80/api/version/api_key/QSJFHXGIOQ9VY67O2VQ6

    -- 2014-04-04 18:14:06,601 INFO - [api_client.py : is_server_compatible() : line 220] - Unable to get Airtime version number.
    --
    --
    --
    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
    -- 2014/04/03 23:13:26 [threads:3] Thread "wallclock_main" terminated (1 remaining).

    -- 2014/04/03 23:13:28 [threads:3] Thread "http polling" terminated (0 remaining).
    -- 2014/04/03 23:13:28 [main:3] Cleaning downloaded files...
    -- 2014/04/03 23:13:28 [main:3] Freeing memory...
    -- 2014/04/03 23:13:28 >>> LOG END

    --
    --
    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

    -- 2014-04-04 18:13:40,813 INFO - [Thread-1] [watchersyncer.py : __init__()] : LINE 19 - Created timeout thread...
    --
    2014-04-04 18:13:40,814 INFO - [Thread-1] [airtime.py :
    init_rabbit_mq()] : LINE 36 - Initializing RabbitMQ message consumer...

    -- 2014-04-04 18:13:40,828 INFO - [Thread-1] [airtime.py : init_rabbit_mq()] : LINE 48 - Initialized RabbitMQ consumer.
    -- 2014-04-04 18:13:40,828 DEBUG - [Thread-1] [api_client.py : __call__()] : LINE 134 - http://felixer-laptop:80/api/media-monitor-setup/format/json/api_key/QSJFHXGIOQ9VY67O2VQ6

    -- 2014-04-04 18:13:40,838 INFO - [Thread-1] [syncdb.py : reload_directories()] : LINE 49 - HTTP Error 503: Service Unavailable
    image

Add a Comment