It is in the loading of new objects (they can be client, fileset or
schedules).
I complete the data, save it and do everything right, without error, but it
is not displayed. However, in the .conf it is.
It has happened to me on 2 occasions when I have JOB running of more than
1TB
On Thu, Nov 18, 2021 at 2:13 PM Marcin Haba <ganius...@gmail.com> wrote:
> Hello Jose,
>
> If the reload command does not refresh configuration using bconsole,
> it will not work with Baculum either.
>
> For the debug, if this reload problem happens, a good test could be to
> enable it and run 'reload' in bconsole. At the end you can check the
> content of the trace file.
>
> For the error on data load or edit, what exactly do you mean? What
> error message do you see?
>
> Best regards,
> Marcin Haba (gani)
>
> On Thu, 18 Nov 2021 at 12:19, Jose Alberto <j.se...@gmail.com> wrote:
> >
> > Baculum 11.0.5.4
> >
> > Thanks Marcin for responding.
> >
> > Yes, I have reloaded from baculum and from bconsole, but the changes are
> not activated. They are in the dir.conf but they are not activated. Forced
> must restart catalog and dir for the changes to take effect and if there is
> a job running I must wait for it to finish.
> >
> > What catches my attention is the postgres process q8e refers to the
> database bacula with the user bacula, in idle state (I see that with a pf
> -ef | grep bacula)
> >
> > As we are currently in a deployment of incorporation of new clients (30)
> and running the backups immediately, it is likely that it could happen
> again and I will apply the debug that you have recommended.
> >
> > The other thing that occurs to me, is an error in the data load or
> edition. Although if it were so, it would be reflected as a syntax error.
> >
> >
> >
> > On Wed, Nov 17, 2021 at 10:32 PM Marcin Haba <ganius...@gmail.com>
> wrote:
> >>
> >> Hello Jose,
> >>
> >> It looks that for some reason there isn't executed bconsole 'reload'
> >> command after saving the new Bacula config. If for your Baculum user
> >> you use restricted access by the Bacula Console ACL function, I would
> >> propose to check if allowed Console {} resource config the 'reload'
> >> command is defined. If not, then it can be the reason.
> >>
> >> I would also propose to do a test if the 'reload' command works from
> >> Baculum. It can be done on the Baculum web console page (under the
> >> console menu button at the top left side of the interface). You could
> >> try to change something manually by editing bacula-dir.conf (eg. add a
> >> job or change a directive value) and then in Baculum in the web
> >> console run 'reload' command and check if this new change is available
> >> on the interface.
> >>
> >> If it happens randomly with long time running jobs, as you described,
> >> it can be that for some unknown reason the 'reload' command couldn't
> >> be applied. If from the Console ACL side the reload command can be
> >> executed, then before adding a new resource from Baculum I would
> >> propose to enable debug both in Bacula Director and in Baculum API and
> >> Baculum Web. For Bacula Director it can be bconsole command:
> >>
> >> setdebug level=400 trace=1 options=t dir
> >>
> >> In Bacula Director working directory will be created a file named
> >> <your_director_name>.trace
> >>
> >> In Baculum API and Baculum Web is possible to enable debug in the
> >> application settings page on the interface. Debug files will be in the
> >> web server document root directory in location
> >> protected/API/Logs/baculum-api.log and
> >> protected/Web/Logs/baculum-web.log.
> >>
> >> Once the debug is enabled, then please try to add a resource to Bacula
> >> by Baculum Web. At the end please check all debug files if there is
> >> something wrong.
> >>
> >> What Bacula and Baculum version are you using?
> >>
> >> Best regards,
> >> Marcin Haba (gani)
> >>
> >> On Thu, 18 Nov 2021 at 00:21, Jose Alberto <j.se...@gmail.com> wrote:
> >> >
> >> > It has happened to me, on 2 occasions, when they run jobs that last
> more than 10 hours. When creating objects using the baculum, they are not
> reflected. For example, if I add a client it is not reflected in the
> baculum or in the bconsole (client status), but in the bacula-dir.conf. It
> is as if the objects remain pending to be activated. To solve I have 2
> options to restart catalog and director or wait for the job to finish and
> restart catalog and director. It has only happened to me with backups that
> last 10 hours or more. The funny thing about a Postgres process (ps -ef) in
> state: idle
> >> >
> >> > --
> >> > #############################
> >> > # Sistema Operativo: Debian #
> >> > # Caracas, Venezuela #
> >> > #############################
> >> > _______________________________________________
> >> > Bacula-users mailing list
> >> > Bacula-users@lists.sourceforge.net
> >> > https://lists.sourceforge.net/lists/listinfo/bacula-users
> >>
> >>
> >>
> >> --
> >> "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
> >
> >
> >
> > --
> > #############################
> > # Sistema Operativo: Debian #
> > # Caracas, Venezuela #
> > #############################
>
>
>
> --
> "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
>
--
#############################
# Sistema Operativo: Debian #
# Caracas, Venezuela #
#############################
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
