Re: [Bacula-users] Upgrade to focal zorched bacula again

2021-09-21 Thread Martin Simmons
To debug the bconsole problem, try running it with the -d500 command line argument. You'll probably need to look at the release notes for Apache to see why the baculum-api.conf doesn't work. __Martin > On Mon, 20 Sep 2021 11:10:15 -0700, Robert Earl said: > > Hi all! > We recently upgraded

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Otaci Martins
My mistake in last message. Here is the correct text: ... The fact is that the only difference is how bacula-sd is invoked: 1. $ sudo systemctl start bacula-sd => UPLOAD ERROR 2. $ sudo bacula-sd -fP -c /opt/bacula/etc/bacula-sd.conf => UPLOAD OK Best regards. Otaci MArtins Em ter., 21

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Otaci Martins
Heitor, this is only a LAB not a production system. First i am using user=root, but after your last message i changed to user=bacula with same results. The cache /tmp in this LAB does not affect the results here. The fact is that the only difference is how bacula-sd is invoked: 1. $ sudo syst

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Heitor Faria
Hello Otaci, IMHO your scenario is kind of confusing. 1. Your service init file is using the root Linux user. Like I wrote before, not recommendable: "[Service] Type=simple User=root" 2. You are using /tmp as cache/volume storage, what is absolutely not recommendable. Regards, ___

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Otaci Martins
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 ou

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Heitor Faria
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-897

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Otaci Martins
Hi Heitor, You got this because the real bucket name was changed to "mybucket" in order to hide it. Here is the response with the real bucket name: AccessDenied Access Denied 10DA27806ZQK31JP GwrZZV1ZKQ2GzZcpCyVUys/wQmZP21n3VLP7mkIdiIivWCZGh5mtOmnBr8/REmj7G/Yp3aLPJGM= So, why there is no ac

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Heitor Faria
Hello Otaci, If you click in the error URL it will point you what's is wrong. I believe you are using the wrong service AWS endpoint address: "This XML file does not appear to have any style information associated with it. The document tree is shown below. PermanentRedirect The bucket you are

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Otaci Martins
Hi Radosław Korzeniewski, Yes, SELinux is enabled. I've disabled it but the result is the same. Also, I've stopped the local firewall and got the same result. Tks Otaci Martins otaci Em ter., 21 de set. de 2021 às 04:43, Radosław Korzeniewski < rados...@korzeniewski.net> escreveu: > Hello, > >

Re: [Bacula-users] bacula-sd can't upload to AWS S3

2021-09-21 Thread Radosław Korzeniewski
Hello, pon., 20 wrz 2021 o 21:29 Otaci Martins 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