Bacula-users

Re: [Bacula-users] Bacula 5.2.5 - Postgresql 9.1 - libpq.a - dir inserting attributes ??

2012-11-29 09:31:17
Subject: Re: [Bacula-users] Bacula 5.2.5 - Postgresql 9.1 - libpq.a - dir inserting attributes ??
From: Dan Langille <dan AT langille DOT org>
To: <olivier.delestre AT univ-rouen DOT fr>
Date: Thu, 29 Nov 2012 09:28:37 -0500
On 2012-11-29 09:04, Olivier Delestre wrote:
> Le 29/11/2012 14:51, Dan Langille a écrit :
>> On 2012-11-29 08:34, Olivier Delestre wrote:
>>> Le 29/11/2012 13:55, Dan Langille a écrit :
>>>> On 2012-11-29 07:38, Olivier Delestre wrote:
>>>>> Hi,
>>>>>
>>>>>  I upgrade bacula 5.0.3 ( psql 8.4 ) to 5.2.5 ( psql 9.1 ) on 
>>>>> ubuntu
>>>>> 12.04.1 LTS.
>>>>>
>>>>>  I asked about :
>>>>>
>>>>>  1) The documentation of bacula that saying :
>>>>>
>>>>> "If you configure the Batch Insert code in Bacula (attribute 
>>>>> inserts
>>>>> are
>>>>> 10 times faster), you MUST be using a PostgreSQL that was built 
>>>>> with
>>>>> the --ENABLE-THREAD-SAFETY option, otherwise you will get
>>>>> DATA CORRUPTION. Most major Linux distros have thread safety 
>>>>> turned
>>>>> on, but
>>>>> it is better to check. One way is to see if the PostgreSQL 
>>>>> library
>>>>> that
>>>>> Bacula will be linked against references pthreads. This can be 
>>>>> done
>>>>> with a command such as:
>>>>> nm /usr/lib/libpq.a | grep pthread_mutex_lock "
>>>>>
>>>>> But, no such file. What is its usefulness ?
>>>>
>>>> Different operating systems install this file in different places. 
>>>> Here is
>>>> how I found it on a FreeBSD system:
>>>>
>>>> $ locate libpq.a
>>>> /usr/local/lib/libpq.a
>>>>
>>>> And running the command:
>>>>
>>>> $ nm /usr/local/lib/libpq.a | grep pthread_mutex_lock
>>>>          U pthread_mutex_lock
>>>>          U pthread_mutex_lock
>>>>
>>>>
>>>>> i found it by installing postgresql-server-dev-9.1. Not installed 
>>>>> from
>>>>> scratch install or upgrade...
>>>>>
>>>>> I think the package bacula 5.2.5 is compiled with 
>>>>> enable-batch-insert
>>>>> and postgresql 5.2.5 with enable-thread-safety ( obtain source 
>>>>> package
>>>>> with apt-get source xxx )
>>>>
>>>> Do you have any unanswered questions?
>>>
>>> I found /usr/lib/libpq.a if i installed postgresql-server-dev-9.1 
>>> on
>>> my test machine. what use is it ?
>>
>> I'm sorry, but I don't know for sure.  I'm sure it is used by that 
>> package.  :)
>>
>>>
>>>>
>>>>> 2) else since the update, i have a client with a state of "dir
>>>>> inserting attribute" for 3 hours :(
>>>>> This Client have 1,8 To and 16 Millions of files. An idea if 
>>>>> something
>>>>> change since ??
>>>>
>>>> That's a lot of inserts to do.    It can take a while to insert 16 
>>>> million rows.
>>>>
>>>>>
>>>>> No grant privileges on Tables restoreobject* , like this urls say 
>>>>> (
>>>>>
>>>>>
>>>>> 
>>>>> http://www.mail-archive.com/bacula-users AT lists.sourceforge DOT 
>>>>> net/msg51149.html
>>>>>
>>>>>
>>>>> )
>>>>
>>>> I'm not sure why you mention this... :)
>>> these are things that I could etrangent notes for the update...
>>> Not important ? ...
>>
>> I don't know.
>>
>>>>
>>>>>
>>>>> everything works well apart this status "DIR inserting attribute" 
>>>>> for
>>>>> one big client and libpq.a not installed. I'm a little worried.
>>>>
>>>> Are you sure that libpq.a is not installed?  Please check again...
>>> In prod, i very sure.
>>>>
>>>>>
>>>>> Thank for any information.
>>>>
>>>>
>>> I search ...  I found a notion of "Spool attributes" ??
>>
>> It sounds like your system is already spooling attributes.
>>
>> Perhaps if you pasted your Job and JobDefs (if applicable) for the 
>> Job
>> in question.
> ../..
> JobDefs {
>   Name = "DefaultJob"
>   Type = Backup
>   Level = Incremental
>   Schedule = "WeeklyCycle"
>   Storage = File
>   Messages = Standard
> #
>   Reschedule On Error = yes
>   Reschedule Interval = 1h
>   Reschedule Times = 2
> # Fenetre = Max start delay + Max Run Time
> # duree de demarrage max du job de 24h
>   Max Start Delay = 24h
> # temps execution max du job 36 ou 12h
>   Full Max Run Time = 36h
>   Differential Max Run Time = 36h
>   Incremental Max Run Time = 36h
> ##  Incremental Max Run Time = 12h
>   Priority = 10
> }
> #
> # chargement des clients
> #
> @|"sh -c 'for f in /etc/bacula/Conf.d/Client/*.conf ; do echo @${f} ; 
> done'"
> #
> ../..
>
> Job {
>   Name = "mail"
>   Enabled = yes
>   Client = mail-fd
>   JobDefs = "DefaultJob"
>   FileSet = "fileset_mail"
>   Pool = mail
>   Storage = mail
>   Schedule = "Weekly-mail"
>   Full Max Run Time = 47h
> ## debut modif le 20100512
> #  Incremental Max Run Time = 14h
>   Incremental Max Run Time = 16h
>   Reschedule On Error = no
>   Reschedule Times = 1
> ## fin modif le 20100512
>   ClientRunBeforeJob = "/etc/bacula/scripts/before.sh"
> ##  ClientRunAfterJob  = "/etc/bacula/scripts/after.sh"
> RunScript {
>     RunsWhen = After
>     RunsOnFailure = yes
>     RunsOnClient  = yes
>     RunsOnSuccess = yes
>     Command = "/etc/bacula/scripts/after.sh"
>     }
> ##
>   Messages = MAIL-mail
>   Write Bootstrap = "/var/lib/bacula/mail.bsr"
> }
>
> If you see something .

I am out of time just now.  Hopefully someone else on the list can take 
over.

(remember to do a reply-all)


-- 
Dan Langille - http://langille.org/

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
VERIFY Test and improve your parallel project with help from experts 
and peers. http://goparallel.sourceforge.net
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users