Post Reply 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
JAVA restart necessary to fix inactive Minimserver?
01-06-2013, 15:17
Post: #2
RE: JAVA restart necessary to fix inactive Minimserver?
(01-06-2013 11:54)hvaleton Wrote:  Hi Simon,

The strangest thing happened today: I could not 'see' the Minimserver from any of my control points. I looked at the (verbose) logging and could not find anything out of the ordinary. Then I restarted MinimServer on my Qnap and it gave no error (neither on the Qnap QPKG centre page nor in the logging file) but still it was invisible to the AP's and the icon on my PC remained grey.Confused
Then I restarted the Java on my Qnap via the QPKG page: still a grey icon.Angry
Lastly, I restarted MinimServer again and then the icon turned via yellow to the familiar green again.Smile
This is the first time this happened to me. Perhaps it is a known bug that such a thing happens at certain intervals?
Does it have anything to do with:
"Fix QNAP startup crash ("Java heap space" message and/or grey icon problem) "
that I read in the 0.52 release notes?
Of course I'm just guessing here, but I'd like to be able to put my finger on it.Confused

Thanks in advance, and keep up the good work on your amazing software!

regards, Hans Valeton

The 0.52 problem was fixed a long time ago, so that's not related to this problem.

Stopping and restarting Java shouldn't make any dfference, and isn't recommended. Stopping Java just removes some symbolic links, and restarting Java creates these links again.

The best thing to do if you have a problem like this is to disable MinimServer from the QNAP QPKG Center. Doing this automatically creates a diagnostic file containing various useful information. This file is named minimserver-diag.tar.gz and is located in the Public share of the QNAP. Please attach this file to a forum post here, and I'll take a look at it.

This file should have been created when you stopped and restarted MinimServer the first time after the original problem. When you stopped and restarted MinimServer for the second time, this file would have been overwritten by a second copy, overwriting the diagnostic information that was in the first copy. Without stopping MinimServer first, please attach the current version of this file (the second copy) to a forum post, and I'll look at it to see if it contains any clues.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: JAVA restart necessary to fix inactive Minimserver? - simoncn - 01-06-2013 15:17

Forum Jump:

User(s) browsing this thread: 1 Guest(s)