Den Weirdness
so I just am experiencing something WEIRD right now.
it's kinda like I am being connected to two dens at once but also kinda not,
after installing Wayk on a Server I am doing updates for (wayk spawns WAY earlier and dies FAR earlier than RDP making it much easier for the heart in my opinion) I decided to throw it into the Den I set up for my testing to not overexpose it, obviously my Laptop still being on the default den (when needing to support random people I cannot just explain to them how to connect to a special den, lol) needed to follow into my den as well, so I just changed over and it seemed fine, until I started poking around my den for fun again.
not only is the session which is happening literally as I am writing this post not being listed, but also is my laptop (according to the den site) not connected to that den, so I went to check the wayk dashboard (basically a listing of the registered machines on the standard wayk den) and it was connected over there, then being confused even more I looked at my wayk client and it says that my Wayk ID is the one from the standard wayk den instead of the one I should be connected to.
so for some reason I am both connected to a server over my custom wayk den (the server is being shown online over there), while at the same time, I am connected to the standard wayk den.
am I the only one utterly confused right now.
Edit: the session I started right after being forcefully signed out due to me starting a reboot does seem to properly appear in my den, while it still shows my Laptop as offline
Edit 2: next session after reboot also shows up on den, rest unchanged
All Comments (5)
Hello
Just to be sure I have it right: you deployed Wayk Now on a remote server, and pointed it to your custom Wayk Den. You updated your laptop to point to the same Wayk Den and started a session. The session does not show up on Wayk Den (despite being active). Your laptop (the client machine) shows in the machine listing on den.wayk.net but not in the dashboard for your custom Wayk Den. Finally, the Wayk Now UI shows the six-digit ID from den.wayk.net?
It sounds strange indeed; I think that to provide an answer we would definitely need to see the logs from your laptop. The service log is enabled by default and should be in %programdata%\wayk\logs\NowService.log (/etc/wayk/logs/NowService.log on Linux). Hopefully you had your client log enabled too, and that would be in %appdata%\wayk\logs\WaykNow.log (~/.config/wayk/logs/WaykNow.log). If not - please enable it (to debug level) and see if you can reproduce the issue again. You could send the logs to wayk@devolutions.net.
Thanks and kind regards,
Richard Markievicz
Hello
Just to be sure I have it right: you deployed Wayk Now on a remote server,
yes
and pointed it to your custom Wayk Den.
yes
You updated your laptop to point to the same Wayk Den
exactly
and started a session.
just as you say
The session does not show up on Wayk Den (despite being active).
yup, here's where the weirdness started (although as noted by the edits only one of the sessions seemed dead, others were in as they should be
Your laptop (the client machine) shows in the machine listing on den.wayk.net
actually dashboard, but basically the same idea
but not in the dashboard for your custom Wayk Den.
exactly
Finally, the Wayk Now UI shows the six-digit ID from den.wayk.net?
see why I am confused
It sounds strange indeed; I think that to provide an answer we would definitely need to see the logs from your laptop. The service log is enabled by default and should be in %programdata%\wayk\logs\NowService.log (/etc/wayk/logs/NowService.log on Linux). Hopefully you had your client log enabled too, and that would be in %appdata%\wayk\logs\WaykNow.log (~/.config/wayk/logs/WaykNow.log). If not - please enable it (to debug level) and see if you can reproduce the issue again. You could send the logs to wayk@devolutions.net.
Thanks and kind regards,
I look for the logs and send them to you by DM, I dont wanna check for stuff I need to redact in a probably way too long log as I doubt I could just easily reproduce it out of nowhere, when it probably catches itself.
Hello again
Thanks for sending the log files, I have had a look at them. The reason for the issue is because of a version mismatch between the different Wayk Now components on your system: the Wayk Now client is 2020.1.7, but the unattended service is 2020.1.6. We don't support such a configuration, the versions must match or you might see unexpected behaviour like that. On Windows - where we distribute the .msi and the .exe as distinct downloads - it's semi-easy to fall into that situation (for example, you installed Wayk Now using the .msi a long time ago and then forgot about it, and then download and run the .exe) and the client is smart enough to detect that and warn the user via a dialog box.
On Linux, the "service health" features are lagging a bit behind the Windows version, so you don't currently get a warning in this case. However I am curious how this could have occurred, since we only currently distribute the .deb which packages everything together. Do you have an idea how your wayk-now binary could be from a newer release than now-service?
Thanks and kind regards,
Richard Markievicz
wait a sec WHAT?
you are not the only one curious how this can happen. when you said that the wayk components were different versions, I kinda was, "these are both on the same system, and update via apt".
no idea whether the update process is flawed when not rebooting or whatever because I didnt (I generally dont when I wouldnt need to (like I mean in case of linux-* packages as the kernel gets an update a reboot is kinda required)
Edit, what I just saw after digging a bit in the logs myself is that the last instance of ANY version string in my log was 6th May, which has been quite a while.
just ran
sudo systemctl restart now-service
and we're going, so maybe force a service restart when an update happens.
also if you get the chance to do a breaking change, maybe call your service something that doesnt require half an eternity of dumbly digging around to find the name, I mean when searching for wayk (what is the unique part of the wayk-now product name) it might be helpful to have these four characters in the related software.
Hello again
I am equally as confused as you are; the .deb prerm and postinst maintainer scripts explicitly stop, destroy and then recreate the systemd service; I confirmed that by running `sudo dpkg -D2 -i wayk-now...`, as well as running the maintainer scripts manually. So I'm afraid I don't have an explanation for the behaviour you see. However, we've added a forced restart of the service component to the postinst maintainer script that should prevent the same scenario from occurring, and that will be incorporated in the next release.
Regarding the naming: the Linux application just follows Windows, where the name of the binary is not reflected in the service manager / service control. We'll review that again if we get chance. There's a famous quote that says "There are only two hard things in Computer Science: cache invalidation and naming things."
Thanks again for the bug report,
Richard Markievicz