Re: New BackupPC Server Hardware; Existing Data Pool

[Tim via users]

On Tue, 2024-02-20 at 07:43 -0500, Tim Evans 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
> 
> 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.

Shot in the dark, approaching this from the webserver since I'm not
familiar with BackupPC:  How old was your previous backup server?

If the webserver is Apache, they've changed how they handle the server
configuration over time.  Now, very little of the default main config
file is used to configure it, just about everything is an individual
configuration file in /etc/httpd/conf.d/.

If you've simply migrated configuration files, they mightn't be that
compatible with the new regime.  You may need to adapt configuration
files.  CGI may be different.  If you use secure connections, you might
need to debug your SSL configuration (old certs, different
configuration techniques, etc).
 
-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64
--
___
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

Re: New BackupPC Server Hardware; Existing Data Pool

[Tim Evans]

On 2/20/24 07:51, Richard Shaw wrote:
On Tue, Feb 20, 2024 at 6:43 AM Tim Evans > 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.

--
___
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

Re: New BackupPC Server Hardware; Existing Data Pool

[Richard Shaw]

On Tue, Feb 20, 2024 at 6:43 AM Tim Evans  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
--
___
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

New BackupPC Server Hardware; Existing Data Pool

[Tim Evans]

[ 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