Forticlient EMS Web Access Doesn't Work After Upgrade

[alvarotorales]

Hi,

I upgraded my Forticlient EMS to the 7.4.5 version and now i can't access to the web portal. When i try to run the command "service restart --all" in the linux console i have the next error:

get services status: start apache2 service: exit status 1
exit error: [exit status 1], exitStatus: 1

Can someone help me with this issue please?

[AEK]

Hi Alvaro

What was the version of your EMS before the upgrade?

I hope you took a backup before the upgrade, just in case you can't fix it.

[alvarotorales]

Hi AEK, mi version before upgrade was VM 7.4.3.1926. 

I have the database backup, but I need to know if anyone has had a similar error and was able to resolve it, otherwise I'll have to revert to the previous version / snapshot.

[antonsp]

Same issue on my side.
Upgraded from 7.4.4 → 7.4.5, took a full DB backup beforehand.
After the upgrade, EMS stopped responding on HTTPS.
Tried console access  in TTY2, super-admin creds just wouldn’t authenticate.
Kept getting a login error, completely locked out.

[funkylicious]

hi, what do these commands show ?

systemctl status apache2

netstat -tulpn | grep apache

emscli service get apache2

emscli service log apache2 --follow

try maybe a systemctl restart apache2 and emscli service restart apache2

[alvarotorales]

Hi @funkylicious , i think that linux commands are unavailable on this new version of EMS 7.4.5.2111 (Mature)

ems@fcems-server $> systemctl status apache2
Error: unknown command "systemctl" for ""
Run ' --help' for usage.
unknown command "systemctl" for ""
exit error: [exit status 1], exitStatus: 1
ems@fcems-server $> netstat -tulp | grep apache
Error: unknown command "netstat" for ""
Run ' --help' for usage.
unknown command "netstat" for ""
exit error: [exit status 1], exitStatus: 1
ems@fcems-server $> emscli service get apache2
Error: unknown command "emscli" for ""
Run ' --help' for usage.
unknown command "emscli" for ""
exit error: [exit status 1], exitStatus: 1
ems@fcems-server $>
--help (help for this command)
cache (for querying the contents of the DAS cache)
config (for querying and updating EMS config files)
db (attempts to connect to the EMS DB using psql)
diag (for troubleshooting issues with particular endpoints)
execute (for executing commands on the host)
fds (for managing FDS (FortiGuard Distribution Servers) services)
ha (for checking and managing EMS High Availability parameters)
redirect (redirects an EMS instance to access a remote EMS DB instead of the local DB)
service (for querying and managing the statuses and log levels of EMS services)
system (for querying and updating system parameters on the machine where EMS is installed)
ws (Command used to run webservice operations (api.doc))

I try with this command that is available

ems@fcems-server $> service restart apache2
get services status: start apache2 service: exit status 1
exit error: [exit status 1], exitStatus: 1

[AEK]

Try the following command sequence.

service enable-debug apache2
service restart apache2
service get apache2
service log apache2
service disable-debug apache2

Ref:  https://docs.fortinet.com/document/forticlient/7.4.5/ems-cli-reference/546442/service

It should provide you with the error logs.

[alvarotorales]

Hi @AEK , i follow this steps and i attach here the error:

ems@fcems-server $> service enable-debug apache2
enable services debug: flip log level: exit status 2 -> output: psql: error: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: database "[DB_PREFIX]fcm" does not exist

exit error: [exit status 1], exitStatus: 1
ems@fcems-server $> service restart apache2
get services status: start apache2 service: exit status 1
exit error: [exit status 1], exitStatus: 1
ems@fcems-server $> service get apache2
[apache2] -> [PID: 1351074][failed] [Result: exit-code] [CPU: 0.0%, RAM: 0.0%] -> Tue 2025-12-23 11:25:29 UTC; 4s ago
ems@fcems-server $> service log apache2
==> /var/log/apache2/error.log <==
[Mon Dec 22 00:00:09.885366 2025] [ssl:warn] [pid 99982:tid 99982] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 22 00:00:09.885800 2025] [ssl:warn] [pid 99982:tid 99982] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 22 00:00:09.886040 2025] [remoteip:notice] [pid 99982:tid 99982] AH03492: RemoteIPProxyProtocol: enabled on 0.0.0.0:9443
[Mon Dec 22 00:00:09.886359 2025] [mpm_worker:notice] [pid 99982:tid 99982] AH00292: Apache/2.4.63 (Ubuntu) OpenSSL/3.1.7 mod_wsgi/4.9.4 Python/3.10 configured -- resuming normal operations
[Mon Dec 22 00:00:09.886368 2025] [core:notice] [pid 99982:tid 99982] AH00094: Command line: '/usr/sbin/apache2'
[Mon Dec 22 00:00:09.886385 2025] [mpm_worker:warn] [pid 99982:tid 99982] AH00291: long lost child came home! (pid 1026071)
[Mon Dec 22 00:00:09.886399 2025] [mpm_worker:warn] [pid 99982:tid 99982] AH00291: long lost child came home! (pid 1026072)
[Mon Dec 22 00:00:09.886412 2025] [mpm_worker:warn] [pid 99982:tid 99982] AH00291: long lost child came home! (pid 1026073)
[Mon Dec 22 00:00:09.886425 2025] [mpm_worker:warn] [pid 99982:tid 99982] AH00291: long lost child came home! (pid 1026074)
[Mon Dec 22 14:02:37.106873 2025] [wsgi:error] [pid 1048762:tid 1048766] INFO:_mod_wsgi_db83a6fdc62df21203c3601f8d239f0c:Checking database connection...
[Mon Dec 22 14:02:37.135635 2025] [wsgi:error] [pid 1048762:tid 1048766] INFO:_mod_wsgi_db83a6fdc62df21203c3601f8d239f0c:Database connection successful.
[Mon Dec 22 14:48:30.140660 2025] [mpm_worker:notice] [pid 99982:tid 99982] AH00296: caught SIGWINCH, shutting down gracefully
[Mon Dec 22 14:48:33.499818 2025] [core:warn] [pid 99982:tid 99982] AH00045: child process 1048763 still did not exit, sending a SIGTERM
[Mon Dec 22 14:48:35.501927 2025] [core:warn] [pid 99982:tid 99982] AH00045: child process 1048763 still did not exit, sending a SIGTERM
[Mon Dec 22 14:48:39.602523 2025] [ssl:warn] [pid 1068942:tid 1068942] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 22 14:48:39.602961 2025] [ssl:warn] [pid 1068942:tid 1068942] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 22 14:48:39.603218 2025] [remoteip:notice] [pid 1068942:tid 1068942] AH03492: RemoteIPProxyProtocol: enabled on 0.0.0.0:9443
[Mon Dec 22 14:48:39.609987 2025] [ssl:warn] [pid 1068948:tid 1068948] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 22 14:48:39.610454 2025] [ssl:warn] [pid 1068948:tid 1068948] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Mon Dec 22 14:48:39.610688 2025] [remoteip:notice] [pid 1068948:tid 1068948] AH03492: RemoteIPProxyProtocol: enabled on 0.0.0.0:9443
[Mon Dec 22 14:48:39.611477 2025] [mpm_worker:notice] [pid 1068948:tid 1068948] AH00292: Apache/2.4.63 (Ubuntu) OpenSSL/3.1.7 mod_wsgi/4.9.4 Python/3.10 configured -- resuming normal operations
[Mon Dec 22 14:48:39.611485 2025] [core:notice] [pid 1068948:tid 1068948] AH00094: Command line: '/usr/sbin/apache2'
[Mon Dec 22 14:48:39.943802 2025] [wsgi:error] [pid 1068955:tid 1068959] INFO:_mod_wsgi_db83a6fdc62df21203c3601f8d239f0c:Checking database connection...
[Mon Dec 22 14:48:39.965420 2025] [wsgi:error] [pid 1068955:tid 1068959] INFO:_mod_wsgi_db83a6fdc62df21203c3601f8d239f0c:Database connection successful.
[Mon Dec 22 14:49:14.821491 2025] [mpm_worker:notice] [pid 1068948:tid 1068948] AH00296: caught SIGWINCH, shutting down gracefully
ems@fcems-server $> service disable-debug apache2
disable services debug: flip log level: exit status 2 -> output: psql: error: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: database "[DB_PREFIX]fcm" does not exist

exit error: [exit status 1], exitStatus: 1

[AEK]

Here I note this error message.

exit status 2 -> output: psql: error: connection to server at "localhost" (127.0.0.1), port 5432 failed: FATAL: database "[DB_PREFIX]fcm" does not exist

It looks like the error is not in Apache itself but seems there is an error while connecting to the EMS DB. Sorry I have no idea on how to fix this. Hope other experienced member can help.

On the other hand you can try this command to see which services are down.

service status --all