sock connection problem

[pindaroli]

Type: Bug Report

• Try to follow the update procedure described in the README and try again before opening this issue.

Your Environment

services:
flood:
hostname: flood
image: jesec/flood
user: 1000:1000
restart: unless-stopped
command: --port 3001 --allowedpath /data
environment:
HOME: /config

volumes:
  - /home/olindo/dlconf:/config
  - /home/olindo/drevo/rtorrent/data:/data
ports:
  - 3001:3001

rtorrent:
hostname: rtorrent
image: jesec/rtorrent
user: 1000:1000
restart: unless-stopped
command: -o network.port_range.set=6881-6881,system.daemon.set=true
environment:
HOME: /config
volumes:
- /home/olindo/dlconf:/config
- /home/olindo/drevo/rtorrent/data:/data
ports:
- 6881:6881

Summary

Doesn't add torrent i foun in the log:

Error: connect ECONNREFUSED /config/.local/share/rtorrent/rtorrent.sock
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1146:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '/config/.local/share/rtorrent/rtorrent.sock'
}

Expected Behavior

it connects and regulary work

Current Behavior

Possible Solution

Steps to Reproduce

Context

[trim21]

did you mount your socket file into flood container correctly？

maybe socket file is not located at /config/.local/share/rtorrent/rtorrent.sock of container, can you find it in your host dir /home/olindo/dlconf/.local/share/rtorrent/ ?.

[pindaroli]

added your suggest mapping and now:
rtorrent: Could not lock session directory: "/config/.local/share/rtorrent/.session/", held by "rtorrent-flood:+17".
Hint: use a consistent hostname so rTorrent can safely handle stale locks.
and now ?

[trim21]

I have no idea about this, you may need to see the document of rtorrent. Is there some old lock file exists? Or you are running multiple rtorrent instance?

[pindaroli]

No it's inside a docker container