Coronium Core - Version 2.1.1 Critical Update

Third Party Coronium
#1

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.

There has been a major change in the client-side initialization, so please read about that in the documentation here: https://develephant.github.io/coronium-core-docs/client/guide/#application-scope

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.

Installation : https://develephant.github.io/coronium-core-docs/server/installation/digitalocean/

v2.1.0 Updater : https://develephant.github.io/coronium-core-docs/server/guide/updates/#210-to-211

Documentation : https://develephant.github.io/coronium-core-docs/

Plugin : https://marketplace.coronalabs.com/plugin/coronium-core

Let me know if you run into any issues. And again, my apologies for the database bug.

-dev

#2

Hi,

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”

#3

yeah im stuck  -_-

#4

I figured it out what happens and how to solve it.

When the question regarding mongoDB appear, do not answer at once.

Wait a while (i dont know how long is neccessary) before answering.

It seems the install file which fails need time to “appear” and that is what we need to wait for.

I suggest you add this to the install instruction in the documentation and/or fix it.

Now that I know what it is I also remember that I have the exact issue when I installed CC the first time around.

anaqim

#5

Hi,

My apologies for the delay.

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.

Glad it got worked out.

-dev

#6

Hi again,

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.

anaqim

#7

Hi,

I have had another user mention an issue on the 512MB droplet. I’ve changed the minimum droplet size to 1GB in the documentation.

Thanks for the reminder. 

-dev

#8

Hi,

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.

Anyway, my 2 cents.

#9

Hi,

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”

#10

yeah im stuck  -_-

#11

I figured it out what happens and how to solve it.

When the question regarding mongoDB appear, do not answer at once.

Wait a while (i dont know how long is neccessary) before answering.

It seems the install file which fails need time to “appear” and that is what we need to wait for.

I suggest you add this to the install instruction in the documentation and/or fix it.

Now that I know what it is I also remember that I have the exact issue when I installed CC the first time around.

anaqim

#12

Hi,

My apologies for the delay.

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.

Glad it got worked out.

-dev

#13

Hi again,

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.

anaqim

#14

Hi,

I have had another user mention an issue on the 512MB droplet. I’ve changed the minimum droplet size to 1GB in the documentation.

Thanks for the reminder. 

-dev

#15

Hi,

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.

Anyway, my 2 cents.