Yes, Heitor, i know bacula-sd must run with bacula user. But when i was
debbuging with "sudo bacula-sd -fP -d 200", and the volumes were
successfully uploaded, i guess if could be a matter of user permission and
runned bacula-sd service with user root, but without success.

So, here is the debug output when running bacula-sd from command line
(upload OK):

$ sudo bacula-sd -u bacula -fP -d 200
bacula-sd: address_conf.c:289-0 Initaddr 0.0.0.0:9103
LAB001PGSQL-SD: jcr.c:131-0 read_last_jobs seek to 192
LAB001PGSQL-SD: jcr.c:138-0 Read num_items=10
LAB001PGSQL-SD: plugins.c:97-0 load_plugins
LAB001PGSQL-SD: plugins.c:133-0 Rejected plugin: want=*-sd.so got
name=bpipe-fd.so len=11
LAB001PGSQL-SD: plugins.c:133-0 Rejected plugin: want=*-sd.so got name=
bacula-sd-cloud-driver-11.0.5.so len=32
LAB001PGSQL-SD: plugins.c:133-0 Rejected plugin: want=*-sd.so got name=
bacula-sd-cloud-s3-driver-11.0.5.so len=35
LAB001PGSQL-SD: plugins.c:121-0 Failed to find any plugins in
/opt/bacula/plugins
LAB001PGSQL-SD: stored.c:704-0 calling init_dev AWSS3-DRIVE-01
LAB001PGSQL-SD: init_dev.c:141-0 init_dev dev_type=14
LAB001PGSQL-SD: init_dev.c:177-0 Num drivers=15
LAB001PGSQL-SD: init_dev.c:190-0 loadable=1 type=14 loaded=0 name=cloud
handle=0
LAB001PGSQL-SD: init_dev.c:476-0 loadable=1 type=14 loaded=0 name=cloud
handle=0
LAB001PGSQL-SD: init_dev.c:481-0 Open SD driver at /opt/bacula/plugins/
bacula-sd-cloud-driver-11.0.5.so
LAB001PGSQL-SD: init_dev.c:484-0 Driver=cloud handle=7ffadc00ba20
LAB001PGSQL-SD: init_dev.c:486-0 Lookup "BaculaSDdriver" in driver=cloud
LAB001PGSQL-SD: init_dev.c:488-0 Driver=cloud entry point=7ffae8b024d0
LAB001PGSQL-SD: cloud_dev.c:876-0 Open SD driver at /opt/bacula/plugins/
bacula-sd-cloud-s3-driver-11.0.5.so
LAB001PGSQL-SD: cloud_dev.c:879-0 Driver=s3 handle=7ffadc00cec0
LAB001PGSQL-SD: cloud_dev.c:881-0 Lookup "BaculaCloudDriver" in driver=s3
LAB001PGSQL-SD: cloud_dev.c:883-0 Driver=s3 entry point=7ffae88ead30
LAB001PGSQL-SD: htable.c:67-0 malloc buf=7ffaf47e4038 size=1000000
rem=999976
LAB001PGSQL-SD: init_dev.c:235-0 init_dev allocated: 7ffadc00c048
LAB001PGSQL-SD: init_dev.c:437-0 init_dev: tape=0 dev_name=/tmp/hdd03
LAB001PGSQL-SD: dev.c:1143-0 DEVICE::register_metrics called.
0x7ffadc00c048 collector=0x1b24998
LAB001PGSQL-SD: stored.c:706-0 SD init done AWSS3-DRIVE-01 (0x7ffadc00c048)
LAB001PGSQL-SD: block_util.c:174-0 New block adata=0 len=64512
block=7ffadc019f80
LAB001PGSQL-SD: acquire.c:671-0 Attach 0xdc019928 to dev "AWSS3-DRIVE-01"
(/tmp/hdd03)
LAB001PGSQL-SD: events.c:48-0 Events: code=SD0002 daemon=LAB001PGSQL-SD
ref=0x238f type=daemon source=*Daemon* text=Device initialization
AWSS3-DRIVE-01
LAB001PGSQL-SD: events.c:48-0 Events: code=SD0001 daemon=LAB001PGSQL-SD
ref=0x238f type=daemon source=*Daemon* text=Storage startup
LAB001PGSQL-SD: bnet_server.c:90-0 Addresses 0.0.0.0:9103
LAB001PGSQL-SD: bsock.c:861-0 socket=4 who=client host=192.168.10.12
port=9103    <== After this point we can see output of "cloud list
storage=S3CLOUD" command.
LAB001PGSQL-SD: bnet_server.c:235-0 Accept
socket=192.168.10.12.9103:192.168.10.12.47838 s=0x1b26ae8
LAB001PGSQL-SD: dircmd.c:196-0 Got a DIR connection at 21-Sep-2021 10:17:05
LAB001PGSQL-SD: authenticatebase.cc:365-0 TLSPSK Remote need 0
LAB001PGSQL-SD: authenticatebase.cc:335-0 TLSPSK Local need 0
LAB001PGSQL-SD: cram-md5.c:68-0 send: auth cram-md5 challenge
<452667247.1632230225@LAB001PGSQL-SD> ssl=0
LAB001PGSQL-SD: cram-md5.c:132-0 cram-get received: auth cram-md5
<56019976.1632230225@BACULA11-DIR> ssl=0
LAB001PGSQL-SD: cram-md5.c:156-0 sending resp to challenge:
c+/ec2dS+/wbd4/iDyVQuC
LAB001PGSQL-SD: dircmd.c:227-0 Message channel init completed.
LAB001PGSQL-SD: dircmd.c:234-0 <dird: cloudlist Storage=AWSS3-DRIVE-01
Volume= MediaType=CloudAWS Slot=0 drive=-1
LAB001PGSQL-SD: dircmd.c:248-0 Do command: cloudlist
LAB001PGSQL-SD: dircmd.c:1200-0 Found device AWSS3-DRIVE-01
LAB001PGSQL-SD: dircmd.c:1244-0 Found device AWSS3-DRIVE-01
LAB001PGSQL-SD: block_util.c:174-0 New block adata=0 len=64512
block=7ffadc00b1c0
LAB001PGSQL-SD: acquire.c:671-0 Attach 0xdc019f78 to dev "AWSS3-DRIVE-01"
(/tmp/hdd03)
---
Result:
*cloud list storage=S3CLOUD
Using Catalog "BACULA11-CA"
Connecting to Storage daemon S3CLOUD at 192.168.10.12:9103 ...
+--------------------+-----------+----------------------+----------------------+---------------+
|    Volume Name     |   Status  |     Media Type       |       Pool
    |    VolBytes   |
+--------------------+-----------+----------------------+----------------------+---------------+
|         AWSS3-0076 |      Full |             CloudAWS |
AWSS3-PO |      8.528 MB |
| BACKUP-CATALOGO |    Append |             CloudAWS |             AWSS3-PO
|      1.015 MB |
+--------------------+-----------+----------------------+----------------------+---------------+

And, here is the output after changing systemd bacula-sd daemon to start
with debug (upload error):

$ systemctl start bacula-sd
$ systemctl status -n 100 bacula-sd
● bacula-sd.service - Bacula Storage Daemon service
   Loaded: loaded (/etc/systemd/system/bacula-sd.service; enabled; vendor
preset: disabled)
   Active: active (running) since Tue 2021-09-21 10:20:30 -03; 8min ago
 Main PID: 2437 (bacula-sd)
   CGroup: /system.slice/bacula-sd.service
           └─2437 /opt/bacula/bin/bacula-sd -fP -d 200 -c
/opt/bacula/etc/bacula-sd.conf

Sep 21 10:20:30 LAB001PGSQL systemd[1]: Started Bacula Storage Daemon
service.
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: bacula-sd:
address_conf.c:289-0 Initaddr 0.0.0.0:9103
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: jcr.c:131-0
read_last_jobs seek to 192
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: jcr.c:138-0
Read num_items=10
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: plugins.c:97-0
load_plugins
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
plugins.c:133-0 Rejected plugin: want=*-sd.so got name=bpipe-fd.so len=11
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
plugins.c:133-0 Rejected plugin: want=*-sd.so got name=
bacula-sd-cloud-driver-11.0.5.so len=32
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
plugins.c:133-0 Rejected plugin: want=*-sd.so got name=
bacula-sd-cloud-s3-driver-11.0.5.so len=35
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
plugins.c:121-0 Failed to find any plugins in /opt/bacula/plugins
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: stored.c:704-0
calling init_dev AWSS3-DRIVE-01
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:141-0 init_dev dev_type=14
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:177-0 Num drivers=15
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:190-0 loadable=1 type=14 loaded=0 name=cloud handle=0
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:476-0 loadable=1 type=14 loaded=0 name=cloud handle=0
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:481-0 Open SD driver at /opt/bacula/plugins/
bacula-sd-cloud-driver-11.0.5.so
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:484-0 Driver=cloud handle=7fc2ec00ba20
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:486-0 Lookup "BaculaSDdriver" in driver=cloud
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:488-0 Driver=cloud entry point=7fc2f8a224d0
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cloud_dev.c:876-0 Open SD driver at /opt/bacula/plugins/
bacula-sd-cloud-s3-driver-11.0.5.so
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cloud_dev.c:879-0 Driver=s3 handle=7fc2ec00cec0
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cloud_dev.c:881-0 Lookup "BaculaCloudDriver" in driver=s3
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cloud_dev.c:883-0 Driver=s3 entry point=7fc2f880ad30
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: htable.c:67-0
malloc buf=7fc3044f1038 size=1000000 rem=999976
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:235-0 init_dev allocated: 7fc2ec00c048
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
init_dev.c:437-0 init_dev: tape=0 dev_name=/tmp/hdd03
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: dev.c:1143-0
DEVICE::register_metrics called. 0x7fc2ec00c048 collector=0x14c35a8
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: stored.c:706-0
SD init done AWSS3-DRIVE-01 (0x7fc2ec00c048)
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
block_util.c:174-0 New block adata=0 len=64512 block=7fc2ec019f80
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
acquire.c:671-0 Attach 0xec019928 to dev "AWSS3-DRIVE-01" (/tmp/hdd03)
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: events.c:48-0
Events: code=SD0002 daemon=LAB001PGSQL-SD ref=0x238f type=daemon
source=*Daemon* text=Device initialization AWSS3-DRIVE-01
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: events.c:48-0
Events: code=SD0001 daemon=LAB001PGSQL-SD ref=0x238f type=daemon
source=*Daemon* text=Storage startup
Sep 21 10:20:30 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
bnet_server.c:90-0 Addresses 0.0.0.0:9103
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: bsock.c:861-0
socket=4 who=client host=192.168.10.12 port=9103  <== After this point we
can see output of "cloud list storage=S3CLOUD" command.
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
bnet_server.c:235-0 Accept socket=192.168.10.12.9103:192.168.10.12.47844
s=0x14c5668
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: dircmd.c:196-0
Got a DIR connection at 21-Sep-2021 10:26:07
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
authenticatebase.cc:365-0 TLSPSK Remote need 0
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
authenticatebase.cc:335-0 TLSPSK Local need 0
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cram-md5.c:68-0 send: auth cram-md5 challenge
<832215562.1632230767@LAB001PGSQL-SD> ssl=0
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cram-md5.c:132-0 cram-get received: auth cram-md5
<934531061.1632230767@BACULA11-DIR> ssl=0
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
cram-md5.c:156-0 sending resp to challenge: R8/qOj/1B7kh97wbg/ZhvB
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: dircmd.c:227-0
Message channel init completed.
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: dircmd.c:234-0
<dird: cloudlist Storage=AWSS3-DRIVE-01 Volume= MediaType=CloudAWS Slot=0
drive=-1
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD: dircmd.c:248-0
Do command: cloudlist
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
dircmd.c:1200-0 Found device AWSS3-DRIVE-01
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
dircmd.c:1244-0 Found device AWSS3-DRIVE-01
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
block_util.c:174-0 New block adata=0 len=64512 block=7fc2ec00b1c0
Sep 21 10:26:07 LAB001PGSQL bacula-sd[2437]: LAB001PGSQL-SD:
acquire.c:671-0 Attach 0xec019f78 to dev "AWSS3-DRIVE-01" (/tmp/hdd03)
---
Result:
*cloud list storage=S3CLOUD
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
Obs: mybucket replaces the real bucket name.
---

As we can see, debug does not show differences in the two scenarios.

Best regards.
Otaci Martins

Em ter., 21 de set. de 2021 às 09:05, Heitor Faria <hei...@bacula.com.br>
escreveu:

> Otaci,
>
> "sudo /opt/bacula/bin/bacula-sd -fP -c /opt/bacula/etc/bacula-sd.conf"
>
> Please run the SD with the Linux always bacula user. Debug mode should
> give you more information. E.g.
>
> "sudo -u bacula bacula-sd -d 200"
>
> Rgds.
> --
> MSc Heitor Faria (Miami/USA)
> CEO Bacula LatAm
> mobile1: + 1 909 655-8971
> mobile2: + 55 61 98268-4220
>
> América Latina
> [ http://bacula.lat/]
>
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to