Coronium Core 2.1.1 is now live. This is a critical update release.
What’s new:
Full support for multiple applications with separate scope for users and metrics.
Webmin “Today” view for global application usage metrics for the current day.
If you have not created your own custom databases using 2.1.0 or don’t mind re-importing them, I highly recommend a fresh install of 2.1.1.
As noted in a previous post, an unfortunate bug was found that will require a fresh coronium administration database (this will not affect any user built databases). This bug has been resolved and this issue will not come up again in the future.
If you do opt to use the updater, be sure to backup your database or create a snapshot.
Documentation has been about 90% updated to reflect the changes, but the screencasts are out of date. I will be updating them over the next couple of days. Major changes in the Webmin are not fully reflected at this time. So feel free to post any questions until the docs are complete.
Decided to wipe it all and create a new droplet, as per your recommendation, but after 3 attempts to install it with mongo db, I keep ending up with a “An installation error occured, Please visit support at…” message.
I never get to the point where I am prompted for db passwords.
Any ideas?
EDIT, also get this at the top of the screen:
“up.sh: line 84: /usr/local/bin/coronium-dbsetup: No such file or directory”
It has something to do with whatever DigitalOcean is still doing in the background while the system is being initialized. I’ll see if I can work in some type of check, but the situation is random making it difficult to catch.
I think I do note in a screencast to give the instance a little bit of time to “warm” up.
I made some further tests and I suspect the reason for this is not what digitalocean does in the background, but that some process in your installer struggles on the 5$ droplet.
Here is what I did:
Created a 5$ droplet
Started your install script
On the “install mongoDB?” question I waited 23 minutes before I pressed n.
Installation failed.
Resized the droplet to the 10$ size (basically more RAM).
Started your install script
On the “install mongoDB?” question I immediately pressed n.
Installation completed successfully
I havent seen any posts from other users about this issue, which leads me to believe most create the 10$ droplet, as per your recommendation in the documentation.
You of course know better what goes on under the hood, but I bet you will be able to replicate this.
Not so sure thats the better approach, cause when its up and running, the 512MB droplet works fine.
Since you cannot resize a droplet down from the original size, it would be good for users to know that it is possible to use a 512MB droplet, as long as it is resized to 1024MB before installing. Thereafter, just resize it back to 512MB.
Decided to wipe it all and create a new droplet, as per your recommendation, but after 3 attempts to install it with mongo db, I keep ending up with a “An installation error occured, Please visit support at…” message.
I never get to the point where I am prompted for db passwords.
Any ideas?
EDIT, also get this at the top of the screen:
“up.sh: line 84: /usr/local/bin/coronium-dbsetup: No such file or directory”
It has something to do with whatever DigitalOcean is still doing in the background while the system is being initialized. I’ll see if I can work in some type of check, but the situation is random making it difficult to catch.
I think I do note in a screencast to give the instance a little bit of time to “warm” up.
I made some further tests and I suspect the reason for this is not what digitalocean does in the background, but that some process in your installer struggles on the 5$ droplet.
Here is what I did:
Created a 5$ droplet
Started your install script
On the “install mongoDB?” question I waited 23 minutes before I pressed n.
Installation failed.
Resized the droplet to the 10$ size (basically more RAM).
Started your install script
On the “install mongoDB?” question I immediately pressed n.
Installation completed successfully
I havent seen any posts from other users about this issue, which leads me to believe most create the 10$ droplet, as per your recommendation in the documentation.
You of course know better what goes on under the hood, but I bet you will be able to replicate this.
Not so sure thats the better approach, cause when its up and running, the 512MB droplet works fine.
Since you cannot resize a droplet down from the original size, it would be good for users to know that it is possible to use a 512MB droplet, as long as it is resized to 1024MB before installing. Thereafter, just resize it back to 512MB.