[Pdns-users] remotebackend: Cannot connect to socket: No such file or directory

[Aki Tuomi]

This is why you should always use /run and not /tmp... Sockets belong under /run/<unit>/ in systemd world.

[Service]
RuntimeDirectory=remotebackend

..

and put socket to /run/remotebackend/remotebackend.sock

Aki


> On 05/04/2022 7:31 PM Mohamed Lrhazi via Pdns-users <pdns-users at mailman.powerdns.com> wrote:
> 
> 
> Oh, it was PrivateTmp=true in the systemd unit!!!!
> 
> 
> 
> 
> On Wed, May 4, 2022 at 12:22 PM Mohamed Lrhazi <lrhazi at gmail.com> wrote:
> > 
> > Hello,
> > 
> > Am stuck trying to get remote backend to work... error is :
> > 
> > May 04 12:13:28 ip-172-31-26-14.ec2.internal pdns_server[9515]: Cannot connect to socket: No such file or directory
> > 
> > pdns_server is running as user pdns and group pdns
> > 
> > the sock file does exist, and is also owned by pdns:pdns :
> > 
> > ls -l /tmp/remotebackend.sock
> > srwxrwxrwx 1 pdns pdns 0 May 4 12:01 /tmp/remotebackend.sock
> > 
> > strace shows the errors as well:
> > 
> > [pid 9521] write(2, "Reconnecting to backend\n", 24 <unfinished ...>
> > [pid 9519] poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1 <unfinished ...>
> > [pid 9521] <... write resumed> ) = 24
> > [pid 9521] socket(AF_UNIX, SOCK_STREAM, 0) = 16
> > [pid 9521] connect(16, {sa_family=AF_UNIX, sun_path="/tmp/remotebackend.sock"}, 110) = -1 ENOENT (No such file or directory)
> > [pid 9521] write(2, "Cannot connect to socket: No suc"..., 52) = 52
> > [pid 9521] close(16) = 0
> > 
> > I am using Amazon Linux.. pdns installed from EPEL... is there some chrooting done by pdns?
> > 
> > Thanks a lot,
> > Mohamed.
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users