Thoughts, with most important probably being middle and end thought:
1. Can set permissions using ACL with getfacl and setfacl. Google and see
man pages. However, this is probably not the best solution since...
2. You might need to add an exemption to a sudoers allow list file. Odds
are there should be a baculum file in the relevant directory (I think
/etc/sudoers?) with paths pointing to various places baculum is supposed to
be able to access.
2.1 Are you installing bacula from the Debian repositories? This method
uses non-standard (for bacula conventions) file locations sometimes. Also,
code might not be the latest. The baculum API setup should prompt you to
add entries to the sudoers file, but keep in mind that if the files
requested are actually somewhere else you'll have to give the correct
locations. Also, the file must end with a newline.
3. If installing from the Debian repositories, consider switching to the
baacula community project repos instead. To do that, go the link below
("download > Deb, RPM, OSX packages" on the bacula community site), enter
your name and email into the contact info section at the bottom of the
page, and click submit. The main caveat is that it may inform you that a
relevant download link will be emailed to you. This is not correct. It is
present on the page that loads directly after you submit your information,
in a link in the middle of the page, labeled is "here". Not super easy to
find, needs improvement imo. Heads up, the instructions to add the custom
bacula repos hosted by the project currently advise user to use apt-key
which is deprecated. Idk what the preferred solution is in this case, but
you've been warned there.
I figure items 2 / 2.1 are probably what you need. Also, consider looking
into bacularis! It's a more actively maintained friendly fork for baculum.
The developer is on this list, and I've seen him commit patches very
rapidly for issues people report. I'm super grateful for his hard work and
I think his efforts to make bacula more accessible are very important.
Robert Gerber
402-237-8692
r...@craeon.net
On Sat, Oct 14, 2023, 11:18 PM Vaughan Wickham <v...@zen.net.au> wrote:
> Hello
>
>
>
> I’m in the middle of first time run of Baculum on Debian 11 with Bacula
> Director >= 11.0
>
>
>
> I’m up to step 4, the Bacula configuration interface.
>
>
>
> When I perform the test, after updating all the paths, I am seeing an
> error on access to the Baculum working directory for Bacula config.
>
>
>
> Error: Provided directory path is not writable by web server.
>
>
>
> The web server that I’m using is apache2.
>
>
>
> I’m guessing that I need to configure apache2 to have write access to:
>
>
>
> /etc/baculum/Config-api-cache
>
>
>
> But I’ve not setup apache previously and having looked on Google, it’s not
> clear to me what the steps are to grant apache2 write access to:
>
>
>
> /etc/baculum/Config-api-cache
>
>
>
> I’m hoping that someone on the list, can provide some direction.
>
>
>
> Thanks
>
>
>
> Regards,
>
> Vaughan
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
