All Collections
Knowledge Base
Enterprise Workloads
Troubleshooting - Enterprise Workloads
Fail to activate a Linux file server error Invalid argument error : Invalid timezone (#10000007f) (Error Code : PHOENIX127
Fail to activate a Linux file server error Invalid argument error : Invalid timezone (#10000007f) (Error Code : PHOENIX127
Updated over a week ago

Title

Fail to activate a Linux file server error Invalid argument error : Invalid timezone (#10000007f) (Error Code : PHOENIX127)

Problem description

The Linux file server fails to active due to invalid time zone on the server.

Cause

The server has incorrect time zone configuration, causing the 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). Traceback -Traceback (most recent call last):

File "roboCRoutines.py", line 127, in activate

File "roboCRoutines.py", line 216, in fs_activate

File "inSyncLib/inSyncRPCBase.py", line 680, in __call__

File "inSyncLib/inSyncRPCBase.py", line 1296, in _safe_request

File "inSyncLib/inSyncRPCBase.py", line 1302, in _issue_request

File "inSyncLib/inSyncRPCBase.py", line 858, in _issue_request

File "inSyncLib/inSyncRPCBase.py", line 900, in __wait_response

SyncError: Invalid argument error : Invalid timezone (#10000007f) (Error Code : PHOENIX127)

Resolution

- Verify the output for the command:

" cat /etc/sysconfig/clock "

ZONE=Europe/London

- Ran the below commands to update the zone to Europe/London

" mv /etc/localtime /tmp "

" ln -s /usr/share/zoneinfo/Europe/London /etc/localtime "

- Re-try the activation and it should complete successfully.

See also

Did this answer your question?