Hi everyone,
Does anyone have any ideas about this problem, please? It's got me stumped.
Simply, I can start the BackupPC service cleanly from the command line, and see the processes running, but the CGI thinks it's not running.
Starting up with "service backuppc start" returns "OK". Checking service status shows the following:
-----------
backuppc.service - BackupPC server
Loaded: loaded (/lib/systemd/system/backuppc.service; enabled)
Active: active (exited) since Thu, 17 Nov 2011 22:24:04 +0000; 1s ago
Process: 16866 ExecStart=/usr/share/BackupPC/bin/BackupPC -d (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/backuppc.service
t 16868 /usr/bin/perl /usr/share/BackupPC/bin/BackupPC -d
m 16869 /usr/bin/perl /usr/share/BackupPC/bin/BackupPC_trashClean
-----------
Slightly strange is the active (exited) bit - proc 16866 is indeed gone, but it has spawned a BackupPC daemon as proc 16868, which is running:
-----------
PID TTY STAT TIME COMMAND
16868 ? S 0:00 /usr/bin/perl /usr/share/BackupPC/bin/BackupPC -d
-----------
The pid and LOCK files look ok in /var/log/BackupPC. Permissions are ok to let the backuppc user write them.
BackupPC_serverMesg can communicate with the server:
-----------
Got reply: %Info = ("ConfigLTime" => "1321568644","ConfigModTime" => "1321567367","DUlastValueTime" => "1321568644","nextWakeup" => "1321570800","DUDailyMax" => 28,"DUDailyMaxTime" => "1321566315","Version" => "3.2.1","pid" => 16868,"DUlastValue" => 28,"startTime" => "1321568644","HostsModTime" => "1321396894");
-----------
Clearly, it knows that the server is proc 16868.
The CGI interface, however, says
----------- "Unable to connect to BackupPC server. The BackupPC server at wibble.local port -1 is not currently running (maybe you just stopped it, or haven't yet started it)."
-----------
The "start server" button on the CGI has no effect on that, same message comes back up.
The CGI will allow me to edit config files and such like, so apache and running the backuppc cgi scripts seems to be basically ok.
There's nothing interesting in backuppc's log or /var/log/messages. OS is Fedora - FC16 64-bit.
Anyone experienced this or have an idea of what could be causing it?
Thanks very much!
Jeff
