



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


To view this discussion on the web, visit https://groups.google.com/d/msgid/bacularis/de8d3b3f-07ce-4235-83ab-ed9b3e97a763n%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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.
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.
(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 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/04fb5167-679f-4eed-8e1b-556399e2b88an%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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).
(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?
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.