Bug 4033 - d_scan output in log.txt
: d_scan output in log.txt
Status: RESOLVED PATCHWELCOME
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: 6.5b1
: PC Windows XP
: P2 major (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-01 09:09 UTC by Chris Owens
Modified: 2008-09-15 14:39 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 Chris Owens 2006-09-01 09:09:42 UTC
The output of d_scan that appears in log.txt is much, much more sparse than we had in 6.3.

In fact it appears to be just one line:

Setup::rescan - initiating scan of type: [wipecache]

Full log output is of course still available by running scanner.exe with the --d_scan option from the command line.
Comment 1 KDF 2006-09-01 09:43:13 UTC
I thought it was to be used on combination with other.  --d_scan --d_import shows more, --d_info, d_musicmagic and d_moodlogic should all be passed to the sacanner process.  admittedly, I'm usually doing this from command line.  maybe the logfile option isn't being passed to scanner?
Comment 2 Dan Sully 2006-09-02 16:58:12 UTC
--logfile needs to be passed. It's not right now.
Comment 3 Dan Sully 2006-09-03 15:02:45 UTC
Fixed in change 9388

Note that since http://localhost:9000/log.txt is kept in memory, it is inherently broken for logging with a multi-process application. I've added the passing of --logfile to the scanner process, but that data won't get back to the main server.

Logging is being completely rewritten for 7.0, so it will be addressed properly there.
Comment 4 Chris Owens 2006-09-03 15:07:17 UTC
Does that mean that in order for me or support to get a scanner log from a customer, we'll have to have them run it from the command line?
Comment 5 Dan Sully 2006-09-03 15:09:02 UTC
Unfortunately yes.

The only alternative I can think of is to always log to a file, and then display that log when requesting /log.txt

But there's no easy way to truncate / rotate that now, so it could grow incredibly large, both on disk, and when loading that file in a web browser.
Comment 6 Chris Owens 2006-09-03 15:11:48 UTC
FYI Kevin.  Might be a good idea to have your team familiarize themselves with running scanner.exe from the command line.
Comment 7 Chris Owens 2006-09-18 09:45:31 UTC
My workaround is as follows:

Open up a command prompt window, and type "cd \program files\slimserver\server"
to get to the right directory.  Then type "scanner --wipe --d_import --d_scan >
log.txt 2>&1" to save the output of the scanner process into a file called
log.txt.  You can of course use a different filename if you wish.

The strange "2>&1" bit on the end is necessary to also grab the output that is
sent to stderr, if you're familiar with programming.