From: Chris B. <xa...@xa...> - 2011-05-29 17:54:44
|
The subject is fairly self explanatory but I will attach the virtualmin-install.log and some details about the environment It is a VPS but that shouldn't matter, I've installed Virtualmin on both my FreeBSD 7, 8 and 9 VM's as well as a Debian VM, I've also successfully installed Virtualmin on my local Debian 6 (Squeeze) box. The VPS is running Debian 6 and is up to date. I think the problem may be that the things it wants to install, already are (they were installed by my host, not by me.) So what gives? -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? |
From: Joe C. <jo...@vi...> - 2011-05-30 00:48:53
|
I don't think the mailing list allows attachments, so we can't see your log. The most common causes of install failures on Debian include having software installed that conflicts with the software Virtualmin is trying to install (apt will not allow dependency resolution to override existing conflicting packages) and apt problems (i.e. some package was not configured or in an unresolved state, and needs to be fixed before you can install anything that depends on that package). This is why we so strongly recommend a _freshly installed_ operating system. It's impossible to account for all of the interdependencies when we're installing dozens of packages. Common problems on VPS systems include not enough memory (so-called "burst memory" on OpenVZ systems is rarely actually available...it just means your VPS provider has oversold the heck out of the server, and is pretending like you have a lot more memory than you actually do; trying to allocate it will fail intermittently, which is pretty much the worst possible thing memory can do, since it leads to mysterious failures rather than sensible out of memory errors and it doesn't show up as memory problems in top or free), custom installations that don't have a complete OS install or are missing files that Virtualmin or some of its packages require. You probably want to remove the Apache related packages and try again (many of the MPM types conflict and can prevent installation). And then remove any other packages that Virtualmin installs to see if there is some conflicting combination. On 5/29/2011 1:32 PM, Chris Brennan wrote: > The subject is fairly self explanatory but I will attach the > virtualmin-install.log and some details about the environment > > It is a VPS but that shouldn't matter, I've installed Virtualmin on > both my FreeBSD 7, 8 and 9 VM's as well as a Debian VM, I've also > successfully installed Virtualmin on my local Debian 6 (Squeeze) box. > The VPS is running Debian 6 and is up to date. I think the problem may > be that the things it wants to install, already are (they were > installed by my host, not by me.) So what gives? > |
From: Chris B. <xa...@xa...> - 2011-05-30 17:07:02
|
On Sun, May 29, 2011 at 8:48 PM, Joe Cooper <jo...@vi...> wrote: I don't think the mailing list allows attachments, so we can't see your log. > > The most common causes of install failures on Debian include having > software installed that conflicts with the software Virtualmin is trying > to install (apt will not allow dependency resolution to override > existing conflicting packages) and apt problems (i.e. some package was > not configured or in an unresolved state, and needs to be fixed before > you can install anything that depends on that package). This is why we > so strongly recommend a _freshly installed_ operating system. It's > impossible to account for all of the interdependencies when we're > installing dozens of packages. > > Common problems on VPS systems include not enough memory (so-called > "burst memory" on OpenVZ systems is rarely actually available...it just > means your VPS provider has oversold the heck out of the server, and is > pretending like you have a lot more memory than you actually do; trying > to allocate it will fail intermittently, which is pretty much the worst > possible thing memory can do, since it leads to mysterious failures > rather than sensible out of memory errors and it doesn't show up as > memory problems in top or free), custom installations that don't have a > complete OS install or are missing files that Virtualmin or some of its > packages require. > > You probably want to remove the Apache related packages and try again > (many of the MPM types conflict and can prevent installation). And then > remove any other packages that Virtualmin installs to see if there is > some conflicting combination. Joe, Thanks for taking the time to answer this. As I suspected, it was the fact that the vps host installed things for me before handing control over to me. I can try and get them to do a clean reinstall, installing nothing else or I can manually remove what's needed (if I know what to remove that is!) That being said, the log can be found here (at a temp location here at home) -> http://home.xaerolimit.net:2500/~chris/backup/virtualmin-install.log Is there a list of what virtualmin does install, so I can go in and just blanketly remove everything and start fresh? -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? |
From: Steve H. <st...@gr...> - 2011-05-30 01:03:36
Attachments:
smime.p7s
|
Another thing to check is whether having /tmp/mounted noexec will cause problems... it often is on VPSes. IIRC with debian on parallels, if you shut down mysql, you can then umount /tmp/and /var/tmp. Do all of your installs, and then reboot. Even apt often requires the ability to run executables off /tmp ( I know there are loads of exotic alternatives to this approach, but I'm all for an easy life! ). hth, Steve On Sun, 2011-05-29 at 20:48 -0400, Joe Cooper wrote: > I don't think the mailing list allows attachments, so we can't see your log. > > The most common causes of install failures on Debian include having > software installed that conflicts with the software Virtualmin is trying > to install (apt will not allow dependency resolution to override > existing conflicting packages) and apt problems (i.e. some package was > not configured or in an unresolved state, and needs to be fixed before > you can install anything that depends on that package). This is why we > so strongly recommend a _freshly installed_ operating system. It's > impossible to account for all of the interdependencies when we're > installing dozens of packages. > > Common problems on VPS systems include not enough memory (so-called > "burst memory" on OpenVZ systems is rarely actually available...it just > means your VPS provider has oversold the heck out of the server, and is > pretending like you have a lot more memory than you actually do; trying > to allocate it will fail intermittently, which is pretty much the worst > possible thing memory can do, since it leads to mysterious failures > rather than sensible out of memory errors and it doesn't show up as > memory problems in top or free), custom installations that don't have a > complete OS install or are missing files that Virtualmin or some of its > packages require. > > You probably want to remove the Apache related packages and try again > (many of the MPM types conflict and can prevent installation). And then > remove any other packages that Virtualmin installs to see if there is > some conflicting combination. > > On 5/29/2011 1:32 PM, Chris Brennan wrote: > > The subject is fairly self explanatory but I will attach the > > virtualmin-install.log and some details about the environment > > > > It is a VPS but that shouldn't matter, I've installed Virtualmin on > > both my FreeBSD 7, 8 and 9 VM's as well as a Debian VM, I've also > > successfully installed Virtualmin on my local Debian 6 (Squeeze) box. > > The VPS is running Debian 6 and is up to date. I think the problem may > > be that the things it wants to install, already are (they were > > installed by my host, not by me.) So what gives? > > > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > - > Forwarded by the Webmin mailing list at web...@li... > To remove yourself from this list, go to > http://lists.sourceforge.net/lists/listinfo/webadmin-list -- Steve Holdoway BSc(Hons) MNZCS <st...@gr...> http://www.greengecko.co.nz MSN: st...@gr... Skype: sholdowa |
From: Chris B. <xa...@xa...> - 2011-05-30 17:09:41
|
On Sun, May 29, 2011 at 9:03 PM, Steve Holdoway <st...@gr...> wrote: Another thing to check is whether having /tmp/mounted noexec will cause > problems... it often is on VPSes. > > IIRC with debian on parallels, if you shut down mysql, you can then > umount /tmp/and /var/tmp. Do all of your installs, and then reboot. Even > apt often requires the ability to run executables off /tmp ( I know > there are loads of exotic alternatives to this approach, but I'm all for > an easy life! ). > > hth, > Eh? I'm totally lost here .... If parallels is a vps thing then I really am lost, VPS's in general are new to me so I am rapidly learning how things function on a real vps where I don't have access to the primary host-os. But /var/tmp isn't mounted noexec root@ratfink:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/vzfs 300G 217M 300G 1% / tmpfs 128M 0 128M 0% /lib/init/rw tmpfs 128M 0 128M 0% /dev/shm root@ratfink:~# -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? |
From: Steve H. <st...@gr...> - 2011-05-30 22:06:18
Attachments:
smime.p7s
|
On Mon, 2011-05-30 at 13:09 -0400, Chris Brennan wrote: > On Sun, May 29, 2011 at 9:03 PM, Steve Holdoway <st...@gr...> wrote: > Another thing to check is whether having /tmp/mounted noexec > will cause > problems... it often is on VPSes. > > IIRC with debian on parallels, if you shut down mysql, you can > then > umount /tmp/and /var/tmp. Do all of your installs, and then > reboot. Even > apt often requires the ability to run executables off /tmp ( I > know > there are loads of exotic alternatives to this approach, but > I'm all for > an easy life! ). > > hth, > > > Eh? I'm totally lost here .... If parallels is a vps thing then I > really am lost, VPS's in general are new to me so I am rapidly > learning how things function on a real vps where I don't have access > to the primary host-os. But /var/tmp isn't mounted noexec > > > root@ratfink:~# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/vzfs 300G 217M 300G 1% / > tmpfs 128M 0 128M 0% /lib/init/rw > tmpfs 128M 0 128M 0% /dev/shm > root@ratfink:~# > > Parallels is virtualisation technology, and the one that you could well be using - according to the disk naming. The command you need is mount... $ mount /dev/vzfs on / type vzfs (rw) /dev/simfs on /tmp type simfs (rw,nosuid,nodev,noexec) /dev/simfs on /var/tmp type simfs (rw,nosuid,nodev,noexec) none on /proc type proc (rw,nosuid,noexec,nodiratime) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) none on /sys type sysfs (rw) none on /dev type tmpfs (rw) none on /dev/pts type devpts (rw) ( this is off one of my VPSes - CentOS but no matter ). You can see that bothe /tmp and /var/tmp are mounted noexec. This can cause problems when install scripts want to spawn more processes. Steve -- Steve Holdoway BSc(Hons) MNZCS <st...@gr...> http://www.greengecko.co.nz MSN: st...@gr... Skype: sholdowa |
From: Chris B. <xa...@xa...> - 2011-05-30 23:10:18
|
On Mon, May 30, 2011 at 6:05 PM, Steve Holdoway <st...@gr...>wrote: > On Mon, 2011-05-30 at 13:09 -0400, Chris Brennan wrote: > > On Sun, May 29, 2011 at 9:03 PM, Steve Holdoway <st...@gr...> > wrote: > > Another thing to check is whether having /tmp/mounted noexec > > will cause > > problems... it often is on VPSes. > > > > IIRC with debian on parallels, if you shut down mysql, you can > > then > > umount /tmp/and /var/tmp. Do all of your installs, and then > > reboot. Even > > apt often requires the ability to run executables off /tmp ( I > > know > > there are loads of exotic alternatives to this approach, but > > I'm all for > > an easy life! ). > > > > hth, > > > > > > Eh? I'm totally lost here .... If parallels is a vps thing then I > > really am lost, VPS's in general are new to me so I am rapidly > > learning how things function on a real vps where I don't have access > > to the primary host-os. But /var/tmp isn't mounted noexec > > > > > > root@ratfink:~# df -h > > Filesystem Size Used Avail Use% Mounted on > > /dev/vzfs 300G 217M 300G 1% / > > tmpfs 128M 0 128M 0% /lib/init/rw > > tmpfs 128M 0 128M 0% /dev/shm > > root@ratfink:~# > > > > > Parallels is virtualisation technology, and the one that you could well > be using - according to the disk naming. The command you need is > mount... > > $ mount > /dev/vzfs on / type vzfs (rw) > /dev/simfs on /tmp type simfs (rw,nosuid,nodev,noexec) > /dev/simfs on /var/tmp type simfs (rw,nosuid,nodev,noexec) > none on /proc type proc (rw,nosuid,noexec,nodiratime) > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > none on /sys type sysfs (rw) > none on /dev type tmpfs (rw) > none on /dev/pts type devpts (rw) > > ( this is off one of my VPSes - CentOS but no matter ). > > You can see that bothe /tmp and /var/tmp are mounted noexec. This can > cause problems when install scripts want to spawn more processes. > ell, I don't think that as the problem, but thanks for answering my question. chris@ratfink:~$ mount /dev/vzfs on / type vzfs (rw,relatime,usrquota,grpquota) proc on /proc type proc (rw,relatime) sysfs on /sys type sysfs (rw,relatime) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,relatime) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime) chris@ratfink:~$ -- > A: Yes. > >Q: Are you sure? > >>A: Because it reverses the logical flow of conversation. > >>>Q: Why is top posting frowned upon? |