Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: WayneJVM on January 26, 2009, 06:14:35 PM
-
After following the instructions posted by Daniel about how to install backuppc.fws-3.0 multiple times over a couple of days on clean installations of SME 7.4 on a test server. I have had no luck in getting the contrib to run.
As recommended, I am using the USBManager to mount an external USB drive to /opt/backuppc. This works fine. Installed the contrib as instructed on a clean build of 7.4 (http://sme.firewall-services.com/spip.php?article44).
When I try to access backuppc from http://yourserver/backuppc or from the server-manager panel I get an error 500 Internal server error with the following message from the httpd server:
[Mon Jan 26 10:02:43 2009] [error] [client 192.168.0.67] Setuid script "/opt/backuppc/cgi-bin/BackupPC_Admin" on nosuid filesystem.
[Mon Jan 26 10:02:43 2009] [error] [client 192.168.0.67] Premature end of script headers: BackupPC_Admin
Any ideas?
-
hi
could you please tell us how did you format the external disk?
and please, post the result of
mount
(naturally with external disk mounted)
Thank you
Ciao
Stefano
-
It's actually a ext3 drive that I formated some time ago on another SME 7.3 server. I don't recall the exact process that I used. I'll reformat the drive and get back with you. Is there anything that I should keep in mind for the format?
-
It's actually a ext3 drive that I formated some time ago on another SME 7.3 server. I don't recall the exact process that I used. I'll reformat the drive and get back with you. Is there anything that I should keep in mind for the format?
ext3 should work..
anyway, you did not answer my request :-)
in your next post, please write also the output of
cat /etc/fstab
Ciao
Stefano
-
cat /etc/fstab:
/dev/main/root / ext3 usrquota,grpquota 1 1
/dev/md1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/main/swap swap swap defaults 0 0
/dev/hdb /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0
the mount comand:
/dev/mapper/main-root on / type ext3 (rw,usrquota,grpquota)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/md1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/dev/sda1 on /opt/backuppc type ext3 (rw,nosuid,nodev)
I believe the nosuid is the problem but don't know how to correct it.
Thanks!
-
Anybody have any ideas? I'm still at a loss.
Thanks!
-
Hi. I'm not sure what options are used with the contrib USB manager. Juste try to mount this disk manually (unmount it first with the USB manager contrib, then, on the command line:
mount /dev/sda1 /opt/backuppc
-
Progress...
mounting the USB drive by hand seems to have helped in one regard, I am no longer getting the Internal Server error. However, (you knew this was coming) I am now getting "Error: Unable to connect to BackupPC server". Perhaps a permissions issue? I have tried logging in as admin and backuppc users. Both receive the same error.
Ideas?
Thanks!
-
This just means that backuppc is not started.
/etc/init.d/backuppc start
will stat it. The service should be started automatically on boot next time. I'd suggest you dont use the USB Manager contrib to mount this drive, and instead, add a line like this in /etc/fstab:
/dev/sda1 /opt/backuppc ext3 noatime 0 0
(or if you can change the mount options with the USB Manager contrib, just remove the nosuid)
-
That did the trick! Thanks.
The USB manager contrib seems to have been the root of this problem. Users should NOT use the USB Manager to mount a drive for use with Backuppc.
-
The USB manager contrib seems to have been the root of this problem. Users should NOT use the USB Manager to mount a drive for use with Backuppc.
Please let the author of the contrib know about this. The best place to do this is the Bugtracker, there is an entry for smeserver-usbdiskmanager in the contribution section. Ib this way it will either be fixed or documented. Thanks.