Bruno,

The communication with the BackupPC server happens via a unix-domain
socket.  That's a special file that allows the server (BackupPC) to
listen to connections from clients (eg: CGI via apache/BackupPC_admin
or BackupPC_serverMesg or BackupPC_dump).

In non-FHS installations the socket is located at TOPDIR/log/BackupPC.sock.
In FHS installation it should be at /var/log/BackupPC/BackupPC.sock.

The fact that backups are working means that programs started by
BackupPC (eg: BackupPC_dump) can in fact connect to the server.

So apache either is looking in the wrong place for the socket file
(eg, if you had an old or second BackupPC install with different paths)
or it no longer has permissions to read the socket (eg: it isn't
running as the BackupPC user).

You can also configure BackupPC to use a TCP socket (typically when
the BackupPC server and apache are on different hosts).  That involves
setting $Conf{ServerPort}, $Conf{ServerMesgSecret} and $Conf{ServerHost}.
If that works, then your problem might not be completely solved since
you could still have a permission or config problem (meaning you won't
be able to access backup history and files using the CGI interface).

Craig

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/