Another user on here mentioned his 512 MB RAM Digital Ocean droplet was only utilizing about 18% of memory so I’m starting to think my install is a bit d*cked. I ran htop and see multiple instances of various processes (screenshot attached). Any idea what is causing the duplication/unnecessary consumption of resources? I didn’t seem to have any issues upgrading my fresh Digital Ocean install to 1.2.1 and here are the steps I took, based off of my late night notes at the time:
**> Complete Digital Ocean install steps:
HowTo: Install Kegbot Server on Digital Ocean
Complete steps to upgrade from 1.1.1 to 1.2.1:
root@my-kegbot:~# su - kegbot
kegbot@my-kegbot:~$ . kegbot-server.venv/bin/activate
(kegbot-server.venv)kegbot@my-kegbot:~$ pip install --upgrade kegbot
(kegbot-server.venv)kegbot@my-kegbot:~$ kegbot upgrade
At this point after the upgrade and reboot, the web page will display 502 bad gateway errors. To get past this, modify the kegbot.conf file located in /etc/supervisor/conf.d/ to include the following statements:
group:kegbot]
programs=gunicorn,workers
[program:gunicorn]
command=/home/kegbot/kegbot-server.venv/bin/gunicorn pykeg.web.wsgi:application -w 3
directory=/home/kegbot
user=kegbot
autostart=true
autorestart=true
redirect_stderr=true
[program:workers]
command=/home/kegbot/kegbot-server.venv/bin/kegbot run_workers
directory=/home/kegbot
stopasgroup=true
user=kegbot
autostart=true
autorestart=true
redirect_stderr=true**
Perhaps I messed up the install and upgrade to 1.2.1, but I never got any error messages and everything seemed to work alright until I noticed the random unlogged pours and resource exhaustion. As always, thanks.
