This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
never mind if that first paste ends up posting. this is the results of mount
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)<br><br>Post edited by: antishane, at: 2009/03/31 17:22
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw,grpquota,usrquota)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
im sorry, i pasted out of the wrong ssh console. it is actually this..
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
Ahh... that's a bit different. In that case, the / mountpoint doesn't have quotas enabled on it.
Your fstab should have "grpquota,usrquota" setup in it as options for /dev/sda1. After you add that, you can either remount /, or reboot to apply those options.
-Eric
im glad there is this section called newbees because i can not get this to work yet.
i added that stuff to it and now here is what it looks like:
/dev/sda1 on / type ext3 (rw,noatime,grpquota,usrquota,errors=remount-ro)
proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
but still -
The module could not find the mount point for your home directories filesystem /home. Quotas editing has been disabled.
is there anyway to get the install.sh script to download 3.66? here's what is frustrating, 2 identical machines (slice virtual with centos 5.2 on both from the same image). the working machine never had that message from the check.cgi during setups or at all. the second machine is installing 3.67 from the instal.sh script. the output from the command 'mount' is exactly the same on both of them, the module config (Disk and Network Filesystems)is the same on both of them.
<div class='quote'>is there anyway to get the install.sh script to download 3.66?</div>
This brings up two big, "Why" questions:
Why do you want install.sh to do something on a system that's already installed? Once Virtualmin is running you should never run install.sh again. Not for updates, not for downgrades, not for anything.
Why do you want an older version? There are two possible causes for this warning, and neither should make you think "I need to downgrade to an older version" as the solution:
1. You really don't have quota support on this new system, and Virtualmin is correctly telling you so. 3.67 might be more accurate at detecting when quotas don't actually work, even if the mtab or fstab says they should. VPS systems are often tricky with regard to quotas. Try using some of the command line quota tools to see if you actually have quotas:
repquota /home
This will give an error if quotas aren't actually working, and will display a per user report if quotas are working. If they aren't working, we'll need to start troubleshooting why (downgrading to 3.66 isn't going to fix the problem, it just might ignore it silently).
2. 3.67 has a bug in detecting whether quotas are available or not, and while your system actually does have working quotas, Virtualmin fails to detect them. The solution here is to file a bug in the tracker, and get the bug fixed. (Then you <i>might</i> consider downgrading...but I suspect Jamie will provide a workaround in the ticket that doesn't involve using old versions.)
while my quota's are working fine, the above cmd gives me:
repquota: Mountpoint (or device) /home not found.
repquota: Not all specified mountpoints are using quota
<div class='quote'>while my quota's are working fine, the above cmd gives me:
repquota: Mountpoint (or device) /home not found.
repquota: Not all specified mountpoints are using quota </div>
That just means you don't have a separate /home partition.
In your case if would be:
repquota /
Maybe in the OP's case as well. I didn't pay attention to the mounted file system information, though I think he posted it.
"Why do you want install.sh to do something on a system that's already installed? Why do you want an older version?"
This is the same question twice. It would be nice to have the install.sh script that would install 3.66 because it appeared to work (because it listed no quota errors), so obviously if I could do an automated installation of 3.66 my problem would be solved without trying to re-invent a wheel.
install.sh is for installation of the full stack using the local package manager...it doesn't care about versions. It doesn't even <i>know</i> about versions, and it would be a dramatically different creature if it did.
install.sh is not for picking and choosing what packages you want installed. That's what your package manager is for (though they also assume you want the latest available version).
<div class='quote'>3.66 because it appeared to work (because it listed no quota errors), so obviously if I could do an automated installation of 3.66 my problem would be solved without trying to re-invent a wheel.</div>
But then you'd have other problems. We don't roll out new versions for our health or amusement. There were several security issues in Install Scripts in 3.66. There was a major memory usage enhancement in 3.67. Rolling backward is not the right solution. If there is a bug, we will fix it, and fast.
You can, of course, install specific versions using rpm:
Assuming you're using GPL. (If using Professional, you'll need to use your serial number and license key as username and password to download the package first.)
I kinda suspect you'll get 3.66 installed only to find that it behaves exactly the same way. I don't remember any changes in the way we detect quotas, but I may have missed the check-in. ;-)
Anyway, I saw Jamie had replied to your ticket about this, so give him what he asked for (if you haven't already), and the problem will begin to get resolved.
You haven't mentioned what you got from the repquota command. Again, it may be that quotas aren't actually working on the new system. Quotas can be very tricky on VPS systems.
[root@beef2-1 ~]# repquota /home
repquota: Mountpoint (or device) /home not found.
repquota: Not all specified mountpoints are using quota.
[root@beef2-1 ~]#
I appreciate you pointing out the security benefits of 3.67. Yes I am using GPL because I am seriously thinking of getting pro. Ultimately I will have a local box to run this from but I was just wanting to be familiar with it to make sure it would suite my needs.
Thanks for the quick responses! That is something that I almost never seen from any software company and that is making me real comfortable with this consideration.
never mind if that first paste ends up posting. this is the results of mount
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)<br><br>Post edited by: antishane, at: 2009/03/31 17:22
Howdy,
If you log in over SSH, and type "mount", what output do you receive?
-Eric
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw,grpquota,usrquota)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
Hrm, it should be able figure that out, you certainly don't have anything unusual going on there.
What I'd recommend is filing a bug report, using the Bugs and Issues link below, and Jamie should be able to help get your system straightened out.
Thanks,
-Eric
im sorry, i pasted out of the wrong ssh console. it is actually this..
/dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro)
proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
Ahh... that's a bit different. In that case, the / mountpoint doesn't have quotas enabled on it.
Your fstab should have "grpquota,usrquota" setup in it as options for /dev/sda1. After you add that, you can either remount /, or reboot to apply those options.
-Eric
ok, ill give it a shot. thanks
im glad there is this section called newbees because i can not get this to work yet.
i added that stuff to it and now here is what it looks like:
/dev/sda1 on / type ext3 (rw,noatime,grpquota,usrquota,errors=remount-ro)
proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
but still -
The module could not find the mount point for your home directories filesystem /home. Quotas editing has been disabled.
is there anyway to get the install.sh script to download 3.66? here's what is frustrating, 2 identical machines (slice virtual with centos 5.2 on both from the same image). the working machine never had that message from the check.cgi during setups or at all. the second machine is installing 3.67 from the instal.sh script. the output from the command 'mount' is exactly the same on both of them, the module config (Disk and Network Filesystems)is the same on both of them.
confused
<div class='quote'>is there anyway to get the install.sh script to download 3.66?</div>
This brings up two big, "Why" questions:
Why do you want install.sh to do something on a system that's already installed? Once Virtualmin is running you should never run install.sh again. Not for updates, not for downgrades, not for anything.
Why do you want an older version? There are two possible causes for this warning, and neither should make you think "I need to downgrade to an older version" as the solution:
1. You really don't have quota support on this new system, and Virtualmin is correctly telling you so. 3.67 might be more accurate at detecting when quotas don't actually work, even if the mtab or fstab says they should. VPS systems are often tricky with regard to quotas. Try using some of the command line quota tools to see if you actually have quotas:
repquota /home
This will give an error if quotas aren't actually working, and will display a per user report if quotas are working. If they aren't working, we'll need to start troubleshooting why (downgrading to 3.66 isn't going to fix the problem, it just might ignore it silently).
2. 3.67 has a bug in detecting whether quotas are available or not, and while your system actually does have working quotas, Virtualmin fails to detect them. The solution here is to file a bug in the tracker, and get the bug fixed. (Then you <i>might</i> consider downgrading...but I suspect Jamie will provide a workaround in the ticket that doesn't involve using old versions.)
--
Check out the forum guidelines!
while my quota's are working fine, the above cmd gives me:
repquota: Mountpoint (or device) /home not found.
repquota: Not all specified mountpoints are using quota
<div class='quote'>while my quota's are working fine, the above cmd gives me:
repquota: Mountpoint (or device) /home not found.
repquota: Not all specified mountpoints are using quota </div>
That just means you don't have a separate /home partition.
In your case if would be:
repquota /
Maybe in the OP's case as well. I didn't pay attention to the mounted file system information, though I think he posted it.
Sorry for the confusion.
--
Check out the forum guidelines!
aha yes this latter cmd gives a lot of output
thank you
"Why do you want install.sh to do something on a system that's already installed? Why do you want an older version?"
This is the same question twice. It would be nice to have the install.sh script that would install 3.66 because it appeared to work (because it listed no quota errors), so obviously if I could do an automated installation of 3.66 my problem would be solved without trying to re-invent a wheel.
I think we're talking past one another.
install.sh is for installation of the full stack using the local package manager...it doesn't care about versions. It doesn't even <i>know</i> about versions, and it would be a dramatically different creature if it did.
install.sh is not for picking and choosing what packages you want installed. That's what your package manager is for (though they also assume you want the latest available version).
<div class='quote'>3.66 because it appeared to work (because it listed no quota errors), so obviously if I could do an automated installation of 3.66 my problem would be solved without trying to re-invent a wheel.</div>
But then you'd have other problems. We don't roll out new versions for our health or amusement. There were several security issues in Install Scripts in 3.66. There was a major memory usage enhancement in 3.67. Rolling backward is not the right solution. If there is a bug, we will fix it, and fast.
You can, of course, install specific versions using rpm:
rpm -ivh --oldpackage http://software.virtualmin.com/gpl/universal/wbm-virtual-server-3.66.gpl...
Assuming you're using GPL. (If using Professional, you'll need to use your serial number and license key as username and password to download the package first.)
I kinda suspect you'll get 3.66 installed only to find that it behaves exactly the same way. I don't remember any changes in the way we detect quotas, but I may have missed the check-in. ;-)
Anyway, I saw Jamie had replied to your ticket about this, so give him what he asked for (if you haven't already), and the problem will begin to get resolved.
You haven't mentioned what you got from the repquota command. Again, it may be that quotas aren't actually working on the new system. Quotas can be very tricky on VPS systems.
--
Check out the forum guidelines!
Oh ya, my bad.
[root@beef2-1 ~]# repquota /home
repquota: Mountpoint (or device) /home not found.
repquota: Not all specified mountpoints are using quota.
[root@beef2-1 ~]#
I appreciate you pointing out the security benefits of 3.67. Yes I am using GPL because I am seriously thinking of getting pro. Ultimately I will have a local box to run this from but I was just wanting to be familiar with it to make sure it would suite my needs.
Thanks for the quick responses! That is something that I almost never seen from any software company and that is making me real comfortable with this consideration.
Shane