kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
<CaptainCalliope> Office hours call in about 40 minutes.
<CaptainCalliope> Unfortunately I won't be able to make it.
tet3 has joined #sandstorm
<tet3> Hello sandstormers! I was running sandstorm on a brand-new Ubuntu 18.04 VPS, and decided I wanted to run apps in Docker containers instead. I've uninstalled Sandstorm, but still have postgres, mongod, and node processes running under a '999' user, that were running under the sandstorm user before I deleted it.
<tet3> They restart on reboot or when killed. How do I get rid of them?
<abliss> something like `sudo service sandstorm disable` maybe?
<abliss> check for `/etc/systemd/system/sandstorm.service`
<abliss> I personally never figured out how the newfangled systemd stuff works, but if that's what's restarting it, I'm sure you can google for a tutorial on removing things from systemd.
<kentonv> tet3, Sandstorm doesn't use postgres, are you sure those processes came from Sandstorm?
<kentonv> tet3, does /opt/sandstorm still exist? If not, then those processes definitely couldn't be from Sandstorm...
<tet3> Ok - they are tied to the wekan Docker container, it turns out. But they were definitely running as the sandstorm user before. I did install wekan on Sandstorm, and then as a Docker container - could that be why it wants those processes to run as that user?
<tet3> I rm -rf'd /opt/sandstorm and rebooted again, which led me to start looking at the docker containers more closely
<kentonv> yes, when you had wekan running under Sandstorm, you probably would have seen a 'node' and a 'mongod' process as a result
<kentonv> of course, those would have been totally different installations of node and mongod
<kentonv> I don't think wekan uses postgres but there might be other apps that do
<tet3> right, I've got it now - I was just confusing the mongo and node processes I saw as 999 as being the ones that had been running under Sandstorm.
<kentonv> oh, and also sandstorm itself runs a 'node' and a 'mongod' process (but not postgres)
<tet3> Yeah, the postgres comes from miniflux. Ok, all sorted. Not Sandstorm, thanks for your help!
<kentonv> np
tet3 has left #sandstorm [#sandstorm]
<kentonv> (btw for others: sorry I'm not in the call, baby duty)
<isd> no worries
coyotebush has joined #sandstorm
michaeln3 has quit [Ping timeout: 260 seconds]
frigginglorious has quit [Ping timeout: 260 seconds]
frigginglorious has joined #sandstorm
nicooo has quit [Remote host closed the connection]
nicooo has joined #sandstorm
xet7 has quit [Remote host closed the connection]
xet7 has joined #sandstorm
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 260 seconds]
michaeln3 has joined #sandstorm
michaeln3 has quit [Remote host closed the connection]
michaeln3 has joined #sandstorm
michaeln3 has quit [Remote host closed the connection]
michaeln3 has joined #sandstorm
nicooo has quit [Ping timeout: 240 seconds]
nicooo has joined #sandstorm
nicooo has quit [Remote host closed the connection]
nicooo has joined #sandstorm
michaeln3 has quit [Remote host closed the connection]