Laurin d'Volts wrote: > On Sun, 2009-04-05 at 16:04 +0200, Holger Parplies wrote: >> - That file doesn't exist? Is there one with a different name in >> /etc/apache2/sites-enable that seems relevant? One in >> /etc/apache2/sites-available? Do the directories /etc/apache2, >> /etc/apache2/sites-enabled and /etc/apache2/sites-available exist? >> - Is apache really running? Hint: 'ps e -C apache2'. > > I understand something could be broken with Sid on the computer I'm > using. However, the other computer I'm using also uses Sid. This makes > me thinks a couple of things: > > 1. Backuppc is not configured correctly
So far nothing you have posted indicates that you have gotten as far as even trying to execute the cgi script. If you did, you would have a more specific error message both in your browser page and in the apache logs. > 2. Something system configuration is not correct That is somewhat obvious, but it is a complex system with many parts configured differently than what other people are using. > 3. Apache is not setup correctly This seems to be the case, but normally the things included with distributions are set up automatically when you install the packages. > 4. The system is broke > 5. Perhaps it's an undiscussed bug. Have you done normal system updates? I can't imagine a component as important as apache being broken in a distribution for very long. > I don't know much about backuppc. We can help with that part, but apache has to execute the cgi first. > I didn't know that understanding apache was a requirement for it. > I was hoping for the tutorials and documentation on backuppc to cover > more of these things in detail. Because I couldn't find a lot of > information, I came here. If things don't start working soon, I'll > figure something out myself. However, I think I'll post here for the > next while. Most distributions come with apache set up and working, and if you use the full url to it's pre-configured cgi location (perhaps http://host.domain/cgi-bin/BackupPC_Admin) the only additional change needed is to set up authentication. > I turned off the firewall to test backuppc CGI. As a note, I keep seeing > my system talk about 127.0.1.1 as being a pingable IP. I find that > unusual. So, maybe that has some importance. I don't know what file > relates to that issue. I'm able to ping 127.0.0.1 and 127.0.1.1. > I tried using 127.0.1.1 in the browser: http://127.0.1.1/backuppc > and that didn't work. By convention (or perhaps a requirement of the tcp/ip spec) every machine has a loopback interface at 127.0.0.1 that is only usable within that same machine. If you use it, you must be running the browser on the same machine and you can use the name localhost instead of the address. The entire 127.x.x.x range is reserved for local use, but it is unusual for anything to use more than 127.0.0.1 so I'm not sure what is going on with 127.0.1.1. > seakit...@widerule:~$ cat /etc/apache2/sites-enabled/000-default > <VirtualHost *:80> > ServerAdmin webmas...@localhost > > DocumentRoot /var/www > <Directory /> > Options FollowSymLinks > AllowOverride None > </Directory> > <Directory /var/www/> > Options Indexes FollowSymLinks MultiViews > AllowOverride None > Order allow,deny > allow from all > </Directory> > > ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ > <Directory "/usr/lib/cgi-bin"> > AllowOverride None > Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch > Order allow,deny > Allow from all > </Directory> > > ErrorLog /var/log/apache2/error.log > > # Possible values include: debug, info, notice, warn, error, > crit, > # alert, emerg. > LogLevel warn > > CustomLog /var/log/apache2/access.log combined > > Alias /doc/ "/usr/share/doc/" > <Directory "/usr/share/doc/"> > Options Indexes MultiViews FollowSymLinks > AllowOverride None > Order deny,allow > Deny from all > Allow from 127.0.0.0/255.0.0.0 ::1/128 > </Directory> > > </VirtualHost> I don't have a debian box to check, but I thought they added another ScriptAlias for backuppc so you could use a url like http://hostname/backuppc and I don't see it there. I do see the locations for the error and access logs. If apache is working at all, every attempt to load a page should write a line to the access.log and any problems will be written to the error.log. Once you have apache working to the point that these logs have some information, someone may be able to help you with the backuppc part. > seakit...@widerule:~$ ps e -C apache2 > PID TTY STAT TIME COMMAND I think that means apache isn't running (but on my system the process is named httpd). If it attempted to start and failed, it would have written something to the error log file that might explain the problem. If it didn't start, you need to set the system up to start it. -- Les Mikesell [email protected] ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
