Login to VLR using Admin user fails with error "Http failure response for request:Handlers/login: 0 Unknown Error"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• Login to VLR Appliance Management using Admin user fails with following error
  
  "Http failure response for request:Handlers/login: 0 Unknown Error"


• Following error is observed after VLR appliance reboot:
  
  
  
  
  
• Login with 'Admin' user through virtual console or SSH throws error : 
  "Login incorrect".
  
  
• No lock issue observed with Admin user as verified from GNU GRUB menu.
  
  
• Resetting the Admin user password from GNU GRUB menu fails to fix the login issue:
  Resetting/Unlocking admin & root account passwords on vSphere Replication & Site Recovery Manager
  
  
• Configured Custom SSL Certificates (Root, Intermediate and Server) for the VLR appliance are valid.
  
  
  
• dr-config.log reports Invalid login errors:
  
  (in /opt/vmware/support/logs/drconfigui/dr-config.log)

  YYYY-MM-DD HH:MM:SS,801 [srm-reactive-thread-11] WARN  com.vmware.dr.configservice.login.LoginHandler ########-####-####-####-############ login - DrRequestHandlerError:

  (drConfig.fault.InvalidLogin) {
   faultCause = null,
   faultMessage = null
}
        at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(Unknown Source)

Environment

• VMware Live Recovery 9.0.5

Cause

• Issue is caused due to System (Photon) clock failing to synchronize with NTP server time.
  
  (in /var/log/messages):
  
  2026-05-18T13:31:15.335218+10:00 BAIT-LSRS-PRV01 ntpd[13298]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
2026-05-18T13:31:15.301051+10:00 BAIT-LSRS-PRV01 startup.sh[1067]: 2026-05-18T13:31:15.300+10:00 verbose dr-backup[01658] [SRM@6876 sub=AsyncSi
teConnections.LocalSsoServer connID=sso-9a] DoPing: Ping succeeded
2026-05-18T13:31:15.334981+10:00 BAIT-LSRS-PRV01 ntpd[13298]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
  
  
  
• Same error is reflected in ntpd service status using systemctl:
  

  [ /var/log ]# systemctl status ntpd
ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systend/system/ntpd. service; enabled; preset: dis
Active: active (running) since Mon YYYY-MM-DD HH:MM:SS <time-zone>; ##min ago
Docs: man:ntpd
Process: 1231 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/
Main PID: #### (ntpd)
Tasks: 2 (limit: 28796)
Memory: 2.4M
CPU: 115ms
CGroup: /system.slice/ntpd.service
L1265 /usr/bin/ntpd -g -u ntp:ntp

  MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: gps base set to YYYY-MM-DD (week ####)
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: Listen and drop on 0 v6wildcard [::]:123
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: Listen and drop on 1 v4wildcard 0.0.0.0:123
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: Listen normally on 2 lo #.0.0.1:123
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: Listen normally on 3 eth0 #.#.#.#:123
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: Listen normally on 4 lo [::1]:123
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: Listening on routing socket on fd #21 for interface updates
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
MTH DD HH:MM:SS <VLR-FQDN> ntpd[1265]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

Resolution

• Perform following steps to resolve the issue:

1. 1. Take snapshot of VLSR appliance.

       

   2. Stop the NTP service:
      # systemctl stop ntpd

       

   3. Remove the existing drift file: 
      # rm /var/lib/ntp/drift/ntp.drift

       

   4. Force an immediate time step: 
      # ntpdate -b -u [NTP_IP]

      (Note : Run this command for all NTP servers if there are multiple configured.)

       

   5. Start the NTP service:
      # systemctl start ntpd

       

   6. Verify synchronization status:
      # ntpq -p