Bug 12041 - OSX: Need method to start server with logging, without need for command line box
: OSX: Need method to start server with logging, without need for command line box
Status: RESOLVED WONTFIX
Product: Logitech Media Server
Classification: Unclassified
Component: Mac Preference Pane
: 7.4.0
: Macintosh MacOS X 10.5
: P5 trivial (vote)
: 7.6.0
Assigned To: Michael Herger
: Support-Important
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-13 15:42 UTC by Dan Evans
Modified: 2011-05-24 11:17 UTC (History)
3 users (show)

See Also:
Category: Feature


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-05-13 15:42:06 UTC
If the server starts and crashes, we don't have an easy way to capture that log.  We need one.

Unless the new button/link to the server log will display a server log even if the server crashed.  Michael?
Comment 1 Michael Herger 2009-05-13 15:47:21 UTC
What logging would you need the most?
Comment 2 Dan Evans 2009-05-13 15:58:37 UTC
This case is entirely about the server log, to gather information about what caused the crash.
Comment 3 Michael Herger 2009-05-14 00:28:18 UTC
If SC is able to log, then it does this already. Or do you have to enable  
some additional logging options to get what you want? If so: which options?
Comment 4 Dan Evans 2009-05-14 15:35:52 UTC
We don't add any flags besides "--debug server".  If that flag is already assumed in the logs, then maybe you're right and we're done?

Just so I understand:  

 * if you start the server and it runs for 30 mins and then crashes, we'll have a log of some kind.  I think that's clear.

 * if instead you start the server and it _immediately_ crashes, will we have a log to view?  This is the case where currently our only option is running via command-line and capturing that information from terminal or a DOS box.

What do you think?
Comment 5 Michael Herger 2009-05-14 22:55:26 UTC
Would it make sense to enable this logging when running SC in failsafe  
mode?
Comment 6 Dan Evans 2009-05-15 10:35:04 UTC
I think so, yes.  The goal really is to capture some log so either Support or Engineering can determine the failure.  Whatever we can do have that tool available would be ideal.

Per my question in comment #4, if it crashes immediately is the log empty?
Comment 7 Michael Herger 2009-05-15 12:27:14 UTC
> Per my question in comment #4, if it crashes immediately is the log  
> empty?

Depends why and at what exact point it crashes: if it's gone before  
logging is initialized (eg. missing/incompatible modules), then the log  
will be empty. --d_startup might help in this case.
Comment 8 Chris Owens 2009-05-20 09:23:00 UTC
Just making sure Matt is cc'ed on all of these, per his email request.
Comment 9 Michael Herger 2009-07-06 05:22:46 UTC
Starting in failsafe mode will now add logging options to detect startup failure (Windows only).

For my notes: On OSX we'll either have to extend Launcher.m or call the server-start.sh script from the PrefPane directly. We then can add the parameters needed.
Comment 10 Michael Herger 2009-07-28 06:28:48 UTC
change 27857 - add log set popup to OSX prefpane
Comment 11 Michael Herger 2009-07-28 06:35:05 UTC
Oops... wrong bug closed.
Comment 12 SVN Bot 2009-08-24 09:11:17 UTC
 == Auto-comment from SVN commit #28254 to the slim repo by michael ==
 == https://svn.slimdevices.com/slim?view=revision&revision=28254 ==

Bug: 12041 +0.5
Description: re-arrange startup options to better fit localized screens
Comment 13 Ben Klaas 2009-08-26 07:49:56 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 14 Michael Herger 2009-10-12 07:57:35 UTC
I'm sorry, applying new targeting guidelines
Comment 15 Bradley D. Wall 2011-05-24 11:17:02 UTC
lowering priority due to "wontfix"