You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using docker-compose to setup NSQ according to here.
Additionally, I have add --data-path=/data/nsqd to nsqd node, and I got
FATAL: failed to instantiate nsqd - --data-path=/data/nsqd in use (possibly by another instance of nsqd)
According to source code, this may be caused by a dirlock opertion.
I've used auditctl -w /data/nsqd -p war -k whatsgoingon to monitor /data/nsqd, when someone touched (war: write/access/read) it, some log will print to /var/log/audit/audit.log.
I reastart the nsqd, but still got the same error (via docker-compose logs)
FATAL: failed to instantiate nsqd - --data-path=/data/nsqd in use (possibly by another instance of nsqd)
but no message showing in audit.log (via tailf /var/log/audit/audit.log | grep "whatsgoingon"). this means that during starting the nsqd, no one touched /data/nsqd.
I scraped the dir lock source code and build a test program, when os.Open("/data/nsqd"), the monitor shows the touch action as expected.
I wonder why nsq think someone touching the --data-path but acturally no one there, and this maybe a bug.
The text was updated successfully, but these errors were encountered:
mreiferson
changed the title
failed to instantiate nsqd - --data-path xxx possibly by another instance of nsqd
nsqd: failed to instantiate nsqd - --data-path xxx possibly by another instance of nsqd
Jun 14, 2020
docker version: Docker version 18.06.3-ce, build d7080c1
docker-compose version:
docker-compose version 1.17.1, build unknown
docker-py version: 2.5.1
CPython version: 2.7.15+
OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
host info: Ubuntu 18.04.3 LTS (ubuntu server)
I'm using docker-compose to setup NSQ according to here.
Additionally, I have add
--data-path=/data/nsqd
tonsqd
node, and I gotAccording to source code, this may be caused by a
dirlock
opertion.I've used
auditctl -w /data/nsqd -p war -k whatsgoingon
to monitor/data/nsqd
, when someone touched (war
:write/access/read
) it, some log will print to/var/log/audit/audit.log
.I reastart the
nsqd
, but still got the same error (viadocker-compose logs
)but no message showing in
audit.log
(viatailf /var/log/audit/audit.log | grep "whatsgoingon"
). this means that during starting thensqd
, no one touched/data/nsqd
.I scraped the dir lock source code and build a test program, when
os.Open("/data/nsqd")
, the monitor shows the touch action as expected.I wonder why nsq think someone touching the
--data-path
but acturally no one there, and this maybe a bug.The text was updated successfully, but these errors were encountered: