Bug 4685 - SlimServer 6.5.1 - Slimtray shows SlimServer status incorrectly
: SlimServer 6.5.1 - Slimtray shows SlimServer status incorrectly
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Slimtray
: 6.5.1
: PC Windows Vista
: P2 normal with 3 votes (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-19 13:02 UTC by Darren Lloyd
Modified: 2008-12-18 11:11 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Lloyd 2007-01-19 13:02:55 UTC
If I uninstall 6.5, reboot, install 6.5.1 on the same machine, reboot, when
the machine comes up, SlimServer is stopped (it is set to automatically
start during the installation).

I can unregister and then re-register the service successfully.

Note, the path is (C:\Program Files (x86)\SlimServer\server>).

Now if I reboot the machine, when it comes up the SlimServer taskbar icon
says "SlimServer Starting", but it never starts.

Double click on the icon, nothing happens.

Open Internet Explorer and go localhost:9000/, I get a blank page.

(C:\Program Files (x86)\SlimServer\server\slim.exe is in my Firewall Exceptions list).

If I reboot the machine, Slim Server is stopped (according the system tray icon).

If I run compmgmt.msc and look at the services, initially the SlimServer and SlimServerMySQL services are running, but after a while they both stop. (No apparent error message).

I can start the SlimServer service manually, and both services start running again.

Right click on Slim Server in the system tray, exit. Launch Slim Server again, it says it is starting and brings up the localhost:9000 page (blank).

Both of the SlimServer services in compmgmt.msc have now stopped running.......

I have no choice but to go back to using 6.5. (Which works fine).

** There is an open support ticket for this TMID:20255 **
Comment 1 Chris Owens 2007-02-06 16:51:00 UTC
Hi Darren, the support ticket you note doesn't have much information in it.

Are you working with the regular windows installer?  Or are you installing from the zip file?  Or running from activestate perl with the Slimserver tarball distribution?

I haven't been able to reproduce this yet.

Thanks for any info.
Comment 2 Darren Lloyd 2007-02-06 17:07:43 UTC
(In reply to comment #1)
> Hi Darren, the support ticket you note doesn't have much information in it.
> Are you working with the regular windows installer?  Or are you installing from
> the zip file?  Or running from activestate perl with the Slimserver tarball
> distribution?
> I haven't been able to reproduce this yet.
> Thanks for any info.

Hi Chris,

Thanks for looking into this. I used SlimServer_6.5_v2007-01-08.exe.

Comment 3 Chris Owens 2007-02-07 14:35:14 UTC
One of our support guys was telling me that he's noticed that there may be an issue with the 'slimtray.exe' program that creates the little icon in the system tray.

Darren, if you launch a command line and go to the Slimserver directory and run slim.exe directly, does it give an error message?  Does it seem to work?  If you go to the Slimserver url  (http://localhost:9000) can you get to the web interface?
Comment 4 Darren Lloyd 2007-02-07 15:42:58 UTC
(In reply to comment #3)
> One of our support guys was telling me that he's noticed that there may be an
> issue with the 'slimtray.exe' program that creates the little icon in the
> system tray.
> Darren, if you launch a command line and go to the Slimserver directory and run
> slim.exe directly, does it give an error message?  Does it seem to work?  If
> you go to the Slimserver url  (http://localhost:9000) can you get to the web
> interface?

Hi Chris,

I'll have to reinstall 6.5.1 and give it a try.

Comment 5 Darren Lloyd 2007-02-07 17:11:59 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > One of our support guys was telling me that he's noticed that there may be an
> > issue with the 'slimtray.exe' program that creates the little icon in the
> > system tray.
> > Darren, if you launch a command line and go to the Slimserver directory and run
> > slim.exe directly, does it give an error message?  Does it seem to work?  If
> > you go to the Slimserver url  (http://localhost:9000) can you get to the web
> > interface?
> Hi Chris,
> I'll have to reinstall 6.5.1 and give it a try.

OK, I uninstalled 6.5.0, rebooted and deleted the C:\Program Files (x86)\SlimServer folder.

Downloaded SlimServer_v6.5.1.exe and installed it with default options.

When I run slim.exe from the command prompt I get the following:

C:\Program Files (x86)\SlimServer\server>slim.exe
2007-02-07 17:05:43.6321 commit ineffective with AutoCommit enabled at C:\Progra
m Files (x86)\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 706.
2007-02-07 17:05:43.6331 Commmit ineffective while AutoCommit is on at C:\Progra
m Files (x86)\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 706.
2007-02-07 17:05:43.6351 ERROR: DBD::mysql::db commit failed: Commmit ineffectiv
e while AutoCommit is on at C:\Program Files (x86)\SlimServer\server\CPAN/DBIx/C
lass/Storage/DBI.pm line 706.

2007-02-07 17:05:43.6365 ERROR: Backtrace follows:

2007-02-07 17:05:43.6393 Backtrace:

   frame 0: Slim::Schema::throw_exception (/PerlApp/DBIx/Class/Schema.pm line 60
6)
   frame 1: DBIx::Class::Schema::txn_do (/PerlApp/Slim/Music/Import.pm line 241)

   frame 2: (eval) (/PerlApp/Slim/Music/Import.pm line 233)
   frame 3: Slim::Music::Import::setIsScanning (/PerlApp/Slim/Music/Import.pm li
ne 152)
   frame 4: Slim::Music::Import::launchScan (/PerlApp/Slim/Control/Commands.pm l
ine 1947)
   frame 5: Slim::Control::Commands::wipecacheCommand (/PerlApp/Slim/Control/Req
uest.pm line 1483)
   frame 6: (eval) (/PerlApp/Slim/Control/Request.pm line 1483)
   frame 7: Slim::Control::Request::execute (/PerlApp/Slim/Control/Request.pm li
ne 772)
   frame 8: Slim::Control::Request::executeRequest (slimserver.pl line 959)
   frame 9: main::checkDataSource (slimserver.pl line 418)
   frame 10: main::init (slimserver.pl line 443)
   frame 11: main::main (slimserver.pl line 58)
   frame 12: PerlSvc::Interactive (perlsvc.pl line 1486)
   frame 13: PerlSvc::_interactive (slimserver.pl line 0)
   frame 14: (eval) (slimserver.pl line 0)
Comment 6 Darren Lloyd 2007-02-08 17:34:18 UTC
I reinstalled 6.5.1 and added mysqld.exe and scanner.exe to the firewall exceptions, and that did the trick.

Note: I also had to set the SlimServer service to Automatic (Delayed Start). The SlimServerMySQL service was already running.

Anyway, 6.5.1 is now working OK.

The SlimServer Tray Tool doesn’t work (as per bug 4747), it states SlimServer is stopped when it is running. (Using http://localhost:9000 does work, so I can live without the system tray tool for now).
Comment 7 Chris Owens 2007-02-09 12:27:48 UTC
split off the slimtray issue to bug 4756.  But I'm not sure if that's the only issue here, so I'm leaving this bug open as well.
Comment 8 Chris Owens 2007-03-19 09:54:09 UTC
Ross, haven't you tested this one?
Comment 9 Ross Levine 2007-03-19 12:52:49 UTC
Yes I've verified this. Installing 6.5.1 works but SlimTray is incorrectly displaying the status of SlimServer. SlimServer does start automatically after the reboot, it just doesn't look like it's working because SlimTray reports the status as stopped. 
Comment 10 Ross Levine 2007-03-20 15:12:29 UTC
Updating the subject of this bug to more accurately reflect the bug. 
Comment 11 Ross Levine 2007-03-21 15:33:36 UTC
Assigning this to Dan. Let me know if you need anything else from QA. 
Comment 12 Chris Owens 2007-03-22 12:23:45 UTC
It would be ideal if this could go in to 6.5.2 if it's not too risky.
Comment 13 Dan Sully 2007-03-22 12:37:47 UTC
There were fixes to SlimTray that went in a few days ago for both 6.5.2 and 7
Comment 14 Ross Levine 2007-03-23 17:29:10 UTC
Verified as fixed in 6.5.2 and 7.0a1
Comment 15 Chris Owens 2007-05-22 12:10:24 UTC
Fixed in 6.5.2, which is now released and available for download at http://www.slimdevices.com/su_downloads.html

If you're still experiencing this bug, please re-open it!