+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Problems with MinimWatch and Updates (/showthread.php?tid=6178)
Pages: 1 2
Problems with MinimWatch and Updates - Oliviander - 16-04-2021 23:43
Hi Simon,
I am a longtime user of MinimServer and since 2.0
proud paying customer
And while the product itself is getting better and better
I encounter more and more problems with MinimWatch
and the update process.
And as I am not sure whether they are independent or not
I will lay out the whole situation.
I have Minimserver installed on a virtual DEBIAN Server
and have 9 Instances running.
MinimWatch 0.83 worked flawless for me even under WIN10
but after I upgraded the whole System to 2.0
MinimWatch is not working reliably.
When I start Minimwatch Somtimes it takes minutes
until all Instances are displayed.
I guess it can't be a network issue because the Linn Kinsky Controlpoint
running on the same PC is reliably displaying all 9 Instances in a second or two. (Yes I am still using this old contol point because I am still waiting for a better one to be released on PC or anywhere)
Then, when I press the about button of an Insance sometimes all instances
vanish (and reappear after sometime). I could live with that by now because actually I don't have to use
MinimWatch too often.
But today the updateprocess (update 193) didn't start and therefore
I looked deeper into the problems.
Until now when I started MinimWatch it announced the update
with a pop up window - and I just could click through the 3 Windows for each Instance (Even that was cumbersome with 9 Instances but ok my fault to have so many)
But today - nothing - so I had to manually open the options window of each Instance and always the other Instances were vanishing and I had to wait - sometimes minutes for them to reappear.
In the meantime I forgot wich Instances were already updated.
So it took me a long time to get trough
Therefore I took a look in your manual and my preferences
and saw that I have the autoupdate set to true
and that to the description the update should occur
automatically - but that actually never worked for me
I had always to click through the windows.
Maybe this is working as intended but In my opininion
the manual says otherwise.
So there are 2 Questions
1. what could be the source of my MinimWatch delay and instability
and what can I do against it ?
2. Is there a better option for the updateprocess (without having
to click more than once per Instance).
Thx in advance
PS: I just discovered the .updatereminder property
(it is set to the default: 1)
and I guess update 193 was just to new to pop up -
but that still leaves my main questions.
RE: Problems with MinimWatch and Updates - simoncn - 17-04-2021 14:28
MinimServer update 193 is not yet enabled for automatic update. You can see this from the first paragraph of the release notes. Depending on what is in an update, it might be enabled for automatic update immediately or I might wait a couple of days to see if there any reported issues before doing this.
I would like to work with you to understand what is causing the issues with MinimWatch 2 and MinimServer 2. The first step is to have a repeatable scenario so that debug logs can be produced. For example, if you stop MinimWatch and then restart it after a few seconds, do you always see the problem with slow discovery?
To update all 9 instances in a more efficient manner, you can use command scripting. I will post instructions for this later today.
RE: Problems with MinimWatch and Updates - simoncn - 17-04-2021 17:45
To install update 193 using command scripting, do the following:
1) Create a file named myscript.txt (or any other name) containing the following lines:
install minimserver-update-193
relaunch
2) Run this command as follows: (assuming you are running it on Linux, other platforms are available)
minimserver/bin/mscript -a nn.nn.nn.nn:pppp myscript.txt
where nn.nn.nn.nn is the IP address of the instance and pppp is the http.port number of the instance
3) Repeat step 2 for all other instances
RE: Problems with MinimWatch and Updates - Oliviander - 18-04-2021 07:05
(17-04-2021 14:28)simoncn Wrote: I would like to work with you to understand what is causing the issues with MinimWatch 2 and MinimServer 2. The first step is to have a repeatable scenario so that debug logs can be produced. For example, if you stop MinimWatch and then restart it after a few seconds, do you always see the problem with slow discovery?
Ok let's do this
I have WIN10 Machine 64bit running minim watch.
I disabled all networkadapters except the one leading to
the correct network.
(there is actually a defective 10G adapter on my mainboard
which can't be removed but I have it disabled and all other applications work flawlessly)
I just restarted my windows machine.
Minimwatch takes this long time just after boot
and on each minimwatch restart after that.
I already tried this with the firewall disabled
and its just the same.
The discovery looks completely random:
Sometimes the first Instance is discovered immediately
but sometimes it takes up to 2 min until the first instance is discovered.
and it's the same with the following discoveries.
The order of the discoveries is completely random too.
I sent you a tracelog from a minmwatch start
as an attachment
(you can see that it took 10 minutes until the last
Instance was discovered)
and thx for your support
RE: Problems with MinimWatch and Updates - simoncn - 18-04-2021 10:46
Thanks for this log. When MinimWatch starts, it sends an M-SEARCH multicast discovery message to the active subnet 172.19.0.0. Any MinimServer instance that receives this message sends a response. These responses are not being received by MinimWatch. This means that either the M-SEARCH message from MinimWatch is being blocked by your network or the M-SEARCH responses from the MinimServer instances are being blocked by your network.
To confirm which of these it is, please do the following:
1) On one (only) of the MinimServer instances, set the ohnet.debug property to All. I will refer to this instance as the test MinimServer instance.
2) On the test MinimServer instance (only), set the logging level to Debug (not Trace)
3) On MinimWatch, set the ohnet.debug property to All and set the logging level to Debug (not Trace)
4) Exit MinimWatch
5) Exit and restart the test MinimServer instance
6) Start MinimWatch
7) Wait until the test MinimServer instance has been discovered by MinimWatch
8) Copy the minimwatch.log file to another location
9) Copy the minimserver.log file of the test MinimServer instance to another location
10) Compress both these log files to save space. This step is important.
11) If these files are small enough, attach them to a forum post. If they are too large for this, let me know and I will tell you how you can get them to me.
Important: Do not save either of these log files using the log window. You must use the minimwatch.log file and minimserver.log file from disk as described above. The disk files contain essential information that is not written when you save the log using the log window.
RE: Problems with MinimWatch and Updates - Oliviander - 18-04-2021 18:20
Hi Simon,
this is really weird:
I set up all along your description.
And Then : Everything worked like a charm.
All Instances showing up in 1 sec.
So I assumed that the restart of the Debian VM
might have resolved the issue.
So I reverted all back to default.
But then: the same problem was there again
I was baffled.
As all instances were showing up immediately in that try,
I assumed that the problem rather occured in minimwatch
and experimented with the properties.
And Voila I can now reproduce the error to 100%
If do nothing else except setting the log level of minimwatch to "Debug"
everything works like a charm.
When I revert the setting to "Info" or "Verbose"
the error occurs again.
(Trace seems to work too - but I am not sure if it worked
when I made the logfile I have sent - maybe I didn't look
Because I played a Videogame while waitin for the log)
I didn'tattach the logfile because everything is working as intended
when I do it that way - But if you still need it I will
Of course make it for you.
I hope you can make something out of that.
RE: Problems with MinimWatch and Updates - simoncn - 18-04-2021 22:12
Please do produce the logs that I requested, exactly as I said in my post. I hope these logs will give me useful information, together with this latest information from you that enabling Debug causes the problem not to occur. The changed behaviour is likely to be caused by small timing differences. Many thanks for your help with this.
Edit: It would also be useful (perhaps even more useful than the above) to get the minimserver.log file from one of the servers (produced as described in my previous post) in the case where Debug logging is disabled in MinimWatch and the problem is occurring.
RE: Problems with MinimWatch and Updates - Oliviander - 19-04-2021 15:50
I just had a real long message ready and then accidently
closed my browser
so here i am for a2nd try:Just when I wanted to create the logfiles for you I discovered
that I accidently didn't reset the ohnet.debug property
in MinimWatch to default.
(probably forgot to save before closing the window as with this post
)So I tried and discovered that the problem occurs when I reset
this property to default not dependend on the logging level
So now I can tell the discovery only works with
MinimWatch settings:
ohnet.debug: All
and
logging level: either debug or trace
all other settings result in the problem that it takes
about 10 minutes to discover all instances.
So now I send you 3 pairs of logfiles
Chosen testserver is
1_Klassik
http.port: 9801
ohnet.port: 9901
ohnet.debug: All
logging level: debug
this server and all other servers were restarted for each setting
MinimWatch settings are:
1. version (no problems)
ohnet.debug: All
logging_level: debug
2. version (no discovery after a few minutes)
ohnet.debug: All
logging_level: verbose
3. version (no discovery after a few minutes)
ohnet.debug: Default
logging_level: debug
During my experiments yesterday
using settings 2 and 3 I had at least some discoveries after a few minutes
but not today - can't imagine why.
After returning to settings 1 it was always working again in every case
yesterday and today
but only after a restart of MinimWatch
Ok I could only attach Version 1
Versions 2 and 3 are too large (1MB limit is not very large :rolleyes
If you want Versions 2 and 3 let me know how
(they are not that large and smaller than 2MB)
RE: Problems with MinimWatch and Updates - simoncn - 19-04-2021 17:41
Thanks very much for doing this. Please upload zip files 2 and 3 to my FTP server. I will send you a PM now with the server details.
RE: Problems with MinimWatch and Updates - simoncn - 19-04-2021 22:11
Thanks very much for these logs.
It looks like the machine running MinimWatch has the IP address 172.19.0.66. What devices have the IP addresses 172.19.9.100 and 172.20.25.31?
How does the 172.19.0.0 subnet communicate with the 172.19.9.0 subnet?
How does the 172.20.9.0 subnet communicate with the 172.20.25.0 subnet?
Do you have Minimwatch 0.8 running anywhere in your network?
There are some anomalies in the server logs for test 2 and test 3. This might be because the server was not restarted before running test 2 and before running test 3.
I would like to focus on test 3 because this shows the problem and provides a reasonable amount of log information. Please run test 3 again but this time stop and relaunch MinimServer before you start the test. Many thanks.