Wayk Den ID resets

Hi Bern

We were tracking this issue and I believe it should be fixed in the latest release. Can you confirm whether this still happens in 2.1.2?

As for the lease time and whether the self-hosted Wayk Den will allow static IDs, I will have to check with someone from the Wayk Den team.

Thanks again

Thanks Richard. I am running 2.1.2, so yeas this still happens.

my questions as to lease times and static ID's were mostly as a query to if this behavior is normal. If it is something you are aware of as an issue, I'm sure you will get it fixed up, but if there is anything I can do to help in testing, please let me know.

Hi Bern

Thanks for getting back to me. I did some cursory testing and couldn't get my Den ID to reset on the latest version. I will do some more investigation into the issue and get back to you.

Thanks again

Richard, I have had the same issue with Wayk crashing on a remote workstation and coming back with a different ID. Probably Wayk Den sees the incoming connection from the remote as a new connection and assigns a new ID. I think the problem that needs to be addressed though is why the connection from the remote to the Den drops... I am using the latest version of wayknow.exe on both ends as I did not want to install using an MSI.
I think Wayk is fantastic when it works and am anxiously awaiting the self hosted Den as well as the unattended install.

Thanks for the great work.

Raphael

Hi Raphael,

The Wayk Den ID should remain the same, except in some rare cases. We are in the process of migrating to a new implementation of the Wayk Den. Earlier this week, we switched between the old and the new, and then reverted back when we noticed a few remaining stability issues. The switching between the two Wayk Dens could have caused the ID to switch. We are doing some more testing to make sure that the next time we make the switch, it works fine this time, such that this won't happen again. With the on premises version, this should not happen.


Best regards,

It just happened to me again, but to be fair, I haven't tried to connect to that system in a couple of weeks, so the changes to the DEN may have caused it. That said I just want to report that the remote system was showing as connected to the DEN, with the old non-functional ID, so I was a bit confused as to why I was unable to connect. I quit Wayk on the remote, and restarted it, and the new functional ID appeared. If it matters the remote system was the same MAC Pro that I have been having connection issues with in the reverse direction as reported in another thread, so the issue may also be related to the quirks on that Yosemite based Mac Pro system.

Just thought I would post these findings in case it helps in any way.

Hello Bern

It sounds indeed like the issues were related to the switchover of the Den backend. as Marc-André postulated.

The incorrect ID you saw during that period is a tricky scenario to validate, and since everything should have settled down now, please post back if you notice any further weirdness in this regard. To circle back to the original post, I've been testing a bunch of different scenarios and the Den ID has remained stable on all my machines. So I'm confident that this should be working well now.

Thanks again,

I just had another ID reset on that same MAC Pro I referred to earlier. I have also noticed that I can't connect to this machine if the screensaver is active. Perhaps this had something to do with it?

Hi Bern

Thanks for the update.

Can you normally connect while the screensaver is active on your Mac Pro? Or it was only an issue when the ID reset?

I never could connect while the screensaver is active. I actually use dwservice to remote in and wiggle the mouse before connecting to WaykNow

Hi Bern

That is extremely strange; I just tried it on a Yosemite machine and it worked ok for me.

Just to clarify, are we talking about the screen saver, or a sleeping display?

Thanks again,

My display does not go to sleep. So it is only a screen saver

Hi Bern

It's quite strange, and I'm not sure that the two things (unable to wake the screensaver, and the Den ID getting reset) are related.

If possible, I'll ask you to check again the screen saver when 2.2 is released (it is almost at beta stage). There is no specific fix in there, but we made some a fundamental change to how we use syscalls on macOS that could have caused some strange behaviours (especially on older systems).

I'll let you know when the 2.2 is available. Thanks for your patience!

Thanks Richard.

I will indeed try 2.2 when available. I only suggested that the two issues may be related because you mentioned that there are some bugs in the OSX syscall implementations. I don't profess to be an application programmer, per se, but I am an electronics technician by trade, and a programmer of AMX A/V control systems, so I do understand that sometimes symptoms that should not be related turn out to be related due to unforeseen reasons. I just thought I would throw my observations your way as a potential area to investigate.

Hi Bern,

Just a quick update: we have deployed the new Wayk Den yesterday, this time it shouldn't have caused a Wayk ID reset.

About the screensaver issue, I think it may be related to another long standing issue we've had where the brightness is set to the maximum on connection. This issue has been inconsistent and we've had problem pinpointing the root cause, but we now think they may both be related. In one case, we don't correctly wake up the system (screensaver remains), in some other cases, we keep waking up the system (full brightness). We'll investigate this new lead and come back to you.

Best regards,

Hi Bern

For sure! Any observations or correlations that you can suggest are definitely helpful, even if something seems outlandish or completely unrelated. You know how these things work... :)

As Marc-André mentioned in his reply, we've done some work today around waking the system if it has a sleeping display. I've also added extra logging in the relevant functions.

We'll ask you to try it out with 2.2 (which is in QA this week).

Thanks again,

Hi Bern

The 2.2 release is available now, and should show up as an update or you can grab it directly: https://wayk.devolutions.net/home/download

Thanks and have a nice weekend

Thanks Richard. I have downloaded 2.2. It seems to have addressed the issues I was having with not being able to connect to my mac at the office due to the screensaver being active. Hopefully the issue of the den ID resetting had also been addressed.

....looking better with every version. Keep up the good work.

Hi Bern

Great stuff!

Hi Richard. I have been playing with the new release of WaykNow, and I will say that it is a lot better, but I still get some intermittent connection errors trying to connect to the Mac at work, requiring me to log in with dwservice and restart WaykNow in order to connect. Usually when this happens, I get an error at home saying the the TLS handshake couldn't be completed.

As I said, this is intermittent, so it may be difficult to track down, and given that the OS on my mac is several versions old, it may not be something that is addressable without "breaking" WaykNow for newer OS versions, but if there is something you would like to see regarding this, let me know, and I will try to get you some logs the next time it happens.

Hi Bern

Apologies for the delayed response, I have been out of the office for a couple of days.

I'm really happy to hear that things are working a lot better with the 2.2 release.

One thing that I could ask you to check for me when this happens again - if you are having the log level set to ERROR, you might see a corresponding entry in the log file like "mbedtls_ssl_handshake server failure: 0xXXX". The presence (or not) of that message, and the error number, would be helpful information!

Thanks for the help,

Hi Guys,

I just experienced another den ID reset on my Mac at the office. I have not seen this happen on my Win7 system at home aside from the one time I posted about at the top of this thread, but it has been multiple times on my Mac.

Hi Bern,


We are currently looking into your issue and we have a new version of our WaykDen Servers coming soon that should fix this. In the mean time, if you could provide us some logs in the event of an other ID reset (with your log level set to DEBUG in WaykNow : here's how).

This could really help us track this down and make sure that the next release fix the issue for good!

Thanks and have a nice weekend!