FortiClient
FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
Anil_Solakoglu
Article Id 333080

Description

This article describes how to deal with the EMS console that is not reachable due to any timezone offset-related errors.  

Scope

FortiClient EMS Windows, Console.

Solution

To troubleshoot the issue diagnostic logs from EMS need to be collected in debug mode. The Python logs specifically contain similar logs about timezone offset that do not match.

 

Sample error: 

 

ValueError: Timezone offset does not match system offset: 7200 != 10800. Please, check your config files.\r

 

Anil_Solakoglu_0-1723634768847.png

 

There is a difference between actual time on the server time and expected value on the EMS server.

This could be caused by summertime zone differences on many occasions.

 

The issue occurs when the timezone offset is specified in the code and the actual timezone offset of the system or server where the code is running.

 

7200 Represents UTC +2.

 

1 Hour equals 3600 seconds.

 

So two hours represents 7200 seconds.

 

According to the calculation, the error message indicates the difference between time zones.

 

7200 != 10800

 

10800 represents UTC +3.

 

10800 – 7200 = 3600 Seconds.

 

3600 Seconds = 1 Hour.

 

To summarize in that sample Expected value for the EMS server is simply 7200 (UTC +2) and the server operates at 10800 (UTC +3).

 

To fix the issue:

 

The timezone needs to be adjusted to UTC +2 on the OS level to meet the expected value.

However, changing the timezone of the OS level will not be enough to change the EMS system time.

Since EMS applies timezone changes each time when the Apache service restarts.

To restart the server OS where EMS is installed completely will change the timezone on the EMS GUI as well.   

Alternatively stopping service without restarting the EMS server completely will do the same task as well.

 

CLI:

sc stop FCEMS_Monitor

sc stop FCEMS_Apache

Powershell:

 

Stop-Service -Name "FCEMS_Monitor"

Stop-Service -Name "FCEMS_Apache"

 

To Restart EMS services, it is only necessary to run the Monitor. It will start every service automatically through the CLI.

 

CLI:

 

sc start FCEMS_Monitor

 

PowerShell:

 

Start-Service -Name "FCEMS_Monitor"