[qmailtoaster] Re: Has something changed in QT?
Do you have the latest qmailtoaster-plus and qmailtoaster-plus.repo packages when you do this? You'll need the latest of both. I'm not sure what that ISO does regarding updating. Patrick Ring wrote: Interesting I notice now that there are 2 kernels listed in the splash screen (grub)(...one is SMP and the other is not). I'll check on that. However, "newmodel" errors out at the same spot if I install QMT ISO, reboot, and run newmodel (no "yum update"). I'll check that though. Thanks, Patrick M. Ring P. Ring Technologies Louisiana Web Host, LLC. 985-868-4200 -Original Message- From: Maxwell Smart [mailto:c...@yother.com] Sent: Monday, January 04, 2010 6:14 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Has something changed in QT? Are you certain you're booting the proper kernel. I ran into the very same problem and never did figure out how to get it to boot into the proper kernel. CJ On 01/04/2010 03:51 PM, Patrick Ring wrote: OK. I finally got back to working on this. (sorry for the delay) I tried a "yum install kernel-smp-devel" (installed/complete), rebooted, then tried running the newmodel script. Got the same errors. Should I attempt to download/build the fuse and see where this takes me? My goal, originally, was just to make a quick-and-dirty test server based on the older QMT ISO (w/ CentOS 4.x)... Though it has become a bit of a challenge (for the update). It's running in a VMWare ESXi 3.5 instance. I guess the only reason I wanted to update was for the up-to-date SPAM, virus, etc. (I know the def's update frequently as cron's, but I figured patched programs) Thanks, Patrick M. Ring P. Ring Technologies Louisiana Web Host, LLC. 985-868-4200 -Original Message- From: Borg [mailto:b...@borgnet.ro] Sent: Saturday, January 02, 2010 5:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Has something changed in QT? The upgrade from 4.8 to 5.4 put only the smp kernel. I hand installed the kernel-smp-devel. Maybe is an issue with the fact that smp kernel is the default kernel installed by the new version? On the other hand, we are talking about a major upgrade to a higher version. I didn't expected to run so smoothly. The problem with fuse.ko and ltld.h were the only I had. I made two upgrades, one in vmware and one on a physical machine, both with the same problem but easily fixed. How is your install Patrick? Eric Shubert wrote: I don't believe that autofs comes into play with fuse and unionfs, which is what qtp-newmodel uses now. On the other hand, a missing fuse.ko module is consistent with the error message(s) we're seeing. That's likely the problem. I'm not positive where that module comes from. I think it's built as part of the installation of the dkms-fuse package. If kernel-smp-devel is missing (and you're running the smp kernel), that's likely the culprit. Such a dependency might be missing. I'd like to get this fixed if we can pin this down. Borg wrote: I forgot, here's all i have done. In my case fuse was installed but fuse.ko missing. I installed kernel headers for current running kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I have fuse-2.7.4-1.nodist package. In fuse source you'll find script for config and install. I run ./configure, ./install-sh, make and make install. Then modprobe fuse run swiftly and newmodel had no problems further. Maybe autofs is not needed but it was a trial and error to find the problem with fuse. Borg wrote: I cheched bash history and I am sure I started autofs right before running newmodel. And found a new thing. Although fuse reports to be installed, fuse.ko is missing, so I had to install kernel-headers and in my case kernel-smp-devel. Patrick Ring wrote: I did run across a thread on this list that talked about disabling autofs... So, do you think I need to make sure it is ON and not 0FF then? Thank you, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: Borg To: qmailtoaster-list@qmailtoaster.com Sent: Sat Jan 02 04:51:24 2010 Subject: Re: [qmailtoaster] Has something changed in QT? Hello to all. I stumbled across the same problem. I installed qmt iso based on centos4 then updated to 4.8. After that I booted the last centos5 from dvd and upgraded. Then when tried to newmodel, got the same error. But is only a matter of installing dkms-fuse and, do not forget to /etc/init/d/autofs start. I think the autofs is the answer. Then everything went ok. Also, later on configuring i remember i had to manually install libtool-ltld-devel to provide ltld.h. Sorry if i am not explaining very exactly but I made all these last year in oct
RE: [qmailtoaster] Re: Has something changed in QT?
Interesting I notice now that there are 2 kernels listed in the splash screen (grub)(...one is SMP and the other is not). I'll check on that. However, "newmodel" errors out at the same spot if I install QMT ISO, reboot, and run newmodel (no "yum update"). I'll check that though. Thanks, Patrick M. Ring P. Ring Technologies Louisiana Web Host, LLC. 985-868-4200 -Original Message- From: Maxwell Smart [mailto:c...@yother.com] Sent: Monday, January 04, 2010 6:14 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Has something changed in QT? Are you certain you're booting the proper kernel. I ran into the very same problem and never did figure out how to get it to boot into the proper kernel. CJ On 01/04/2010 03:51 PM, Patrick Ring wrote: > OK. I finally got back to working on this. (sorry for the delay) > > I tried a "yum install kernel-smp-devel" (installed/complete), > rebooted, then tried running the newmodel script. Got the same errors. > > Should I attempt to download/build the fuse and see where this takes me? > > My goal, originally, was just to make a quick-and-dirty test server > based on the older QMT ISO (w/ CentOS 4.x)... Though it has become a > bit of a challenge (for the update). It's running in a VMWare ESXi 3.5 > instance. I guess the only reason I wanted to update was for the > up-to-date SPAM, virus, etc. (I know the def's update frequently as > cron's, but I figured patched programs) > > Thanks, > Patrick M. Ring > P. Ring Technologies > Louisiana Web Host, LLC. > 985-868-4200 > > -Original Message- > From: Borg [mailto:b...@borgnet.ro] > Sent: Saturday, January 02, 2010 5:24 PM > To: qmailtoaster-list@qmailtoaster.com > Subject: Re: [qmailtoaster] Re: Has something changed in QT? > > The upgrade from 4.8 to 5.4 put only the smp kernel. I hand installed > the kernel-smp-devel. Maybe is an issue with the fact that smp kernel > is the default kernel installed by the new version? > On the other hand, we are talking about a major upgrade to a higher > version. I didn't expected to run so smoothly. The problem with > fuse.ko and ltld.h were the only I had. I made two upgrades, one in > vmware and one on a physical machine, both with the same problem but easily fixed. > How is your install Patrick? > > Eric Shubert wrote: > >> I don't believe that autofs comes into play with fuse and unionfs, >> which is what qtp-newmodel uses now. >> >> On the other hand, a missing fuse.ko module is consistent with the >> error message(s) we're seeing. That's likely the problem. I'm not >> positive where that module comes from. I think it's built as part of >> the installation of the dkms-fuse package. >> >> If kernel-smp-devel is missing (and you're running the smp kernel), >> that's likely the culprit. Such a dependency might be missing. I'd >> like to get this fixed if we can pin this down. >> >> Borg wrote: >> >>> I forgot, here's all i have done. In my case fuse was installed but >>> fuse.ko missing. I installed kernel headers for current running >>> kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I >>> have fuse-2.7.4-1.nodist package. In fuse source you'll find script >>> for config and install. I run ./configure, ./install-sh, make and >>> make install. Then modprobe fuse run swiftly and newmodel had no >>> problems further. >>> Maybe autofs is not needed but it was a trial and error to find the >>> problem with fuse. >>> >>> >>> Borg wrote: >>> >>>> I cheched bash history and I am sure I started autofs right before >>>> running newmodel. And found a new thing. Although fuse reports to >>>> be >>>> > >>>> installed, fuse.ko is missing, so I had to install kernel-headers >>>> and in my case kernel-smp-devel. >>>> Patrick Ring wrote: >>>> >>>>> I did run across a thread on this list that talked about disabling >>>>> autofs... So, do you think I need to make sure it is ON and not >>>>> 0FF >>>>> > >>>>> then? >>>>> Thank you, >>>>> Patrick Ring >>>>> -- >>>>> Sent from my BlackBerry Wireless Device >>>>> >>>>> >>>>> -Original Message- >>>>> From: Borg >>>>> To: qmailtoaster-list@qmailtoaster.
Re: [qmailtoaster] Re: Has something changed in QT?
Are you certain you're booting the proper kernel. I ran into the very same problem and never did figure out how to get it to boot into the proper kernel. CJ On 01/04/2010 03:51 PM, Patrick Ring wrote: > OK. I finally got back to working on this. (sorry for the delay) > > I tried a "yum install kernel-smp-devel" (installed/complete), rebooted, > then tried running the newmodel script. Got the same errors. > > Should I attempt to download/build the fuse and see where this takes me? > > My goal, originally, was just to make a quick-and-dirty test server > based on the older QMT ISO (w/ CentOS 4.x)... Though it has become a bit > of a challenge (for the update). It's running in a VMWare ESXi 3.5 > instance. I guess the only reason I wanted to update was for the > up-to-date SPAM, virus, etc. (I know the def's update frequently as > cron's, but I figured patched programs) > > Thanks, > Patrick M. Ring > P. Ring Technologies > Louisiana Web Host, LLC. > 985-868-4200 > > -Original Message- > From: Borg [mailto:b...@borgnet.ro] > Sent: Saturday, January 02, 2010 5:24 PM > To: qmailtoaster-list@qmailtoaster.com > Subject: Re: [qmailtoaster] Re: Has something changed in QT? > > The upgrade from 4.8 to 5.4 put only the smp kernel. I hand installed > the kernel-smp-devel. Maybe is an issue with the fact that smp kernel is > the default kernel installed by the new version? > On the other hand, we are talking about a major upgrade to a higher > version. I didn't expected to run so smoothly. The problem with fuse.ko > and ltld.h were the only I had. I made two upgrades, one in vmware and > one on a physical machine, both with the same problem but easily fixed. > How is your install Patrick? > > Eric Shubert wrote: > >> I don't believe that autofs comes into play with fuse and unionfs, >> which is what qtp-newmodel uses now. >> >> On the other hand, a missing fuse.ko module is consistent with the >> error message(s) we're seeing. That's likely the problem. I'm not >> positive where that module comes from. I think it's built as part of >> the installation of the dkms-fuse package. >> >> If kernel-smp-devel is missing (and you're running the smp kernel), >> that's likely the culprit. Such a dependency might be missing. I'd >> like to get this fixed if we can pin this down. >> >> Borg wrote: >> >>> I forgot, here's all i have done. In my case fuse was installed but >>> fuse.ko missing. I installed kernel headers for current running >>> kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I >>> have fuse-2.7.4-1.nodist package. In fuse source you'll find script >>> for config and install. I run ./configure, ./install-sh, make and >>> make install. Then modprobe fuse run swiftly and newmodel had no >>> problems further. >>> Maybe autofs is not needed but it was a trial and error to find the >>> problem with fuse. >>> >>> >>> Borg wrote: >>> >>>> I cheched bash history and I am sure I started autofs right before >>>> running newmodel. And found a new thing. Although fuse reports to be >>>> > >>>> installed, fuse.ko is missing, so I had to install kernel-headers >>>> and in my case kernel-smp-devel. >>>> Patrick Ring wrote: >>>> >>>>> I did run across a thread on this list that talked about disabling >>>>> autofs... So, do you think I need to make sure it is ON and not 0FF >>>>> > >>>>> then? >>>>> Thank you, >>>>> Patrick Ring >>>>> -- >>>>> Sent from my BlackBerry Wireless Device >>>>> >>>>> >>>>> -Original Message- >>>>> From: Borg >>>>> To: qmailtoaster-list@qmailtoaster.com >>>>> >>>>> Sent: Sat Jan 02 04:51:24 2010 >>>>> Subject: Re: [qmailtoaster] Has something changed in QT? >>>>> >>>>> Hello to all. >>>>> I stumbled across the same problem. I installed qmt iso based on >>>>> centos4 >>>>> then updated to 4.8. After that I booted the last centos5 from dvd >>>>> and upgraded. Then when tried to newmodel, got the same error. But >>>>> is only a matter of installing dkms-fuse and, do not forget to >>>>> /etc/init/d/autofs start. I think the autofs is the an
RE: [qmailtoaster] Re: Has something changed in QT?
OK. I finally got back to working on this. (sorry for the delay) I tried a "yum install kernel-smp-devel" (installed/complete), rebooted, then tried running the newmodel script. Got the same errors. Should I attempt to download/build the fuse and see where this takes me? My goal, originally, was just to make a quick-and-dirty test server based on the older QMT ISO (w/ CentOS 4.x)... Though it has become a bit of a challenge (for the update). It's running in a VMWare ESXi 3.5 instance. I guess the only reason I wanted to update was for the up-to-date SPAM, virus, etc. (I know the def's update frequently as cron's, but I figured patched programs) Thanks, Patrick M. Ring P. Ring Technologies Louisiana Web Host, LLC. 985-868-4200 -Original Message- From: Borg [mailto:b...@borgnet.ro] Sent: Saturday, January 02, 2010 5:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Has something changed in QT? The upgrade from 4.8 to 5.4 put only the smp kernel. I hand installed the kernel-smp-devel. Maybe is an issue with the fact that smp kernel is the default kernel installed by the new version? On the other hand, we are talking about a major upgrade to a higher version. I didn't expected to run so smoothly. The problem with fuse.ko and ltld.h were the only I had. I made two upgrades, one in vmware and one on a physical machine, both with the same problem but easily fixed. How is your install Patrick? Eric Shubert wrote: > I don't believe that autofs comes into play with fuse and unionfs, > which is what qtp-newmodel uses now. > > On the other hand, a missing fuse.ko module is consistent with the > error message(s) we're seeing. That's likely the problem. I'm not > positive where that module comes from. I think it's built as part of > the installation of the dkms-fuse package. > > If kernel-smp-devel is missing (and you're running the smp kernel), > that's likely the culprit. Such a dependency might be missing. I'd > like to get this fixed if we can pin this down. > > Borg wrote: >> I forgot, here's all i have done. In my case fuse was installed but >> fuse.ko missing. I installed kernel headers for current running >> kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I >> have fuse-2.7.4-1.nodist package. In fuse source you'll find script >> for config and install. I run ./configure, ./install-sh, make and >> make install. Then modprobe fuse run swiftly and newmodel had no >> problems further. >> Maybe autofs is not needed but it was a trial and error to find the >> problem with fuse. >> >> >> Borg wrote: >>> I cheched bash history and I am sure I started autofs right before >>> running newmodel. And found a new thing. Although fuse reports to be >>> installed, fuse.ko is missing, so I had to install kernel-headers >>> and in my case kernel-smp-devel. >>> Patrick Ring wrote: >>>> >>>> I did run across a thread on this list that talked about disabling >>>> autofs... So, do you think I need to make sure it is ON and not 0FF >>>> then? >>>> Thank you, >>>> Patrick Ring >>>> -- >>>> Sent from my BlackBerry Wireless Device >>>> >>>> >>>> -Original Message- >>>> From: Borg >>>> To: qmailtoaster-list@qmailtoaster.com >>>> >>>> Sent: Sat Jan 02 04:51:24 2010 >>>> Subject: Re: [qmailtoaster] Has something changed in QT? >>>> >>>> Hello to all. >>>> I stumbled across the same problem. I installed qmt iso based on >>>> centos4 >>>> then updated to 4.8. After that I booted the last centos5 from dvd >>>> and upgraded. Then when tried to newmodel, got the same error. But >>>> is only a matter of installing dkms-fuse and, do not forget to >>>> /etc/init/d/autofs start. I think the autofs is the answer. Then >>>> everything went ok. >>>> Also, >>>> later on configuring i remember i had to manually install >>>> libtool-ltld-devel to provide ltld.h. >>>> Sorry if i am not explaining very exactly but I made all these last >>>> year in october and i do not remember all the operations step by >>>> step. Hope this help. >>>> Regards. >>>> >>>> Aristotel Neamtu >>>> >>>> >>>> Patrick Ring wrote: >>>> > I am putting together a virtual (VMWare) with the QmailToaster >>>> > ISO (CentOS 4.X). >>>> > > I'm
Re: [qmailtoaster] Re: Has something changed in QT?
I haven't yet gotten back to it...just got back into town. I'll hopefully get some time tonight. Thanks, Pat. -- Sent from my BlackBerry Wireless Device -Original Message- From: Borg To: qmailtoaster-list@qmailtoaster.com Sent: Sat Jan 02 17:24:08 2010 Subject: Re: [qmailtoaster] Re: Has something changed in QT? The upgrade from 4.8 to 5.4 put only the smp kernel. I hand installed the kernel-smp-devel. Maybe is an issue with the fact that smp kernel is the default kernel installed by the new version? On the other hand, we are talking about a major upgrade to a higher version. I didn't expected to run so smoothly. The problem with fuse.ko and ltld.h were the only I had. I made two upgrades, one in vmware and one on a physical machine, both with the same problem but easily fixed. How is your install Patrick? Eric Shubert wrote: > I don't believe that autofs comes into play with fuse and unionfs, > which is what qtp-newmodel uses now. > > On the other hand, a missing fuse.ko module is consistent with the > error message(s) we're seeing. That's likely the problem. I'm not > positive where that module comes from. I think it's built as part of > the installation of the dkms-fuse package. > > If kernel-smp-devel is missing (and you're running the smp kernel), > that's likely the culprit. Such a dependency might be missing. I'd > like to get this fixed if we can pin this down. > > Borg wrote: >> I forgot, here's all i have done. In my case fuse was installed but >> fuse.ko missing. I installed kernel headers for current running >> kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I >> have fuse-2.7.4-1.nodist package. In fuse source you'll find script >> for config and install. I run ./configure, ./install-sh, make and >> make install. Then modprobe fuse run swiftly and newmodel had no >> problems further. >> Maybe autofs is not needed but it was a trial and error to find the >> problem with fuse. >> >> >> Borg wrote: >>> I cheched bash history and I am sure I started autofs right before >>> running newmodel. And found a new thing. Although fuse reports to be >>> installed, fuse.ko is missing, so I had to install kernel-headers >>> and in my case kernel-smp-devel. >>> Patrick Ring wrote: >>>> >>>> I did run across a thread on this list that talked about disabling >>>> autofs... So, do you think I need to make sure it is ON and not 0FF >>>> then? >>>> Thank you, >>>> Patrick Ring >>>> -- >>>> Sent from my BlackBerry Wireless Device >>>> >>>> >>>> -Original Message- >>>> From: Borg >>>> To: qmailtoaster-list@qmailtoaster.com >>>> >>>> Sent: Sat Jan 02 04:51:24 2010 >>>> Subject: Re: [qmailtoaster] Has something changed in QT? >>>> >>>> Hello to all. >>>> I stumbled across the same problem. I installed qmt iso based on >>>> centos4 >>>> then updated to 4.8. After that I booted the last centos5 from dvd and >>>> upgraded. Then when tried to newmodel, got the same error. But is >>>> only a >>>> matter of installing dkms-fuse and, do not forget to >>>> /etc/init/d/autofs >>>> start. I think the autofs is the answer. Then everything went ok. >>>> Also, >>>> later on configuring i remember i had to manually install >>>> libtool-ltld-devel to provide ltld.h. >>>> Sorry if i am not explaining very exactly but I made all these last >>>> year >>>> in october and i do not remember all the operations step by step. Hope >>>> this help. >>>> Regards. >>>> >>>> Aristotel Neamtu >>>> >>>> >>>> Patrick Ring wrote: >>>> > I am putting together a virtual (VMWare) with the QmailToaster ISO >>>> > (CentOS 4.X). >>>> > > I'm having problems with the newmodel script (of QTP) erroring out >>>> > when it goes to mount the sandbox. >>>> > In the past this always worked for me. (In the past I have not used >>>> > the QmailToaster ISO disk...I usually loaded CentOS and then >>>> > built/loaded QT) >>>> > > Specifically the errors occur right after >>>> > Installing: fuse >>>> > Installing: kernel-devel >>>> > Installing: dkms >>>> > Installing: fuse-uni
Re: [qmailtoaster] Re: Has something changed in QT?
The upgrade from 4.8 to 5.4 put only the smp kernel. I hand installed the kernel-smp-devel. Maybe is an issue with the fact that smp kernel is the default kernel installed by the new version? On the other hand, we are talking about a major upgrade to a higher version. I didn't expected to run so smoothly. The problem with fuse.ko and ltld.h were the only I had. I made two upgrades, one in vmware and one on a physical machine, both with the same problem but easily fixed. How is your install Patrick? Eric Shubert wrote: I don't believe that autofs comes into play with fuse and unionfs, which is what qtp-newmodel uses now. On the other hand, a missing fuse.ko module is consistent with the error message(s) we're seeing. That's likely the problem. I'm not positive where that module comes from. I think it's built as part of the installation of the dkms-fuse package. If kernel-smp-devel is missing (and you're running the smp kernel), that's likely the culprit. Such a dependency might be missing. I'd like to get this fixed if we can pin this down. Borg wrote: I forgot, here's all i have done. In my case fuse was installed but fuse.ko missing. I installed kernel headers for current running kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I have fuse-2.7.4-1.nodist package. In fuse source you'll find script for config and install. I run ./configure, ./install-sh, make and make install. Then modprobe fuse run swiftly and newmodel had no problems further. Maybe autofs is not needed but it was a trial and error to find the problem with fuse. Borg wrote: I cheched bash history and I am sure I started autofs right before running newmodel. And found a new thing. Although fuse reports to be installed, fuse.ko is missing, so I had to install kernel-headers and in my case kernel-smp-devel. Patrick Ring wrote: I did run across a thread on this list that talked about disabling autofs... So, do you think I need to make sure it is ON and not 0FF then? Thank you, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: Borg To: qmailtoaster-list@qmailtoaster.com Sent: Sat Jan 02 04:51:24 2010 Subject: Re: [qmailtoaster] Has something changed in QT? Hello to all. I stumbled across the same problem. I installed qmt iso based on centos4 then updated to 4.8. After that I booted the last centos5 from dvd and upgraded. Then when tried to newmodel, got the same error. But is only a matter of installing dkms-fuse and, do not forget to /etc/init/d/autofs start. I think the autofs is the answer. Then everything went ok. Also, later on configuring i remember i had to manually install libtool-ltld-devel to provide ltld.h. Sorry if i am not explaining very exactly but I made all these last year in october and i do not remember all the operations step by step. Hope this help. Regards. Aristotel Neamtu Patrick Ring wrote: > I am putting together a virtual (VMWare) with the QmailToaster ISO > (CentOS 4.X). > > I'm having problems with the newmodel script (of QTP) erroring out > when it goes to mount the sandbox. > In the past this always worked for me. (In the past I have not used > the QmailToaster ISO disk...I usually loaded CentOS and then > built/loaded QT) > > Specifically the errors occur right after > Installing: fuse > Installing: kernel-devel > Installing: dkms > Installing: fuse-unionfs > Installing: dkms-fuse > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > 0:0.23-1.qtp > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > Then right after it says "Complete!" > fuse: device not found, try 'modprobe fuse' first > FATAL: Module fuse not found. > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist > cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist > Try 'cp --help' for more information. > qtp-mount-sandbox: sandbox was not mounted successfully > > qtp-newmodel - qtp-mount-sandbox failed, exiting > > Anyway, I've tried to perform newmodel both before and after a "yum > update", and I stumbled across a previous thread that recommended > turning off the "autofs" service. No change either way. > > Has something changed in the newmodel script? Or is there something
[qmailtoaster] Re: Has something changed in QT?
I don't believe that autofs comes into play with fuse and unionfs, which is what qtp-newmodel uses now. On the other hand, a missing fuse.ko module is consistent with the error message(s) we're seeing. That's likely the problem. I'm not positive where that module comes from. I think it's built as part of the installation of the dkms-fuse package. If kernel-smp-devel is missing (and you're running the smp kernel), that's likely the culprit. Such a dependency might be missing. I'd like to get this fixed if we can pin this down. Borg wrote: I forgot, here's all i have done. In my case fuse was installed but fuse.ko missing. I installed kernel headers for current running kernel and fuse sources then I rebuilt fuse.ko. For fuse sources I have fuse-2.7.4-1.nodist package. In fuse source you'll find script for config and install. I run ./configure, ./install-sh, make and make install. Then modprobe fuse run swiftly and newmodel had no problems further. Maybe autofs is not needed but it was a trial and error to find the problem with fuse. Borg wrote: I cheched bash history and I am sure I started autofs right before running newmodel. And found a new thing. Although fuse reports to be installed, fuse.ko is missing, so I had to install kernel-headers and in my case kernel-smp-devel. Patrick Ring wrote: I did run across a thread on this list that talked about disabling autofs... So, do you think I need to make sure it is ON and not 0FF then? Thank you, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: Borg To: qmailtoaster-list@qmailtoaster.com Sent: Sat Jan 02 04:51:24 2010 Subject: Re: [qmailtoaster] Has something changed in QT? Hello to all. I stumbled across the same problem. I installed qmt iso based on centos4 then updated to 4.8. After that I booted the last centos5 from dvd and upgraded. Then when tried to newmodel, got the same error. But is only a matter of installing dkms-fuse and, do not forget to /etc/init/d/autofs start. I think the autofs is the answer. Then everything went ok. Also, later on configuring i remember i had to manually install libtool-ltld-devel to provide ltld.h. Sorry if i am not explaining very exactly but I made all these last year in october and i do not remember all the operations step by step. Hope this help. Regards. Aristotel Neamtu Patrick Ring wrote: > I am putting together a virtual (VMWare) with the QmailToaster ISO > (CentOS 4.X). > > I'm having problems with the newmodel script (of QTP) erroring out > when it goes to mount the sandbox. > In the past this always worked for me. (In the past I have not used > the QmailToaster ISO disk...I usually loaded CentOS and then > built/loaded QT) > > Specifically the errors occur right after > Installing: fuse > Installing: kernel-devel > Installing: dkms > Installing: fuse-unionfs > Installing: dkms-fuse > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > 0:0.23-1.qtp > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > Then right after it says "Complete!" > fuse: device not found, try 'modprobe fuse' first > FATAL: Module fuse not found. > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist > cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist > Try 'cp --help' for more information. > qtp-mount-sandbox: sandbox was not mounted successfully > > qtp-newmodel - qtp-mount-sandbox failed, exiting > > Anyway, I've tried to perform newmodel both before and after a "yum > update", and I stumbled across a previous thread that recommended > turning off the "autofs" service. No change either way. > > Has something changed in the newmodel script? Or is there something > different between the CentOS/QT from the ISO vs when I load manually? > > Please advise. > Thank you, > Patrick Ring > > > > Patrick M. Ring > P. Ring Technologies > Louisiana Web Host, LLC. > 985-868-4200 > > > > __ Information from ESET NOD32 Antivirus, version of virus > signature database 4736 (20100101) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com __ Information from ESET NOD32 Antivirus, version of virus signature database 4736 (20100101) __ The message wa
Re: [qmailtoaster] Re: Has something changed in QT?
I'll definitely post my methods and results. Thanks. -- Sent from my BlackBerry Wireless Device -Original Message- From: news To: qmailtoaster-list@qmailtoaster.com Sent: Fri Jan 01 21:37:11 2010 Subject: [qmailtoaster] Re: Has something changed in QT? Great. I'll be curious to know how you make out. Patrick Ring wrote: > I'm out of town right now, but I'll be able to work with it tomorrow > afternoon. > > When I did last work with it, newmodel would start and download and then > look like it was going to run, and then right after the sandbox (as the > error portion I posted said) error out. > > On the first attemp, I loaded the QMT ISO, rebooted, ran yum update (for > CentOS 4.8), rebooted, and ran newmodel. In trying to get it to work (on > that attempt), I also tried toggling the autofs service (found a QMT > list thread about that). > > I appreciated the input, I'm going to keep trying when I get back > tomorrow. Worst case, I'll probably just load up a fresh load from > scratch (instead of the ISO)... The ISO was just so convenient. > > Thanks, > Patrick Ring > > -- > Sent from my BlackBerry Wireless Device > > > -Original Message- > From: news > To: qmailtoaster-list@qmailtoaster.com > Sent: Fri Jan 01 20:37:56 2010 > Subject: [qmailtoaster] Re: Has something changed in QT? > > Is it working now, or still not working? > I don't recall precisely what might have happened that caused it to work > ok after this failure, except possibly a reboot. > > You should run > # yum update > and reboot before running the latest qtp-newmodel. > > Patrick Ring wrote: > > On the attempt (to run newmodel) where I had run the yum update, I did > > reboot after it was complete. > > > > I'm fairly certain I rebooted after the QMT ISO finished the install as > > well. > > > > In either case I had not done anything between the install and the new > > model script besides reboot. > > > > Thanks, > > Patrick Ring > > ---------- > > Sent from my BlackBerry Wireless Device > > > > > > -Original Message- > > From: news > > To: qmailtoaster-list@qmailtoaster.com > > > Sent: Thu Dec 31 17:21:10 2009 > > Subject: [qmailtoaster] Re: Has something changed in QT? > > > > The fuse subsystem is fairly new to qtp-newmodel. It has been tested on > > current CentOS 4. > > > > I seem to remember having the same problem with CentOS5. Have you > > rebooted since you updated to the latest kernel? > > > > Patrick Ring wrote: > > > I am putting together a virtual (VMWare) with the QmailToaster ISO > > > (CentOS 4.X). > > > > > > I'm having problems with the newmodel script (of QTP) erroring out > when > > > it goes to mount the sandbox. > > > In the past this always worked for me. (In the past I have not > used the > > > QmailToaster ISO disk...I usually loaded CentOS and then > built/loaded QT) > > > > > > Specifically the errors occur right after > > > Installing: fuse > > > Installing: kernel-devel > > > Installing: dkms > > > Installing: fuse-unionfs > > > Installing: dkms-fuse > > > > > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > > > 0:0.23-1.qtp > > > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > > > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > > > > > Then right after it says "Complete!" > > > fuse: device not found, try 'modprobe fuse' first > > > FATAL: Module fuse not found. > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' first > > > fuse: device not found, try 'modprobe fuse' firs
[qmailtoaster] Re: Has something changed in QT?
Great. I'll be curious to know how you make out. Patrick Ring wrote: I'm out of town right now, but I'll be able to work with it tomorrow afternoon. When I did last work with it, newmodel would start and download and then look like it was going to run, and then right after the sandbox (as the error portion I posted said) error out. On the first attemp, I loaded the QMT ISO, rebooted, ran yum update (for CentOS 4.8), rebooted, and ran newmodel. In trying to get it to work (on that attempt), I also tried toggling the autofs service (found a QMT list thread about that). I appreciated the input, I'm going to keep trying when I get back tomorrow. Worst case, I'll probably just load up a fresh load from scratch (instead of the ISO)... The ISO was just so convenient. Thanks, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: news To: qmailtoaster-list@qmailtoaster.com Sent: Fri Jan 01 20:37:56 2010 Subject: [qmailtoaster] Re: Has something changed in QT? Is it working now, or still not working? I don't recall precisely what might have happened that caused it to work ok after this failure, except possibly a reboot. You should run # yum update and reboot before running the latest qtp-newmodel. Patrick Ring wrote: > On the attempt (to run newmodel) where I had run the yum update, I did > reboot after it was complete. > > I'm fairly certain I rebooted after the QMT ISO finished the install as > well. > > In either case I had not done anything between the install and the new > model script besides reboot. > > Thanks, > Patrick Ring > -- > Sent from my BlackBerry Wireless Device > > > -Original Message- > From: news > To: qmailtoaster-list@qmailtoaster.com > Sent: Thu Dec 31 17:21:10 2009 > Subject: [qmailtoaster] Re: Has something changed in QT? > > The fuse subsystem is fairly new to qtp-newmodel. It has been tested on > current CentOS 4. > > I seem to remember having the same problem with CentOS5. Have you > rebooted since you updated to the latest kernel? > > Patrick Ring wrote: > > I am putting together a virtual (VMWare) with the QmailToaster ISO > > (CentOS 4.X). > > > > I'm having problems with the newmodel script (of QTP) erroring out when > > it goes to mount the sandbox. > > In the past this always worked for me. (In the past I have not used the > > QmailToaster ISO disk...I usually loaded CentOS and then built/loaded QT) > > > > Specifically the errors occur right after > > Installing: fuse > > Installing: kernel-devel > > Installing: dkms > > Installing: fuse-unionfs > > Installing: dkms-fuse > > > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > > 0:0.23-1.qtp > > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > > > Then right after it says "Complete!" > > fuse: device not found, try 'modprobe fuse' first > > FATAL: Module fuse not found. > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist > > cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist > > Try 'cp --help' for more information. > > qtp-mount-sandbox: sandbox was not mounted successfully > > > > qtp-newmodel - qtp-mount-sandbox failed, exiting > > > > Anyway, I've tried to perform newmodel both before and after a "yum > > update", and I stumbled across a previous thread that recommended > > turning off the "autofs" service. No change either way. > > > > Has something changed in the newmodel script? Or is there something > > diffe
Re: [qmailtoaster] Re: Has something changed in QT?
I'm out of town right now, but I'll be able to work with it tomorrow afternoon. When I did last work with it, newmodel would start and download and then look like it was going to run, and then right after the sandbox (as the error portion I posted said) error out. On the first attemp, I loaded the QMT ISO, rebooted, ran yum update (for CentOS 4.8), rebooted, and ran newmodel. In trying to get it to work (on that attempt), I also tried toggling the autofs service (found a QMT list thread about that). I appreciated the input, I'm going to keep trying when I get back tomorrow. Worst case, I'll probably just load up a fresh load from scratch (instead of the ISO)... The ISO was just so convenient. Thanks, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: news To: qmailtoaster-list@qmailtoaster.com Sent: Fri Jan 01 20:37:56 2010 Subject: [qmailtoaster] Re: Has something changed in QT? Is it working now, or still not working? I don't recall precisely what might have happened that caused it to work ok after this failure, except possibly a reboot. You should run # yum update and reboot before running the latest qtp-newmodel. Patrick Ring wrote: > On the attempt (to run newmodel) where I had run the yum update, I did > reboot after it was complete. > > I'm fairly certain I rebooted after the QMT ISO finished the install as > well. > > In either case I had not done anything between the install and the new > model script besides reboot. > > Thanks, > Patrick Ring > -- > Sent from my BlackBerry Wireless Device > > > -Original Message- > From: news > To: qmailtoaster-list@qmailtoaster.com > Sent: Thu Dec 31 17:21:10 2009 > Subject: [qmailtoaster] Re: Has something changed in QT? > > The fuse subsystem is fairly new to qtp-newmodel. It has been tested on > current CentOS 4. > > I seem to remember having the same problem with CentOS5. Have you > rebooted since you updated to the latest kernel? > > Patrick Ring wrote: > > I am putting together a virtual (VMWare) with the QmailToaster ISO > > (CentOS 4.X). > > > > I'm having problems with the newmodel script (of QTP) erroring out when > > it goes to mount the sandbox. > > In the past this always worked for me. (In the past I have not used the > > QmailToaster ISO disk...I usually loaded CentOS and then built/loaded QT) > > > > Specifically the errors occur right after > > Installing: fuse > > Installing: kernel-devel > > Installing: dkms > > Installing: fuse-unionfs > > Installing: dkms-fuse > > > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > > 0:0.23-1.qtp > > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > > > Then right after it says "Complete!" > > fuse: device not found, try 'modprobe fuse' first > > FATAL: Module fuse not found. > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > fuse: device not found, try 'modprobe fuse' first > > mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist > > cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist > > Try 'cp --help' for more information. > > qtp-mount-sandbox: sandbox was not mounted successfully > > > > qtp-newmodel - qtp-mount-sandbox failed, exiting > > > > Anyway, I've tried to perform newmodel both before and after a "yum > > update", and I stumbled across a previous thread that recommended > > turning off the "autofs" service. No change either way. > > > > Has something changed in the newmodel script? Or is there something > > different between the CentOS/QT from the ISO vs when I load manually? > > > > Please advise. > > Thank you, > > Patrick Ring &
[qmailtoaster] Re: Has something changed in QT?
Is it working now, or still not working? I don't recall precisely what might have happened that caused it to work ok after this failure, except possibly a reboot. You should run # yum update and reboot before running the latest qtp-newmodel. Patrick Ring wrote: On the attempt (to run newmodel) where I had run the yum update, I did reboot after it was complete. I'm fairly certain I rebooted after the QMT ISO finished the install as well. In either case I had not done anything between the install and the new model script besides reboot. Thanks, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: news To: qmailtoaster-list@qmailtoaster.com Sent: Thu Dec 31 17:21:10 2009 Subject: [qmailtoaster] Re: Has something changed in QT? The fuse subsystem is fairly new to qtp-newmodel. It has been tested on current CentOS 4. I seem to remember having the same problem with CentOS5. Have you rebooted since you updated to the latest kernel? Patrick Ring wrote: > I am putting together a virtual (VMWare) with the QmailToaster ISO > (CentOS 4.X). > > I'm having problems with the newmodel script (of QTP) erroring out when > it goes to mount the sandbox. > In the past this always worked for me. (In the past I have not used the > QmailToaster ISO disk...I usually loaded CentOS and then built/loaded QT) > > Specifically the errors occur right after > Installing: fuse > Installing: kernel-devel > Installing: dkms > Installing: fuse-unionfs > Installing: dkms-fuse > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > 0:0.23-1.qtp > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > Then right after it says "Complete!" > fuse: device not found, try 'modprobe fuse' first > FATAL: Module fuse not found. > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist > cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist > Try 'cp --help' for more information. > qtp-mount-sandbox: sandbox was not mounted successfully > > qtp-newmodel - qtp-mount-sandbox failed, exiting > > Anyway, I've tried to perform newmodel both before and after a "yum > update", and I stumbled across a previous thread that recommended > turning off the "autofs" service. No change either way. > > Has something changed in the newmodel script? Or is there something > different between the CentOS/QT from the ISO vs when I load manually? > > Please advise. > Thank you, > Patrick Ring > > > > Patrick M. Ring > P. Ring Technologies > Louisiana Web Host, LLC. > 985-868-4200 > -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Has something changed in QT?
On the attempt (to run newmodel) where I had run the yum update, I did reboot after it was complete. I'm fairly certain I rebooted after the QMT ISO finished the install as well. In either case I had not done anything between the install and the new model script besides reboot. Thanks, Patrick Ring -- Sent from my BlackBerry Wireless Device -Original Message- From: news To: qmailtoaster-list@qmailtoaster.com Sent: Thu Dec 31 17:21:10 2009 Subject: [qmailtoaster] Re: Has something changed in QT? The fuse subsystem is fairly new to qtp-newmodel. It has been tested on current CentOS 4. I seem to remember having the same problem with CentOS5. Have you rebooted since you updated to the latest kernel? Patrick Ring wrote: > I am putting together a virtual (VMWare) with the QmailToaster ISO > (CentOS 4.X). > > I'm having problems with the newmodel script (of QTP) erroring out when > it goes to mount the sandbox. > In the past this always worked for me. (In the past I have not used the > QmailToaster ISO disk...I usually loaded CentOS and then built/loaded QT) > > Specifically the errors occur right after > Installing: fuse > Installing: kernel-devel > Installing: dkms > Installing: fuse-unionfs > Installing: dkms-fuse > > Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 > 0:0.23-1.qtp > Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 > 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL > > Then right after it says "Complete!" > fuse: device not found, try 'modprobe fuse' first > FATAL: Module fuse not found. > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > fuse: device not found, try 'modprobe fuse' first > mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist > cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist > Try 'cp --help' for more information. > qtp-mount-sandbox: sandbox was not mounted successfully > > qtp-newmodel - qtp-mount-sandbox failed, exiting > > Anyway, I've tried to perform newmodel both before and after a "yum > update", and I stumbled across a previous thread that recommended > turning off the "autofs" service. No change either way. > > Has something changed in the newmodel script? Or is there something > different between the CentOS/QT from the ISO vs when I load manually? > > Please advise. > Thank you, > Patrick Ring > > > > Patrick M. Ring > P. Ring Technologies > Louisiana Web Host, LLC. > 985-868-4200 > -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Re: Has something changed in QT?
The fuse subsystem is fairly new to qtp-newmodel. It has been tested on current CentOS 4. I seem to remember having the same problem with CentOS5. Have you rebooted since you updated to the latest kernel? Patrick Ring wrote: I am putting together a virtual (VMWare) with the QmailToaster ISO (CentOS 4.X). I'm having problems with the newmodel script (of QTP) erroring out when it goes to mount the sandbox. In the past this always worked for me. (In the past I have not used the QmailToaster ISO disk...I usually loaded CentOS and then built/loaded QT) Specifically the errors occur right after Installing: fuse Installing: kernel-devel Installing: dkms Installing: fuse-unionfs Installing: dkms-fuse Installed: dkms-fuse.noarch 0:2.7.4-1.nodist.rf fuse-unionfs.i386 0:0.23-1.qtp Dependancy Installed: dkms.noarch 0:2.0.22.0-1.el4.rf fuse.i386 0:2.7.4-1.qtp kernel-devel.i686 0:2.6.9-89.0.18.EL Then right after it says "Complete!" fuse: device not found, try 'modprobe fuse' first FATAL: Module fuse not found. fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first mount: mount point /mnt/qtp-sandbox/var/lib/rpm does not exist cp: '/mnt/qtp-sandbox/var/lib/rpm' : specified directory does not exist Try 'cp --help' for more information. qtp-mount-sandbox: sandbox was not mounted successfully qtp-newmodel - qtp-mount-sandbox failed, exiting Anyway, I've tried to perform newmodel both before and after a "yum update", and I stumbled across a previous thread that recommended turning off the "autofs" service. No change either way. Has something changed in the newmodel script? Or is there something different between the CentOS/QT from the ISO vs when I load manually? Please advise. Thank you, Patrick Ring Patrick M. Ring P. Ring Technologies Louisiana Web Host, LLC. 985-868-4200 -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
