Dear Craig,
on first attempt, I have just pulled this docker image:
https://github.com/adferrand/docker-backuppc
On the second attempt, I have created a ubuntu 18.04 container, and used
the script you have linked as root (there is normally no other user in
containers). Obviously I had to remove "sudo" prefixes
The result is the same. The /var/www/html/BackupPC is not completly
empty, there are some pngs, gifs, js and css files. Please see complete
list below. Stdout of configure.pl is attached.
Jan
P.S. I successfully run Backuppc v3 using docker, and there is
apperantly many people running the above mentioned image.
0000000.gif 0010000.gif 0011001.gif 1001000.gif 1010001.gif
1100100.gif 1100111.gif 1101101.gif 1110000.gif 1110101.gif
1111000.gif 1111101.gif BackupPC_retro_v2.css favicon.ico
icon-hardlink.png logo320.png
0000011.gif 0010001.gif 1000000.gif 1001100.gif 1011000.gif
1100101.gif 1101000.gif 1101110.gif 1110001.gif 1110110.gif
1111001.gif 1111110.gif BackupPC_retro_v3.css icon-dir.png
icon-symlink.png sorttable.js
0001000.gif 0011000.gif 1000100.gif 1010000.gif 1100000.gif
1100110.gif 1101100.gif 1101111.gif 1110100.gif 1110111.gif
1111100.gif 1111111.gif BackupPC_stnd.css icon-file.png logo.gif
On 12/31/18 3:02 AM, Craig Barratt via BackupPC-users wrote:
> You'll need to be more explicit about what you installed and all the
> steps you took.
>
> Specifically, did you follow these instructions
> <https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-tarball-or-git-on-Ubuntu>?
>
> After you run configure.pl <http://configure.pl> near the middle of the
> script, what output does it generate? Can you confirm after it runs
> that /var/www/html/BackupPC is empty?
>
> Craig
>
>
>
> On Mon, Dec 31, 2018 at 8:49 AM Jan Stransky
> <jan.stransky.c...@gmail.com <mailto:jan.stransky.c...@gmail.com>> wrote:
>
> Hi,
> I am trying to install BackupPC v4.3.0 from Github (more or less).
> I have tried to use docker image (adferrand/docker-backuppc), and ubuntu
> installation script from BPC Docs, and after the installation, I am
> getting 404 error from the web server. I have checked the web server
> configuration, but the folder, shich is targeted
> (/var/www/html/BackupPC) doesn't contain any index or other
> HTML-like file.
> Is it a bug, or am I doing something wrong?
> Cheers,
> Jan
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> <mailto:BackupPC-users@lists.sourceforge.net>
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
Is this a new installation or upgrade for BackupPC? If this is
an upgrade please tell me the full path of the existing BackupPC
configuration file (eg: /etc/BackupPC/config.pl). Otherwise, just
hit return.
--> Full path to existing main config.pl []
I found the following locations for these programs:
bzip2 => /bin/bzip2
cat => /bin/cat
df => /bin/df
gtar/tar => /bin/tar
gzip => /bin/gzip
hostname => /bin/hostname
nmblookup => /usr/bin/nmblookup
par2 => /usr/bin/par2
perl => /usr/bin/perl
ping =>
ping6 =>
rrdtool => /usr/bin/rrdtool
rsync => /usr/bin/rsync
rsync_bpc => /usr/local/bin/rsync_bpc
sendmail => /usr/sbin/sendmail
smbclient => /usr/bin/smbclient
split => /usr/bin/split
ssh/ssh2 => /usr/bin/ssh
--> Are these paths correct? [y]
Please tell me the hostname of the machine that BackupPC will run on.
--> BackupPC will run on host [backuppc]
BackupPC should run as a dedicated user with limited privileges. You
need to create a user. This user will need read/write permission on
the main data directory and read/execute permission on the install
directory (these directories will be setup shortly).
The primary group for this user should also be chosen carefully.
The data directories and files will have group read permission,
so group members can access backup files.
--> BackupPC should run as user [backuppc]
Please specify an install directory for BackupPC. This is where the
BackupPC scripts, library and documentation will be installed.
--> Install directory (full path) [/usr/local/BackupPC]
Please specify a data directory for BackupPC. This is where all the
PC backup data is stored. This file system needs to be big enough to
accommodate all the PCs you expect to backup (eg: at least several GB
per machine).
--> Data directory (full path) [/var/lib/backuppc]
BackupPC has SCGI and CGI perl interfaces that run under Apache. You need
to pick which one to run.
For SCGI, Apache uses the scgi_mod module to communicate with BackupPC_Admin_SCGI,
which handles the requests. This allows Apache to run as a different user as
backuppc. To use SCGI you need to set SCGIServerPort to any spare
non-privileged TCP port number. A negative value disables SCGI.
Important security warning!! The SCGIServerPort must not be accessible by
anyone untrusted. That means you can't allow untrusted users access to the
BackupPC server, and you should block the SCGIServerPort TCP port from
network access.
The traditional alternative is to use CGI. In this case, an executable needs
to be installed Apache's cgi-bin directory. This executable needs to run as
set-uid backuppc, or it can be run under mod_perl with Apache
running as user backuppc.
--> SCGI port (-1 to disable) [-1]
--> CGI bin directory (full path, or empty for no CGI) [/var/www/cgi-bin/BackupPC]
BackupPC's CGI and SCGI script need to display various PNG/GIF
images that should be stored where Apache can serve them. They
should be placed somewhere under Apache's DocumentRoot. BackupPC
also needs to know the URL to access these images. Example:
Apache image directory: /var/www/htdocs/BackupPC
URL for image directory: /BackupPC
The URL for the image directory should start with a slash.
--> Apache image directory (full path, or empty for no S/CGI) [/var/www/html/BackupPC]
--> URL for image directory (omit http://host; starts with '/', or empty for no S/CGI) [/BackupPC]
Ok, we're about to:
- install the binaries, lib and docs in /usr/local/BackupPC
- create the data directory /var/lib/backuppc
- optionally install the cgi-bin interface
- create/update the config.pl file /etc/BackupPC/config.pl
--> Do you want to continue? [y]
Created /usr/local/BackupPC/bin
Created /usr/local/BackupPC/share
Created /usr/local/BackupPC/share/doc
Created /usr/local/BackupPC/share/doc/BackupPC
Created /usr/local/BackupPC/lib
Created /usr/local/BackupPC/lib/BackupPC
Created /usr/local/BackupPC/lib/BackupPC/CGI
Created /usr/local/BackupPC/lib/BackupPC/Config
Created /usr/local/BackupPC/lib/BackupPC/Lang
Created /usr/local/BackupPC/lib/BackupPC/Storage
Created /usr/local/BackupPC/lib/BackupPC/Xfer
Created /usr/local/BackupPC/lib/BackupPC/Zip
Created /usr/local/BackupPC/lib/Net
Created /usr/local/BackupPC/lib/Net/FTP
Created /var/www/html/BackupPC
Created /var/lib/backuppc
Created /var/lib/backuppc/pool
Created /var/lib/backuppc/cpool
Created /var/lib/backuppc/pc
Created /etc/BackupPC
Created /var/log/BackupPC
Created /var/run/BackupPC
Installing binaries in /usr/local/BackupPC/bin
Installing library in /usr/local/BackupPC/lib
Installing images in /var/www/html/BackupPC
Making systemd and init.d scripts
Making Apache configuration file for suid-perl
Installing docs in /usr/local/BackupPC/share/doc/BackupPC
Installing cgi script BackupPC_Admin in /var/www/cgi-bin/BackupPC
Installing config.pl and hosts in /etc/BackupPC
Ok, it looks like we are finished. There are several more things you
will need to do:
- Browse through the config file, /etc/BackupPC/config.pl,
and make sure all the settings are correct. In particular,
you will need to set $Conf{CgiAdminUsers} so you have
administration privileges in the CGI interface.
- Edit the list of hosts to backup in /etc/BackupPC/hosts.
- Read the documentation in /usr/local/BackupPC/doc/BackupPC.html.
Please pay special attention to the security section.
- Verify that the CGI script BackupPC_Admin runs correctly. You might
need to change the permissions or group ownership of BackupPC_Admin.
If this is an upgrade and you are using mod_perl, you will need
to restart Apache. Otherwise it will have stale code.
- BackupPC should be ready to start. Don't forget to run it
as user backuppc! The installation also contains
a systemd/backuppc.service script that can be installed so
that BackupPC can auto-start on boot. This will also enable
administrative users to start the server from the CGI interface.
See systemd/README.
Enjoy!
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
