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

[Bas van den Dikkenberg]

I build opendnssec from source and are running it on VM (so hardware failure unlikly) the os is ubuntu. 


My systemd file looks like this:

[Unit]
Description=OpenDNSSEC Enforcer daemon
After=network.target mysql.service
ConditionPathExists=!/etc/opendnssec/prevent-startup
Requires=mysql.service

[Service]
Type=simple
EnvironmentFile=-/etc/default/opendnssec
EnvironmentFile=-/etc/default/opendnssec-enforcer
ExecStart=/usr/local/sbin/ods-enforcerd -d $DAEMON_ARGS $ODS_ENFORCERD_OPT
User=opendnssec
Group=opendnssec
RuntimeDirectory=opendnssec

[Install]
WantedBy=multi-user.target


So it should create the dir on start
-----Oorspronkelijk bericht-----
Van: Berry van Halderen <berry at nlnetlabs.nl> 
Verzonden: maandag 11 oktober 2021 09:32
Aan: Bas van den Dikkenberg <bas at dikkenberg.net>
CC: opendnssec-user at lists.opendnssec.org
Onderwerp: Re: [Opendnssec-user] cannot connect to command handler: connect() failed: No such file or directory

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 start.

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

Correct, it should be more informative.  The directory that is probably missing 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
   /var/run/opendnssec/enforcer.sock
So the directory /var/run/opendnssec should exist.

Some linux distributions clean out /var/run entirely upon reboot, so it is 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 nowadays also provide an RPM to mitigate problematic distribution.  Perhaps I should also provide another distribution package?

With kind regards,
\Berry


> 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