Problem with Airtime after upgrading to Ubuntu 14.04 LTS
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    Greetings to all,

    I recently upgraded my 12.04 distro to 14.04 and since then airtime seems not to be working right.

    What I noticed first is that the login screen would give me that screen

    image

    When I select "Continue to this site (not recommended)" I get this screen

    image

    I have been messing around with the various configuration files of airtime and apache but I don't seem to make any progress.

    I also encountered a problem with the apt-get upgrade command and icecast2 where it says:

    Errors were encountered while processing:
     icecast2
    E: Sub-process /usr/bin/dpkg returned an error code (1)


    I don't know if this is related with the airtime problem.

    The airtime-check-system command outputs:

    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = UNKNOWN
    MACHINE_ARCHITECTURE           = UNKNOWN
    TOTAL_MEMORY_MBYTES            = UNKNOWN
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = UNKNOWN
    OS                             = Ubuntu 14.04.3 LTS i686
    CPU                            = AMD Athlon(tm) II X2 250 Processor
    WEB_SERVER                     = Apache/2.4.7 (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
    -- 2016-02-13 17:07:49,021 ERROR - [replaygainupdater.py : run() : line 81] - <urlopen error [Errno 111] Connection refused>
    -- 2016-02-13 17:09:02,212 DEBUG - [api_client.py : __call__() : line 134] - http://localhost:80/api/get-stream-parameters/api_key/VYRBGEXW95CP35RSI1K2/format/json
    -- 2016-02-13 17:09:02,213 ERROR - [listenerstat.py : run() : line 140] - Exception: <urlopen error [Errno 111] Connection refused>
    -- 2016-02-13 17:11:02,272 DEBUG - [api_client.py : __call__() : line 134] - http://localhost:80/api/get-stream-parameters/api_key/VYRBGEXW95CP35RSI1K2/format/json
    -- 2016-02-13 17:11:02,273 ERROR - [listenerstat.py : run() : line 140] - Exception: <urlopen error [Errno 111] Connection refused>
    --
    --
    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
    -- 2016/02/13 17:12:29 [stderr:3] ImportError: No module named _io
    -- 2016/02/13 17:12:29 [threads:3] Thread "http polling" terminated (0 remaining).
    -- 2016/02/13 17:12:29 [main:3] Cleaning downloaded files...
    -- 2016/02/13 17:12:29 [main:3] Freeing memory...
    -- 2016/02/13 17:12:29 >>> 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
    -- 2016-02-13 17:12:25,661 ERROR - [Thread-5] [eventdrainer.py : cb()] : LINE 22 - Error connecting to RabbitMQ Server.                                       Trying again in few seconds
    -- 2016-02-13 17:12:30,663 INFO - [Thread-5] [airtime.py : init_rabbit_mq()] : LINE 36 - Initializing RabbitMQ message consumer...
    -- 2016-02-13 17:12:30,664 INFO - [Thread-5] [airtime.py : init_rabbit_mq()] : LINE 50 - Failed to initialize RabbitMQ consumer
    -- 2016-02-13 17:12:30,664 ERROR - [Thread-5] [airtime.py : init_rabbit_mq()] : LINE 51 - [Errno 111] Connection refused
    -- 2016-02-13 17:12:30,664 ERROR - [Thread-5] [eventdrainer.py : cb()] : LINE 22 - Error connecting to RabbitMQ Server.                                       Trying again in few seconds
    --
    --
    -- There appears to be a problem with your Airtime installation.



    Please I would appreciate it very much if you would give a solution to this problem.
    Thanks in advance.
    img1.jpg
    800 x 500 - 44K
    img2.jpg
    800 x 500 - 25K
    img3.jpg
    582 x 67 - 22K
    Post edited by pame webradio at 2016-02-14 12:50:39
  • 16 Comments sorted by
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    I have made some progress.

    I installed the latest version of airtime (2.5.2) and now I am able to login on the web UI from Firefox or Internet Explorer, Google Chrome is giving me a hard time with the certificates.

    Though I can schedule music to play, the ON AIR sign stays grey. Also the stream cannot connect to Icecast, i get a constant "Getting information from the server"


    img4.jpg
    599 x 182 - 49K
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    Update 2:

    I noticed something, every time the song changes the ON AIR sign lights up for about 2-3 seconds and then it goes grey again.

    I also noticed that uploaded items don't show up on the library.
    I succesfully added a song from the ADD MEDIA menu but when I searched for it in the Library menu, the song wasn't there.

    The status option in the Options Menu shows that everything is working fine.

    Please if someone has any clue about what is going on I would really appreciate it.
    Post edited by pame webradio at 2016-02-15 06:33:34
  • Vote Up0Vote Down James DunnJames Dunn
    Posts: 226Member
    Is your icecast server running? ( pgrep icecast )
    What does airtime-check-system say now?
    Are all your airtime services running? ( service airtime-media-monitor status / service airtime-playout status / service airtime-liquidsoap status )
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    Icecast is located on a remote hosting service and is working. I've tested with airtime pro and is actually working.

    the airtime-check-system command returns:

    root@pame-radio:/home/pamehellas# airtime-check-system
    airtime-check-system: command not found

    root@pame-radio:/home/pamehellas# service airtime-media-monitor status
    airtime-media-monitor start/running, process 22152

    root@pame-radio:/home/pamehellas# service airtime-playout status
    airtime-playout start/running, process 859

    root@pame-radio:/home/pamehellas# service airtime-liquidsoap status
    airtime-liquidsoap start/running, process 22304
  • Vote Up0Vote Down James DunnJames Dunn
    Posts: 226Member
    Are your icecasts password correct?

    Have you tried disabling the icecast streams and enabling hardware output to see if that works?

    What's in the airtime logs? Particularly /var/log/airtime/zendphp.log?
  • Vote Up0Vote Down Roger WilcoRoger Wilco
    Posts: 784Banned

    Requirements

    • PostgresSQL database management and
    • Debian Wheezy or
    • Ubuntu Linux 12.04 LTS 
    • For a server edition OS, minimum 1 GHz processor and 512 MB of RAM
    • For a desktop edition, minimum 1GB of RAM


    Use Debian 7 and your problems will likely evaporate. Stubbornly use something newer because reasons? There be dragons...


  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    The icecast passwords are correct, tried them over and over.

    Just tried disabling icecast stream and enabling hardware output with ALSA and Pulseaudio but it's all the same.

    What should I look for in the log file? It's quite huge.

    @ Roger Wilco

    I will propably end up doing exactly that, but I don't want to go down withoun a fight :P
    Post edited by pame webradio at 2016-02-15 13:02:33
  • Vote Up0Vote Down Roger WilcoRoger Wilco
    Posts: 784Banned
    Yeah, don't waste time flapping your arms trying to fly :)
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    Hello again,

    I followed @ Roger Wilco's advice and installed Debian 7.9 Wheezy and Airtime 2.5.1 from fresh.

    There seems to be a problem again as airtime-check-system outputs:

    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = UNKNOWN
    MACHINE_ARCHITECTURE           = UNKNOWN
    TOTAL_MEMORY_MBYTES            = UNKNOWN
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = UNKNOWN
    OS                             = Debian GNU/Linux 7.9 (wheezy) i686
    CPU                            = AMD Athlon(tm) II X2 250 Processor
    WEB_SERVER                     = Boa/0.94.13
    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
    -- 2016-02-17 20:07:10,151 INFO - [api_client.py : is_server_compatible() : line 220] - Unable to get Airtime version number.
    --
    -- 2016-02-17 20:07:15,156 DEBUG - [api_client.py : __call__() : line 134] - http://pameradio.dyndns-server.com:80/api/version/api_key/SIWIS5IQR45                               B46HR12K6
    -- 2016-02-17 20:07:15,164 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%
    tail: cannot open `/var/log/airtime/pypo-liquidsoap/ls_script.log' for reading: No such file or directory
    -- Displaying log file /var/log/airtime/pypo-liquidsoap/ls_script.log
    --
    --
    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
    -- 2016-02-17 20:07:08,470 INFO - [Thread-1] [watchersyncer.py : __init__()] : LINE 19 - Created timeout thread...
    -- 2016-02-17 20:07:08,470 INFO - [Thread-1] [airtime.py : init_rabbit_mq()] : LINE 36 - Initializing RabbitMQ message consumer...
    -- 2016-02-17 20:07:08,474 INFO - [Thread-1] [airtime.py : init_rabbit_mq()] : LINE 48 - Initialized RabbitMQ consumer.
    -- 2016-02-17 20:07:08,474 DEBUG - [Thread-1] [api_client.py : __call__()] : LINE 134 - http://pameradio.dyndns-server.com:80/api/media-monitor-se                               tup/format/json/api_key/SIWIS5IQR45B46HR12K6
    -- 2016-02-17 20:07:08,483 INFO - [Thread-1] [syncdb.py : reload_directories()] : LINE 49 - HTTP Error 401: Unauthorized
    --
    --
    -- There appears to be a problem with your Airtime installation.

    The first line with the asterisks is the DDNS hostname.


    service airtime-media-monitor status &
    service airtime-playout status

    output exactly the same as airtime-check-system

    service airtime-liquidsoap status
    root@pameradio:~# service airtime-liquidsoap status
    Liquidsoap Playout Engine is running

    Have I made something wrong? I followed the steps on the Airtime manual as they are stated but I get the same problematic Airtime installation as previously with Ubuntu 14.04
    Post edited by pame webradio at 2016-02-17 13:18:46
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    Well that is odd, I discovered that if I change the base url to localhost in the /etc/airtime/airtime.conf from my DDNS hostname then I get this:

    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 3.2.0-4-686-pae
    MACHINE_ARCHITECTURE           = i686
    TOTAL_MEMORY_MBYTES            = 1943984
    TOTAL_SWAP_MBYTES              = 3929084
    AIRTIME_VERSION                = 2.5.1
    OS                             = Debian GNU/Linux 7.9 (wheezy) i686
    CPU                            = AMD Athlon(tm) II X2 250 Processor
    WEB_SERVER                     = Apache/2.2.22 (Debian)
    PLAYOUT_ENGINE_PROCESS_ID      = 3624
    PLAYOUT_ENGINE_RUNNING_SECONDS = 279
    PLAYOUT_ENGINE_MEM_PERC        = 0.5%
    PLAYOUT_ENGINE_CPU_PERC        = 0.0%
    LIQUIDSOAP_PROCESS_ID          = 4301
    LIQUIDSOAP_RUNNING_SECONDS     = 71
    LIQUIDSOAP_MEM_PERC            = 0.7%
    LIQUIDSOAP_CPU_PERC            = 3.4%
    MEDIA_MONITOR_PROCESS_ID       = 4445
    MEDIA_MONITOR_RUNNING_SECONDS  = 61
    MEDIA_MONITOR_MEM_PERC         = 0.5%
    MEDIA_MONITOR_CPU_PERC         = 0.0%
    -- Your installation of Airtime looks OK!

    I am confused!! :S
  • Vote Up0Vote Down Roger WilcoRoger Wilco
    Posts: 784Banned
    The scripts double-check to make sure your installation can actually be reached at the FQDN you provide at installation. Why on earth do you need to use DYNDNS? Your server should have a fixed IP...
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    My icecast server which is located elsewhere does have a fixed IP, my airtime server is a, let's say local PC which needs DDNS to be reached remotely when I am not there through ssh and also to be reached by MIXXX when needed.

    The thing is that I obviously don't remember which setting is making the difference.
  • Vote Up0Vote Down Roger WilcoRoger Wilco
    Posts: 784Banned
    Why not install it on a cloud server so you're not at the mercy of your local telephone and/or telegraph company? :)
  • Vote Up0Vote Down Voisses TechVoisses Tech
    Posts: 1,423Member
    @pame webradio

    Most Cloud server require you to have a US credit card or Paypal.Some even require you to have an USA address.
    So for those who will need this Lets Go.

    I do not use 2.5.2 and so all my reference is only for 2.5.1
    1. Apache in 12.04  and 14.04 are different in a number of ways but in particular like versions,webroot and virtual host.Since Airtime do not  use http as a login then change the http port you run Airtime on
    You Need to change login with admin rights ( like sudo su)
    • pico /etc/airtime/api_client.cfg
    • pico /etc/airtime/airtime.conf
    ports to whatever you like (say port 8084)

    You Need to add listen 8084
    • pico /etc/apache2/ports.conf

    You need to change the virtual host port for airtime from 80 to 8084

    pico /etc/apache2/sites-available/airtime-vhost.conf

    then

    restart apache

    /etc/init.d/apache2 restart

    then follow this troubleshoot step

    https://forum.sourcefabric.org/discussion/15654/airtime-troubleshoot-for-dummies-like-me-basic-things-you-can-do-to-see-under-the-hood

    Remember now that your login IP is

    http://urIP:8084

    the port is only for test purpose use whatever you have available.

    I never had to do RabbitMQ hostname changes becuse once I fived for the changes ads per above all works fine

    You might want to have a look at this

    http://sourcefabric.booktype.pro/airtime-25-for-broadcasters/troubleshooting/

    RabbitMQ hostname changes

    Now my Recommendation on Servers.If you have a serious production  or Radio Station,then
    • Purchase a simple instance airtime-pro* as your Main server then
    • Puchase a domain name and give your listeners that,then
    • You can Use a cloud server to host your shoutcast or icecast server or Just get some friends or family to share with you most people do not use their upload speed so you can use any small device (RPI) and either relay or as back up
    • If you do the later you have created your own mesh network

    * the cheapest is around $4 more than the cheapest VPS ,You will be getting upgrades,assisting with the community and have one of the Best Support team behind you.


    Good Luck




    Post edited by Voisses Tech at 2016-02-18 13:52:01
    Anyone reading this a find it funny about my grammar , I make no apology ,Go get a translator.
    "The Problem with education today is that it takes a university degree to switch on a light bulb"
    "You learn from your mistakes but wise people learn from others mistakes avoid Making mistakes there is not sufficient rooms to make them"
    "Innuendo","If's","Assumptions" and "Fear" are for politician.Who,What,where,When and How are for those seeking knowledge and care about Humanity.
    "I might be in Mud but that does not Make me a Wild Hog(pig)"
    “Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius — and a lot of courage to move in the opposite direction.”
    "The only thing that remains constant is change itself"
    May the force be with you,until our path or destiny bring us in tandem.
  • Vote Up0Vote Down Voisses TechVoisses Tech
    Posts: 1,423Member
    I cannot see all your Diagram but in

    1.  Airtime Uses https instead if http you need togo to the site(second option) accept the certificate
    2. donot dpkg icecast2 .As far as I know you cannot reconfigure  Icecast ,  use apt-get remove icecast2  or instead purge it sudo purge icecast2 to remove the configuration files
    3. I do not us2 2.5.2,I see too much people complain,and I will smash my computer if I cannot fix it.Lol (Anger mangement)   2.5.2 was perfectly done that all should be fixed from the interface
    4. and so on   
    Anyone reading this a find it funny about my grammar , I make no apology ,Go get a translator.
    "The Problem with education today is that it takes a university degree to switch on a light bulb"
    "You learn from your mistakes but wise people learn from others mistakes avoid Making mistakes there is not sufficient rooms to make them"
    "Innuendo","If's","Assumptions" and "Fear" are for politician.Who,What,where,When and How are for those seeking knowledge and care about Humanity.
    "I might be in Mud but that does not Make me a Wild Hog(pig)"
    “Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius — and a lot of courage to move in the opposite direction.”
    "The only thing that remains constant is change itself"
    May the force be with you,until our path or destiny bring us in tandem.
  • Vote Up0Vote Down pame webradiopame webradio
    Posts: 15Member
    Status update:

    A bit late but I've been busy getting airtime to the previous state with Library and with every day life.

    Well Airtime was working correctly when I added the NameServer xxxxxx.xxxxxxx.xxx line in the apache conf file.

    The real problem about logging to Airtime from Google Chrome, was Google Chrome itself.

    It needed to be cleaned from cookies from the beginning of time to forget older SSL cefrtificates.

    After I did this everything came back to normal.

    Thanks for all the advices. 
Add a Comment