On Tuesday, May 19, 2015 at 2:36:36 PM UTC+1, Marco van Wieringen wrote: > G Jo <g.johnston <at> kainos.com> writes: > > > > > Hi, > > > > I'm trying to get the pgsql-plugin configured to do hot postgres backup > > and test PITR but without much joy to date. > > > > I've copied the example fileset configurations given at > > https://github.com/inteos/pgsql-plugin/wiki/FileSet-configuration > > and the entires from my > I guess you build your plugin using the code at: > > https://github.com/bareos/contrib-pgsql-plugin > > As that is the only one that might actually work on Bareos as > our plugin interface has been updated overtime to actually fully > work so the original code will not work as it won't get any events > as on Bareos you need to register your events while on the older > Baculas you always got all events even the ones you are not interested in. > > Currently this plugin is not fully supported hence it being in a contrib > git repository. Last time I tried it worked though. > > > > > pgsql:/opt/bacula/etc/pgsql.conf:db" requested, but is not loaded. > > > Ok what does a status client=ip-172-31-72-8-fd show in bconsole ? > > It should show what plugins are loaded and should inlude the pgsql one > if it does not the the plugin is not loaded and the above error is correct. > > Check your bareos-fd.conf on the client and make sure the PluginDir is > set. e.g. > > Plugin Directory = ... > Plugin Names = "pgsql" > > The Plugin Names will only try to load pgsql-fd.so and not any other plugin. > > > I've checked everything i can think of. Permissions to the > > pgsql.conf file are ok etc. > > > > Any pointers gratefully received and if you need me to expand on > > my configuration then let me know. > > > > -- > Marco van Wieringen [email protected] > Bareos GmbH & Co. KG Phone: +49-221-63069389 > http://www.bareos.com > > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 > Komplementär: Bareos Verwaltungs-GmbH > Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, > P. Storz, M. v. Wieringen
========================================================================== Hi Marco, Firstly thank you very much for taking the time to respond to my posting, it’s very much appreciated. In turn to address the points and the queries from your reply: [MVW] - I guess you build your plugin using the code at: https://github.com/bareos/contrib-pgsql-plugin] [GJ] – Yes i believe that’s what we used. [MVW] - Currently this plugin is not fully supported hence it being in a contrib git repository. Last time I tried it worked though. [GJ] – Interesting to note both that the plugin is not fully supported but that you have gotten it to work previously. [MVW] Ok what does a status client=ip-172-31-72-8-fd show in bconsole ? It should show what plugins are loaded and should inlude the pgsql one if it does not the the plugin is not loaded and the above error is correct. Check your bareos-fd.conf on the client and make sure the PluginDir is set. e.g. Plugin Directory = ... Plugin Names = "pgsql" [GJ] On 1st execution the status client=ip-172-31-72-8-fd returned nothing so no plugins where loaded. *status client=ip-172-31-72-8-fd Connecting to Client ip-172-31-72-8-fd at ip-172-31-72-8:9102 I checked my initial bareos-fd.conf configuration and it was as follows with the Plugin Directory explicitly named as /opt/bacula/plugins but no entry for Plugin Names FileDaemon { # this is me Name = ip-172-31-72-8-fd Plugin Directory = /opt/bacula/plugins Permissions wise the /opt/bacula/plugins directory tree has ownership bareos:bareos and permissions 755. The pgsql-fd.so shared library is present in the directory e.g [root@ip-172-31-72-8 plugins]# ls -l -rwxr-xr-x 1 bareos bareos 100234 May 7 12:25 pgsql-fd.so [MVW] The Plugin Names will only try to load pgsql-fd.so and not any other plugin. [GJ] I modified my bareos-fd.conf file to explicitly name the pgsql Plugin e.g. Plugin Directory = /opt/bacula/plugins Plugin Names = "pgsql" restarted the ip-172-31-72-8-fd fileDaemon but again the status client=ip-172-31-72-8-fd returned nothing in bconsole. [GJ] Now the default bareos Plugin Directory which is initially commented in rgw bareos-fd.conf file out is Plugin Directory = /usr/lib64/bareos/plugins I modified the file to use this plugin directory instead of /opt/bacula/plugins and restarted the bareos-fd service. This time the bconsole command status client=ip-172-31-72-8-fd returned details that the bpipe plugin had been loaded *status client=ip-172-31-72-8-fd Connecting to Client ip-172-31-72-8-fd at ip-172-31-72-8:9102 Plugin Info: Plugin : bpipe-fd.so Description: Bareos Pipe File Daemon Plugin Version : 2, Date: January 2014 Author : Kern Sibbald License : Bareos AGPLv3 Checking the contents of the /usr/lib64/bareos/plugins directory I found only the bpipe-fd.so library. Having proved that the bpipe plugin library could be loaded from the /usr/lib64/bareos/plugins directory I copied the pgsql plugin library from /opt/bacula/plugins to leave the directory contents as root@ip-172-31-72-8 plugins]# pwd /usr/lib64/bareos/plugins [root@ip-172-31-72-8 plugins]# ls -l total 120 -rwxr-xr-x 1 root root 20056 Dec 31 18:00 bpipe-fd.so -rwxr-xr-x 1 root root 100234 May 15 10:02 pgsql-fd.so I restarted the bareos-fd daemon service but with the 2 plugin libraries in place console command status client=ip-172-31-72-8-fd only loaded the bpipe plugin. I then tried changing the bareos-fd.conf config to name only the pgsql plugin using this configuraiton Plugin Directory = /usr/lib64/bareos/plugins Plugin Names = "pgsql" And this time status client=ip-172-31-72-8-fd showed that no plugins where loaded. As a penultimate attempt I tried with the pgsql-fd.so plugin being the only plugin library in /usr/lib64/bareos/plugins but again it failed to register as a plugin via status client=ip-172-31-72-8-fd with and without explicitly naming it in Plugin Names. And finally I tried renaming the pgsql-fd.so to bpipe-fd.so to try and fool bareos into loading it but again no plugins where loaded. So, in summary no matter what I tried, the pgsql plugin failed to load. I’ve run out of things to try so I’d be grateful if could review my logic and see if you can suggest anything. One thing I should mention in case it is relevant On the director server our bareos catalog database is a mysql database containing 30 tables. However as the pgsql plugin demands a postgres database it is stored in a separate postgres instance with 4 tables. The pgsql-archlog binary is successfully copying archive log metadata from the 17.31.72.8 server to the director server postgres instance postgres@ip-172-31-21-156:~$ psql -Upgcat -dcatdb psql (9.4.1) Type "help" for help. catdb=> select * from pgsql_archivelogs; id | client | filename | create_date | mod_date | status ----+-------------+--------------------------+----------------------------+----------------------------+-------- 20 | 172.31.72.8 | 000000010000000000000093 | 2015-05-20 05:32:15.292626 | 2015-05-20 05:32:15.914786 | 3 (20 rows) Many thanks, George [email protected] +44 28 90 571211 -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
