Quantcast
Channel: Airtime Support Discussions on Sourcefabric Forum
Viewing all articles
Browse latest Browse all 1390

Liquidsoap_Process_ID - failed (trouble whit play random song)

$
0
0
Hi, all!

After upgrade 2.2.1 to 2.3.0 - 
airtime-check-system
AIRTIME_SERVER_RESPONDING      = OK
KERNEL_VERSION                 = 3.2.0-35-generic-pae
MACHINE_ARCHITECTURE           = i686
TOTAL_MEMORY_MBYTES            = 1025192
TOTAL_SWAP_MBYTES              = 0
AIRTIME_VERSION                = 2.3.0
OS                             = Ubuntu 12.04.2 LTS i686
CPU                            = AMD Athlon(tm) 64 Processor 3000+
WEB_SERVER                     = Apache/2.2.22 (Ubuntu)
PLAYOUT_ENGINE_PROCESS_ID      = 1468
PLAYOUT_ENGINE_RUNNING_SECONDS = 315
PLAYOUT_ENGINE_MEM_PERC        = 0.9%
PLAYOUT_ENGINE_CPU_PERC        = 0.0%
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/02/13 12:30:46 [threads:3] Thread "wallclock_main" terminated (1 remaining).
-- 2013/02/13 12:30:47 [threads:3] Thread "http polling" terminated (0 remaining).
-- 2013/02/13 12:30:47 [main:3] Cleaning downloaded files...
-- 2013/02/13 12:30:47 [main:3] Freeing memory...
-- 2013/02/13 12:30:47 >>> LOG END
--
--
MEDIA_MONITOR_PROCESS_ID       = 1977
MEDIA_MONITOR_RUNNING_SECONDS  = 304
MEDIA_MONITOR_MEM_PERC         = 1.2%
MEDIA_MONITOR_CPU_PERC         = 0.0%
RABBITMQ_PROCESS_ID            = 1554
RABBITMQ_RUNNING_SECONDS       = 314
RABBITMQ_MEM_PERC              = 1.5%
RABBITMQ_CPU_PERC              = 0.0%
-- There appears to be a problem with your Airtime installation.

service airtime-liquidsoap restart
Restarting Liquidsoap: ('Error loading config file: %s', error(111, 'Connection refused'))
start-stop-daemon: warning: failed to kill 8724: No such process
Done.

Icecast don't show mountpoint.
In streams setting all "ok".
In system status all components "ok", but airtime_liquidsoap have 0d 0h 0m 0s uptime.

what's wrong?

Viewing all articles
Browse latest Browse all 1390

Trending Articles