My "log file" seem to expoled from time to time.

[Giraff]

I don't know why this is happing and I does not experience any change in the use of my players.
My hard drive is just full from one day to another.

When I search for the change in my system I find the log file for LMS at a size of ~15 - 20 GB!
I then delete the log file and the system continues and there can go up to 2 months before it happens again...

Maybe the is a connection with this issue but I'm not sure.
http://forums.slimdevices.com/showth...t-complete-%28

I'm running this LMS on my HP ML110 server with Windows SBS 2008.
LMS version: Logitech Media Server Version: 7.7.2 - r33893 @ Wed Mar 14 05:47:42 PDT 2012

[carp]

When I search for the change in my system I find the log file for LMS at a size of ~15 - 20 GB!
I then delete the log file and the system continues and there can go up to 2 months before it happens again...

This happens on my system (LMServer 7.7.2 - r33893 on WHS 1.x) whenever I try to play a CUE file (i.e. a CUE file that "divides" an MP3 file (e.g. one file that contains a complete live concert or a DJ mix - in both cases you so not want a break between the songs) into single songs. "Try" means: I click on "Play", then the time of the song is running, but I do not hear anything of the song. Instead, the log file is flooded with error messages and is growing very fast.

[Giraff]

Yesterday my server filled the log file again!
And it was not an CUE file playing

It was in the middle of the night so no music was playing...

I'm not at home at the moment so I have to delete the file and didn't have the time to read it.
I will read it next time. Than I hope to see what's wrong...

Dos the developer have any thing to say to this???

[Apesbrain]

I've also had this problem but not so much on recent builds. (Just checked and my largest log is just over 5MB.) At the time I solved it rather inelegantly by turning off all logging. Launch the web UI and go to Settings > Advanced > Logging and turn them all to "Off". Be sure to tick the box at the top of the page where it says "Save logging settings for use at next application restart". Even so, this doesn't always stick over time and sometimes you need to redo it. Certainly it needs to be redone after an LMS update.

Of course, if you later have a problem with the server you may need to turn them all back to "Debug". Maybe the wisest option is to set them to one of the interim settings that are not so verbose as "Debug"; someone else can hopefully advise on that.

(It would be a great time-saver if this Logging page had a switch to "Set all to XXX".)

BTW, I have to think that there is something suspicious about a log file that is growing that quickly. Maybe it is trying to tell you something is not going well? Oh, right, I just read your other thread.

[Giraff]

At the time I solved it rather inelegantly by turning off all logging. Launch the web UI and go to Settings > Advanced > Logging and turn them all to "Off". Be sure to tick the box at the top of the page where it says "Save logging settings for use at next application restart". Even so, this doesn't always stick over time and sometimes you need to redo it. Certainly it needs to be redone after an LMS update.

I didn't noteisd this option before and dame! there are many LOGGING... Maybe this is why it fill up the logfile in short time...

I will not use this option at the moment, I'v wait on till I'm home, so I can read the log file before deleting it.

Thanks for the input Apesbrain

[Mark Miksis]

At the risk of stating the obvious, the log file itself should tell you what's going on Have your tried looking at the log after this happens to see if it is filled with the same error repeating over and over?

[Giraff]

At the risk of stating the obvious, the log file itself should tell you what's going on Have your tried looking at the log after this happens to see if it is filled with the same error repeating over and over?

I now I can see lots of things in my log file, but the last tree times it got filled I was not home
Therefore I could only delete the file and the server continues.

Next time I will hope to be home and be able to look in the file

On the other hand. What should a non technical person do to this ??? Just a question...

[Mark Miksis]

On the other hand. What should a non technical person do to this ??? Just a question...

Look for whatever is filling it up. You will likely find the same message or messages repeated over and over. Post that here.

[Giraff]

I have opened a 12gb's log file with this program, "Large Text File Viewer 5.2".
http://www.swiftgear.com/ltfviewer/features.html
and thanks to that I can see whats fill up.

Here about 3 million lines into the file:
[12-10-01 00:45:03.7810] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Web::HTTP::sendStreamingResponse: Invalid frame offset 4130 for frame 0 (5869) at /<C:\PROGRA~2\Squeezebox\server\SqueezeSvr.exe>Sl im/Player/Protocols/File.pm line 250.
; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe217bf4)


Here 22 million lines into the file:
[12-10-01 02:11:36.7226] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Web::HTTP::sendStreamingResponse: Invalid frame offset 4130 for frame 0 (5869) at /<C:\PROGRA~2\Squeezebox\server\SqueezeSvr.exe>Sl im/Player/Protocols/File.pm line 250.
; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe217bf4)


Here about 32 million lines into the file:
[12-10-01 03:16:07.2078] Slim::Networking::IO::Select::__ANON__ (147) Error: Select task failed calling Slim::Web::HTTP::sendStreamingResponse: Invalid frame offset 4130 for frame 0 (5869) at /<C:\PROGRA~2\Squeezebox\server\SqueezeSvr.exe>Sl im/Player/Protocols/File.pm line 250.
; fh=Slim::Web::HTTP::ClientConn=GLOB(0xe217bf4)


The only thing changing is the time in the log file.
My thoughts about this is that is from a streaming and the streaming has not being stopped correctly. So the server tries to stream to something that does not exists any more.
Let me hear what you all have to say to this?!?