<ert>
anyone getting an issue with sandstorm where the it says sandstorm is started then you do a status and it says sandstorm is not running?
ill_logic has joined #sandstorm
<TimMc>
Anything in the logs?
<ert>
yes - it says mongodb fails, but nothing in the mongo logs
<ert>
**mongod failed to start. Initial exit code: ; status = 1; bailing out now.
<ert>
that is from sandstorm log
<TimMc>
Hmm. Port collision? Corrupted files? Mongo probably has its own logs.
<ert>
where would those logs be located on a ubuntu install
<ert>
i just ran the default sandstorm install curl bash script
<ert>
and edited the config
<ert>
should be all defaults for the DB config
<TimMc>
I can check my own box.
<TimMc>
sandstorm/var/log/mongo.log
<ert>
yes - that is the log that did not get updated
<ert>
so it points me to that log in the sandstorm error log, but then there is no new message there about why the mongodb did not work
<TimMc>
Hmm. Hopefully someone who knows more about mongo (or sandatorm) will come along. (There's also the mailing list, if it comes to that.)
<ert>
have you ever had to do a fresh install and load in backups?
dwrensha has quit [Quit: Lost terminal]
<ert>
can you tell me your folder permissions structure? This might be what I altered recursively that messed up application access
xet7 has quit [Quit: Leaving]
xet7 has joined #sandstorm
<TimMc>
Yeah, I restored from backup when I moved to a new server.
<TimMc>
You could do a fresh install in another dir and check that the permissions are the same.
Telesight has joined #sandstorm
<ert>
when you load the backups on another server, will users be able to login just the same?
<TimMc>
Sure, as long as the hostname is the same.
<TimMc>
(and ports)
<TimMc>
Just make sure sandstorm is fully stopped before taking the backup.
<TimMc>
(Or make sure to take backups using a snapshotting filesystem.)
<ert>
is there a step by step on the first option? I was thinking I could just load the backup file in via sandstorm while it was up and running. Doesn't seem like that is what I am after.
<TimMc>
Sandstorm docs do have instructions on this.
ecloud has quit [Quit: No Ping reply in 210 seconds.]
ecloud has joined #sandstorm
ecloud has quit [Ping timeout: 240 seconds]
ecloud has joined #sandstorm
deep-book-gk_ has joined #sandstorm
deep-book-gk_ has left #sandstorm [#sandstorm]
<ert>
well I followed that guide and I do not see my grains in the new install
<ert>
I get an error when I try to load the backup in the sandstorm environment
<ert>
Error: remote exception: Peer disconnected.
<ert>
at Error (native)
<ert>
type: disconnected
<ert>
C++ location:(remote):??
<TimMc>
Huh.
<ert>
I think I solved this one, the folder copied to the wrong dir.
<ert>
now the grain overview page looks right and the settings and users
<TimMc>
yay!
<ert>
the problem though is the grains won't open
<ert>
Error: remote exception: expected result >= minBytes; Premature EOF
<ert>
and the 'Size' column in the grain listing has the correct sizes of several MB
demonimin has quit [Ping timeout: 260 seconds]
demonimin has joined #sandstorm
<ert>
I did a fresh install on another computer and tried this backup copy method, but I am not sure if this means I need to do the "Run the install script, and allow it to configure a systemd/sysvinit service." step
strugee has quit [Ping timeout: 246 seconds]
strugee has joined #sandstorm
<ert>
is there a way to remove the grains from the backup?
xet7 has quit [Ping timeout: 248 seconds]
Telesight has quit [Remote host closed the connection]
xet7 has joined #sandstorm
xet7 has quit [Remote host closed the connection]
dwrensha has joined #sandstorm
<ert>
any way to force the grains to delete and wipe them out completely?
dwrensha has quit [Quit: Lost terminal]
<ert>
just seems like oasis site functions work fine, but I cannot get them working locally