Bug 6626 - Debian package gives error at install time
: Debian package gives error at install time
Status: CLOSED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Platform Support
: 7.0
: PC Ubuntu Linux
: P2 normal (vote)
: ---
Assigned To: Matt Wise
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-16 12:22 UTC by Patrick Dixon
Modified: 2008-12-18 11:12 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Dixon 2008-01-16 12:22:42 UTC
Ubuntu 7.04 Fiesty

I update via apt-get regularly, and today, for the first time, got this error when doing so:-

Get: 1 http://debian.slimdevices.com unstable/main squeezecenter 7.0-16329 [17.3MB]
Fetched 17.3MB in 1m6s (261kB/s)
(Reading database ... 85104 files and directories currently installed.)
Preparing to replace squeezecenter 7.0-16284 (using .../squeezecenter_7.0-16329_all.deb) ...
Stopping SqueezeCenter Audio Server.
Unpacking replacement squeezecenter ...
Setting up squeezecenter (7.0-16329) ...
chown: changing ownership of `/var/cache/squeezecenter/squeezecenter-mysql.pid': No such file or directory
dpkg: error processing squeezecenter (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
squeezecenter
E: Sub-process /usr/bin/dpkg returned an error code (1)

Squeezecenter appeared to start correctly after a sudo /etc/init.d/squeezecenter start.

Bug 6574 may be related.
Comment 1 Patrick Dixon 2008-01-16 12:27:20 UTC
Squeezecenter was already running when apt-get upgrade was run.

I subsequently ran
dpkg --configure squeezecenter

and it restarted squeezecenter and produced no errors.
Comment 2 Matt Wise 2008-01-18 09:21:51 UTC
I'm looking into it, but it doesn't appear that the error was caused by the installation, but by the startup of SqueezeCenter itself... 
Comment 3 Patrick Dixon 2008-01-18 09:41:04 UTC
I subequently had a problem where Squeezecenter & Jive became very unresponsive, the Player UI also giving me Artist -> Artist -> Artist when I right arrowed.

The log was full of these:-

[08-01-17 17:25:18.1755] Log::Log4perl::Logger::and_die (850) Warning: FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use) at /usr/share/perl5/Slim/Networking/UDP.pm line 37
2008-01-17 17:25:21 SqueezeCenter died. Restarting.
[08-01-17 17:25:26.9974] Slim::Networking::UDP::init (37) FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use)
[08-01-17 17:25:26.9979] Log::Log4perl::Logger::and_die (850) Warning: FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use) at /usr/share/perl5/Slim/Networking/UDP.pm line 37
2008-01-17 17:25:29 SqueezeCenter died. Restarting.
[08-01-17 17:25:35.0229] Slim::Networking::UDP::init (37) FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use)
[08-01-17 17:25:35.0235] Log::Log4perl::Logger::and_die (850) Warning: FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use) at /usr/share/perl5/Slim/Networking/UDP.pm line 37
2008-01-17 17:25:39 SqueezeCenter died. Restarting.
[08-01-17 17:25:44.3078] Slim::Networking::UDP::init (37) FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use)
[08-01-17 17:25:44.3083] Log::Log4perl::Logger::and_die (850) Warning: FATAL: There is already another copy of the SqueezeCenter running on this machine. (Address already in use) at /usr/share/perl5/Slim/Networking/UDP.pm line 37
2008-01-17 17:25:47 SqueezeCenter died. Restarting.

Investigation showed that two instances of squeezecenter were running:-

dixon@mediaserver:~$ sudo ps ax |grep squeeze
7649 ? Ss 0:00 /bin/bash /usr/sbin/squeezecenter_safe /usr/sbin/squeezecenter --prefsfile /etc/squeezecenter/squeezecenter.pref --logdir /var/log/squeezecenter/ --cachedir /var/cache/squeezecenter
18869 ? S 0:01 /usr/bin/perl -w /usr/sbin/squeezecenter --prefsfile /etc/squeezecenter/squeezecenter.pref --logdir /var/log/squeezecenter/ --cachedir /var/cache/squeezecenter
18871 ? Sl 0:00 /usr/sbin/mysqld --defaults-file=/var/cache/squeezecenter/my.cnf
18892 pts/0 R+ 0:00 grep squeeze
26167 ? Ss 0:00 /bin/bash /usr/sbin/squeezecenter_safe /usr/sbin/squeezecenter --prefsfile /etc/squeezecenter/squeezecenter.pref --logdir /var/log/squeezecenter/ --cachedir /var/cache/squeezecenter
26169 ? S 1:56 /usr/bin/perl -w /usr/sbin/squeezecenter --prefsfile /etc/squeezecenter/squeezecenter.pref --logdir /var/log/squeezecenter/ --cachedir /var/cache/squeezecenter

I had to kill both and restart to get things back to normal.

I'm not sure if/how this is related, but presumably the startup script didn't kill the previously running squeezecenter and the recovery restart didn't seem to resolve the issue either.
Comment 4 Mark Miksis 2008-01-18 10:09:52 UTC
(In reply to comment #2)
> I'm looking into it, but it doesn't appear that the error was caused by the
> installation, but by the startup of SqueezeCenter itself... 
> 

The error message seems to state that it is occurring during execution of the postinst script.
Comment 5 Matt Wise 2008-01-29 07:36:13 UTC
Near as I can tell, this has more to do with the last build of SqueezeCenter not dying correctly, than the new one starting up. Unfortunately the squeezecenter-mysql.pid code is burried deep in MySQLHelper.pm and I'm not 100% sure what it's doing.

I havnt seen this issue reproduced (and i've tried) -- can we close this for now and just keep an eye out for future issues? 
Comment 6 Patrick Dixon 2008-01-29 08:14:19 UTC
I haven't seen it since.
Comment 7 Matt Wise 2008-01-29 08:21:04 UTC
I think we can safely close this and call it a fluke... 
Comment 8 Chris Owens 2008-03-07 09:04:43 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.