NocoDB is an open source #NoCode platform that turns any database into a smart spreadsheet.

https://www.nocodb.com
https://github.com/nocodb/nocodb

WizNote is a Evernote alternative

Docker image of WizNote Server free

Hi guys,

The fastest way to migrate any WordPress installation to Cloudron is very simple:

1. Export the /wp-content/ folder on the origin server to a wp-content.zip file
2. Export the database on the source server to a .sql file. In phpmyadmin, select all the tables, and export to bbdd.sql
3. Create a clean install of WordPress on the target Cloudron
4. Once created, go to the file manager of the Cloudron WordPress installation and into the /public/ folder:

• upload the wp-content.zip file
• delete existing /wp-content/ folder
• unzip the file wp-content.zip
• change ownership to www-data from /wp-content/ folder which has been unzipped

5. Finally, upload the .sql file of the database from step 2 to the path /app/data/

After this, all that remains is to migrate the database. To do this, go to the application console in Cloudron. Once in it, you just have to type:

cd ..

cd data

wp db reset

wp db import bbdd.sql

With this, the migration is complete.

@girish Thanks!

You just have to use the command in the server terminal to identify the host IP.

docker inspect mysql | grep IPAddress

With this and with the credentials of the application database, you can connect Redash.

NocoDB is an open source #NoCode platform that turns any database into a smart spreadsheet.

https://www.nocodb.com
https://github.com/nocodb/nocodb

@girish Thanks!

Hi guys,

The fastest way to migrate any WordPress installation to Cloudron is very simple:

1. Export the /wp-content/ folder on the origin server to a wp-content.zip file
2. Export the database on the source server to a .sql file. In phpmyadmin, select all the tables, and export to bbdd.sql
3. Create a clean install of WordPress on the target Cloudron
4. Once created, go to the file manager of the Cloudron WordPress installation and into the /public/ folder:

• upload the wp-content.zip file
• delete existing /wp-content/ folder
• unzip the file wp-content.zip
• change ownership to www-data from /wp-content/ folder which has been unzipped

5. Finally, upload the .sql file of the database from step 2 to the path /app/data/

After this, all that remains is to migrate the database. To do this, go to the application console in Cloudron. Once in it, you just have to type:

cd ..

cd data

wp db reset

wp db import bbdd.sql

With this, the migration is complete.

In the rClone documentation I see that there is the following flag that may solve the writing problem of box.tar.gz:

--delete-before          When synchronizing, delete files on destination before transferring

I will change the mount command within the crontab and launch a new test to see if it is corrected that way.

Thanks for the help @nebulon

@nebulon Yes, the drive mounts automatically every time the server is rebooted via crontab.

I have rebooted the server, removed several heavy applications from the backup (to rule out memory issues) and the only LAMP application containing non-Cloudron code.

The result of the new backup is the same, the error occurs when saving the file /mnt/backups/snapshot/box.tar.gz

Mar 24 16:11:15 box:shell backup-snapshot/box spawn: /usr/bin/sudo -S -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/box tgz {"localRoot":"/home/yellowtent/boxdata","layout":[]}
Mar 24 16:11:16 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:16.764Z box:backupupload Backing up {"localRoot":"/home/yellowtent/boxdata","layout":[]} to snapshot/box
Mar 24 16:11:16 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:16.817Z box:settings initCache: pre-load settings
Mar 24 16:11:16 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:16.834Z box:backupupload process: rss: 73887744 heapTotal: 55631872 heapUsed: 22185072 external: 1840481
Mar 24 16:11:16 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:16.834Z box:backupupload v8 heap : used 22189400 total: 55631872 max: 4345298944
Mar 24 16:11:16 box:backups upload: id snapshot/box format tgz dataLayout {"localRoot":"/home/yellowtent/boxdata","layout":[]}
Mar 24 16:11:16 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:16.847Z box:storage/filesystem checkPreconditions: getting disk usage of /home/yellowtent/boxdata
Mar 24 16:11:16 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:16.859Z box:storage/filesystem checkPreconditions: 3872786 bytes
Mar 24 16:11:18 box:tasks 359: {"percent":97.875,"message":"Uploading backup 1M@1MBps (box)"}
Mar 24 16:11:18 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:18.267Z box:storage/filesystem upload /mnt/backups/snapshot/box.tar.gz: done.
Mar 24 16:11:18 box:shell backup-snapshot/box (stdout): 2021-03-24T15:11:18.267Z box:backupupload upload completed. error: null
Mar 24 16:11:18 box:backups runBackupUpload: result - {"result":""}
Mar 24 16:11:19 box:backups uploadBoxSnapshot: took 3.414 seconds
Mar 24 16:11:19 box:backups Rotating box backup to id 2021-03-24-145230-064/box_2021-03-24-151119-388_v6.2.4
Mar 24 16:11:19 box:tasks 359: {"percent":97.875,"message":"box: Copying /mnt/backups/snapshot/box.tar.gz to /mnt/backups/2021-03-24-145230-064/box_2021-03-24-151119-388_v6.2.4.tar.gz"}
Mar 24 16:11:19 box:shell copy spawn: /bin/cp -a /mnt/backups/snapshot/box.tar.gz /mnt/backups/2021-03-24-145230-064/box_2021-03-24-151119-388_v6.2.4.tar.gz
Mar 24 16:11:37 box:shell copy (stdout): /bin/cp: error reading '/mnt/backups/snapshot/box.tar.gz': Input/output error
Mar 24 16:11:37 box:shell copy code: 1, signal: null
Mar 24 16:11:37 box:taskworker Task took 1147.049 seconds
Mar 24 16:11:37 box:tasks setCompleted - 359: {"result":null,"error":{"stack":"BoxError: copy exited with code 1 signal null\n at /home/yellowtent/box/src/storage/filesystem.js:203:51\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:315:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)","name":"BoxError","reason":"External Error","details":{},"message":"copy exited with code 1 signal null"}}
Mar 24 16:11:37 box:tasks 359: {"percent":100,"result":null,"error":{"stack":"BoxError: copy exited with code 1 signal null\n at /home/yellowtent/box/src/storage/filesystem.js:203:51\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:315:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)","name":"BoxError","reason":"External Error","details":{},"message":"copy exited with code 1 signal null"}}

Is this file the only one to be replaced? Is that so?

Could it be that when it is replaced (and a new one is not generated like the rest of the application files) it may give an error due to the time lag in the synchronization with Google Drive through rClone?

What I do not know is why this error has started to occur for two days, when the copy system has worked well in the previous days ...

The backup system configuration is as follows:

The folder has a Google Drive team drive mounted with rClone to store the backups.

It has been working normally from the beginning except for the last two days, which is when it has started to give this error.

Cloudron is already updated to version 6.2.4

Hi guys

In the last two days I am getting the following 'Failed to backup' email with the following text:

Cloudron failed to create a complete backup. Please see https://docs.cloudron.io/troubleshooting/#backups for troubleshooting.

Checking the backup system, I verify that the backup has been generated in all the applications, but in the Cloudron backups section the error 'copy exited with code 1 signal null' appears.

Reviewing the log, these are the last lines that show where the failure occurs:

Mar 24 11:58:36 box:tasks 356: {"percent":97.875,"message":"box: Copying /mnt/backups/snapshot/box.tar.gz to /mnt/backups/2021-03-24-101056-946/box_2021-03-24-105836-281_v6.2.4.tar.gz"}
Mar 24 11:58:36 box:shell copy spawn: /bin/cp -a /mnt/backups/snapshot/box.tar.gz /mnt/backups/2021-03-24-101056-946/box_2021-03-24-105836-281_v6.2.4.tar.gz
Mar 24 11:58:46 box:shell copy (stdout): /bin/cp: error reading '/mnt/backups/snapshot/box.tar.gz'
Mar 24 11:58:46 box:shell copy (stdout): : Input/output error
Mar 24 11:58:46 box:shell copy code: 1, signal: null
Mar 24 11:58:46 box:taskworker Task took 2869.561 seconds
Mar 24 11:58:46 box:tasks setCompleted - 356: {"result":null,"error":{"stack":"BoxError: copy exited with code 1 signal null\n at /home/yellowtent/box/src/storage/filesystem.js:203:51\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:315:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)","name":"BoxError","reason":"External Error","details":{},"message":"copy exited with code 1 signal null"}}
Mar 24 11:58:46 box:tasks 356: {"percent":100,"result":null,"error":{"stack":"BoxError: copy exited with code 1 signal null\n at /home/yellowtent/box/src/storage/filesystem.js:203:51\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)\n at ChildProcess.emit (events.js:315:20)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)","name":"BoxError","reason":"External Error","details":{},"message":"copy exited with code 1 signal null"}}

Apparently, the failure occurs when the Cloudron itself is backed up, since as I said before, the copies of all the applications are made.

Any hints or suggestions to solve the problem?

Thanks.

Thanks @girish. But I have a question. The source Moodle is on a different server than Cloudron's Moodle ... it's a server with a Plesk panel

In that case, how can the source installation identify which server to send the data to? Wouldn't it be necessary to indicate the IP of the destination server? Or the socket? If I only indicate postgresql, I don't think the data can be migrated from one server to another ... right?

The query

env | grep POSTGRESQL

in the terminal returns the following values:

CLOUDRON_POSTGRESQL_URL=postgres://...
CLOUDRON_POSTGRESQL_DATABASE=
CLOUDRON_POSTGRESQL_PASSWORD=
CLOUDRON_POSTGRESQL_USERNAME=
CLOUDRON_POSTGRESQL_HOST=postgresql
CLOUDRON_POSTGRESQL_PORT=5432

But what is the value to be entered in the 'Server' field? The IP of the server? Socket IP? Domain?

Thanks for the help guys!

You just have to use the command in the server terminal to identify the host IP.

docker inspect mysql | grep IPAddress

With this and with the credentials of the application database, you can connect Redash.