After spending an hour trying to find out why my slave didn’t attempt to sync with my supermaster server (my domains were set to MASTER, axfr worked from the slave, etc..), I came across the fact that even though your server is authorative and will handle requests, it will not pretend to be an actual MASTER server unless master=yes is set in the configuration file.
One reload and suddenly all the domains synced magically.
Do check that one if you’re not seeing any notify-requests or any entries in your logfiles at all when updating or requesting a sync (through pdns_control).
After updating our debian installation on one of our servers we were left with a non-functioning Trac installation. An exception were thrown with a message about ClearSilver suddenly missing from our installation.
Solution: Debian packages ClearSilver ready for python:
apt-get install python-clearsilver
.. and party like it’s 2010!
We’ve just installed rdiff-backup on some of our older RedHat Enterprise Linux 64-bit servers. We decided to install the .tar.gz-distributions and you can build your own rpms from these source packages (I won’t cover that here). There are a few pitfalls you’ll have to avoid.
First: librsync needs to be built with the 64-bit lib directory as the standard linkage, and needs to be compiled as a shared module.
To do this, provide configure with a few hints:
./configure LDFLAGS=-L/usr/lib64 --enable-shared --enable-lib64
make installldconfig to be sure that your LD cache has been updated (make install should do this, but .. just to be sure.)
The “.. can not be used when making a shared object; recompile with -fPIC” error for librsync will occur if you build it without –enable-shared, while “/usr/lib/libpopt.so: could not read symbols: File in wrong format” will occur if you build the library with the standard 32 bit libraries.
After this rdiff-backup compiled as it should:
python setup.py install
After rdiff-backup builds it python module and other small items, you might have to run ldconfig again (if you get “ImportError: librsync.so.1: cannot open shared object file: No such file or directory”, try this):
If you still get the above error, check that the directory where librsync was installed is present in either one of the files in
/etc/ld.so.conf.d/ or in
/etc/ld.so.conf itself. After adding the path to the library directory (which by default will be
rdiff-backup should now (hopefully) work as expected.