Update stuck in "File info" stage

General discussion about netjukebox
Post Reply
Martin Tomsa
User
Posts: 2
Joined: Wed Feb 12, 2020 11:47 pm

Update stuck in "File info" stage

Post by Martin Tomsa »

I have about 30 gigabytes of music, uplink to netjukebox environment is about 1 megabyte per second.

When I do an Update of my library, it gets stuck in "File info" stage forever. How do I find out what is going on there?

I'm not sure if it is caused by volume of my library. I can inspect logs of my webserver, MySQL and whatever else, but before that - what is being done in "File info" stage? Does netjukebox inspect every single bit of my library?

Are there any logs of update process?

Thank you for any help.

Martin Tomsa
User
Posts: 2
Joined: Wed Feb 12, 2020 11:47 pm

Re: Update stuck in "File info" stage

Post by Martin Tomsa »

Update:

I tried running `php -f update.php` manually and it gave me this nice output:

Code: Select all

netjukebox 6.61
Copyright (C) 2001-2020 Willem Bartels
GNU General Public License version 3 or later; see LICENSE.txt


Processing structure...
Processing bitmap...
Processing file info...
Cleanup...
Music Player Daemon update...
Script execution time: 7:58
Anyway, I still wonder how to find out what went wrong when I updated the library from user interface.

Can anyone provide any details on update process internals, please?

User avatar
wbartels
netjukebox developer
Posts: 823
Joined: Thu Nov 04, 2004 3:12 pm
Location: Netherlands
Contact:

Re: Update stuck in "File info" stage

Post by wbartels »

I come back to this in the weekend!

User avatar
wbartels
netjukebox developer
Posts: 823
Joined: Thu Nov 04, 2004 3:12 pm
Location: Netherlands
Contact:

Re: Update stuck in "File info" stage

Post by wbartels »

Sorry for the late response. The first update will always take a long time! This is because all the images will be converted to a lower resolution for the web interface. After that the getID3 library needs to retrieve/calculate the playtime, encoder, bitrate, etc. See screenshot below. These information is stored together with an track_id and filemodificationtime so that on the next run only the changed files need to be updated.

With my setup (27113 tracks) I have done an new database installation and the first update took: 12 minutes and 19 seconds
The second run: 11 seconds

I think you need to be patient the first update.
Attachments
Screenshot 2020-02-16 at 22.25.21.png
Screenshot 2020-02-16 at 22.25.21.png (130.24 KiB) Viewed 1735 times

Post Reply