MinimServer start error: see system log.

[Paradox2701]

Hi Simon,
the problem has surfaced. I tried to capture what I can gather, with the minimserver-out.log file is captured at 19.42 on my NAS. I have also attached the minimserver log (truncated a lot of issues with naming of files/tagging) and the error log on my NAS. Hope all these are helpful.

(05-04-2016 09:32)simoncn Wrote:  

(05-04-2016 02:24)Paradox2701 Wrote:  Hi Simon,
there is no more 'on the right' of the error log. It just has that full stop.
For the error, the interesting thing is that as I mentioned the music still plays. Apparently the server will restart itself (??my wild guess??) and be able to run. When I reached home at 8 pm I could start the music using the UPnP controller just fine. The only indication of any error I get is that it is an error in the NAS log. So it has kind of bewildered me a bit. As I rescanned the server, I think I lost that minim-out log that you required that has time stamp 19:32, without realizing I erased that particular log.

From this, it seems that a stray '.' was somehow written to the minimserver-out.log file and this caused MinimServer to write the '.' to the system log. MinimServer did not fail to start and this is why it was running normally at 8 pm. You can safely ignore any similar occurrences. I will try to find out what caused the '.' to be written.

[simoncn]

(05-04-2016 16:22)Paradox2701 Wrote:  Hi Simon,
the problem has surfaced. I tried to capture what I can gather, with the minimserver-out.log file is captured at 19.42 on my NAS. I have also attached the minimserver log (truncated a lot of issues with naming of files/tagging) and the error log on my NAS. Hope all these are helpful.

This is very puzzling. I don't think it is related to the naming/tagging issues but I am finding it hard to come up with any reasonable explanation. I will "sleep on it" now and come back to it tomorrow morning.

[simoncn]

(05-04-2016 22:27)simoncn Wrote:  This is very puzzling. I don't think it is related to the naming/tagging issues but I am finding it hard to come up with any reasonable explanation. I will "sleep on it" now and come back to it tomorrow morning.

I think this might be a timing issue with the MinimServer launch script. If MinimServer is running correctly, you can safely ignore this message. I will change the launch script in the next version of MinimServer to close the potential timing window.

Thanks very much for letting me know about this problem!

[Paradox2701]

Thank Simon for your wonderful work. And am very very appreciative that you made this wonderful music server for classical music, and made it accessible to everyone.

(06-04-2016 08:37)simoncn Wrote:  

(05-04-2016 22:27)simoncn Wrote:  This is very puzzling. I don't think it is related to the naming/tagging issues but I am finding it hard to come up with any reasonable explanation. I will "sleep on it" now and come back to it tomorrow morning.

I think this might be a timing issue with the MinimServer launch script. If MinimServer is running correctly, you can safely ignore this message. I will change the launch script in the next version of MinimServer to close the potential timing window.

Thanks very much for letting me know about this problem!