Discrepency with the Library size

[lyapounov]

Hi

all my music is stored in a database, through an automatic process.

I have one table which contains all my tracks.

The number of record in this table is 146195

However, the log in Minimserver says my library contains 146194 audio files

I have carefully checked: my database and my files are in perfect sync; there is no audio file not in the database, no extra record in the database and no discrepency between filenames in database and on the hard drive.

At that level: either Mariadb is wrong on my Synology, but I doubt,

Or Minimserver's value is wrong by 1 below.

Just for info

[simoncn]

Could the missing file have a file extension that is not supported by MinimServer?

To identify the missing file, you could try the following:
1) Set the logging level to Trace
2) Do a rescan
3) From the (very very large) minimserver.log file, extract all lines containing "using cache entry for"
4) Sort these extracted lines

[lyapounov]

(22-12-2022 18:27)simoncn Wrote:  Could the missing file have a file extension that is not supported by MinimServer?

To identify the missing file, you could try the following:
1) Set the logging level to Trace
2) Do a rescan
3) From the (very very large) minimserver.log file, extract all lines containing "using cache entry for"
4) Sort these extracted lines

Hi Simon

no line contains "using cache entry for".

FYI I have only flac and dsf file in my library. As I extract all infos using the php GetID3 library, I made a SQL search on the type mime being neither audio/flac nor application/octet-stream and found no record.

So all my files are really either flac or dsf

[simoncn]

Did you set the logging level to Trace? Did you check the minimserver.log file, not the log window?

[lyapounov]

(22-12-2022 20:13)simoncn Wrote:  Did you set the logging level to Trace? Did you check the minimserver.log file, not the log window?

O well... yes but no. My apologies, Simon...

So two elements:

1) I have 170164 occurences of "using cache entry for" in the now correct log file

2) I have a crash file dating today. I have attached it; I don't know if it is relevent.

[lyapounov]

(22-12-2022 20:29)lyapounov Wrote:  

(22-12-2022 20:13)simoncn Wrote:  Did you set the logging level to Trace? Did you check the minimserver.log file, not the log window?

O well... yes but no. My apologies, Simon...

So two elements:

1) I have 170164 occurences of "using cache entry for" in the now correct log file

2) I have a crash file dating today. I have attached it; I don't know if it is relevent.

[simoncn]

The additional "using cache entry for" lines are for folders, not audio files. If you search for "processAudioItem: adding", this should give a better count but it won't be easy to identify the missing file because these trace lines only have filenames, not file paths.

Thanks for the crash log file. The crash seems to be caused by a network communication error between a web client (most likely the configuration web page) and MinimServer. Did you have the MinimWatch log window open while creating the trace log? This would put extreme stress on MinimServer and your network.

[lyapounov]

I have 146194 entries with "processAudioItem: adding" in my log file; which is coherent with your figure.

What I will do is write a program to read them, and compare with my database entry, in order to find the missing one.

I'll keep you posted

[simoncn]

Your program could look for this three-line sequence:

...... using cache entry for ......
...... processAudioItem: writing cache entry ......
...... processAudioItem: adding ......

The first of these three lines contains a full path for the file.

[lyapounov]

OK, I found the missing file by reading your log file and comparing with my database.

For some strange reason, this file had a lot of empty tags: no album tag, no track tag etc... But it was not an audio file as well; totally corrupted.

Thx Simon !!