- User Since
- Nov 11 2014, 04:38 (213 w, 3 d)
Wed, Dec 12
Sun, Dec 9
(currently, the port doesn't answer anymore, you perhaps closed the old egg instance?)
Yes, there is already an eggdrop listening on this port:
It seems another process uses the port 2003.
So to avoid queue to be clobbered again: while sleep 30; do clear-video-queue; done &
Not related with Let's Encrypt the issue is with api51.
$ certbot renew ... The following certs were successfully renewed: /usr/local/etc/letsencrypt/live/infra.nasqueron.org/fullchain.pem (success) /usr/local/etc/letsencrypt/live/packages.nasqueron.org/fullchain.pem (success) ...
Shadow, fix test for 30 seconds
Sat, Dec 8
Backlog has been cleared, but I let this task open, as there is some actionable to follow-up, like write a postmortem.
Decrease a little bit the threshold, I've seen several times ffmpeg processes becoming quasi-zombies at 0:38 CPU time
Fix shadow use issues
To detect easily this situation in the future we can use this nagios check:
There are big ffmpeg video rendering tasks currently:
I restarted Sidekiq, it's currently processing new jobs. I'm watching the queues evolution, processed count increases, enqueued is currently stable.