Hello,

pon., 20 wrz 2021 o 21:29 Otaci Martins <otaci.mart...@gmail.com>
napisał(a):

> bacula-sd can't upload volumes to AWS S3 if running as systemd daemon, but
> if called directly by terminal cli the upload works perfectly.
>
> 1. Steps to reproduce the upload error:
> ---------------------------------------
> $ sudo systemctl start bacula-sd
>
> $ ps -ef | grep bacula
> root     12573     1  0 15:39 ?        00:00:00 /opt/bacula/bin/bacula-sd
> -fP -c /opt/bacula/etc/bacula-sd.conf
> root     13555     1  0 Sep15 ?        00:00:01 /opt/bacula/bin/bacula-fd
> -fP -c /opt/bacula/etc/bacula-fd.conf
> bacula   29641     1  0 10:58 ?        00:00:00 /opt/bacula/bin/bacula-dir
> -fP -c /opt/bacula/etc/bacula-dir.conf
>
> $ echo "cloud list storage=S3CLOUD" | bconsole
> Connecting to Director 192.168.10.12:9101
> 1000 OK: 10002 BACULA11-DIR Version: 11.0.5 (03 June 2021)
> Enter a period to cancel a command.
> cloud list storage=S3CLOUD
> Automatically selected Catalog: BACULA11-CA
> Using Catalog "BACULA11-CA"
> Connecting to Storage daemon S3CLOUD at 192.168.10.12:9103 ...
> 3900 Error cannot get cloud Volume list. ERR=S3_list_bucket
> ERR=FailedToConnect CURL Effective URL:
> https://mybucket.s3.sa-east-1.amazonaws.com/?delimiter=%2F CURL OS Error:
> 110 CURL Effective URL:
> https://mybucket.s3.sa-east-1.amazonaws.com/?delimiter=%2F CURL OS Error:
> 110
>

The OS Error 110 (AFAIK) is a "Connection Timeout". Do you have SELinux
enabled? If yes then test with selinux disabled.

best regards
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to