I just leave the 3 repository and do an apt-get update...

root@s15437562:/etc/apt# apt-get update
Hit http://update.onlinehome-server.info lucid Release.gpg
Hit http://update.onlinehome-server.info lucid-updates Release.gpg
Hit http://update.onlinehome-server.info lucid-security Release.gpg
Hit http://update.onlinehome-server.info lucid Release
Hit http://update.onlinehome-server.info lucid-updates Release
Hit http://update.onlinehome-server.info lucid-security Release
Hit http://update.onlinehome-server.info lucid/main Packages
Hit http://update.onlinehome-server.info lucid/restricted Packages
Hit http://update.onlinehome-server.info lucid/universe Packages
Hit http://update.onlinehome-server.info lucid-updates/main Packages
Hit http://update.onlinehome-server.info lucid-updates/restricted Packages
Hit http://update.onlinehome-server.info lucid-updates/universe Packages
Hit http://update.onlinehome-server.info lucid-security/main Packages
Hit http://update.onlinehome-server.info lucid-security/restricted Packages
Hit http://update.onlinehome-server.info lucid-security/universe Packages
Reading package lists... Done
root@s15437562:/etc/apt# apt-get install lame
Reading package lists... Done
Building dependency tree
Reading state information... Done
lame is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.

~# apt-get install libmp3lame0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libmp3lame0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package libmp3lame0 has no installation candidate

Hi Martin,

apparently, the repository doesn't contain libmp3lame-dev


apt-get install libmp3lame-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package libmp3lame-dev

Nicolas,

I tried recreating your problem on Ubuntu 10.04 64 bit server and couldn't. As Andrey said your /etc/apt/sources.list is a little messy, I'm not sure why you have references to Ubuntu 8.04 (Hardy Heron) in there, but this is definitely messing things up.

I'm providing a sample sources.list file, you should edit yours to to make sure you have all repositories available to you. Make sure you backup your sources.list somewhere safe first.

I decided to upgrade to 1.61 and am running into the same problem. Did the same setup as always, timezones are correct
mount point is okay and shown on my icecast server but the only thing playing is the airtime - offline stream. In currently playing the items are shown but the on air button is gray ( good to have an offline function now, now i need the on air button )


update : Fixed by apt-get install libmp3lame-dev Somehow that file was missing or outdated.

Radio A6

Hi Verheek -
Looks like you are using the GIT version of Airtime. It is undergoing
development at the moment and is not stable. We suggest you stick with
1.6.1.

- Paul




On Tue, Mar 15, 2011 at 1:48 PM, Verheek <
airtime-support@lists.sourcefabric.org> wrote:

> Mid-song Airtime went from on air to off. The interface carried on but
> my playback is says offline.
>
> I had just started a 40 min schedule of songs I have played before.
>
> I have an up-to-date lucid and git pull of Airtime. I had just re-installed
> it.
>
> Here is the last bit of pypo-push. The problem started around 13:31:xx.
> Playout started at 13:20:00.
>
> Quote:
>
> @400000004d7f9fca0a6de624 2011-03-15 13:20:00,174 DEBUG - [pypopush.py :
> push() : line 102] - Doing callback to server to update 'played' status.
> @400000004d7f9fca0a7106ec 2011-03-15 13:20:00,175 DEBUG - [api_client.py :
> notify_scheduled_item_start_playing() : line 270] - http://localhost/api/notify-schedule-group-play/api_key/%%ap
> i_key%%/schedule_id/1
> @400000004d7f9fca1148b0b4 2011-03-15 13:20:00,289 INFO - [api_client.py :
> notify_scheduled_item_start_playing() : line 276] - API-Status 1
> @400000004d7f9fca1148b49c 2011-03-15 13:20:00,289 INFO - [api_client.py :
> notify_scheduled_item_start_playing() : line 277] - API-Message
> @400000004d7fa0401f3a126c 2011-03-15 13:21:58,523 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa0b91d2d4e94 2011-03-15 13:23:59,489 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa13223e45cb4 2011-03-15 13:26:00,602 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa18514c6a82c 2011-03-15 13:27:23,348 ERROR - [pypopush.py :
> load_schedule() : line 204] -
> @400000004d7fa185158badac 2011-03-15 13:27:23,361 WARNING - [pypopush.py :
> push() : line 69] - Unable to loop schedule - maybe write in progress?
> @400000004d7fa185158db91c 2011-03-15 13:27:23,361 WARNING - [pypopush.py :
> push() : line 70] - Will try again in next loop.
> @400000004d7fa1ab2b6e00fc 2011-03-15 13:28:01,728 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa22434184fb4 2011-03-15 13:30:02,873 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa239029bdab4 2011-03-15 13:30:23,043 ERROR - [pypopush.py :
> load_schedule() : line 204] -
> @400000004d7fa23902b0ca14 2011-03-15 13:30:23,045 WARNING - [pypopush.py :
> push() : line 69] - Unable to loop schedule - maybe write in progress?
> @400000004d7fa23902b37d7c 2011-03-15 13:30:23,045 WARNING - [pypopush.py :
> push() : line 70] - Will try again in next loop.
> @400000004d7fa29e012af534 2011-03-15 13:32:04,019 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa31306dd416c 2011-03-15 13:34:01,115 ERROR - [pypopush.py :
> load_schedule() : line 204] -
> @400000004d7fa31306f34624 2011-03-15 13:34:01,116 WARNING - [pypopush.py :
> push() : line 69] - Unable to loop schedule - maybe write in progress?
> @400000004d7fa31306f5a784 2011-03-15 13:34:01,116 WARNING - [pypopush.py :
> push() : line 70] - Will try again in next loop.
> @400000004d7fa317096403bc 2011-03-15 13:34:05,157 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa3901240727c 2011-03-15 13:36:06,306 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa40919a57bac 2011-03-15 13:38:07,430 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa462101418b4 2011-03-15 13:39:36,269 ERROR - [pypopush.py :
> load_schedule() : line 204] - invalid literal for long() with base 10: ''
> @400000004d7fa46210288efc 2011-03-15 13:39:36,271 WARNING - [pypopush.py :
> push() : line 69] - Unable to loop schedule - maybe write in progress?
> @400000004d7fa462102a9a6c 2011-03-15 13:39:36,271 WARNING - [pypopush.py :
> push() : line 70] - Will try again in next loop.
> @400000004d7fa48222625094 2011-03-15 13:40:08,576 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
> @400000004d7fa4fb2cd414f4 2011-03-15 13:42:09,751 INFO - [pypo-cli.py :
> <module>() : line 168] - heartbeat
>
>
>
> Also, would it be possible to have a re-cue button to cause pypo to
> re-fetch the last song and jump into the correct time position?
>
> Jeremy
>

Did you try this solution already?:
http://forum.sourcefabric.org/index.php/mv/msg/3404/9637/#ms g_9637



On Tue, Mar 15, 2011 at 3:05 PM, Verheek <
airtime-support@lists.sourcefabric.org> wrote:

> Thanks Paul.
>
> I went back to a fresh copy of 1.6.1 per the install page and a couple
> minutes into the first song it went off air again.
>
> Jeremy
>

The latest 1.7.0 Airtime git revision should solve the going offline issue.