Potentially booter process stops working after long idling?

H

hhspiny

Member
still have problem with booter process after server is up and running for a while (can be days, and during which use computer console too). therefore, difficult to replicate. however, eventually it happens.

The direct phenomenon is blank screen after connection, and have to reboot to get it back. it happened quite often in previous versions, and I thought 1.32 fixed it, but got it again today. also found out today, that if sending "control-shift-alt" from client, it started to work again, however, a). the clipboard did not sync anymore between client and server b). the hardware encoding seemed not working, i.e. a bit laggy.

as I only use booter process only, not sure if the same happens with user's instance.

I will follow-up if I get more such event.
 
mirillis

mirillis

Administrator
Staff member
I will do more tests with booter process only today and upload a new remotly_wincore.dll (also with new registry value DisableHwDec to disable all hardware related decode stuff).
 
mirillis

mirillis

Administrator
Staff member
Can you let me know if you have "Default" set as network interface in Settings->General?
 
mirillis

mirillis

Administrator
Staff member
Hi hhspiny,

I'm not so sure about this. Go this problem once last week:

- Running full version everything looked OK on the UI but this particular PC was visible as "offline" on all clients
- Tried to connect from this problematic PC and it worked (only the host part was not working)
- Using Settings changed Network Interface from Default to the physical name of the interface (which is the same device as there was only one network interface)
- Problem fixed, all clients start to see this PC as "online"

We need to chceck if there is any communication from the state server with a PC which is in this strange state.

Possible workarounds include:
1. Send a remote command like "Wake-On-Lan" which will:
* restart Remotly.exe from remote client
* perform host network interface switch remotely which seems to cure the problem locally
* Reboot the PC remotely
* Sign out from Windows user account remotely
2. Find and fix the problem which is very difficult as this is not happening often
 
You must log in or register to reply here.
Top