|
If an error is encountered during EMS console access such as 'Error: An unexpected error occurred during startup. Please check the logs for details', follow these steps:
Ensure that all EMS services are running by executing the command:
systemctl --all --type=service | grep -E 'fcems|apache|redis|postgres'
If the services are up, examine the error log for any timezone-related errors:
Apache Logs:
sudo tar -czf /tmp/apache_logs.tar.gz /var/log/apache2
\apache_logs\error.log
[Thu May 20 00:00:06.231385 2025] [wsgi:error] [pid 164493:tid 164497] tzlocal.utils.ZoneInfoNotFoundError: 'Multiple conflicting time zone configurations found:\\n/etc/timezone: Etc/UTC\\n/etc/localtime is a symlink to: Europe/London\\nFix the configuration, or set the time zone in a TZ environment variable.\\n'
To Resolve Timezone Mismatch:
Step 1: Check the Current Timezone:
ls -l /etc/localtime
Something like:
lrwxrwxrwx 1 root root 32 Jan 1 12:34 /etc/localtime -> /usr/share/zoneinfo/Europe/London
Step 2: View the Content of /etc/timezone:
cat /etc/timezone
If this shows Etc/UTC, but /etc/localtime points to Europe/London, there is a mismatch.
Step 4: Set the Correct Timezone:
sudo timedatectl set-timezone Europe/London
To confirm the fix:
timedatectl
It should appear like this:
Time zone: Europe/London (BST, +0100)
When both the time zone and the local time are set to ETC/UTC, it is expected behaviour for EMS to be accessible after rebooting the machine.
Additional troubleshooting steps:
The issue may persist even after verifying that both command outputs below are the same:
cat /etc/timezone
ls -l /etc/localtime
If this is the case, it is likely that the tzdata package on the local server itself is somehow corrupted.
To resolve this, run the following command to reinstall the tzdata package:
sudo apt install --reinstall tzdata
After tzdata package is reinstalled, EMS console should be accessible.
|
