No, but even it did it would be consistently different. So it’s not a two-clocks problem.
The actual clock in use will be that provided by the Java environment, which may or may not be the same as the host system.
But none of us can see that. What we can see is a message that your rule sent to the logger, and the logger then put a timestamp on it.
It’s not that uncommon to find timestamps arriving in the log file out of order when events occur close together, which is a good hint that the log timestamping is not quite as straightforward as it appears.
Tell us more about the scheduling that you think is going wrong. Tell us more about “Whenever I run it, it is working” - run how?. Which is related to what in the events log snippet?
May we know exactly what is not working?
It is very easy to inadvertently build rules in openHAB that are subject to race conditions, based on false assumptions about how it all works. I couldn’t say if that is your problem, as the nature of your real problem is a secret at the moment.
Example -
rule "race demo"
when
Item someItem received command
then
logInfo("test", "my state is " + someItem.state.toString)
logInfo("test" "but I expected it to be " + receivedCommand.toString)
end
The results may or may not be different.