Database Error
  • Vote Up0Vote Down VerheekVerheek
    Posts: 158Member
    Hello,

    Have been running airtime on Ubuntu Lucid for sometime.   But Airtime stopped playing out and zendphp.log is filled with these errors:

    2012-09-19T05:13:58+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] FATAL:  connection limit exceeded for non-superusers] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:00+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] FATAL:  connection limit exceeded for non-superusers] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:00+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] FATAL:  sorry, too many clients already] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:11+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:13+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:24+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] FATAL:  connection limit exceeded for non-superusers] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:26+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:28+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:28+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:28+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107
    2012-09-19T05:14:28+00:00 INFO (6): Could not connect to database: Unable to open PDO connection [wrapped: SQLSTATE[08006] [7] timeout expired] - file:/usr/share/airtime/application/models/Preference.php:107

    Airtime-check-system shows:

    AIRTIME_STATUS_URL             = http://localhost:80/api/status/format/json/api_key/%%api_key%%
    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 2.6.38-8-lowlatency
    MACHINE_ARCHITECTURE           = x86_64
    TOTAL_MEMORY_MBYTES            = 2057420
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = 2.1.3
    OS                             = Ubuntu 10.04.4 LTS x86_64
    CPU                            = Intel(R) Xeon(R) CPU           X5550  @ 2.67GHz
    WEB_SERVER                     = Apache/2.2.14 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = NOT MONITORED
    PLAYOUT_ENGINE_RUNNING_SECONDS = 1
    PLAYOUT_ENGINE_MEM_PERC        = 0%
    PLAYOUT_ENGINE_CPU_PERC        = 0%
    LIQUIDSOAP_PROCESS_ID          = NOT MONITORED
    LIQUIDSOAP_RUNNING_SECONDS     = 1
    LIQUIDSOAP_MEM_PERC            = 0%
    LIQUIDSOAP_CPU_PERC            = 0%
    MEDIA_MONITOR_PROCESS_ID       = 7521
    MEDIA_MONITOR_RUNNING_SECONDS  = 5462581
    MEDIA_MONITOR_MEM_PERC         = 0.7%
    MEDIA_MONITOR_CPU_PERC         = 0.0%
    RABBITMQ_PROCESS_ID            = 1621
    RABBITMQ_RUNNING_SECONDS       = 5462544
    RABBITMQ_MEM_PERC              = 0.4%
    RABBITMQ_CPU_PERC              = 0.0%

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

    which explains why there is no playout.

    Any ideas?


  • 10 Comments sorted by
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    try to restart monit :

    service monit restart

    and after this

    airtime-check-system
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down VerheekVerheek
    Posts: 158Member
    Tried that and it said:

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

    Not sure how it could become empty suddenly..

    Airtime-check-system:

    AIRTIME_STATUS_URL             = http://localhost:80/api/status/format/json/api_key/%%api_key%%
    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 2.6.38-8-lowlatency
    MACHINE_ARCHITECTURE           = x86_64
    TOTAL_MEMORY_MBYTES            = 2057420
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = 2.1.3
    OS                             = Ubuntu 10.04.4 LTS x86_64
    CPU                            = Intel(R) Xeon(R) CPU           X5550  @ 2.67GHz
    WEB_SERVER                     = Apache/2.2.14 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = NOT MONITORED
    PLAYOUT_ENGINE_RUNNING_SECONDS = 1
    PLAYOUT_ENGINE_MEM_PERC        = 0%
    PLAYOUT_ENGINE_CPU_PERC        = 0%
    LIQUIDSOAP_PROCESS_ID          = NOT MONITORED
    LIQUIDSOAP_RUNNING_SECONDS     = 1
    LIQUIDSOAP_MEM_PERC            = 0%
    LIQUIDSOAP_CPU_PERC            = 0%
    MEDIA_MONITOR_PROCESS_ID       = 7521
    MEDIA_MONITOR_RUNNING_SECONDS  = 5463741
    MEDIA_MONITOR_MEM_PERC         = 0.7%
    MEDIA_MONITOR_CPU_PERC         = 0.0%
    RABBITMQ_PROCESS_ID            = 1621
    RABBITMQ_RUNNING_SECONDS       = 5463704
    RABBITMQ_MEM_PERC              = 0.4%
    RABBITMQ_CPU_PERC              = 0.0%

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

    Post edited by Verheek at 2012-09-19 17:04:06
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    try this :

    dpkg-reconfigure airtime

    and press enter every time without change nothing...
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down VerheekVerheek
    Posts: 158Member
    I restarted airtime-playout and away it went.  But I wonder what happened?

  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    look at yours logs...

    /var/log/airtime
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down Bob ZurunclεBob Zurunclε
    Posts: 113Member
    I'm having the same problem running 2.3.1-1 installed via synaptic package manager

    The only thing that fixes the issue is to do a reinstall over the existing and all starts working again

    Any suggestions?

    thanks
  • Vote Up0Vote Down Bob ZurunclεBob Zurunclε
    Posts: 113Member
    We are still having this issue...

    Anyone have any suggestions?

    Thanks
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    open a console
    do an :

    sudo apt-get --purge remove airtime

    this command remove completely airtime

    and after this do an :

    sudo apt-get install airtime

    if you have errors, posts them here
    Post edited by Albert FR at 2013-05-30 05:52:48
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    a stupid question ?

    Postgresql is installed on your machine ?
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down Bob ZurunclεBob Zurunclε
    Posts: 113Member
    I think it's fixed

    The stream settings were set to use 127.0.0.1 instead of localhost

    I read in another thread that was a potential problem

    Been up for the past few days since the change with zero downtime

    Thanks
Add a Comment