Hello Rob,

Appreciate the suggestions.

It helps to have other people’s ideas.

Responses below

Regards,
Vaughan

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.


  1.  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.


  *   I am using php7.4-fpm. I have restarted the service. BTW, I restarted the 
computer before re-trying to configure Baculum, so not sure whether restarting 
services will help. Nevertheless, it is worth trying.
  *   Have also restarted apache2.
  *   Restarting the services made no difference to the error.


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


Ø    Tried setting chmod to 777 both on the directory and the file. Restarted 
apache2. Made no difference.


  1.  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.


Ø    Tried chmod 777 recursively on the directory. Restarted apache2. Made no 
difference.

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.

> I am being prompted for www-data password when I try: su www-data
> I don’t know the password. Google search says that password blank / no 
> password. But this is not accepted.
> Another Google results says that by default the www-data account is locked 
> down and won’t allow login, which appears to be the case.

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.

> Tried this already.

  *
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?


Ø    Not keen on this option.

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.


Ø    Think I will try this next.

6. Install bacularis using lighttpd. See the bacularis website for instructions.


Ø    Will also try this eventually, or soon if step 5 doesn’t work.

I think the setup of Baculum and even Bacula to be honest is unreasonably 
complicated.
Really appreciate you taking the time to provide suggestions, as it helps me to 
clarify my own thoughts and for instance now I’m prepared to ditch Apache and 
try lighttpd.
Thanks again.
Regards,
Vaughan
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to