search

sekai-soft / guide-nitter-self-hosting

A guide for self-hosting a Nitter instance
MIT License
154 stars 8 forks source link

Issues with Overmind (i think) #13

Closed WarningHPB closed 6 months ago

WarningHPB commented 6 months ago

Hi again,

I've having some issues starting the docker image, I have looked in some of the documentation that you do mention that some of the processes are "orchestrated by overmind" found on the following page: https://github.com/sekai-soft/nitter/blob/master/docs/self-contained-docker-image.md#how-to-use

I have checked the docker logs I get the alot of the following errors: 

Dumping auth env...
Dumping custom path env...
Dumping redis connection env...
Dumping instance customization env...
Dumping instance guardian env...
Writing Procfile...
system | Tmux socket name: overmind-src-nPcc0bznt9M4AaqUGQQeP
system | Tmux session ID: src
system | Listening at ./.overmind.sock
overmind: it looks like Overmind is already running. If it's not, remove ./.overmind.sock and try again

the socket name changes on them but the above are the last one of the messages.

I have tried looking for the "./.overmind.sock" to remove but could not find it.

I haven't changed anything since I have last turned on my raspberry pi, (I power off my pi when i don't need to use it for nitter or other things)

Any help would be appreciated!

KTachibanaM commented 6 months ago

This is super odd since the .overmind.sock is supposed to be ephemeral. Restarting the container should resolve your issue.

WarningHPB commented 6 months ago

I've tried running the command "docker restart nitter" and the same style of errors which I mentioned before appears when I run the "docker logs nitter" but with a differant Tmux socket name.

I've chosen the nuclear option which was to remove the docker image and start a fresh which seems to be back up and working currently.

Not sure if it was related but I did have brief power outage the night before, so don't know if that corrupted the docker image.

A-LAM-3 commented 4 months ago

I'm having the same issue. Whenever I restart Docker I get the same errors and Nitter won't start. I have to do a complete reinstall each time.

ac615223s5 commented 3 months ago

This happens for me whenever the system restarts without waiting for docker to close first. It only gets fixed after recreating the container.