Some of this advice might not follow best practice (basically item 1). You should assess risk accordingly. I am not a bacula or Apache expert. (Really not an Apache expert since I'm using lighthttpd). I might get some command syntax wrong or misremember a process name since I'm typing this from my phone. Double check my work before implementing it.
0. Are you using php-fpm? Try to restart that process (service php-fpm status) (service php-fpm restart). Also restart the Apache2 service (service httpd restart). With lighthttpd and bacularis I have to restart both php-fpm and the bacularis-lighttpd process. 1. Consider testing with permissions set to 777. See below link. Looks like this isn't unique to you. https://github.com/tyler-dane/bacula/blob/master/troubleshooting.md#problem-api-configuration-gives-error-that-your-directory-path-for-new-config-files-is-not-writable-by-apache 2. When you did the chown and chgrp on the relevant folder, did you do it recursively? Maybe there is a file in there that is not writable. 2.1 su yourself into www-data (su www-data) and try to create a file in the working directory (touch /etc/baculum/Config-api-cache/filename.txt). Can you create the file? Can you list directory contents using ls to prove that the file was created and that it is owned by user www-data? Might need to set a shell type for user www-data first before you can actually log into it. Could also just use su -c or something to take action as that user, but a user session as that user is the surest way to be sure that some program running as that user had the rights to do things in that folder. 3. Restart the server. Maybe there is a process we aren't familiar with that needs to be restarted. Sorry about your uptime, but if it's possible see if a system restart fixes the issue. 4. Completely uninstall baculum and all associated packages. Use the apt purge command to completely remove any associated configuration files as well as uninstalling the package. This should in theory let you reinstall fresh. Try again. Did something just go wrong during initial installation? 5. Install baculum using lighttpd instead of apache2. I'm personally using lighttpd, and don't have experience with Apache. Be advised that you'll maybe need to restart the php-fpm service as well as the baculum-lighttpd service. 6. Install bacularis using lighttpd. See the bacularis website for instructions. Robert Gerber 402-237-8692 r...@craeon.net On Sun, Oct 15, 2023, 5:33 PM Vaughan Wickham <v...@zen.net.au> wrote: > Hello, > > > > I now have the following: > > > > ls -ld /etc/baculum/Config-api-apache/ > > drwxrwx--- 2 www-data www-data 4096 Oct 15 14:32 > /etc/baculum/Config-api-apache > > > > Which I understand is what is needed for apache to have write access to > the above file. > > > > Still seeing this error in Baculum setup: > > > > Baculum working directory for Bacula config: > > /etc/baculum/Config-api-cache > > > > Error Provided directory path is not writable by web server. > > > > 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
