efa-project.org

Had a similar error during migration.

Simply changed the /root/ in the command to another directory I have write permission (my home). Later, in restore, I changed the last command in the guide replacing /root/... with this directory.

If I remember well, I worked in the admin user, so my home was ...

Too much time passed, could be I jumped a row :-( . I think is not possible to restore any more, high probability to disrupt a working server.

In any case, no damage, old V4 server is placed outside the mail path and replaced with the new V5. The V4 server is still working, just to access the old ...

Installed, configured and moved the eFa filter from v4 to v5 following your guide (https://wiki.efa-project.org/doku.php?id=efa_v4_to_v5_migration_guide).
Using "The following steps apply if you want to keep your quarantine " steps from the guide, I copied the old quarantine to the new server. The ...

NIce to hear.

I am not so used to RH family of distributions, so I have to ask: As I read around, seems to me Almalinux is also based on Network Manager (nmcli) as Centos Stream 9.

efa-Configure is still not ready (at least looking on github) for nm. Is your work running without eFa-Configure ...

Installed Centos Stream9 server.

All network connection definitions on my Centos stream 9 server (no GUI) have to be administered through NetworkManager (nmcli). The connection definitions are in the /etc/NetworkManager/system-connections directory.

The efa-Configure scripts and Menus (4 - IP ...

OK.

Just for info, error repeated today on update "eFa-1:4.0.4-39.eFa.el8.noarch"

Today, using the function 13 of the eFa Configuration program menu, during the update process i got the error:

Running scriptlet: eFa-1:4.0.4-38.eFa.el8.noarch 17/48
Upgrading : eFa-1:4.0.4-38.eFa.el8.noarch 17/48
Running scriptlet: eFa-1:4.0.4-38.eFa.el8.noarch 17/48

Preparing to update eFa ...

After days of uptime, the system crashed again, only once, 26. May. No new crashes after that, but I found (again) a error in the unbound log after start:

[root@mail crash]# systemctl status unbound
● unbound.service - Unbound recursive Domain Name Server
Loaded: loaded (/usr/lib/systemd/system ...

Are DNS requests being blocked by a firewall somewhere?

No, firewall and firewall logs are under my control, firewall opened to DNS and "green" in logs.
The unbound issue mentioned in last post was caused by a error in the routing tables in ISP routers network. After I notified them and they ...

No crashes from Apr. 26... system and efa filter stable, doing the work.
Tried to revert the MS Exchange NDR settings, had >180 mails in Postfix outbound queue, no problem.

Next days I will revert unbound config changes to check further.

Unbound proved last week to be extremely unstable as ...

Please keep us posted. I would like to recreate the conditions that caused this crash to improve the system.

Sure. I am here and I am watching last 5 days on logs, no crashes. As the side effect of finding causes I saw something in logs during restarts after crashes, we will discuss it later if ...

This is not an EFA problem, but highly likely a problem with your vm.

I am not very sure about this, I can't prove it, it is still a "sensation". Existing logs on previous restarts are always empty before the restart, so I have to wait the next crash.

Why I am not sure it is a infrastructure ...

VM settings:

Virtual network adapter type VMNEX3
SCSI Vmware paravirtual

lspci extract:

03:00.0 Serial Attached SCSI controller: VMware PVSCSI SCSI Controller (rev 02)
0b:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)

The machine and file systems are OK.

Restarts are in some way connected to the apps working on the system, but I have to find the connection. A proof is at Apr.20, when because of "Malformed Database" I had the clamd@scan service "activating", not active, and we had a crash / restart every few ...

Resources are not an issue, the eFa filter is running in a ESX VM on a blade server, so as first step I gave a lot computing resources: 4 cores, 16GB RAM.

The number of restarts is very high, but most of them are invisible to the whole system, the mail throughput is still not so high. At 20 Apr ...

From the installation day I can find a lot of "silent" and unsolicited restarts of the server, I have a lot of directories in /var/crash, about 3 to 5 a day.
Most of them are so short to be almost invisible to the user, but some of them had repercussions on delaying messages (msmilter service was ...

Just some words to introduce me, before I will begin to ask :D
Walter From Croatia, several years of experience in a field of system engineering, networking, and cybersecurity.
Recently I had to replace another mail filtering and Anti-X solution, so I choose to test and eventually implement the ...