Problem description
When attempting to activate a Linux File Server in the Phoenix Management Console, the activation fails with an "Invalid timezone" error. The issue is caused by an incorrect or unsupported timezone configuration on the server.
Cause
The Linux server is configured with an unsupported or incorrect timezone, which causes the Phoenix agent activation to fail.
Traceback
[2021-12-13 15:10:24,580] [INFO] Local time zone received local.
[2021-12-13 15:10:24,581] [INFO] timezone detected :zoneinfo/GB-Eire
[2021-12-13 15:10:24,874] [INFO] Server certificate for backup-phoenix.druva.com validated successfully.
[2021-12-13 15:10:24,874] [INFO] Using OpenSSL version OpenSSL 1.0.2y-fips 16 Feb 2021
[2021-12-13 15:10:24,874] [INFO] Connected to server using TLSv1.2
[2021-12-13 15:10:24,986] [ERROR] Error <class 'inSyncLib.inSyncError.SyncError'>:
Invalid argument error : Invalid timezone (#10000007f) (Error Code : PHOENIX127)
Resolution
Follow the steps below to correct the server timezone and complete activation:
Step 1: Verify Current Timezone
Run the following command to check the current timezone configuration:
cat /etc/sysconfig/clock
Expected Output
ZONE="Europe/London"
If the value is different or shows an unrecognized zone (e.g., GB-Eire), proceed to update the timezone.
Step 2: Update Timezone Configuration
Remove the current localtime setting:
mv /etc/localtime /tmp
Create a symbolic link to a valid timezone file:
ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
(Optional) Update /etc/sysconfig/clock to reflect the correct timezone:
echo 'ZONE="Europe/London"' > /etc/sysconfig/clock
Step 3: Retry Activation
Once the timezone is corrected, attempt to activate the Phoenix File Server agent again. The registration should complete successfully.
Best Practice
Ensure that the server timezone is configured using one of the valid entries from /usr/share/zoneinfo/. Avoid deprecated or region-specific aliases that may not be recognized by Druva Phoenix.