Hello everbody,
I have quite a problem creating a virtual server on Debian Etch 64bit (4.0).
It's a totally fresh installed dedicated server using Webmin 1.470 and Virtualmin 3.68.gpl GPL.
Now when I try to create a virtual server I get following error message.
[code:1]Failed to create virtual server : setquota: Not all specified mountpoints are using quota.[/code:1]
Here is the output of cat /etc/fstab
[code:1]/dev/md1 / ext3 suid,dev,exec 0 1 /dev/sda2 none swap sw /dev/sdb2 none swap sw /dev/md5 /usr xfs defaults 0 2 /dev/md6 /var xfs defaults,usrquota 0 2 /dev/md7 /home xfs grpquota,usrquota,rw 0 2 devpts /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /tmp tmpfs defaults 0 0 [/code:1]
And here is the output of cat /etc/mtab (if you need it)
[code:1]/dev/md1 / ext3 rw 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 procbususb /proc/bus/usb usbfs rw 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0 /dev/md5 /usr xfs rw 0 0 /dev/md6 /var xfs rw,usrquota 0 0 /dev/md7 /home xfs rw,grpquota,usrquota 0 0 none /tmp tmpfs rw 0 0 [/code:1]
I'd appreciate any help since it is pretty urgent.
Cheers, main
Maybe you have this options enabled and you shouldn't:
"Setup IP-based virtual FTP?"
<b>blunt wrote:</b>
<div class='quote'>Maybe you have this options enabled and you shouldn't:
"Setup IP-based virtual FTP?"</div>
Thanks for the info.
As a new virtualmin user this is confusing as it seems that that would need to be enabled for the domains to have any ftp functionality.
I will try it, test and post back results.
This forum software is screwy!
The quote link does not tie to the correct post!
The quote was supposed to be
<b>gromm wrote:</b>
<div class='quote'>Just disable the ProFTPd server in "Features and Plugins" (the Lego block icon). Each virtual domain doesn't need its own separate FTP server unless you have a unique IP for each domain, and you appear to be using one IP for all domains.
This doesn't turn off the FTP server for your customers, it just makes it so that creating new virtual domains on your server works again.</div>
and then I couldn't edit as the edit link says "Opps! There is a bug in the forum software." :)
Well thanks gromm for the advice as disabling the ProFTPd server in "Features and Plugins" allowed me to add new domains and general ftp still works.
Just disable the ProFTPd server in "Features and Plugins" (the Lego block icon). Each virtual domain doesn't need its own separate FTP server unless you have a unique IP for each domain, and you appear to be using one IP for all domains.
This doesn't turn off the FTP server for your customers, it just makes it so that creating new virtual domains on your server works again.
Hrm, I haven't run into that, but just a guess -- if you log into Virtualmin, then:
* Click Webmin on the top-left
* Choose Servers
* Choose Postfix Mail Server
* Click SMTP Server Options
Is the domain you're trying to add listed in the 'Restrict mail relaying' field? Typically, that field is just left at "Default", so if you see it in there, that may be why it's balking.
-Eric
there is a webmin module under system - Disk Quotas
you can enable it there or when not available per haps install it and activate it.
its installed and enabled.
you can run
quotaon -u
quotaon -g
to check:
quotacheck -u -g
to set:
setquota -u
setquota -g
i know the commands myself. still nothing changes...
Is this a virtualized system of some sort? Virtuozzo, OpenVZ, and VServers all have their mount point information copied into place--and the availability of quotas is handled outside of the virtual system. So, the file being copied into place for fstab or mtab needs to accurately reflect the existence of quotas, or Virtualmin won't know that quotas are available.
--
Check out the forum guidelines!
how do i find out if im runing a virtualized system?
<div class='quote'>how do i find out if im runing a virtualized system? </div>
I would think you would already know. ;-)
On VServers based systems, network interfaces usually have silly names, like venet0.
The /proc filesystem may look a little strange and have a few extra (and be missing a few) values.
swap memory may not be available. It'll show as 0 in "top".
/proc/meminfo may have crazy values...like MemFree being bigger than MemTotal (though I think this was a bug in a particular and old VServer implementation).
Xen systems have some proc entries that indicate they are Xen instances. But, your kernel version would also probably have indicated that it was a Xen kernel, and this was doesn't mention Xen.
The kernel log will probably have something about it, as well. (Kernel log is viewable using the "dmesg" command.)
Being on a virtualized system is not the only reason quotas might not work...it's just a common source of trouble.
It could also be that the filesystem is some type that doesn't support quotas, or uses a different set of tools from the usual setquota tools (XFS meets this description, I believe).
But, again, you'd know better than us, since we don't know anything about your system.
--
Check out the forum guidelines!
well its not a virtualised system, and it does support quotas as "Disk quotas" on webmin works perfectly. And when i ry to create a new server, it does create a user and it sets its qoutas. Im just really lost why is it still giving me that error...
Howdy,
Which partitions should be using a quota? And, what's the output of this:
cat /etc/fstab
That error you're getting could be because it's trying to run quotas against a partition that's not setup to do so in the fstab. What could cause that to happen is the trick, and what Joe was thinking when he mentioned the Virtualization issues. But seeing the fstab might help us to get from here to there ;-)
-Eric
my fstab contains this:
proc /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/sda1 none swap sw 0 0
/dev/sda2 / ext3 grpquota,usrquota,rw 0 0
and to addition what ronald has said. how do i know its pointing there?
bump.
i really need this sorted as soon as posible.
Your quota setup in fstasb looks fine. Does mtab also list the quota options?
I've noticed that some systems with homes on the / filesystem have to be rebooted before quotas actually take effect...the install script attempts to remount the filesystem to enable them, but this doesn't always work (I'm not sure why, but probably has something to do with what applications have open files at the time), and a reboot is required.
If you haven't rebooted since enabling quotas in fstab, and setting up the /aquota.group and /aquota.user quota files, I'd recommend giving that a try.
And, of course, if you don't <i>need</i> quotas, you can turn them off in the Module Configuration. And, even if you do need them, you can turn them off while we figure out what the heck is going wrong, so you can actually create virtual servers in the meantime.
As for figuring out what's going wrong, that ones hard. I've never had to troubleshoot quotas, as they've always Just Worked. ;-)
dmesg output after trying to setup a user with quotas, and querying quotas using the repquota command might hold some clues. /var/log/messages also might have something useful.
--
Check out the forum guidelines!
by default VM wants to use suexec, fcgi and place the new domain under /home
I read that apache would be installed from VM repos with suexec enabled pointing at /home instead of /var/www/html
i have no idea how the system has been set up, but might be worth looking at this.
This is probably long fixed for you by now but I was bothered by the same issue for a week until yesterday.
The virtualmin interface was reporting wrong quotas etc, adding new users caused the same error you had I was quite frustrated and figured it was because I was using the free version that it did not work correctly
Then for the hell of it i figured I would turn off quotas and turn them back on. Boom, reporting is fixed, adding users fixed.
/var seems to only have usrquota. That's actually where you need grpquota, since databases live there, and only grpquota can possibly apply. Unless you also have mail on /var (in mbox spools, which is not recommended) you would have little use for usrquota (though I think Virtualmin still wants it enabled).
I don't know if that'll resolve things...but, it's definitely worth a shot (and if it doesn't, filing a bug would be the way forward). Also, Virtualmin can't really enforce quotas accurately if you have two partitions for user data (/home and /var), since quotas apply to each file system separately. So, if you set a 10GB limit, your users could have 10GB of website data and mail in /home and then 10GB of database data in /var, for a total of 20GB. This probably isn't a huge concern. Just something to be aware of.
--
Check out the forum guidelines!
I experienced the same problem : In Virtualmin fresh install create new server give me :
setquota: Not all specified mountpoints are using quota.
The file system of my server is fsx. On the Configuration For module Disk Quotas I noticed the quota commands are for ext filsesystem but as the quotas seems to work well I did not change it.
I then check Webmin / System / Disk and Network Filesystem there I check /home and /var and noticed that /var only has Enable user quotas checked but not Enable group quotas . So I allow group quotas and this solve it for me.
--
Ced
www.lineaire.net