ReadyNAS V0.71 java heap space error

[simoncn]

(02-05-2013 07:54)guenter55 Wrote:  Simon,

Congratulations! good work!

I followed your instructions - and it worked.
My complete music collection is tagged and MinimServer is running.

The last resource info showed 466,000 files read.
The run time was not worse then expected.

regards, Guenter

I'm pleased to hear this. What numbers do you get from resourceInfo after the startup phase is complete and MinimServer is browsing and playing music?

You can reduce the number of resourceInfo messages from the startup phase by increasing the value of the resourceInfo property. For example, if you set this value to 50000, you will get 9 messages during startup instead of getting 466 messages.

[guenter55]

When MinimServer is running (with more than 511.000 files scanned)
the resorce message is:

resourceInfo: heap bytes used 83695640, consumed 85398896, committed 259522560
resourceInfo: non-heap bytes used 8577568, committed 15499264

[simoncn]

(03-05-2013 21:51)guenter55 Wrote:  When MinimServer is running (with more than 511.000 files scanned)
the resorce message is:

resourceInfo: heap bytes used 83695640, consumed 85398896, committed 259522560
resourceInfo: non-heap bytes used 8577568, committed 15499264

Thanks for letting me know. The memory in active use is about 92 MB, which should mean it will run OK on a 256 MB NAS. This is very useful information.

For a future release, I'll investigate how to make the heap size configurable without needing to modify the start.sh file.

[guenter55]

Hi simoncn,

now the server run for several weeks.
Now I did a complete restart of the NAS because I added a disk.
After that I reinstalled minimserver with the changes you suggested.
My database was scanned right and quite fast, may be because I did not scan any tags (I'm used to access my song by directory).
I did a test with a client and it worked o.k.

But the next day the server was down completely and not accessable with
minimwatch (gray logo).
I had to stop and restart it from the readynas dashboard.
The behavior was again the same.

Do you have any idea?

Regards Guenter

[simoncn]

(21-10-2013 19:50)guenter55 Wrote:  Hi simoncn,

now the server run for several weeks.
Now I did a complete restart of the NAS because I added a disk.
After that I reinstalled minimserver with the changes you suggested.

Which changes do you mean?

Quote:My database was scanned right and quite fast, may be because I did not scan any tags (I'm used to access my song by directory).
I did a test with a client and it worked o.k.

But the next day the server was down completely and not accessable with
minimwatch (gray logo).
I had to stop and restart it from the readynas dashboard.
The behavior was again the same.

Do you have any idea?

Regards Guenter

Please post the minimserver.log file. You can find this in the backup share.

[guenter55]

Quote:Which changes do you mean?

Change in start.sh:

LD_LIBRARY_PATH=$MINIMSERVER/libsys $JAVA -Xmx256m -jar ../lib/minimserver.jar --noconsole </dev/null >$OUT_FILE 2>&1 &

Quote:Please post the minimserver.log file. You can find this in the backup share.

I attached the latest log I found in backup.

[simoncn]

(22-10-2013 16:39)guenter55 Wrote:  I attached the latest log I found in backup.

This is a different problem that isn't related to memory usage. To solve it, I'll need to look at the file "85 OLDIES/Ultra Rare Rockabilly/01/10 Don't Push, Don't Shove.mp3". I'll send you a PM with details of where you can upload this file.

[guenter55]

I have uploaded the file.

[guenter55]

Now Minimserver stopped again.
Maybe it is related to access of a client, because it was up for a while.
Yesterday a accessed it successfully, but today in the morning it was down.

I will load a copy of the log to your ftp.

regards, Guenter

[simoncn]

(25-10-2013 15:22)guenter55 Wrote:  Now Minimserver stopped again.
Maybe it is related to access of a client, because it was up for a while.
Yesterday a accessed it successfully, but today in the morning it was down.

I will load a copy of the log to your ftp.

regards, Guenter

Thanks for uploading the log. This is the same problem that was reported in this thread. The other user with the same problem is also using a ReadyNAS. Is there anything else on your ReadyNAS that might be sending the MinimServer process a SIGKILL or SIGINT signal?

You can narrow down the time when this is happening by setting the .logPrefix property to the value 'time'. This will record the time of every log message. Next time MinimServer stops unexpectedly, you can look in the log for the time of the "ending MinimServer" message.