database start -- 1.5.2 on linux

Good morning all,
Just updated Serviio from 1.4.1.2 to 1.5.2 and the database is still reading and scanning and whatever...3 hours and counting now...

...and it seems Serviio does not actually serve up files while this is going on, it's consuming a lot of CPU cycles and am starting to wonder if something is broken somewhere...


====
# systemctl status serviio.service

● serviio.service - Start the serviio DLNA server in headless mode
Loaded: loaded (/usr/lib/systemd/system/serviio.service; enabled)
Active: active (running) since Fri 2015-04-24 14:50:56 MST; 3h 5min ago
Process: 6729 ExecStop=/opt/serviio/bin/serviio.sh -stop (code=exited, status=0/SUCCESS)
Main PID: 6920 (java)
CGroup: /system.slice/serviio.service
└─6920 java -Xmx512M -Xms20M -XX:+UseG1GC -XX:GCTimeRatio=1 -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -Djava.net.preferIPv4Stack=true -Djava.awt.headless=tr...

Apr 24 14:50:56 systemd[1]: Started Start the serviio DLNA server in headless mode.

====

The release notes say that there were changes made to the refresh process since 1.4, and the log shows steady activity, but am not clear if what I am seeing is a normal first-time start up thing or if there is something wrong somewhere...

The old version would start and stay current quickly and without a lot of effort, does any one know if there are significant one-time database updates that are being made with the new rev and it just takes a long time, or is the new process just more labor intensive, or is it having trouble digesting a big audio library? Would giving the JVM more resources help?


thanks and any help appreciated,


rikm

[zip]

It's updating the library to the new version, which involves re-adding all your (video) files. It's usually the case for a new major release.

Good morning zip and thanks for the reply...don't have any video files but I take the point. It took a while but finished eventually...the database seems slower than the previous release, but as I said in another post, it seems to be working harder. Or at least it used more system resources for a longer period of time during the re-create process...

The issue now is the more sluggish feel [as seen at the client end, the android tablet that controls the network gadget, the Pioneer N-50 that is ] the slow response time while browsing the directory tree, I mean, and the stuttering during playback that has occurred at random times.

That's the serious issue...never saw that with v1.4.1.2 so any help there would be appreciated.

As I said in the other post, if there is something I can do to test, or if the derby log was not helpful, please let me know...


thanks again,

rikm

[zip]

This looks more like a network issue, rather than Serviio issue. Don't think there are any changes that would affect speed of browsing between these 2 versions.

Good morning zip and thanks again for your reply,

...well there have been no hardware changes...Fedora went from 20>21 on the music server PC, but the same files have played correctly before...and still play properly via the sound card's direct wire from the server to the stereo...the network is wired gbit and isn't busy... the N-50 only does 100 but that has never been an issue...

Perhaps I shouldn't have called the playback error stuttering...I saw the post on stuttering and re-used the word, but that one was about video on windows and there is no video involved here, just mostly standard rez flac...

The random error is more of a momentary pause and resume, and that coupled with the apparent slowdown on the tablet while browsing the music dir tree make it seem like 1.5.2 is having difficulty keeping up...as I said there are a fairly large number of files and the database seems to be working harder than it was...

All the 'Presentation' options in the console for instance are set Disabled except for Music--Folders, but the database keeps working on finding and parsing playlists and finding and reporting errors in them...the logs are set to DEBUG and fill up and cycle continuously...so it really does seem to be working harder than it was in 1.4.1.2


thanks and again, any help appreciated,


rikm

[zip]

remove the DEBUG logging, it'll take some io load off