My machine does not appear in clients

71 views
Skip to first unread message

Meth

unread,
Jul 12, 2024, 8:49:52 AM7/12/24
to bacularis
Screenshot_20240712_145909.png

Screenshot_20240712_154638.png

Screenshot_20240712_154756.png

Screenshot_20240712_154838.png

https://youtu.be/5nU5TWSZW-0

I am completing the steps as in this video, but I think I made a mistake somewhere or I am not sure if there is a mistake.

After installing the client after these steps, when I click on the Clients tab on Bacularis, I cannot see the last machine I installed there.

Marcin Haba

unread,
Jul 12, 2024, 9:01:33 AM7/12/24
to Meth, bacularis
Hello Meth,

On your screenshots in the window titled "Install Bacula components on API host" there is a red X character in the installing client line. It means that an error happened during installing Bacula Client on the remote host. To see this error you need to click on the "Raw output" tab. Are you seeing in the output some errors?

I have also a question - what type of package repositories do you use in the OS profile "Ubuntu 22.04 Jammy - Test"? Are the Ubuntu system repositories or are they bacula.org package repositories?

Thanks in advance for providing this information.

Best regards,
Marcin Haba (gani)

--
You received this message because you are subscribed to the Google Groups "bacularis" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bacularis+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/bacularis/59a3ae4f-21d6-448e-8737-bf8dfe95e36bn%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
"Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus

Meth

unread,
Jul 12, 2024, 9:07:31 AM7/12/24
to bacularis
Hi, Marcin,

Thank you for your quick response. When I checked that red X, there doesn't seem to be a problem. Also, how can I access the "Raw output"? I looked under /var/log and didn't see much.

As a side note, I actually made the configurations of Ubuntu Jammy - Test exactly the same as in your video. I am also sending a screenshot of that file.

Screenshot_20240712_160554.png

Screenshot_20240712_160614.png
12 Temmuz 2024 Cuma tarihinde saat 16:01:33 UTC+3 itibarıyla Marcin Haba şunları yazdı:

Marcin Haba

unread,
Jul 12, 2024, 9:16:26 AM7/12/24
to Meth, bacularis
Hello Meth,

OK, so you use the package repository from Bacula.org. This way you need to look at this video guide:

https://www.youtube.com/watch?v=EkSceivoUyc

There are additional steps that need to be done for using Bacula.org repositories in Bacularis.

For the Raw output, I mean this function on the attached screenshot that I pointed by red arrow.


Best regards,
Marcin Haba (gani)

For more options, visit https://groups.google.com/d/optout.
raw_output.png

Meth

unread,
Jul 12, 2024, 9:24:18 AM7/12/24
to bacularis

Hi Marcin,

I watched the video you sent from start to finish. I wouldn't have progressed this far without your tutorial videos :). Thank you for your support.

When I looked at the raw output, I found the error. I'm leaving the log below.

sudo /usr/bin/apt -y install bacula-client 2>&1,,WARNING: apt does not have a stable CLI interface. Use with caution in scripts.,,Reading package lists...,Building dependency tree...,Reading state information...,Suggested packages:,  bacula-traymonitor,The following NEW packages will be installed:,  bacula-client,0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded.,Need to get 758 kB of archives.,After this operation, 2.050 kB of additional disk space will be used.,Get:1 https://bacula.org/packages/*****/debs/13.0.2 jammy/main amd64 bacula-client amd64 13.0.2-23022015~jammy [758 kB],debconf: unable to initialize frontend: Dialog,debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.),debconf: falling back to frontend: Readline,debconf: unable to initialize frontend: Readline,debconf: (This frontend requires a controlling tty.),debconf: falling back to frontend: Teletype,dpkg-preconfigure: unable to re-open stdin:,Fetched 758 kB in 1s (818 kB/s),Selecting previously unselected package bacula-client.,(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 367848 files and directories currently installed.),Preparing to unpack .../bacula-client_13.0.2-23022015~jammy_amd64.deb ...,Unpacking bacula-client (13.0.2-23022015~jammy) ...,Setting up bacula-client (13.0.2-23022015~jammy) ...,debconf: unable to initialize frontend: Dialog,debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.),debconf: falling back to frontend: Readline,Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.,Processing triggers for man-db (2.10.2-1) ...,sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /etc/bacula www-data 2>&1,Config validation error.Array
(
    [output] => JSON tool returned wrong exitcode.
 Output:sudo: /usr/sbin/bfdjson: command not found
    [exitcode] => 82
)


How can I fix this situation under bfdjson /opt/bacula/bin/ on my own Client computer (minipc)?

Actually, I thought of moving the command, but I need your opinion since I'm not sure how healthy it would be.

Screenshot_20240712_162301.png


12 Temmuz 2024 Cuma tarihinde saat 16:16:26 UTC+3 itibarıyla Marcin Haba şunları yazdı:

Marcin Haba

unread,
Jul 12, 2024, 9:41:41 AM7/12/24
to Meth, bacularis
Hi Meth,

On Fri, 12 Jul 2024 at 15:24, Meth <bys...@gmail.com> wrote:

Hi Marcin,

I watched the video you sent from start to finish. I wouldn't have progressed this far without your tutorial videos :). Thank you for your support.

Great. Thanks :-) 

(Reading database ... 367848 files and directories currently installed.),Preparing to unpack .../bacula-client_13.0.2-23022015~jammy_amd64.deb ...,Unpacking bacula-client (13.0.2-23022015~jammy) ...,Setting up bacula-client (13.0.2-23022015~jammy) ...,debconf: unable to initialize frontend: Dialog,debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.),debconf: falling back to frontend: Readline,Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.,Processing triggers for man-db (2.10.2-1) ...,sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /etc/bacula www-data 2>&1,Config validation error.Array
(
    [output] => JSON tool returned wrong exitcode.
 Output:sudo: /usr/sbin/bfdjson: command not found
    [exitcode] => 82
)

How can I fix this situation under bfdjson /opt/bacula/bin/ on my own Client computer (minipc)?

You can fix it by going to the API panel on the destination host:

http://10.2.50.150:9097/panel

and there please go to

[Page: Settings] => [Tab: Config] and update there bfdjson entries.

For new Bacularis API instances that you are planning to deploy with OS profile "Ubuntu 22.04 Jammy - Test", you need to change it in the OS profile config on the Bacularis web interface:

[Page: Deployment] => [Tab: OS profiles] => [selected os profile line] => [Button: Edit]

You will see a new window, so in this window you need to find the 'Configuration' section where is the bfdjson path to set.

Good luck.


Best regards,
Marcin Haba (gani) 

Meth

unread,
Jul 12, 2024, 1:29:27 PM7/12/24
to bacularis

Hi, Marcin,

Sorry for the late reply.

I was doing what you said but it said it couldn't find the following files and commands.
When I checked in the system, I couldn't find them either (I checked with the find command.) I could only find bfdjson.

But I could not see a problem in the deployment phase. 



resim_2024-07-12_202843851.png


12 Temmuz 2024 Cuma tarihinde saat 16:41:41 UTC+3 itibarıyla Marcin Haba şunları yazdı:

Meth

unread,
Jul 12, 2024, 1:30:54 PM7/12/24
to bacularis
I solved the bfdjson problem, it's my fault for not giving the path properly... :(

12 Temmuz 2024 Cuma tarihinde saat 20:29:27 UTC+3 itibarıyla Meth şunları yazdı:

Meth

unread,
Jul 12, 2024, 1:39:51 PM7/12/24
to bacularis
While installing the client, I received an error in the Raw output.

(Reading database ... 367848 files and directories currently installed.),Preparing to unpack .../bacula-client_13.0.2-23022015~jammy_amd64.deb ...,Unpacking bacula-client (13.0.2-23022015~jammy) ...,Setting up bacula-client (13.0.2-23022015~jammy) ...,debconf: unable to initialize frontend: Dialog,debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.),debconf: falling back to frontend: Readline,Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.,Processing triggers for man-db (2.10.2-1) ...,sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /etc/bacula www-data 2>&1,Internal error. [Warning] file_put_contents(/opt/bacula/etc/bacula-fd. conf): Failed to open stream: Permission denied (@line 64 in file /usr/share/bacularis/protected/vendor/bacularis/bacularis-common/Common/Modules/ConfigBacula. php).


I actually thought of doing the following steps here, what do you suggest?

ls -l /opt/bacula/etc/bacula-fd.conf

sudo chown www-data:www-data /opt/bacula/etc/bacula-fd.conf
sudo chmod 644 /opt/bacula/etc/bacula-fd.conf

12 Temmuz 2024 Cuma tarihinde saat 20:30:54 UTC+3 itibarıyla Meth şunları yazdı:

Marcin Haba

unread,
Jul 12, 2024, 1:51:59 PM7/12/24
to Meth, bacularis
Hi Meth,

Great to hear that you solved the path problem.

For the permissions, in the deployment process they are set by set_bacula_perm.sh script but it needs to have the correct parameter with path. You can see in on this movie in time 2:35 how to update it for /opt/bacula paths:

https://youtu.be/EkSceivoUyc?t=150

If you want to do it not by script but manually, here you can find example permission settings for the Bacula configuration files:

https://bacularis.app/doc/brief/troubleshooting.html#permission-denied-error-when-saving-bacula-configuration

In that examples is used 'apache' user but in case your Ubuntu environment the user is 'www-data' of course.


Best regards,
Marcin Haba (gani)
--
You received this message because you are subscribed to the Google Groups "bacularis" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bacularis+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Meth

unread,
Jul 12, 2024, 3:10:43 PM7/12/24
to bacularis
Hi, Marcin,

I did as you said, I even watched the video several times to check if I made a mistake. I redeployed the host with the latest OS settings, but I still get the same error.

Do you have any other suggestion? This situation is getting very frustrating.

Here are the steps I did in order;

1.usermod -a -G bacula www-data

2. systemctl restart php8.1-fpm.service
 (In the doc only systemctl restart php-fpm, which is missing in Ubuntu 22.04LTS)

3.systemctl restart nginx.service
(I use nginx as web server)

Since there is a description in the document as follows;

"Please note that the Bacula config directory should have permissions rwxr-xr-x that does allow to modify existing files by bacula user but does not allow creating new config files. To enable creating new files by user group you should set the directory permissions to rwxrwxr-xr-x.

Bacula config file permissions are rw-rw---- that gives read/write access for the file owner/group."

I did this too

4.chmod ugo+rwx ../../bacula-fd.conf


Setting up bacula-client (13.0.2-23022015~jammy) ...,debconf: unable to initialize frontend: Dialog,debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.),debconf: falling back to frontend: Readline,Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.,Processing triggers for man-db (2.10.2-1) ...,sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /opt/bacula/etc www-data 2>&1,Internal error. [Warning] file_put_contents(/opt/bacula/etc/bacula-dir.conf): failed to open stream: Permission denied (@line 64 in file /usr/share/bacularis/protected/vendor/bacularis/bacularis-common/Common/Modules/ConfigBacula.php).
12 Temmuz 2024 Cuma tarihinde saat 20:51:59 UTC+3 itibarıyla Marcin Haba şunları yazdı:

Marcin Haba

unread,
Jul 12, 2024, 7:54:01 PM7/12/24
to Meth, bacularis
On Fri, 12 Jul 2024 at 21:10, Meth <bys...@gmail.com> wrote:
Setting up bacula-client (13.0.2-23022015~jammy) ...,debconf: unable to initialize frontend: Dialog,debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.),debconf: falling back to frontend: Readline,Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.,Processing triggers for man-db (2.10.2-1) ...,sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /opt/bacula/etc www-data 2>&1,Internal error. [Warning] file_put_contents(/opt/bacula/etc/bacula-dir.conf): failed to open stream: Permission denied (@line 64 in file /usr/share/bacularis/protected/vendor/bacularis/bacularis-common/Common/Modules/ConfigBacula.php).

Hi Meth,

You fixed the permissions on the host with the Bacula File Daemon on the File Daemon host. That is fine.

This error is about permissions to the Bacula Director config file on the Bacula Director host:


[Warning] file_put_contents(/opt/bacula/etc/bacula-dir.conf): failed to open stream: Permission denied

So, now you need to look at the host with the Bacula Director and fix the permissions there.


Best regards,
Marcin Haba (gani)

Meth

unread,
Jul 16, 2024, 4:49:48 AM7/16/24
to bacularis
Hi Marcin,

First of all, thank you very much for your help. I hope you are having a good week.

As you said, I edited the permissions on the host machine where Bacularis is installed;

ls -lthr /opt/bacula/etc/

-rw-r----- 1 bacula bacula 263 Jul 12 10:31 bconsole.conf
-rw-r----- 1 bacula root 1.2K Jul 12 10:31 bacula-fd.conf
-rw-r----- 1 bacula bacula 9.2K Jul 12 10:31 bacula-dir.conf
-rw-r----- 1 bacula bacula 9.7K Jul 12 10:31 bacula-sd.conf

After this step, I did the following;

usermod -a -G bacula www-data

cd /opt/bacula/etc/

chmod ugo+rwx *

-rwxrwxrwx 1 bacula bacula 263 Jul 12 10:31 bconsole.conf
-rwxrwxrwx 1 bacula root 1133 Jul 12 10:31 bacula-fd.conf
-rwxrwxrwx 1 bacula bacula 9365 Jul 12 10:31 bacula-dir.conf
-rwxrwxrwx 1 bacula bacula 9921 Jul 12 10:31 bacula-sd.conf

systemctl restart php7.4-fpm.service
systemctl restart apache2.service

After these steps When I reinstalled Bacularis Client on the 50.150 client machine, the Raw Output looked like this.

(Reading database ... 367847 files and directories currently installed.)
Preparing to unpack .../bacula-client_13.0.2-23022015~jammy_amd64.deb ...
Unpacking bacula-client (13.0.2-23022015~jammy) ...
Setting up bacula-client (13.0.2-23022015~jammy) ...
debconf: unable to initialize frontend: Dialog

debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.
Processing triggers for man-db (2.10.2-1) ...
sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /opt/bacula/etc www-data 2>&1

Non-zero exitcode returned by software management command.
Output:sudo /usr/bin/systemctl enable bacula-client 2>&1
Failed to enable unit: Unit file bacula-client.service does not exist.

I think the service did not start at the end, what should I do after this step?

13 Temmuz 2024 Cumartesi tarihinde saat 02:54:01 UTC+3 itibarıyla Marcin Haba şunları yazdı:

Marcin Haba

unread,
Jul 16, 2024, 2:51:48 PM7/16/24
to Meth, bacularis
On Tue, 16 Jul 2024 at 10:49, Meth <bys...@gmail.com> wrote:
(Reading database ... 367847 files and directories currently installed.)
Preparing to unpack .../bacula-client_13.0.2-23022015~jammy_amd64.deb ...
Unpacking bacula-client (13.0.2-23022015~jammy) ...
Setting up bacula-client (13.0.2-23022015~jammy) ...
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Created symlink /etc/systemd/system/multi-user.target.wants/bacula-fd.service → /lib/systemd/system/bacula-fd.service.
Processing triggers for man-db (2.10.2-1) ...
sudo /usr/share/bacularis/protected/tools/set_bacula_perm.sh /opt/bacula/etc www-data 2>&1

Non-zero exitcode returned by software management command.
Output:sudo /usr/bin/systemctl enable bacula-client 2>&1
Failed to enable unit: Unit file bacula-client.service does not exist.

I think the service did not start at the end, what should I do after this step?

Hi Meth,

Thanks for your feedback and the problem description. Good to read that you solved the permission problem on the Director's side.

The command that is wrong is this:


/usr/bin/systemctl enable bacula-client 2>&1

It looks like there is an error in this video guide. Thanks for catching it. You can change in your OS profile the 'bacula-client' systemd unit into 'bacula-fd' unit and it should be fine as on the attached screenshot.

In the future I will try to record a new video guide that will include this fix.

Please note that if you would like to apply this change on already deployed Bacularis API instances, then this change needs to be done also in the API panel for each host. It is in:

[API MENU] => [Page: Settings] => [Tab: Software management] => [Section: File Daemon/Client] => [Input: Client enable command]


Best regards,
Marcin Haba (gani)
 

Marcin Haba

unread,
Jul 16, 2024, 3:00:00 PM7/16/24
to Meth, bacularis
On Tue, 16 Jul 2024 at 20:51, Marcin Haba <gani...@gmail.com> wrote:
On Tue, 16 Jul 2024 at 10:49, Meth <bys...@gmail.com> wrote:
Hi Meth,

Thanks for your feedback and the problem description. Good to read that you solved the permission problem on the Director's side.

The command that is wrong is this:

/usr/bin/systemctl enable bacula-client 2>&1

It looks like there is an error in this video guide. Thanks for catching it. You can change in your OS profile the 'bacula-client' systemd unit into 'bacula-fd' unit and it should be fine as on the attached screenshot.

Hi Meth,

I forgot to attach the screenshot that I mentioned :-) I am doing it now.


Best regards,
Marcin Haba (gani)
os-profile-enable-bacula-client.png

Meth

unread,
Jul 17, 2024, 6:32:15 AM7/17/24
to bacularis
Thank you. Marcin all done. :)

16 Temmuz 2024 Salı tarihinde saat 22:00:00 UTC+3 itibarıyla Marcin Haba şunları yazdı:
Reply all
Reply to author
Forward
0 new messages