Installing Bacularis on a Server with Existing Nginx Installation

michaeldolzani

Dear Bacularis Support Team,

I am planning to install Bacularis via the web interface on a client server that already has Nginx installed and properly configured. I noticed that the default installation command used within the predefined OS profiles is: /usr/bin/apt -y install --reinstall bacularis bacularis-nginx

Since Nginx is already present and functioning on the server, I would like to avoid reinstalling or modifying it. My question is: can I simply duplicate the existing OS profile and modify the installation command to exclude bacularis-nginx, like so: /usr/bin/apt -y install --reinstall bacularis

Would this adjustment be sufficient for a proper installation of Bacularis, or are there additional steps or configurations I need to consider to ensure compatibility with the existing Nginx setup?

Thank you for your assistance.

Best regards

gani

Hello @michaeldolzani,

Yes, excluding bacularis-nginx package from Bacularis install command is a good idea if you don't want to install Bacularis Nginx configuration file.

Before I describe the producedure, I would like to mention that Bacularis modifes only own files. It means that in case Nginx configuration Bacularis deployment will modify only the Bacularis Nginx configuration file (/etc/nginx/sites-available/bacularis.conf).

For the --reinstall parameter, it is there for a case if on the remote side exists any leftover from previous Bacularis installation. This parameter will not reinstall Nginx. In this your deployment case this parameter can be deleted from the install command.

For the installation with existing Nginx web server, below I described two scenarios: one without bacularis-nginx package installed and one with bacularis-nginx package installed. You can choose one of them which better fits to your needs and your environment.

Scenario 1 (without bacularis-nginx)

I would propose to do the following:

Create a new OS profile with copied configuration from the predefined OS profile.
In this new OS profile:
- Set a new name
- On Access tab uncheck HTTPS option. This way Bacularis will not install certificate and will skip setting the HTTPS connection up.
- On Access tab in field Bacularis start command type a neutral command that will not restart Nginx, for example you can type: true. Otherwise your existing Nginx will be restarted right after deploying Bacularis API there.
- On Package management tab in field Bacularis installation command type use /usr/bin/apt -y install bacularis
- On Package management tab in Advanced settings the field Bacularis post-install command: please leave it empty.
Deploy Bacularis using this new OS profile

After successful deploying, you can log in to this host with Nginx and run:

cd /tmp
apt download bacularis-nginx
dpkg-deb -x bacularis-nginx*.deb bacularis-nginx

In this directory /tmp/bacularis-nginx you will have content of the bacularis-nginx package. You can use this file:

/tmp/bacularis-nginx/etc/nginx/sites-available/bacularis.conf

and install it in your Nginx. At the end you can configure SSL certificate and update on the Bacularis web interface side the API host connection from HTTP => HTTPS in:

[Main menu] => [Page: Security] => [Tab: API hosts] =>[Select API host in table] => [Button: Edit]

Here are two screens for this scenario:

Scenario 2 (with bacularis-nginx)

I would propose to do the following:

Create a new OS profile with copied configuration from the predefined OS profile.
In this new OS profile:
- Set a new name
- On Access tab in field Bacularis start command type a neutral command that will not restart Nginx, for example you can type: true. Otherwise your existing Nginx will be restarted right after deploying Bacularis API there.
Deploy Bacularis using this new OS profile

After deployment, you will need to reload the Nginx configuration:

systemctl reload nginx

Please let us know about result. Good luck.

Best regards,
Marcin Haba (gani)

michaeldolzani

Hello @gani ,

Thank you for your detailed explanation and suggestions regarding the installation process.

I attempted to follow the second method you described. However, during the installation, the process becomes stuck at a specific point. I have attached an image to illustrate where it halts.

Could you please advise on how to proceed from this point?

Thank you for your assistance.

Best regards,

gani

Hello @michaeldolzani,

Thanks for your feedback and try.

I would propose to check three things:

The Raw output tab in this deploy window. Are you seeing there anything wrong? Any error in the Install Bacularis step?
Could you check the process list on this remote host, for example: ps auxfwww. Are you seeing there the apt process?
Does this host has access to Internet?

Thanks in advance for checking these points.

Best regards,
Marcin Haba (gani)

michaeldolzani

Dear @gani ,

Thank you for your prompt response and suggestions.

I have conducted the recommended tests, and everything appears to be functioning correctly. I proceeded with Method 1, and Bacularis installed successfully. However, when attempting to install the Bacula client through the Bacularis interface, I encountered an error.

I also verified that the installed PHP version meets the minimum requirement (PHP >= 7.4) .

I would appreciate any further guidance or recommendations you might have to address this issue.

Best regards,

gani

Hello @michaeldolzani,

michaeldolzani I have conducted the recommended tests, and everything appears to be functioning correctly. I proceeded with Method 1, and Bacularis installed successfully.

Great 👍️

michaeldolzani However, when attempting to install the Bacula client through the Bacularis interface, I encountered an error.

This HTTP Error 502 can be caused by different things. The most common that I know is a problem in connection between web server <=> PHP.

Could I ask you about checking if fastcgi_pass path from Bacularis Nginx file exists in your system? You can check this for example in this way:

grep fastcgi_pass /etc/nginx/sites-available/bacularis.conf

and here is result on my Debian 12:

        fastcgi_pass unix:/run/php/php8.2-fpm.sock;

Path in my system:

# ls -l /run/php/php8.2-fpm.sock
srw-rw---- 1 www-data www-data 0 05-23 14:05 /run/php/php8.2-fpm.sock

If your PHP-FPM version in the system is different than this in fastcgi_pass then you need to update this path in the Bacularis Nginx config to match to your path and PHP version in the system. At the end you will need to reload the web server configuration.

Is it this case? Please let us know what you found.

Good luck.

Best regards,
Marcin Haba (gani)