timedatectl set-time freeze

[privalal]

Hi!
I'm using /usr/bin/timedatectl from the bash script.
In general it works fine, but the enduser has detected the one-time script hang during execution of the command:
/usr/bin/timedatectl set-time '2023-04-14 07:40:00'

The only found issue is in the daemon.log:
Apr 14 08:38:46 celab dbus[737]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30009ms)
Apr 14 08:38:56 celab systemd[1]: Time has been changed
Apr 14 08:39:26 celab dbus[737]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30009ms)
Apr 14 07:40:00 celab systemd[1]: Time has been changed
Apr 14 07:40:30 celab dbus[737]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30014ms)
Apr 14 08:40:21 celab systemd[1]: Time has been changed

What can be a root cause of this?

Thanks!!

PS
CentOS 7.9

[jlehtone]

Why do you set the time explicitly?

One could use system role https://access.redhat.com/documentation ... n-rhel-7.9 to set up time sync service (chrony by default) and then the service takes you to "current time".

[privalal]

Why do you set the time explicitly?

Machine works in the isolated network segment, no NTP servers available nearby.
User can change time through script (with gui fronted of course)..

[TrevorH]

Is it being run with root privileges? They will be required for timedatectl to do anything.

[privalal]

Is it being run with root privileges?

sure!
The stack:
User script -->
Application with suid bit (Access: (6775/-rwsrwsr-x) Uid: ( 0/root) Gid: ( 0/ root) -->
timedatectl.
It has executed ~100 times but 101 was fail. strange.