Shows not recorded after upgrade to 1.9.5
  • Hi,

    We have recently completed an upgrade of Airtime to version 1.9.5 from 1.8.2 and it is not recording shows properly. The first one recorded but the following 2 didn't. I restarted airtime-show-recorder just before the hour when the next show was due to start and it is currently recording but I am concerned that the next show will not be recorded. I've attached the show-recorder log, can anyone help with this?

    thanks

    James
  • 28 Comments sorted by
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    This file give no errors
    what said anothers airtime logs ?
    and what said airtime-update-db-settings ?
  • Hi Albert,

    thanks for your reply.

    airtime-update-db-settings has the following warning and error as shown below. How can I disable identifier quoting?

    James

    propel > pgsql-quoting-check:

         [warn] ATTENTION: It appears you are using PostgreSQL and you have identifier-quoting turned on.
         [warn] It is suggested that you disable identifier quoting when using PostgreSQL -- especially if you
         [warn] have case-sensitive columns in your database.
         [warn]
         [warn] To disable identifier quoting, add the following property to your build.properties (or specify
         [warn] it using -D on commandline):
         [warn]
         [warn] propel.disableIdentifierQuoting=true
         [warn]
         [warn] You can ignore this warning if you understand the issues related to case-sensitivity and Propel's
         [warn] DDL-only implementation of identifier quoting.

    propel > mysqli-check:


    propel > sql:

         [echo] +------------------------------------------+
         [echo] |                                          |
         [echo] | Generating SQL for YOUR Propel project!  |
         [echo] |                                          |
         [echo] +------------------------------------------+
    [phingcall] Calling Buildfile '/usr/share/airtime/library/propel/generator/build-propel.xml' with target 'sql-template'
     [property] Loading /usr/share/airtime/library/propel/generator/./default.properties

    propel > sql-template:

    Execution of target "sql-template" failed for the following reason: /usr/share/airtime/library/propel/generator/build-propel.xml:194:10: No schema files were found (matching your schema fileset definition).
    [phingcall] /usr/share/airtime/library/propel/generator/build-propel.xml:194:10: No schema files were found (matching your schema fileset definition).
    Execution of target "sql" failed for the following reason: /usr/share/airtime/library/propel/generator/build-propel.xml:179:22: Execution of the target buildfile failed. Aborting.
    [phingcall] /usr/share/airtime/library/propel/generator/build-propel.xml:179:22: Execution of the target buildfile failed. Aborting.
    Execution of target "main" failed for the following reason: /usr/share/airtime/library/propel/generator/build-propel.xml:89:22: Execution of the target buildfile failed. Aborting.
        [phing] /usr/share/airtime/library/propel/generator/build-propel.xml:89:22: Execution of the target buildfile failed. Aborting.

    BUILD FINISHED

  • Ah, I added propel.disableIdentifierQuoting=true to /usr/share/airtime/build/build.properties and ran sudo airtime-update-db-settings, but it still fails with:

    propel > sql-template:

    Execution of target "sql-template" failed for the following reason: /usr/share/airtime/library/propel/generator/build-propel.xml:194:10: No schema files were found (matching your schema fileset definition).
    [phingcall] /usr/share/airtime/library/propel/generator/build-propel.xml:194:10: No schema files were found (matching your schema fileset definition).
    Execution of target "sql" failed for the following reason: /usr/share/airtime/library/propel/generator/build-propel.xml:179:22: Execution of the target buildfile failed. Aborting.
    [phingcall] /usr/share/airtime/library/propel/generator/build-propel.xml:179:22: Execution of the target buildfile failed. Aborting.
    Execution of target "main" failed for the following reason: /usr/share/airtime/library/propel/generator/build-propel.xml:89:22: Execution of the target buildfile failed. Aborting.
        [phing] /usr/share/airtime/library/propel/generator/build-propel.xml:89:22: Execution of the target buildfile failed. Aborting.

    BUILD FINISHED


    James
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    are you using an ubuntu 10.04-3 ?

    and what said anothers logs ?

    pypo ? liquidsoap ? etc.
    Post edited by Albert FR at 2012-01-23 10:45:35
  • Yes we're using 64bit Ubuntu 10.04.3 LTS with a 2.6.32-37 kernel.

    Shows seem to be getting recorded now although at first they were silent! I had to change line 78 of /usr/lib/airtime/show-recorder/recorder.py from:

    command = "ecasound -f:%s,%s,%s -i alsa -o %s,%s000 -t:%s" % (ss, c, sr, filepath, br, length)

    to

    command = "ecasound -f:%s,%s,%s -i alsahw,0,0 -o %s,%s000 -t:%s" % (ss, c, sr, filepath, br, length)

    So it seems shows are being recorded and played out, is it safe to ignore the above error?
    I've attached all the latest logs.

    James

    317K
  • OK so the shows are still not getting recorded - does anyone have a solution for this error?

    thanks

    James
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    have you downloaded th 64bit version of airtime ???
  • I downloaded this one:

    http://sourceforge.net/projects/airtime/files/1.9.5/airtime-1.9.5.tar.gz

    I don't see a 64bit version...

  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    the 64bit version is on sourcefabric repository,
    but i can't find it anymore :(

    anyway
    working with a 64bits version (for audio applications) is not a good way :/
    that's must work, but in fact you have always problems...

    But,
    I'm looking yours logs and found somes errors...

    - mp3 created have problems :
    they are not correctly closed
    you have overrun problem

    perhaps your computer have not enought memory, or is too slow for this operation...

    you can find errors in the ls_script.log (liquidsoap log)
  • Are you referring to these lines? :

    2012/01/23 16:56:08 [alsa_out(default):3] Using ALSA 1.0.22.
    2012/01/23 16:56:08 [alsa_out(default):3] Samplefreq=44100Hz, Bufsize=15052B, Frame=4B, Periods=17
    2012/01/23 16:56:08 [alsa_out(default):2] Underrun!
    2012/01/23 16:56:08 [alsa_out(default):2] Trying to recover..

    I don't see how the liquidsoap stream generator would have an effect on the recording of shows - in fact I should be able to stop this with 'sudo airtime-playout stop' and the show-recorder daemon should still work, or I am wrong?

    The issue appears to be something to do with the schedule database and pypo pushing the information about shows to be recorded to the show-recorder daemon. Somehow 1.9.5 isn't recognising the shows in the database. New shows entered seem to record ok though. Also, clicking EDIT SHOW and then UPDATE SHOW without making any changes seems to work.

    Our computer is Intel Pentium 4 CPU 3.20GHz, 2GB RAM which exceeds the minimum specified on the sourcefabric website.

    Can anyone suggest how to solve this annoying upgrade issue?

    many thanks

    James

  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    not only this lines

     Ignoring negative cue-in point.
    2012/01/23 17:15:00 [server:3] New client: localhost
    2012/01/23 17:15:00 [queue:3] Finished with "/var/tmp/airtime/pypo/cache/scheduler/2012-01-23-17-10-00/070026ae8f9ff62948ad151991bc2895.mp3".
    2012/01/23 17:15:00 [cue_cut_4804:3] End of track before cue-out point.
    2012/01/23 17:15:00 [fallback_4842:3] Switch to mksafe with forgetful transition.


    the file created is not welle formed, anyway it can't be integrated, try to allocate more buffer to ecasound

    And how i say before, working with a 64bit version is not a sinecure ...

    today 2.0 is out, try this one too ;)
  • So I just tried updating to the latest version of Airtime, 2.0 and more problems :(

    The install fails with the following error:


    * Checking for existing Airtime installation...

    ******************************** Install Begin *********************************
    Ensuring python-virtualenv version > 1.4.8...Success!

    *** Creating Virtualenv for Airtime ***
    Running virtualenv with interpreter /usr/bin/python2.6
    New python executable in /usr/lib/airtime/airtime_virtualenv/bin/python2.6
    Also creating executable in /usr/lib/airtime/airtime_virtualenv/bin/python
    Installing distribute.................................................................................................................................................................................done.

    *** Installing Python Libraries ***
    Unpacking /home/nts-studio/airtime-2.0.0/python_apps/python-virtualenv/airtime_virtual_env.pybundle
    Downloading/unpacking configobj
      Running setup.py egg_info for package configobj
    Downloading/unpacking anyjson
      Running setup.py egg_info for package anyjson
    Downloading/unpacking mutagen
      Running setup.py egg_info for package mutagen
    Downloading/unpacking kombu
      Running setup.py egg_info for package kombu
    Downloading/unpacking amqplib
      Running setup.py egg_info for package amqplib
    Downloading/unpacking pyinotify
      Running setup.py egg_info for package pyinotify
    Downloading/unpacking poster
      Running setup.py egg_info for package poster
    Downloading/unpacking pytz
      Running setup.py egg_info for package pytz
        warning: no files found matching '*.pot' under directory 'pytz'
        warning: no previously-included files found matching 'test_zdump.py'
    Installing collected packages: amqplib, anyjson, configobj, kombu, mutagen, poster, pyinotify, pytz
      Running setup.py install for amqplib
      Running setup.py install for anyjson
      Running setup.py install for configobj
      Running setup.py install for kombu
      Running setup.py install for mutagen
        changing mode of build/scripts-2.6/moggsplit from 644 to 755
        changing mode of build/scripts-2.6/mid3iconv from 644 to 755
        changing mode of build/scripts-2.6/mutagen-pony from 644 to 755
        changing mode of build/scripts-2.6/mutagen-inspect from 644 to 755
        changing mode of build/scripts-2.6/mid3v2 from 644 to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/moggsplit to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mid3iconv to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mutagen-pony to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mutagen-inspect to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mid3v2 to 755
      Running setup.py install for poster
      Running setup.py install for pyinotify
      Running setup.py install for pytz
        warning: no files found matching '*.pot' under directory 'pytz'
        warning: no previously-included files found matching 'test_zdump.py'
    Successfully installed amqplib anyjson configobj kombu mutagen poster pyinotify pytz
    Cleaning up...

    *** Patching Python Libraries ***

       ---Applying Patches for mutagen---
    patching file /usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/mutagen/mp3.py
    Hunk #1 succeeded at 205 (offset -4 lines).
    patching file /usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/mutagen/mp3.py
    Hunk #2 succeeded at 169 (offset -4 lines).
    * Checking for user pypo
    User already exists.
    * Creating /etc/airtime
    * Creating /etc/monit/conf.d/monit-airtime-generic.cfg
    * Creating /etc/cron.d/airtime-crons
    * Creating /usr/lib/airtime
    * Creating symbolic links in /usr/bin
    * Creating /usr/share/airtime
    * Creating /var/log/airtime
    * Creating /var/tmp/airtime
    Existing config file detected at /etc/airtime/airtime.conf
    Existing config file detected at /etc/airtime/pypo.cfg
    Existing config file detected at /etc/airtime/recorder.cfg
    Existing config file detected at /etc/airtime/liquidsoap.cfg
    Existing config file detected at /etc/airtime/media-monitor.cfg

    * Creating INI files
    * Initializing INI files
    * Airtime Version: 2.0.0
    * Storage directory setup
    * Skipping directory already exists: /media/usb/airtime/stor
    * Giving Apache permission to access /media/usb/airtime/stor
    * Skipping directory already exists: /media/usb/airtime/stor/organize
    * Giving Apache permission to access /media/usb/airtime/stor/organize

    * Database Installation
     * Creating Airtime database user
      * Database user 'airtime' created.
     * Creating Airtime database
    createdb: database creation failed: ERROR:  database "airtime" already exists
      * Database 'airtime' already exists.
      * Postgres scripting language already installed

     * Setting Airtime version
    * Waiting for media-monitor processes to start...
    Stopping Airtime Media Monitor: Done.
    Starting Airtime Media Monitor: Done.
    * Detecting OS: ...  Found Ubuntu 10.04.3 LTS (lucid) on amd64 architecture
     * Installing Liquidsoap binary
    * Waiting for pypo processes to start...
     * Restarting any previous Liquidsoap instances
    * Waiting for show-recorder processes to start...
    Stopping Airtime Show Recorder: Done.
    Starting Airtime Show Recorder: Done.
    Stopping daemon monitor: monit.
    Starting daemon monitor: monit won't be started/stopped
     unless it it's configured
     please configure monit and then edit /etc/default/monit
     and set the "startup" variable to 1 in order to allow
     monit to start
    monit: service 'airtime-media-monitor' -- doesn't exist
    monit: service 'airtime-playout' -- doesn't exist
    monit: service 'airtime-liquidsoap' -- doesn't exist
    monit: service 'airtime-show-recorder' -- doesn't exist
    monit: service 'rabbitmq-server' -- doesn't exist

    *** Verifying your system environment, running airtime-check-system ***
    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = UNKNOWN
    MACHINE_ARCHITECTURE           = UNKNOWN
    TOTAL_MEMORY_MBYTES            = UNKNOWN
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = 2.0.0
    OS                             = Ubuntu 10.04.3 LTS x86_64
    CPU                            = Intel(R) Pentium(R) 4 CPU 3.20GHz
    WEB_SERVER                     = Apache/2.2.14 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = FAILED
    PLAYOUT_ENGINE_RUNNING_SECONDS = -1
    PLAYOUT_ENGINE_MEM_PERC        = 0%
    PLAYOUT_ENGINE_CPU_PERC        = 0%
    LIQUIDSOAP_PROCESS_ID          = FAILED
    LIQUIDSOAP_RUNNING_SECONDS     = -1
    LIQUIDSOAP_MEM_PERC            = 0%
    LIQUIDSOAP_CPU_PERC            = 0%
    MEDIA_MONITOR_PROCESS_ID       = FAILED
    MEDIA_MONITOR_RUNNING_SECONDS  = -1
    MEDIA_MONITOR_MEM_PERC         = 0%
    MEDIA_MONITOR_CPU_PERC         = 0%
    SHOW_RECORDER_PROCESS_ID       = FAILED
    SHOW_RECORDER_RUNNING_SECONDS  = -1
    SHOW_RECORDER_MEM_PERC         = 0%
    SHOW_RECORDER_CPU_PERC         = 0%
    RABBITMQ_PROCESS_ID            = FAILED
    RABBITMQ_RUNNING_SECONDS       = -1
    RABBITMQ_MEM_PERC              = 0%
    RABBITMQ_CPU_PERC              = 0%

    -- There appears to be a problem with your Airtime installation.

  • Also I set startup=1 in /etc/default/monit but it still fails.

  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    you have a lot of problems here :(
    open a new thread for 2.0

    thanks
  • Hi James,

    What happens when you remove all files from /etc/monit/conf.d

    and then reinstall airtime (sudo airtime-install -r)
    Airtime Pro Hosting: http://airtime.pro
  • nts-studio@nts-studio2:~$ sudo rm -rf /etc/monit/conf.d
    nts-studio@nts-studio2:~$ cd airtime-2.0.0/install_minimal/
    nts-studio@nts-studio2:~/airtime-2.0.0/install_minimal$ sudo ./airtime-install -r
    * Checking for existing Airtime installation...

    ******************************** Install Begin *********************************
    Ensuring python-virtualenv version > 1.4.8...Success!

    *** Creating Virtualenv for Airtime ***
    Running virtualenv with interpreter /usr/bin/python2.6
    New python executable in /usr/lib/airtime/airtime_virtualenv/bin/python2.6
    Also creating executable in /usr/lib/airtime/airtime_virtualenv/bin/python
    Installing distribute.................................................................................................................................................................................done.

    *** Installing Python Libraries ***
    Unpacking /home/nts-studio/airtime-2.0.0/python_apps/python-virtualenv/airtime_virtual_env.pybundle
    Downloading/unpacking configobj
      Running setup.py egg_info for package configobj
    Downloading/unpacking anyjson
      Running setup.py egg_info for package anyjson
    Downloading/unpacking mutagen
      Running setup.py egg_info for package mutagen
    Downloading/unpacking kombu
      Running setup.py egg_info for package kombu
    Downloading/unpacking amqplib
      Running setup.py egg_info for package amqplib
    Downloading/unpacking pyinotify
      Running setup.py egg_info for package pyinotify
    Downloading/unpacking poster
      Running setup.py egg_info for package poster
    Downloading/unpacking pytz
      Running setup.py egg_info for package pytz
        warning: no files found matching '*.pot' under directory 'pytz'
        warning: no previously-included files found matching 'test_zdump.py'
    Installing collected packages: amqplib, anyjson, configobj, kombu, mutagen, poster, pyinotify, pytz
      Running setup.py install for amqplib
      Running setup.py install for anyjson
      Running setup.py install for configobj
      Running setup.py install for kombu
      Running setup.py install for mutagen
        changing mode of build/scripts-2.6/moggsplit from 644 to 755
        changing mode of build/scripts-2.6/mid3iconv from 644 to 755
        changing mode of build/scripts-2.6/mutagen-pony from 644 to 755
        changing mode of build/scripts-2.6/mutagen-inspect from 644 to 755
        changing mode of build/scripts-2.6/mid3v2 from 644 to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/moggsplit to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mid3iconv to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mutagen-pony to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mutagen-inspect to 755
        changing mode of /usr/lib/airtime/airtime_virtualenv/bin/mid3v2 to 755
      Running setup.py install for poster
      Running setup.py install for pyinotify
      Running setup.py install for pytz
        warning: no files found matching '*.pot' under directory 'pytz'
        warning: no previously-included files found matching 'test_zdump.py'
    Successfully installed amqplib anyjson configobj kombu mutagen poster pyinotify pytz
    Cleaning up...

    *** Patching Python Libraries ***

       ---Applying Patches for mutagen---
    patching file /usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/mutagen/mp3.py
    Hunk #1 succeeded at 205 (offset -4 lines).
    patching file /usr/lib/airtime/airtime_virtualenv/lib/python2.6/site-packages/mutagen/mp3.py
    Hunk #2 succeeded at 169 (offset -4 lines).
    * Checking for user pypo
    User already exists.
    * Creating /etc/airtime
    * Creating /etc/monit/conf.d/monit-airtime-generic.cfg
    * Creating /etc/cron.d/airtime-crons
    * Creating /usr/lib/airtime
    * Creating symbolic links in /usr/bin
    * Creating /usr/share/airtime
    * Creating /var/log/airtime
    * Creating /var/tmp/airtime
    Existing config file detected at /etc/airtime/airtime.conf
    Existing config file detected at /etc/airtime/pypo.cfg
    Existing config file detected at /etc/airtime/recorder.cfg
    Existing config file detected at /etc/airtime/liquidsoap.cfg
    Existing config file detected at /etc/airtime/media-monitor.cfg

    You have existing config files. Do you want to (O)verwrite them, or (P)reserve them? (o/P) p
    * Airtime Version: 2.0.0
    * Storage directory setup
    * Skipping directory already exists: /media/usb/airtime/stor
    * Giving Apache permission to access /media/usb/airtime/stor
    * Skipping directory already exists: /media/usb/airtime/stor/organize
    * Giving Apache permission to access /media/usb/airtime/stor/organize

    * Database Installation
     * Creating Airtime database user
      * Database user 'airtime' created.
     * Creating Airtime database
    createdb: database creation failed: ERROR:  database "airtime" already exists
      * Database 'airtime' already exists.
      * Postgres scripting language already installed

    Database already exists. Do you want to delete all tables and recreate? (y/N)n
     * Setting Airtime version
    * Waiting for media-monitor processes to start...
    Stopping Airtime Media Monitor: Done.
    Starting Airtime Media Monitor: Done.
    * Detecting OS: ...  Found Ubuntu 10.04.3 LTS (lucid) on amd64 architecture
     * Installing Liquidsoap binary
    * Waiting for pypo processes to start...
     * Restarting any previous Liquidsoap instances
    * Waiting for show-recorder processes to start...
    Stopping Airtime Show Recorder: Done.
    Starting Airtime Show Recorder: Done.
    Stopping daemon monitor: monit.
    Starting daemon monitor: empty config, please edit /etc/monit/monitrc.
    monit: service 'airtime-media-monitor' -- doesn't exist
    monit: service 'airtime-playout' -- doesn't exist
    monit: service 'airtime-liquidsoap' -- doesn't exist
    monit: service 'airtime-show-recorder' -- doesn't exist
    monit: service 'rabbitmq-server' -- doesn't exist

    *** Verifying your system environment, running airtime-check-system ***
    AIRTIME_STATUS_URL             = http://localhost/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                = 2.0.0
    OS                             = Ubuntu 10.04.3 LTS x86_64
    CPU                            = Intel(R) Pentium(R) 4 CPU 3.20GHz
    WEB_SERVER                     = Apache/2.2.14 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = FAILED
    PLAYOUT_ENGINE_RUNNING_SECONDS = -1
    PLAYOUT_ENGINE_MEM_PERC        = 0%
    PLAYOUT_ENGINE_CPU_PERC        = 0%
    LIQUIDSOAP_PROCESS_ID          = FAILED
    LIQUIDSOAP_RUNNING_SECONDS     = -1
    LIQUIDSOAP_MEM_PERC            = 0%
    LIQUIDSOAP_CPU_PERC            = 0%
    MEDIA_MONITOR_PROCESS_ID       = FAILED
    MEDIA_MONITOR_RUNNING_SECONDS  = -1
    MEDIA_MONITOR_MEM_PERC         = 0%
    MEDIA_MONITOR_CPU_PERC         = 0%
    SHOW_RECORDER_PROCESS_ID       = FAILED
    SHOW_RECORDER_RUNNING_SECONDS  = -1
    SHOW_RECORDER_MEM_PERC         = 0%
    SHOW_RECORDER_CPU_PERC         = 0%
    RABBITMQ_PROCESS_ID            = FAILED
    RABBITMQ_RUNNING_SECONDS       = -1
    RABBITMQ_MEM_PERC              = 0%
    RABBITMQ_CPU_PERC              = 0%

    -- There appears to be a problem with your Airtime installation.

    -- Please visit http://wiki.sourcefabric.org/x/HABQ
  • Regarding the error message:

    Starting daemon monitor: empty config, please edit /etc/monit/monitrc

    I then checked cat /etc/monit/monitrc and it reveals every line to be commented out with #
    Do I need to edit this file?

    thanks

    James
  • Ok I fixed this by adding
    include /etc/monit/conf.d/*
    to /etc/monit/monitrc as detailed on the wiki page for the manual install of 1.9.x. It doesn't mention this as being necessary in the upgrade process for 1.9.x or 2.0 though - perhaps the wiki should be changed?

    sudo airtime-check-system now passes all tests and it seems to be working although I have a number of buggy web ui things going on for which I just filed a bug report.

    James
  • Hi James,

    That case is supposed to be taken care of (this only happens in Lucid), It may have something to do with the fact that your installation before was not working and caused a bug in our installer. 


    Airtime Pro Hosting: http://airtime.pro
  • Hi Martin,

    Thanks for you reply. We still can't get the upgraded version of airtime to record shows. I have upgraded to 2.0.0 and the schedule is there in the calendar view, but the shows are not getting recorded. Here is the tail of the show-recorder.log:

    nts-studio@nts-studio2:~$ tail /var/log/airtime/show-recorder/show-recorder.log
    2012-01-30 08:59:55,007 DEBUG - [recorder.py : start_record() : line 256] - sleeping 4 seconds until show
    2012-01-30 08:59:59,023 INFO - [recorder.py : record_show() : line 90] - starting record
    2012-01-30 08:59:59,023 INFO - [recorder.py : run() : line 310] - Loop #2
    2012-01-30 08:59:59,024 INFO - [recorder.py : record_show() : line 91] - command ecasound -f:16,2,44100 -i alsa -o /var/tmp/airtime/show-recorder/2012-01-30-09:00:00.ogg,192000 -t:10800.0
    2012-01-30 09:59:59,114 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 09:59:59,115 DEBUG - [recorder.py : start_record() : line 283] - No recording scheduled...
    2012-01-30 09:59:59,115 INFO - [recorder.py : run() : line 310] - Loop #3
    2012-01-30 10:59:59,194 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 10:59:59,194 DEBUG - [recorder.py : start_record() : line 283] - No recording scheduled...
    2012-01-30 10:59:59,195 INFO - [recorder.py : run() : line 310] - Loop #4<br>

    After a reboot or restarting the show-recorder daemon it usually picks up the next show, but other than that it is not working. What are all the messages saying "timed out"? Please can you advise how it is possible to upgrade to version 2.0.0 and preserve our schedule?

    thanks

    James
    Post edited by James Dunn at 2012-01-30 06:38:08
  • Hi James,

    Do you have vorbis-tools installed?
    We recently changed the default file format of recorded show to ogg format and added a new dependency package for that change.

    You can just use full install script to take care tall the dependencies or do it manually.
    http://en.flossmanuals.net/airtime-en-2-0/manual-installation/

    Thanks
  • Yes. Vorbis-tools is installed. I have tried recording to both mp3 and ogg but this is not the problem. The problem is that the show recorder daemon does not receive the shows to be recorded from the schedule after upgrading from 1.8.2. It's like it doesn't know they exist but they are there in the calendar view.

    As you can see from the log above, it says "No recording scheduled..." but there are many show scheduled to be recorded.

    This is an infuriating problem and I have attempted many upgrades which have all failed. Is there a solution or do we have to do a full install of 2.0.0 and re-enter the entire schedule AND import the archive (which is even more of a pain as they all have non-human-readable file names).

    thanks

    James
    Post edited by James Dunn at 2012-01-30 10:38:18
  • Hi James,

    From the log you provided, it looks like it's grabbing the show.

    2012-01-30 08:45:14,908 DEBUG - [recorder.py : get_time_till_next_show() : line 245] - Next show 2012-01-30 09:00:00
    2012-01-30 08:45:14,908 DEBUG - [recorder.py : get_time_till_next_show() : line 246] - Now 2012-01-30 08:45:14.908146
    2012-01-30 08:45:14,908 INFO - [recorder.py : parse_shows() : line 232] - {u'2012-01-30 09:00:00': [datetime.timedelta(0, 10800), u'2830', u'NTS Mornings with MarshmaLLo']}
    2012-01-30 08:45:14,908 INFO - [recorder.py : run() : line 304] - Bootstrap complete: got initial copy of the schedule
    2012-01-30 08:45:14,909 INFO - [recorder.py : run() : line 310] - Loop #1
    2012-01-30 08:59:55,005 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 08:59:55,006 DEBUG - [recorder.py : get_time_till_next_show() : line 245] - Next show 2012-01-30 09:00:00
    2012-01-30 08:59:55,006 DEBUG - [recorder.py : get_time_till_next_show() : line 246] - Now 2012-01-30 08:59:55.006247
    2012-01-30 08:59:55,007 DEBUG - [recorder.py : start_record() : line 256] - sleeping 4 seconds until show
    2012-01-30 08:59:59,023 INFO - [recorder.py : record_show() : line 90] - starting record
    2012-01-30 08:59:59,023 INFO - [recorder.py : run() : line 310] - Loop #2
    2012-01-30 08:59:59,024 INFO - [recorder.py : record_show() : line 91] - command ecasound -f:16,2,44100 -i alsa -o /var/tmp/airtime/show-recorder/2012-01-30-09:00:00.ogg,192000 -t:10800.0

    2012-01-30 09:59:59,114 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 09:59:59,115 DEBUG - [recorder.py : start_record() : line 283] - No recording scheduled...
    2012-01-30 09:59:59,115 INFO - [recorder.py : run() : line 310] - Loop #3
    2012-01-30 10:59:59,194 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 10:59:59,194 DEBUG - [recorder.py : start_record() : line 283] - No recording scheduled...
    2012-01-30 10:59:59,195 INFO - [recorder.py : run() : line 310] - Loop #4

    The part where it's highlighted in red, indicates that it grabbed a show schedule from the and tried to record the show. It runs 'ecasound' sound command but it's not uploading a file to airtime.

    So can you try to run the following command in the command line?

    ecasound -f:16,2,44100 -i alsa -o /var/tmp/airtime/show-recorde/2012-01-30-09:00:00.ogg,192000 -t:10800.0

    and post the output?

    Thanks

  • Yes, it recorded the file /var/tmp/airtime/show-recorder/2012-01-30-09:00:00.ogg. It will grab the next show, usually after a system reboot or with the command:

    sudo service airtime-show-recorder restart

    Or if I cancel a show and enter a new one. But where is the show scheduled for 12:00? It didn't record but it was certainly in the schedule.

    I'm attaching the latest log. When I got up this morning I checked to see if shows during the night had been recorded and they hadn't so I restarted the show-recorder daemon and it picked up the 2012-01-30-09:00:00 show. I then waited to see if the 12:00 show would record and it didn't so again I tried restarting services at 12:02pm. You can see this in the log. Upon the restart it picked up the 2012-01-30-14:00:00 show which recorded. The next show is scheduled for 18:00 but it is not in the show-recorder log yet.... (I'm betting it is not going to be recorded)

    So anyway the ecasound command works fine. If the show-recorder daemon ever issues it! But here's the output anyway:

    sudo ecasound -f:16,2,44100 -i alsa -o /var/tmp/airtime/show-recorde/2012-01-30-09:00:00.ogg,192000 -t:10800.0
    [sudo] password for nts-studio:
    **************************************************************************
    *        ecasound v2.7.0 (C) 1997-2009 Kai Vehmanen and others   
    **************************************************************************
    (eca-chainsetup-parser) Set processing time to 10800.00.
    (eca-chainsetup) Chainsetup "untitled-chainsetup"
    (eca-chainsetup) "rt" buffering mode selected.
    (audioio_alsa) Warning! Period-size differs from current client buffersize.
    (eca-chainsetup) Opened input "alsa", mode "read". Format: s16_le, channels 2, srate 44100, interleaved.
    (eca-chainsetup) Opened output "/var/tmp/airtime/show-recorde/2012-01-30-09:00:00.ogg", mode "write". Format:
    ... s16_le, channels 2, srate 44100, interleaved (locked params).
    - [ Connected chainsetup: "untitled-chainsetup" ] ------------------------
    - [ Controller/Starting batch processing ] -------------------------------
    - [ Engine - Driver start ] ----------------------------------------------
    (audioio-ogg) Starting to encode /var/tmp/airtime/show-recorde/2012-01-30-09:00:00.ogg with vorbize.
    (eca-engine) Using realtime-scheduling (SCHED_FIFO:50).

  • Here's the log

    James
    Post edited by James Dunn at 2012-01-30 12:29:21
  • Latest log - as you can see the 18:00 show didn't record:

    $ tail /var/log/airtime/show-recorder/show-recorder.log
    2012-01-30 16:00:06,414 INFO - [recorder.py : set_metadata_and_save() : line 140] - time: 14-00-00
    2012-01-30 16:00:06,782 DEBUG - [api_client.py : upload_recorded_show() : line 370] - http://localhost:80/api/upload-file/format/json/api_key/%%api_key%%
    2012-01-30 16:00:06,783 DEBUG - [api_client.py : upload_recorded_show() : line 374] - Upload attempt: 1
    2012-01-30 16:00:08,463 INFO - [api_client.py : upload_recorded_show() : line 380] - uploaded show result []
    2012-01-30 17:00:00,320 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 17:00:00,320 DEBUG - [recorder.py : start_record() : line 283] - No recording scheduled...
    2012-01-30 17:00:00,320 INFO - [recorder.py : run() : line 310] - Loop #5
    2012-01-30 18:00:00,420 INFO - [recorder.py : run() : line 315] - timed out
    2012-01-30 18:00:00,421 DEBUG - [recorder.py : start_record() : line 283] - No recording scheduled...
    2012-01-30 18:00:00,421 INFO - [recorder.py : run() : line 310] - Loop #6
    Post edited by James Dunn at 2012-01-30 15:28:47
  • Ok.

    We will look into this issue.

    Thank you.