On 2/20/24 08:57, Tim Evans wrote:
On 2/20/24 07:51, Richard Shaw wrote:
On Tue, Feb 20, 2024 at 6:43 AM Tim Evans <tkevans@xxxxxxxxxxx
<mailto:tkevans@xxxxxxxxxxx>> wrote:
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
As the BackupPC package maintainer, I have never seen this, so it may
be unique to your setup...
The only thing I can think of right now might be to try temporarily
putting SELinux into permissive mode and see if that helps. If so,
maybe relabeling the filesystem if the key.
Thanks, Richard. selinux is disabled. As I mentioned, when BackupPC
was installed on the new system, its user/group got a different
numerical UID/GID than the user on the old system. Having restored all
the configs from the old system from an old-fashioned 'dump' backup,
while I've recursively chown-ed the data pool directory, I'm thinking
there is still stuff somewhere with the wrong ownership.
Following up with both Good and Bad News. Having fixed up the file
ownership for the differing UID/GID's, I can report the Good News that
BackuPC is running and doing its daily backups and self-maintenance,
according to its log files.
Bad News is that I'm still getting the same error (above) when trying to
access the BackuPC admin page with a browser. Googling "unable to
connect to cgi daemon" turns up a lot of references to the httpd 'mpm'
module. Hoping that folks who are familiar with Apache module innards
might have some advice here.
Thanks.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
