We’ve faced an issue with LexFloatServer instance we use for testing purposes. It’s installed on Windows 7 x64 VM instance, which is running 24/7. The problem is that after certain period of time it starts declining lease requests with the following error in logfile:
System Time Modification Detected: 1369
The only assumption I have why this is happening is that LexFloatServer probably doesn’t handle network time synchronization properly.
Could you pls, explain why this could happen and how to overcome this? Thank you.
Are you sure the VM is running 24/7, it happens when your machine sleeps, which pauses the LexFloatServer clock and hence it goes out of sync from your local clock.
Also we’ve ensured that VM is not getting to sleep mode and the time modification problem hasn’t gone. Then we tried to install LexFloatServer on a dedicated hardware, and the issue appeared again in a few hours. Logfile contains the following entries:
2017-04-05, 09:43:59 License Request from: 10.10.101.64
2017-04-05, 09:43:59 System Time Modification Detected: 215
2017-04-05, 09:44:04 License Request from: 10.10.101.64
2017-04-05, 09:44:04 System Time Modification Detected: 215
2017-04-05, 09:47:21 Error: Service control interrogate message by service manager
2017-04-05, 09:47:21 Error: Service control interrogate message by service manager
2017-04-05, 09:47:21 Error: Service control interrogate message by service manager
2017-04-05, 09:49:25 License Request from: 10.10.101.64
2017-04-05, 09:49:25 System Time Modification Detected: 216
Please note how seconds counter (?) increases by one in 5 minutes.
The error logged actually doesn’t affect LexFloatServer. It was recently added to check the issue of LexFloatServer not starting on startup. The service manager on your computer is trying to stop the service, it sometimes occurs due to firewall issues.
2017-04-09, 16:21:48 Info: Starting Floating License Server …
Which is the last time LexFloatServer started - just after the last restart event logged in the event log.
A bit later the following happens:
2017-04-10, 10:07:32 System Time Modification Detected: 134
… and on the next day…
2017-04-11, 10:59:54 System Time Modification Detected: 326
So this proves that:
Machine with LexFloatServer is running since 2017-04-09 16:03 without any interruptions.
LexFloatServer starts reporting system time modification error from 2017-04-10, 10:07.
A difference (in seconds?) between system clock and internal LexFloatServer clock is constantly increasing over time.
Apparently that’s all I can do to investigate the problem on my side - now I would really appreciate thorough investigation on yours.