[ I have also posted this to the low-traffic BackupPC-Users list, but wanted a broader look ]

I'm replacing the very old computer that has run as my local BackupPC server, and want to retain the server's data pool (i.e., all the existing backups).

The old server wrote its data (including its log files) to a network storage appliance via NFS mount. I have set up the new machine (Fedora 39, same as the old one) and copied over all the backuppc server and host config files, and mounted the NFS filesystem containing the old backups. The NFS mount is set up properly on the new hardware--'backuppc' user can write to the data pool.

Seems like this should be simple...

The new BackupPC server starts up--I can see it in process listing; httpd web server is working as well. I get prompted to log in to the server admin page as expected, then get the following httpd "503" error:

"Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."da

The BackupPC log files don't show any activity, nor does journalctl.

I do, however, see this in the httpd error_log:

[Tue Feb 20 06:36:00.553934 2024] [cgid:error] [pid 2519:tid 2670] (13)Permission denied: [client ::1:43404] AH01257: stderr from /usr/libexec/BackupPC/BackupPC_Admin: unable to connect to cgi daemon after multiple tries

Can anyone explain this, and suggest a fix? My first thought was noting UID/GID differences for the 'backuppc' user account on the two servers, but fixing that did not solve the problem.

Thanks.
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to