We see your posts. Posting 3 or 4 times here and elsewhere won't get you to a solution any quicker... please give the community time to respond, it's a weekend after all. :)
As ever, screenshots and logs help people to help you troubleshoot.
subprocess installed post-installation script returned error exit status 1
Processing triggers for python-support ...
Errors were encountered while processing:
airtime
E: Sub-process /usr/bin/dpkg returned an error code (1)
The schedule looks to work, icecast is not connected, the on air light is off.
I restarted all services step by step but when I type invoke-rc.d airtime-playout the result is Restarting Airtime Playout: start-stop-daemon: warning: failed to kill 3301: No such process
I tried all you said in the previous post but... nothing... please help urgently
@Kalim: Around what time did you have problem with On Air light? Is server time and your airtime time in the same time zone? if not what are the timezone?
@Radio-Libriamoci Web: Can you please post log files?
I just solved the problem the day before tomorrow with Martin's Help and within just next hours less than 24 hrs i got the prblem again seems around 12 - 1 PM today
Server time zone is ar_EG.utf-8 and Airtime time zone is EET
Actually if you have a look at my playout log posted in the previous post you'll see that the local default were uncorrect. I fixed it following the steps you suggested and checked the time zones to ensure they're aligned and they are.
Now Airtime is working correctly since more than 2 hours and i'm monitoring it. The playout log do not highlight any issue at this time but let's monitor.
Looking forward a feedback from James, it would be great if other users would share their experience upgrading.
The server time and Airtime time timezone doesn't need to be same. The problem you guys are having is something else. We found this bug in pypo and I'm suspecting that is the root causes of your problem.
Were you guys not scheduling/modifying anything related schedule for more than a hour? and Airtime went off line?
James, Airtime went offline yesterday night just after the upgrade. Early today, after the locales adjustement end the reboot it started and never went offline anymore. One hour later I added couple of file and updated some show. Any other test to be performed?
here attached the last playout log. it looks actually strange (I'm not an expert LOL)
That log doesn't tell me much :(. If it happens again, please try to modify schedule(eg, adding/deleting/editing shows or files from now playing page... anything schedule related.) and see if that will make pypo going?
James this is the pypo log as was few minutes ago root@rlwebradio:~# less +G /var/log/airtime/pypo/pypo.log 3 to local cache /var/tmp/airtime/pypo/cache/scheduler/1234d07462ed9d0a52881e0d293154b7.mp3 2012-06-13 19:42:20,773 DEBUG - [api_client.py : notify_media_item_start_playing() : line 291] - http://localhost:80/api/notify-media-item-start-play/api_key/%%api_key%%/media_id/96709/schedule_id/0 2012-06-13 19:42:20,893 INFO - [api_client.py : notify_media_item_start_playing() : line 296] - API-Status 1 2012-06-13 19:42:20,893 INFO - [api_client.py : notify_media_item_start_playing() : line 297] - API-Message 2012-06-13 19:46:16,618 DEBUG - [api_client.py : notify_media_item_start_playing() : line 291] - http://localhost:80/api/notify-media-item-start-play/api_key/%%api_key%%/media_id/96710/schedule_id/0 2012-06-13 19:46:18,025 INFO - [api_client.py : notify_media_item_start_playing() : line 296] - API-Status 1 2012-06-13 19:46:18,026 INFO - [api_client.py : notify_media_item_start_playing() : line 297] - API-Message 2012-06-13 19:46:18,437 DEBUG - [api_client.py : notify_media_item_start_playing() : line 291] - http://localhost:80/api/notify-media-item-start-play/api_key/%%api_key%%/media_id/96711/schedule_id/0 2012-06-13 19:46:19,206 INFO - [api_client.py : notify_media_item_start_playing() : line 296] - API-Status 1 2012-06-13 19:46:19,207 INFO - [api_client.py : notify_media_item_start_playing() : line 297] - API-Message ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ (END)
I just rebooted: in the nowplaying view the indication of what's on air was uncorrect, one track late. Now it looks to work correctly but for sure we'll face similar issues in the next hours
Karim your should upgrade mainly to fix the issues we both faced in the last couple of days. Do it and post your feedback here please. I fixed and if you fix too it will be the confirmation of the patch working correctly.
I've looked over your logs and it appears files are being push to Liquidsoap and played at regular intervals. I can see as recently as 20:06:13 EET time (the time it appears these logs were created) that the following track began to play: