Jaikoz- Discussion Forum

Anonymous wrote:

paultaylor wrote:

Anonymous wrote:

Has there been any progress on this issue? It's been about a month since I first posted.

i havent forgotten but OpenSuse is not officially supported so i must admit it has not been top priority. I have been trying to use Innotek VirtualBox to get a working Suse installation, but without success.

have the same problem with "this track cannot be analysed" on Suse 10.2 any help to fix it? Using full licence 1.9.4, it's a issue of priviliges?

I can let you test it on mine server if you can't install virtual machine and get OpenSuse if you are interested. let me know at thedop@gmail.com

I wrote it

I see this issue, too.
This is under Gentoo Linux with all latest updates and Sun's VM 1.5.0_11.

Examples: Code:

 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.41.12:WARNING: Unable to create Puid for:29:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.45.07:WARNING: Unable to create Puid for:95:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.45.56:WARNING: Unable to create Puid for:112:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.46.32:WARNING: Unable to create Puid for:127:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.46.45:WARNING: Unable to create Puid for:132:null
 [Fatal Error] :-1:-1: Premature end of file.

I have uploaded all log files (userlog, debuglog and part of the console output) here.

Ok, so this problem has happened on three occasions nows, and always with Linux, I haven't managed to replicate it myself.

Can you clarify for me is this happening consistently for the same files. For example in the debug log where it says Unable to create Puid for:132, the 132 refers to the 133nd file (because records are labelled from zero) in the list when sorted by record number. So if this problem occurs again after identifying the record you could right click on it s record header and just select 'Remote Correct/Correct Acoustic Ids' to retry this one file.

If it does reoccur could you send me the file and/or try against Windows or OSX to see if the problem persists.

Another thing that might be useful would be if you increased the logging output but this will slow down jaikoz so you only really want to do it for when running a test , not all the time. You can increase the logging by using the jaikoz.sh shell script and editing the value -l2 in jaikoz.sh to -l7.

paultaylor wrote:

[...]
Can you clarify for me is this happening consistently for the same files. For example in the debug log where it says Unable to create Puid for:132, the 132 refers to the 133nd file (because records are labelled from zero) in the list when sorted by record number. So if this problem occurs again after identifying the record you could right click on it s record header and just select 'Remote Correct/Correct Acoustic Ids' to retry this one file.
[...]

(The list in the GUI of Jaikoz also starts from 0.)
What I did was first analyse a directory of 517 files with genpuid (all files at once). I saved the output in a file. Then I opened the same directory in Jaikoz, started the acoustic analysis, and waited until 2 songs had shown the error. Then I cancelled the operation, and retried acoustic analysis on them separately. This did work. The PUID for these songs was also present in the saved output of genpuid itself.

Then I closed Jaikoz (without saving anything), reopened it, and did everything exactly the same. There were errors again, but this time on different files! The files that gave errors the first time, had no problem this time. Again right-clicking and analyzing only that file gave no problems. The files that had errors this time also didn't give any error with genpuid.

It is possible that these files are corrupt, but even that can't explain why it doesn't always hang on the same files. What I am wondering about is the error format:
Code:

 [Fatal Error] :-1:-1: Premature end of file.
 23/06/2007 01.06.15:WARNING: Unable to create Puid for:11:null

What programs generate these? The first one doesn't seem like your log format. [edit]I found out it's an error from your XML parser. So probably the output received from genpuid isn't up to par all the time...[/edit] The second one states the list number (so probably from your program) and then 'null'. Where do you print this message? What should follow the list number? Seems like that parameter isn't initialized...

I'll retry this with more debug output later...
I'm also going to try redoing the entire directory with genpuid, seeing if it also sometimes fails on different files.

Nocturnal wrote:

What I am wondering about is the error format:
Code:
 [Fatal Error] :-1:-1: Premature end of file.
 23/06/2007 01.06.15:WARNING: Unable to create Puid for:11:null
 
What programs generate these? The first one doesn't seem like your log format. [edit]I found out it's an error from your XML parser. So probably the output received from genpuid isn't up to par all the time...[/edit] The second one states the list number (so probably from your program) and then 'null'. Where do you print this message? What should follow the list number? Seems like that parameter isn't initialized...

I'll retry this with more debug output later...
I'm also going to try redoing the entire directory with genpuid, seeing if it also sometimes fails on different files.

Thankyou for taking the time to look at this, it appears that the problem is not file related but related to the interaction between Jaikoz and Genpuid.

This lines comes from jaikoz:
23/06/2007 01.06.15:WARNING: Unable to create Puid for:11:null
The null is because there is an exception but it has no error message, it is not because something is not inilitized.

I dont know where
[Fatal Error] :-1:-1: Premature end of file.
is coming from but I guess it is coming from genpuid in some way. Ive just reread your message how do you its from the xmlparser, thats interesting.
Yes please try with more debugging, this may give the extra information I need to fix this.

paultaylor wrote:

I dont know where
[Fatal Error] :-1:-1: Premature end of file.
is coming from but I guess it is coming from genpuid in some way. Ive just reread your message how do you its from the xmlparser, thats interesting.

When you look it up on Google, the first result shows the exact same error message, coming from the Java SAX XML parser. No doubt you also use some kind of Java XML parser on the output of genpuid...

"Premature end of file" would probably refer to the XML data you feed (from genpuid) into the parser, so the problem is probably either the XML returned by genpuid, or the variable you use to store it in (maybe it doesn't get reset properly after every run?)...

BTW, I see this issue on Windows, as well, just not as frequently.

That is important to know, Im reviewing the code BTW are your machines multiple cpus.

Nocturnal wrote:

maybe it doesn't get reset properly after every run...

That isnt the issue, but I have found something else that maybe causing the problem, a debug log showing the problem occurring would be useful if you have a chance.

paultaylor wrote:

Nocturnal wrote:

maybe it doesn't get reset properly after every run...

That isnt the issue, but I have found something else that maybe causing the problem, a debug log showing the problem occurring would be useful if you have a chance.

That's good news!

I don't have a debug log yet. I'm running a session of 22 000+ files now, already going 20+ hours, I really didn't want to slow that down or risk a hang with that many files

. The error only occured 25 times in 10 000 files so it really is a rare bug. I don't actually have multiple CPU's, but I do have Hyperthreading activated, which the OS (both Windows and Linux) will treat as if they were 2 CPU's. I do have some more output (different error messages but I'm pretty sure they're caused by the same problem):
Code:

[Fatal Error] :1:1: Content is not allowed in prolog.
 24/06/2007 19.46.35:WARNING: Unable to create Puid for:2556:null
 [Fatal Error] :1:20: XML document structures must start and end within the same entity.
 24/06/2007 19.55.24:WARNING: Unable to create Puid for:2997:null
 [Fatal Error] :-1:-1: Premature end of file.
 24/06/2007 19.57.38:WARNING: Unable to create Puid for:3132:null
 [Fatal Error] :-1:-1: Premature end of file.
 24/06/2007 19.57.49:WARNING: Unable to create Puid for:3135:null
 [Fatal Error] :1:20: XML document structures must start and end within the same entity.
 24/06/2007 19.57.56:WARNING: Unable to create Puid for:3136:null
 [Fatal Error] :-1:-1: Premature end of file.
 24/06/2007 20.04.30:WARNING: Unable to create Puid for:3505:null
 [Fatal Error] :1:20: XML document structures must start and end within the same entity.
 24/06/2007 20.08.34:WARNING: Unable to create Puid for:3741:null
 [Fatal Error] :-1:-1: Premature end of file.

This shows that it's really a problem with recording of the output of genpuid. Since I doubt the problem is in the output itself, it might be caused by processing the output before it's entirely finished (i.e. it still has to write "npuid>" or something)?

If you need me to beta-test a possible bugfix, let me know.

Nocturnal wrote:

Since I doubt the problem is in the output itself, it might be caused by processing the output before it's entirely finished (i.e. it still has to write "npuid>" or something)?

If you need me to beta-test a possible bugfix, let me know.

Yes I think there is a possibility of reading before output has completed, which would be more likely on a multi-threaded system, I may ask you to beat test sometime this week, thanks.

I believe this is now fixed in Jaikoz 1.10 please let me know

I'm running Suse 10.1 and Jaikoz 1.10 and I'm having this error for every file. 1.10 did not resolve this issue.

Every file, this was not the behaviour that existed before, can you send me a log file please ?

I experience the smae problem with Jaikoz 2.1.0 build 1039 under windows XP. I have 101 mp3 files that Jaikoz doesn't assign a musicIP ID to. It does search for one, (although occaisionally VERY slowly), but they are not actually assigned. It seems to happen to certain artists/albums, but I haven't found in wich these are different from the rest of my collection.

If you tell me hoe to create a log, I'll send you one...