Logfile in 7.6

[mr_hyde]

Hello,

I am not sure if this is the right part of the forum. But since I was not able to find this somwhere else, I decided to go for the general discussion.

I have installed 7.6 on a X86 based QNAP NAS. SbS is running through SSOTS4 and I have not changed anything after installing 7.6. It seems to be that SbS is logging every warning. This was not the case with all earlier SbS versions. In SbS I have set all logging to "on failure", but this did not help. I have added nodebuglog and noinfolog to the startup of SbS, but this resultd also in no change of the behavior.

Does somebody else observe the same behavior, or is this only on the SSOTS based system?

Is there some other "switch" to turn the logging off?

Other than that, I was not able to find serious issues with 7.6.

Thanks
Mr_Hyde

[erland]

Could you give an example of log messages you see in the log which you would like not to be logged ?

[mr_hyde]

Hi erland,

thanks for your response.

Please find attached (log1.zip)a part of the zip file. It can grow up to 7 MB per day.

in Log2.txt you will find another part of the logfile with the start options of SbS.

At that time I have modified slimserver.pl slightly and "disabled" logging in the source code. I know, that this is not the correct way but it works for now.

On this NAS, SbS is set to use its own perl modules. Consequently it uses the log4perl which is in the CPAN. Have not tried the other one whih is in SSOTS.

[code]
sub initLogging {
# open the log files
# Slim::Utils::Log->init({
# 'logconf' => $logconf,
# 'logdir' => $logdir,
# 'logfile' => $logfile,
# 'logtype' => 'server',
# 'debug' => $debug,
# });
}
[\code]

[bobertuk]

Hi erland,

thanks for your response.

Please find attached (log1.zip)a part of the zip file. It can grow up to 7 MB per day.

in Log2.txt you will find another part of the logfile with the start options of SbS.

At that time I have modified slimserver.pl slightly and "disabled" logging in the source code. I know, that this is not the correct way but it works for now.

On this NAS, SbS is set to use its own perl modules. Consequently it uses the log4perl which is in the CPAN. Have not tried the other one whih is in SSOTS.

[code]
sub initLogging {
# open the log files
# Slim::Utils::Log->init({
# 'logconf' => $logconf,
# 'logdir' => $logdir,
# 'logfile' => $logfile,
# 'logtype' => 'server',
# 'debug' => $debug,
# });
}
[\code]

Hi mr_hyde,

I took a look at your log file and I get exactly the same type of output. Trying to set log settings to 'Off' doesn't work for me either.

Bob

[JJZolx]

I have a feeling that stuff may have been added to logging by whoever ports SBS to the QNAP. He probably forgot to disable it.

[mr_hyde]

I have a feeling that stuff may have been added to logging by whoever ports SBS to the QNAP. He probably forgot to disable it.

On the one hand I have the same feeling. On the other hand I do not understand, why I can't observe this with all older versions of SbS (e.g. 7.5.4, 7.5.5)

[JJZolx]

On the one hand I have the same feeling. On the other hand I do not understand, why I can't observe this with all older versions of SbS (e.g. 7.5.4, 7.5.5)

He may have had trouble specifically with getting 7.6 to work, added the additional statements, but neglected to remove them before making the package available.

[mr_hyde]

He may have had trouble specifically with getting 7.6 to work, added the additional statements, but neglected to remove them before making the package available.

ok, I will bring this up in the corresponding QNAP forum.

However, I will try one more thing. As I mentioned, the package is configured to use the SbS CPAN modules. I will try to use at least the log4perl module from the QNAP package. Maybe this has an impact.

[mr_hyde]

Just an update.

I tried to use the log4perl module that has been provided with SSOTS -> no change of the behavior.

Modified the last lines file Log.pm in ../Slim/Utils:

sub PRINT {
        my $self = shift;

#       $Log::Log4perl::caller_depth++;

#       Slim::Utils::Log::logger('')->error("Warning: ", @_);

#       $Log::Log4perl::caller_depth--;
}

This stopped at least the logging of all warnings. I know that this is not the solution, but it helps at least until the problem is fixed.

I compared also the code of the corresponding 7.5.5 package and was not able to find a difference for these parts. What could impact this behavior? Settings through compilation of PERL? However, when I install the 7.5.5 version of SbS under the same system, the behavior is different. And I use the official SbS packages from logitech.

[mherger]

I have a feeling that stuff may have been added to logging by whoever ports SBS to the QNAP. He probably forgot to disable it.

Not sure, rather looks like the SugarCube plugin causing endless errors and warnings due to undefined variables.

[mr_hyde]

Hi Michael,

thanks for the repsonse.


I would assume that was a part, where i played music. However, there are also parts when you receive similar results for MusicinfoSCR, Custombrowse or just from standard functions.

[mr_hyde]

Hey, I have found the problem.

The current SSOTS scripts modify slimserver.pl and scanner.pl by adding a -w flag to the interpreter settings. This causes all the warnings in the logfile.

#!/opt/ssods4/bin/perl -w

Not sure why this had no negative effect in SbS < 7.6 since this flag was "always" in the startup script.

The startup script will be modified. See here:

http://forum.qnap.com/viewtopic.php?f=123&t=41264&p=215693#p215691

[mr_hyde]

Found several entries in the Logfile

0144: [11-08-08 18:02:43.2080] Slim::Utils::Scanner::scanDirectory (318) Found 1 files in /share/Music/Various/Bananarama/Bananarama/01 - Cruel Summer.mp3
0143: [11-08-08 17:58:38.8435] Slim::Utils::Scanner::scanDirectory (318) Found 1 files in /share/Music/Peter Fox/Stadtaffe/03 - Haus Am See.mp3
0142: [11-08-08 17:54:39.9229] Slim::Utils::Scanner::scanDirectory (318) Found 1 files in /share/Music/Various/Aloe Blacc/Good Things [Album]/Aloe Blacc - I Need A Dollar.mp3

The scanner log is set to error. However, this message sounds more like an info. The scanner.pm file has the following code

$log->error( sprintf( "Found %d files in %s\n", scalar @{$files}, $topDir ) );

It reports the fact that it has found a file obviously as error. Is this correct or should this be changed to info? There is at least another line in scanner.pm, where it reports "Scanning: $file" as error.

SbS Version: 7.6.1 33011 but I have seen this also earlier.