-
-
Notifications
You must be signed in to change notification settings - Fork 708
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installer not working: couldn't add user: not authorized on admin #3662
Comments
Did you get anything in that sandstorm.log file? It looks like the failure was maybe in reaching Let's Encrypt here? EDIT: I see you edited that in, sorry! Thanks. |
It looks like the problem is with the command line parameters passed to the bundled But in the process I have now created a dozen ddns urls that I can't seem to recover. But maybe with I am guessing mongodb needs to work for certbot etc. to work too? If that's the case, maybe bail out sooner if mongo isn't working? Thanks anyways. My recommendation is add automated testing inside docker from clean OS installs. Maybe it's something I can contribute? |
Scrap that... it installed some things and now is looping with:
(This all the while Mongodb was still running without --auth on port 6081) |
I think we would definitely appreciate improvements to installer testing. We have the installer-tests folder, but I don't believe it's part of CI at all, and it currently only tries some very old versions of Linux. It looks like someone started working on it last year, and mentioned following it up, but I don't see that having happened... What's also intriguing is that I can't find anything that seems like it should've impacted anything in the latest release relating to this, our Mongo setup hasn't changed much in... a long time... and it's generally worked for people pretty well, this seems to be a new issue. (FWIW, Sandcats does not care about extraneous DDNS URLs. If you don't care about them, neither do we! Your install is only using one.) |
First mongo log: (from initial install)
The log during what seemed to be working - but obviously didn't
And then the logs from sandstorm trying to start mongo while it's already running.
Looks like some initial mongodb initialization or admin and sandcats user creation failed. Can I initiate it manually? Or what version should I go back to? I don't see anything obvious in the commits that touched this... but I'm not familiar with the codebase. |
How much memory does the machine have? On smaller boxes we've had problems with things being OOM killed on startup. I'd hoped #3637 would hae fixed that, but maybe not. We generally recommend at least 2GiB, though what you need will depend on how many grains you expect to be running concurrently. You shouldn't need that much just for install but if my fix was inadequate that could be the issue here too. |
This is a hosted VM. The development installations works fine in Docker. I've been familiarizing myself by trying a few so I can contribute automated tests. |
The text was updated successfully, but these errors were encountered: