@girish For closure, this worked. Thank you!

So, I had to reinstall the OS on my VPS, and thought, 'no prob. I have my cloudron back upped to Exoscale.' The restore process goes well until "Looking to Restore". I enter all teh details and suddenly, this error" The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
What does this mean? Have I lost my Cloudron??
Thank you.

@subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:

docker update --memory "256mb" --memory-swap "1g" graphite

There is no need to restart anything after that?
Thank you so much to the help!

@subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:

docker stats graphite

Thank you for sharing this info. I see that my MEM USAGE was 72.6 / 75 MB limit, so that would indicate why it crashes. How do I increase the limit then?

Why would this happen? I have a VPS with 16 GB of RAM!

Is it because ssdnodes uses the XFS file system, and not ext4? Remember, the only way I could get Cloudron to install was to comment out the check for ext4 in the install script.

This is just one of a few issues that really bug me, and I wish I knew if it was something to do with XFS or something entirely different. I mean, 16 GB.... why would there be any problems running cloudron????

Thank you for looking into this.


Much thanks to @girish for helping me figure out what was wrong. Sendy (sendy.co) is working well in the LAMP app. Yay! It was simply an issue of changing the
$dbHost = 'localhost';

to

$dbHost = 'mysql';

@girish Hi, thank you for helping out. I understand that phpmyadmin requires the cloudron user/passwd, but the actual database info appears to be different. I ran sudo cloudron exec --app long-app-name env | grep MYSQL and it returned a db name, a user name, a password, and a MYSQL_URL (instead of localhost).

So the info would then look like?:

        $dbHost = getenv("mysql://username:password@mysql/database");
        $dbUser = getenv("username");
        $dbPass = getenv("password");
        $dbName = getenv("database");

I think the wording of Host is what's stopping the app from connecting to the db.
I heard from the sendy.co dev and he said that the following should not be altered, so I am not sure what to do. I will try your suggestion, and let you know if it worked or not.

/*  MySQL database connection credentials (please place values between the apostrophes) */
        $dbHost = 'localhost'; //MySQL Hostname
        $dbUser = 'mydbuser'; //MySQL Username
        $dbPass = 'mydnpasswd'; //MySQL Password
        $dbName = 'mydbname'; //MySQL Database Name

@girish Well, I managed to upload the files, and the populate the db, but I have some questions about the db side since I get an error stating the app can't reach the db.

The way the config file for sendy is written looks like this:

/*  MySQL database connection credentials (please place values between the apostrophes) */
        $dbHost = 'localhost'; //MySQL Hostname
        $dbUser = 'mydbuser'; //MySQL Username
        $dbPass = 'mydnpasswd'; //MySQL Password
        $dbName = 'mydbname'; //MySQL Database Name

The way cloudron's mysql add is written looks like this:

   getenv("MYSQL_HOST")
   getenv("MYSQL_PORT")
   gettenv("MYSQL_USERNAME")
   getenv("MYSQL_PASSWORD")
   getenv("MYSQL_DATABASE")

1. do I even need to use a username and password since phpmyadmin tells me there are no privileges, and I can't seem to add any. Or is the username/passwrd the cloudron username/passwrd?
2. How do I reconcile the two db configs? I am guessing that since they are written differently they won't be read the same?

Thank you.

@girish Well, the issue was that the install script was failing at a check for the file system to be ext4. I wrote alot with ssdnodes support and we missed each other's points, it seemed to me. Finally I mentioned that some site I read said Docker needed ext4, and they responded saying they've had no issue with customers running Docker (but did that mean there is no one running Docker, or that customers are running Docker but haven't had problems?). So to find out I went and installed Docker and it worked. Apparently it works on XFS if there is some device driver something or other, overlay2. I checked and the VPS from SSDnodes, while running XFS, did have that overlay2, and thus Docker was running. So that made me wonder why Cloudron wouldn't run. So I actually edited out the ext4 check in the install script, and every thing installed fine, and thus far is running fine, mostly. I have noticed the Graphs page sometimes freezes, and displays only the RAM portion (for example, I have 12 GB RAM free), not the Disk Usage.

So next I will try to migrate my sendy.co installation to the LAMP app on Cloudron.

Unfortunately I've run into a problem with the VPS from SSDnodes. I had used a VPS from them before for Cloudron and it worked fine. This time around the VPS differs somehow even though they say it is the same. The new VPS uses Virtuozzo for the KVM, and the disk is XFS. They claim all their VPSs are like this... so how did my Cloudron work last time on their machines? Anyways, I am trying to get that sorted out (isn't looking hopeful, just a lot of canned responses), so for now don't bother with SSDnodes for Cloudron.