Threaded Mode | Linear Mode

opd · 21-03-2013, 21:37

I've just installed version 0.63.5 on a Synology DS710+. The DSM version is 4.2. I'm having the same problem as others have reported on Synology. I can't see the server on the Kinsky control. The server seems to start OK. There are some errors in the log. But as far as I can see only indications that some file tags can't be parsed.
Is there a secret version for Synology that I should ask for?

simoncn · 21-03-2013, 22:57

(21-03-2013 21:37)opd Wrote: I've just installed version 0.63.5 on a Synology DS710+. The DSM version is 4.2. I'm having the same problem as others have reported on Synology. I can't see the server on the Kinsky control. The server seems to start OK. There are some errors in the log. But as far as I can see only indications that some file tags can't be parsed.
Is there a secret version for Synology that I should ask for?

There is no secret version. Many people are using 0.63.5 successfully. Please reboot the Synology to see if that helps. If not, please zip the log and attach it here.

opd · 21-03-2013, 23:18

(21-03-2013 22:57)simoncn Wrote:
(21-03-2013 21:37)opd Wrote: I've just installed version 0.63.5 on a Synology DS710+. The DSM version is 4.2. I'm having the same problem as others have reported on Synology. I can't see the server on the Kinsky control. The server seems to start OK. There are some errors in the log. But as far as I can see only indications that some file tags can't be parsed.
Is there a secret version for Synology that I should ask for?

There is no secret version. Many people are using 0.63.5 successfully. Please reboot the Synology to see if that helps. If not, please zip the log and attach it here.

OK,
I might have checed the log to early. It seems the server crashes due to limitations in java heap size. Is that a size that can be expanded?

simoncn · 22-03-2013, 01:45

(21-03-2013 23:18)opd Wrote: OK,
I might have checed the log to early. It seems the server crashes due to limitations in java heap size. Is that a size that can be expanded?

Thanks for the quick response.

How large is your music library (tracks, albums, folders)? Do you have a lot of very large tags in your files? What is your setting for indexTags?

opd · 22-03-2013, 07:25

(22-03-2013 01:45)simoncn Wrote:
(21-03-2013 23:18)opd Wrote: OK,
I might have checed the log to early. It seems the server crashes due to limitations in java heap size. Is that a size that can be expanded?

Thanks for the quick response.

How large is your music library (tracks, albums, folders)? Do you have a lot of very large tags in your files? What is your setting for indexTags?

Hm..
There are about 2800 folders, 28000 files, totalt 750 GB.
I don't know if there are large tags. How can I find out? And I don't know where check the setting for indexTags. I think I remember having ticked off for "index" somewhere, but can't find the way back to it now.

winxi · (This post was last modified: 22-03-2013 09:05 by winxi.)

(22-03-2013 07:25)opd Wrote: And I don't know where check the setting for indexTags. I think I remember having ticked off for "index" somewhere, but can't find the way back to it now.

'indexTags' is a native MinimServer property which you can set using MinimWatch - not to be confused with the Synology indexing service.

opd · 22-03-2013, 09:15

(22-03-2013 09:03)winxi Wrote:
(22-03-2013 07:25)opd Wrote: And I don't know where check the setting for indexTags. I think I remember having ticked off for "index" somewhere, but can't find the way back to it now.

'indexTags' is a native MinimServer property which you can set using MinimWatch - not to be confused with the Synology indexing service.

OK, I haven't got as far as installing MinimWatch. I'll try it in the afternoon. But still I don't know if it will work as long as the server crashes.

winxi · 22-03-2013, 09:19

(22-03-2013 09:15)opd Wrote: OK, I haven't got as far as installing MinimWatch. I'll try it in the afternoon. But still I don't know if it will work as long as the server crashes.

This means that the 'indexTags' property should have the default value.

Quote:I don't know if there are large tags. How can I find out?

You can find out more about the tags in your files using a tagging software such as Mp3tag.

opd · 22-03-2013, 09:34

(22-03-2013 09:19)winxi Wrote:
(22-03-2013 09:15)opd Wrote: OK, I haven't got as far as installing MinimWatch. I'll try it in the afternoon. But still I don't know if it will work as long as the server crashes.

This means that the 'indexTags' property should have the default value.

Quote:I don't know if there are large tags. How can I find out?

You can find out more about the tags in your files using a tagging software such as Mp3tag.

OK. I have the Mp3tag program, but rarely use it. Still it seems a bit awkward to look for large tags. Unless there's a function in Mp3tag to identify large tags. I can take a look and see if I find something obvious.

simoncn · 22-03-2013, 10:02

(22-03-2013 07:25)opd Wrote: Hm..
There are about 2800 folders, 28000 files, totalt 750 GB.
I don't know if there are large tags. How can I find out? And I don't know where check the setting for indexTags. I think I remember having ticked off for "index" somewhere, but can't find the way back to it now.

MinimServer is intended to handle up to 100,000 tracks. I'll put together a diagnostic build that will report memory usage. This should give me an idea of what is consuming such a large amount of memory. I'll also add code to the diagnostic build to stop gracefully when it gets an "out of memory" error. This should enable MinimWatch to see it across the network.

I'll need to send you a diagnostic build of MinimWatch as well. What platform (PC or Mac) will you be using to run MinimWatch?