Where is my error ??? ( i need your eyes)

[UnclePhil]

TAG: latest, 3.6.1, 3.5.0 , 3.3.5 -same error-

Even if i put all data to connect to a local minio instance, the dbcopy try to go to amazon

I dont' understand why this happens and why it was working on preceding (but unknow tag) instance.

here some docker exec to show it

docker exec 5ef9dcfd2a05 env

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=5ef9dcfd2a05
BACKUP_LOCATION=minio

... DBDEF 

S3_BUCKET=dbbackup
S3_HOST=192.168.1.4:9000
S3_KEY_ID=REMOVED
S3_KEY_SECRET=REMOVED
S3_PATH=nextcloud
S3_PROTOCOL=http
S3_REGION=home
... 

docker exec 5ef9dcfd2a05 backup-now

Performing Manual Backup
2022-12-03.12:58:19 [NOTICE] ** [db-backup] Dumping all MySQL / MariaDB databases: 'nextcloud' and compressing with 'xzip'
2022-12-03.12:58:19 [INFO] ** [db-backup] DB Backup of 'mysql_all_db_20221203-125819.sql.xz' completed successfully
2022-12-03.12:58:19 [NOTICE] ** [db-backup] Generating MD5 for 'mysql_all_db_20221203-125819.sql.xz'
2022-12-03.12:58:19 [NOTICE] ** [db-backup] Backup of mysql_all_db_20221203-125819.sql.xz created with the size of 29352 bytes
2022-12-03.12:58:33 [NOTICE] ** [db-backup] DB Backup for 'all' time taken: Hours: 0 Minutes: 00 Seconds: 14
2022-12-03.12:58:33 [INFO] ** [db-backup] Backup routines finish time: 2022-12-03 12:58:33 GMT with overall exit code 0
2022-12-03.12:58:33 [NOTICE] ** [db-backup] Backup routines time taken: Hours: 0 Minutes: 00 Seconds: 14
2022-12-03.12:58:33 [INFO] ** [db-backup] Cleaning up old backups on S3 storage

Could not connect to the endpoint URL: "http://s3.here.amazonaws.com/dbbackup?list-type=2&prefix=nextcloud%2F&delimiter=%2F&encoding-type=url"

[UnclePhil]

after another code review ,
it seems that the variable PARAM_AWS_ENDPOINT_URL is not defined when in the cleaning routine - cleanup_old_data() - , and so aws binary go directly to public host

Is this "normal" or a .... problem ??

[tiredofit]

This definitely looks like a problem, not by design.

So if I am to understand here your backups work however the cleanup does not.

[UnclePhil]

Yep, backup files are created, but the cleaning stuck, and then the upload is not done. So no effective backup. And i'm sure that july version was working. but i cannot say wich tag it was.

[tiredofit]

OK, Please try tiredofit/db-backup:develop and try your manual backup now. I am interested to see the output. If you need to mask things like your s3 bucket feel free, but I am very interested in the raw output that comes out.

[UnclePhil]

Same problem , i think it's coming from aws binary

** Performing Manual Backup
2022-12-04.15:00:54 [NOTICE] ** [db-backup] Dumping all MySQL / MariaDB databases: 'nextcloud' and compressing with 'xzip'
2022-12-04.15:00:54 [INFO] ** [db-backup] DB Backup of 'mysql_all_db_20221204-150054.sql.xz' completed successfully
2022-12-04.15:00:54 [NOTICE] ** [db-backup] Generating MD5 for 'mysql_all_db_20221204-150054.sql.xz'
2022-12-04.15:00:54 [NOTICE] ** [db-backup] Backup of mysql_all_db_20221204-150054.sql.xz created with the size of 29228 bytes
2022-12-04.15:01:08 [NOTICE] ** [db-backup] DB Backup for 'all' time taken: Hours: 0 Minutes: 00 Seconds: 14
2022-12-04.15:01:08 [INFO] ** [db-backup] Backup routines finish time: 2022-12-04 15:01:08 GMT with overall exit code 0
2022-12-04.15:01:08 [NOTICE] ** [db-backup] Backup routines time taken: Hours: 0 Minutes: 00 Seconds: 14
+ '[' -n 8640 ']'
+ '[' 0 '!=' 1 ']'
+ case "${BACKUP_LOCATION,,}" in
+ print_info 'Cleaning up old backups on S3 storage'
+ output_off
+ '[' false = true ']'
+ '[' false = true ']'
+ '[' '' = false ']'
++ log_prefix
++ output_off
++ '[' false = true ']'
++ '[' true = true ']'
+++ date +%Y-%m-%d
+++ date +%H:%M:%S
++ echo '2022-12-04.15:01:08 '
++ output_on
++ '[' false = true ']'
+ echo -e '2022-12-04.15:01:08 \e[42m[INFO]\e[49m ** [db-backup] Cleaning up old backups on S3 storage'
2022-12-04.15:01:08 [INFO] ** [db-backup] Cleaning up old backups on S3 storage
++ log_prefix
++ output_off
++ '[' false = true ']'
++ '[' true = true ']'
+++ date +%Y-%m-%d
+++ date +%H:%M:%S
++ echo '2022-12-04.15:01:08 '
++ output_on
++ '[' false = true ']'
++ basename /etc/services.available/10-db-backup/run
+ echo -e '2022-12-04.15:01:08 [INFO] /etc/services.available/10-db-backup/run ** [db-backup] Cleaning up old backups on S3 storage'
+ output_on
+ '[' false = true ']'
+ grep ' DIR ' -v
+ grep ' PRE ' -v
+ aws --endpoint-url http://192.168.1.4:9000 s3 ls s3://dbbackup/nextcloud/
+ read -r s3_file

Could not connect to the endpoint URL: "http://s3.here.amazonaws.com/dbbackup?list-type=2&prefix=nextcloud%2F&delimiter=%2F&encoding-type=url"
+ set +x

I think this is becoming from the aws binary, because when i force the aws credentials variables , and run the same command

dk exec f3d3c663a87b aws --endpoint-url http://192.168.1.4:9000 s3 ls s3://dbbackup/nextcloud

Could not connect to the endpoint URL: "http://s3.here.amazonaws.com/dbbackup?list-type=2&prefix=nextcloud%2F&delimiter=%2F&encoding-type=url"

I've the same result

[UnclePhil]

I'll do that tomorrow .... Le sam. 3 déc. 2022, 22:59, Dave Conroy ***@***.***> a écrit :

…

OK, Please try tiredofit/db-backup:develop and try your manual backup now. I am interested to see the output. If you need to mask things like your s3 bucket feel free, but I am very interested in the raw output that comes out. — Reply to this email directly, view it on GitHub <#187 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADTDE6V5NYN3QCFOLD7UNDWLO7EBANCNFSM6AAAAAASSYADH4> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[UnclePhil]

SOLVED !!!!!!
I'm going to kill someone Monday !!!!

The problem was not in your routine but in the minio server .... the basic configuration of the server has a region "here" configured with Ansible script.
And someone change the region to the name of the company because it's "more relevant"

Sorry for the research

Best regards, and thank you for your product

Ph Koenig

[tiredofit]

Glad you could sort it out :) I bump up against similar in some of my client environments as well!