Weeks of solid behaviour then "Off Air"
  • We have been using Airtime solidly for about 3 weeks now and have had no problems. This morning at about 5AM suddenly it suddenly went "off-air".

    I went through the possible options in the FAQ in case my timezone had mysteriously changed overnight but nothing?

    A hard reset solved the problem but I'd prefer to find out what cause the issue in the first place. I've looked though my logs (attached) and nothing appears to jump out, expect for this:

    @400000004e7677f92f9e50b4 2011/09/18 23:59:59 [fallback_4309:3] Switch to src_4307 with forgetful transition.
    @400000004e7677f92ff9d664 /usr/lib/airtime/pypo/bin/scripts/notify.sh --data='422' --media-id=
    @400000004e7677f93330d5e4 
    @400000004e7677f93330d9cc #########################################
    @400000004e7677f93330d9cc #           *** pypo  ***               #
    @400000004e7677f93330ddb4 #     pypo notification gateway         #
    @400000004e7677f93330ddb4 #########################################
    @400000004e7677f93330ddb4 NOTICE: 'media_id' command-line argument not given.
    @400000004e767f7627ce549c 2011/09/19 00:31:56 [server:3] New client: localhost
    @400000004e768d863b907b54 2011/09/19 01:31:56 [server:3] New client: localhost
    @400000004e769bb20fc12a3c 2011/09/19 02:32:24 [server:3] New client: localhost
    @400000004e76a9de276f9e84 2011/09/19 03:32:52 [server:3] New client: localhost
    @400000004e76b80b21280b74 2011/09/19 04:33:21 [server:3] New client: localhost
    @400000004e76c61b395fef54 2011/09/19 05:33:21 [server:3] New client: localhost
    @400000004e76d4471e520814 2011/09/19 06:33:49 [server:3] New client: localhost
    @400000004e76e2741f787ee4 2011/09/19 07:34:18 [server:3] New client: localhost
    @400000004e76f0a1016fc27c 2011/09/19 08:34:47 [server:3] New client:localhost
    @400000004e76fec51d249c04 2011/09/19 09:35:07 [server:3] New client: localhost



    How can I diagnose this problem? The current playlist is about 12 hours long so any problematic files would of been skipped now. Any clues?

    I'm using 1.8.2.

    regards,

    Chris Weaver
  • 8 Comments sorted by
  • Vote Up0Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    looks like show scheduler is empty

    Could you check server timezone and on admin part? It should be same. May be something changed system time...

    btw, v1.9.4 can resume show playing right after service restart.

  • That's what I thought but there was no difference between Airtime and the
    system clock. There is better post on the forum with my logs attached:

    http://forum.sourcefabric.org/index.php/t/3977/

    We have had some other "odd" behaviour with certain playlists not triggering
    but I haven't experienced it myself (the engineers here reported it once or
    twice).

    - Chris





    On 19 September 2011 11:24, Andrey Podshivalov <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > looks like show scheduler is empty
    >
    > Could you check server timezone and on admin part? It should be same. May
    > be something changed system time...
    >
    > btw, v1.9.4 can resume show playing right after service restart.
    >
    >
    >



    --



    Chris Weaver
    Production Manager
    Resonance104.4FM
    resonancefm.com
    +44 (0)207 407 1210

  • Vote Up0Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    ok, open in browser the link http://**airtime_instance/api/schedule/api_key/**insert_here _key

    the key is available in /etc/airtime/airtime.conf

    You should see a scheduled show with tracks. You can post an output here.

  • I wished I done that earlier as I needed the system for the first broadcast
    show. It's only show the current programme (which is working).

    What are you looking for in this log?





    On 19 September 2011 12:02, Andrey Podshivalov <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > ok, open in browser the link http://**airtime_instance/api/schedule/api_key/**insert_here
    > _key < http://**airtime_instance/api/schedule/api_key/**insert_here _key>
    >
    > the key is available in /etc/airtime/airtime.conf
    >
    > You should see a scheduled show with tracks. You can post an output here.
    >
    >
    >



    --



    Chris Weaver
    Production Manager
    Resonance104.4FM
    resonancefm.com
    +44 (0)207 407 1210

  • Vote Up0Vote Down Andrey PodshivalovAndrey Podshivalov
    Posts: 1,526Member, Administrator, Sourcefabric Team
    just to make sure that scheduler is not empty
  • Hi Chris,

    I took a look at the pypo.log, but it only goes back to 9am in the morning. Do you have anymore files in /var/log/airtime/pypo?

    The logs rotate to a new file after the current log reaches 1MB I believe.

    The liquidsoap log file looks fine.
    Airtime Pro Hosting: http://airtime.pro
  • In /var/log/airtime/pypo/main are the following:


    @400000004e77119a0d646dbc.s @400000004e77265931e7df0c.s
    @400000004e7712061a7ad4dc.u @400000004e772b3c18f57144.s
    @400000004e7712751c13e784.s @400000004e774c60380f2c64.s
    @400000004e7715660aa8ff0c.s current
    @400000004e771e4536697374.s lock
    @400000004e771eed02d1c37c.s state

    Are they additional log files?



    On 19 September 2011 14:54, Martin Konecny <
    airtime-support@lists.sourcefabric.org> wrote:

    > **
    > Hi Chris,
    >
    > I took a look at the pypo.log, but it only goes back to 9am in the morning.
    > Do you have anymore files in /var/log/airtime/pypo?
    >
    > The logs rotate to a new file after the current log reaches 1MB I believe.
    >
    > The liquidsoap log file looks fine.
    >



    --



    Chris Weaver
    Production Manager
    Resonance104.4FM
    resonancefm.com
    +44 (0)207 407 1210

  • As luck (well you can call it that) would have it, we had another "silent" programme today at 13:00. I have copied the directory /var/log/airtime and what was displayed by entering serveraddress.com/api/schedule/api_key. So you can see exactly what was meant to be playing I have attached a screenshot as well.

    I hope we can get to the bottom of this!