Exim4 related error

Hi dear hestia cp user and administrators. I show exim4 is not working but active when I see exim4 status from the server. How to fix it. Who has this condition occurred? Thank you in advance for the answer. (Yandex translator used)

Are you on Debian Buster? If the answer is yes, take a look to this post:

1 Like

Hello sir. I Have Ubuntu 20.04

Exim 4 status is active but v-list-sys-services is showing inactive in this case.

Hello @FirstCodersUz ,

That Ubuntu version has the same “problem” that Debian Buster, use the fix I posted above or wait till next HestiaCP update.


It didn’t work, I would be pleased if you had any other suggestions

Execute and show the output of:
pidof exim4 | tr ' ' '|'

And show the output of (the output would be a bit long):
bash -x /usr/local/hestia/bin/v-list-sys-services

“pidof exim4 | tr ’ ’ ‘|’” result empty

Next time, copy and paste the output and then select the pasted text and click on button </>, it is a pain to read text in schreenshots :slight_smile:

For some reason pidof is not detecting your exim4 pids.

Show the output of these commands please:

pidof -x exim4
ps -ef | grep [e]xim4
systemctl --no-pager status exim4

root@vps ~ # pidof -x exim4
root@vps ~ # ps -ef | grep [e]xim4
root@vps ~ # systemctl --no-pager status exim4
● exim4.service - LSB: exim Mail Transport Agent
Loaded: loaded (/etc/init.d/exim4; generated)
Active: active (exited) since Fri 2023-09-29 00:38:03 +05; 3 days ago
Docs: man:systemd-sysv-generator(8)
Process: 1284953 ExecStart=/etc/init.d/exim4 start (code=exited, status=0/SUCCESS)
Process: 3731456 ExecReload=/etc/init.d/exim4 reload (code=exited, status=0/SUCCESS)

Seems Ubuntu 20.04 uses sys v init scripts for exim and that active (exited) means systemd executed successfully /etc/init.d/exim4 start) but that doesn’t mean exim is running right now.

Are you sure exim is running?

ps -ef | grep -i exim
netstat -ptan | grep LISTEN | grep ':25\|:465\|:587'

Also, check eximlogs:


I saw clamav is not running too and if you configured exim to use it, maybe exim is not running because of that… just guessing.

root@vps ~ # ps -ef | grep -i exim
root 2834552 2790881 0 00:04 pts/3 00:00:00 grep --color=auto -i exim
root@vps ~ # netstat -ptan | grep LISTEN | grep ‘:25|:465|:587’
root@vps ~ #

“Active: active (exited) since Fri 2023-09-29 00:38:03 +05; 3 days ago” I thought this series would realize that exim4 is working.

Well, it’s clear, exim is not running.

service exim4 start

I think I will wait for the next update of hestia. Thank you for the time and answers you took :handshake:

But exim is not running, you won’t have mail in your server…