Casey Price
Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>
Follow us on Twitter <https://twitter.com/#%21/SmileInternet>
Like us on Facebook <https://www.facebook.com/smileglobal>
On 12/11/11 8:11 PM, Eric Shubert wrote:
On 12/11/2011 08:12 PM, Casey Price wrote:
On 12/11/11 6:29 PM, Eric Shubert wrote:
On 12/11/2011 03:20 PM, Casey Price wrote:
Having an issue updating clamav-toaster using qtp-newmodel...
Basically it looks like it is having difficulty using fuse to mount
the
sandbox.
*_See below for details:_*
Shall we build a new sandbox at /mnt/qtp-sandbox? [y]/n: y
Removing sandbox at /mnt/qtp-sandbox ...
qtp-umount-sandbox v0.3.2
qtp-umount-sandbox: sandbox not mounted
Would you like a unionfs/overlay sandbox? (recommended) [y]/n: y
Using FUSE union filesystem ...
qtp-mount-sandbox v0.3.3
qtp-mount-sandbox - installing dkms-fuse ...
qtp-mount-sandbox - this could take a few moments - please be patient
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: pubmirrors.reflected.net
* extras: mirror.wiredtree.com
* rpmforge: apt.sw.be
* updates: mirror.sanctuaryhost.com
Setting up Install Process
No package dkms-fuse available.
Nothing to do
*umount: /mnt/qtp-sandbox/tmp: not mounted
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
fuse: failed to open /dev/fuse: Permission denied
mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist
cp: target `/mnt/qtp-sandbox/var/lib/rpm' is not a directory
qtp-mount-sandbox: sandbox was not mounted successfully
qtp-newmodel - qtp-mount-sandbox failed, exiting
*
Any suggestions? I've checked the permissions on /dev/fuse, and
they are
as follows:
[root@q2rep dev]# ls -ls fuse
0 crw-rw---- 1 root fuse 10, 229 Dec 12 00:48 fuse
Using CentOS 5.7 i386.
Thanks,
--
Casey Price
Which kernel version?
[root@q2rep ~]# uname -a
Linux q2rep.smileglobal.com 2.6.18-274.el5.028stab093.2 #1 SMP Tue Aug
23 16:46:17 MSD 2011 i686 i686 i386 GNU/Linux
(this is an OpenVZ-based VPS), I did a bit of poking around, and it
sounds like OpenVZ doesn't allow the end-user to have any control over
modules (/lib/modules/) is empty. Its weird that everything else up to
this point has worked, but maybe OpenVZ just isn't compatible?
Which qmailtoaster-plus version?
[root@q2rep ~]# qtp-whatami
qtp-whatami v0.3.7 Mon Dec 12 06:09:55 MSK 2011
DISTRO=CentOS
OSVER=5.7
QTARCH=i686
QTKERN=2.6.18-274.el5.028stab093.2
BUILD_DIST=cnt50
BUILD_DIR=/usr/src/redhat
This machine's OS is supported and has been tested
I think the latest kernels don't need fuse or dkms, or something like
that. I don't recall exactly off hand.
Let me know which versions above, and I'll get things fixed up. Might
be fixed already in the source svn repo, but I'll need to check into
it tomorrow.
---------------------------------------------------------------------------------
OpenVZ might be the problem, but I'm not convinced (although I'm no
expert with OpenVZ either).
I'm running it ok with 2.6.18-274.3.1.el5 as a VM under VMware
Server2. OpenVZ is admittedly quite a different beast though. I don't
know if guests can run fuse kernel modules or not, but I would think
they could since they run in user space.
The big problem I see first is that you don't have dkms-fuse
available, but I do:
[root@tacs-mail modules]# rpm -q dkms-fuse
dkms-fuse-2.7.4-1.nodist.rf
[root@tacs-mail modules]# rpm -ql dkms-fuse
/usr/src/fuse-2.7.4-1.nodist.rf
/usr/src/fuse-2.7.4-1.nodist.rf/Makefile.in
/usr/src/fuse-2.7.4-1.nodist.rf/config.h.in
/usr/src/fuse-2.7.4-1.nodist.rf/configure
/usr/src/fuse-2.7.4-1.nodist.rf/configure.ac
/usr/src/fuse-2.7.4-1.nodist.rf/control.c
/usr/src/fuse-2.7.4-1.nodist.rf/dev.c
/usr/src/fuse-2.7.4-1.nodist.rf/dir.c
/usr/src/fuse-2.7.4-1.nodist.rf/dkms.conf
/usr/src/fuse-2.7.4-1.nodist.rf/file.c
/usr/src/fuse-2.7.4-1.nodist.rf/fuse_i.h
/usr/src/fuse-2.7.4-1.nodist.rf/fuse_kernel.h
/usr/src/fuse-2.7.4-1.nodist.rf/inode.c
/usr/src/fuse-2.7.4-1.nodist.rf/install-sh
It came from the rpmforge repo. Is that package no longer available in
RF repo? Please investigate. Note, qtp-newmodel (qtp-install-rpmforge
actually) should have set that repo up for you. There have been some
changes in that area, so please look to see what might be amiss in
that area. I seem to remember RF changed some things around at one
point. Perhaps we haven't rolled the changes for that into a current
QTP release?
It appears that dkms-fuse is no longer available from the RF repo. Did a
little searching and stumbled across this:
The content of this thread is obsolete -- it's pre CentOS-5.4. As of 5.4
(kernel 2.6.18-164), the fuse module is part of the kernel. You do not
need dkms-fuse any more. If you have already installed it under CentOS
5.4, remove it with a*yum remove dkms-fuse*. If you are not running
CentOS 5.4, I suggest you update your system.
Still no luck though. I've contacted the support team for company
running the VPS to see if I could switch over to one of their Xen hosts,
as I know for sure it will work with Xen. I'll let you know if I make
any further progress.
Thanks for digging.
