[Opendnssec-user] cannot connect to command handler: connect() failed: No such file or directory

Berry van Halderen berry at nlnetlabs.nl
Mon Oct 11 07:32:29 UTC 2021

On 2021-10-09 13:35, Bas van den Dikkenberg via Opendnssec-user wrote:
> I have problem at random time my opendnssec shutdown some days not,
> some day's every 10 minutes.
> I see this in the log file:
> Oct  9 12:45:02 domein ods-enforcerd: [engine] cannot connect to
> command handler: connect() failed: No such file or directory
> Oct  9 12:45:02 domein ods-enforcerd: [engine] command handler self
> pipe trick failed, unclean shutdown

I'm also interested why your OpenDNSSEC shuts down, because that isn't 
normal.  I have this too at one of that machine, that shuts down every 
week, but I know that it because of hardware failure (the machine 
literally turns off).

But this isn't related to your problem where ods-enforcer fails to 

> It says an file or Dir is not here, but not witch one,

Correct, it should be more informative.  The directory that is probably 
is specified in your configuration file etc/opendnssec/conf.xml in the
section <Enforcer> and then <SocketFile>.  This is a file path, but the
directories above it should exist.  By default this would be
So the directory /var/run/opendnssec should exist.

Some linux distributions clean out /var/run entirely upon reboot, so it 
the distribution package itself that must ensure that the startup script
re-creates this directory.

Which distribution are you using, or it this a self-build package?  I 
also provide an RPM to mitigate problematic distribution.  Perhaps I 
also provide another distribution package?

With kind regards,

> Any ideas?
> I am running opendnssec version 2.1.10
> With kind regards,
> Bas van den Dikkenberg
> _______________________________________________
> Opendnssec-user mailing list
> Opendnssec-user at lists.opendnssec.org
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-user

More information about the Opendnssec-user mailing list