Giters

pixelated / pixelated-dispatcher

Server component of Pixelated that allows running multiple instances of the user agent on a single server.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

admin should get an error if dispatcher-proxy waits for lock

cz8s opened this issue · comments

commented

Why

the dispatcher-proxy starts but does nothing and does not listen on port 8080 if there is a .lock file

Way to reproduce

  • stop dispatcher-proxy
  • create /var/run/pixelated/pixelated-dispatcher-proxy.pid.lock
  • start distpacher-proxy

outcome: dispatcher-proxy is running, but does not listen on port 8080. The output of
``netstat -tulpen | grep 8080`
is empty.

Definition of done

When starting dispatcher-proxy but a .lock file is already existing, the init-script should fail with an error.

commented

this might be the same for dispatcher-manager

commented

This is a good idea but it isn't our focus now.
Our focus now is the migration of Bitmask libraries latest version to Pixelated code.

I'll close this issue for now, it might be reopened in the future if it makes sense.