Problema upgrading the license a Virtualmin Pro

Hi, I have a problem with the virtualmin server. Since last update I am missing some features like the INSTALL SCRIPTS. I noticed that I have the option to upgrade to Virtualmin Pro, but when I try I receive this message. What can I do?

webmin is already the newest version. You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: linux-image-2.6-686: Depends: linux-image-2.6.26-2-686 but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). .. done

Status: 
Closed (fixed)

Comments

Looks like you may have somehow downgraded from the pro version to the GPL package .. which would explain why script installers aren't working.

What happens if you SSH in as root and run :

apt-get install webmin-virtual-server

if that fails, what does your /etc/apt/sources.list file contain?

This is the error: dl111:~# apt-get install webmin-virtual-server Leyendo lista de paquetes... Hecho Creando árbol de dependencias
Leyendo la información de estado... Hecho Tal vez quiera ejecutar `apt-get -f install' para corregirlo: Los siguientes paquetes tienen dependencias incumplidas: linux-image-2.6-686: Depende: linux-image-2.6.26-2-686 pero no va a instalarse E: Dependencias incumplidas. Intente 'apt-get -f install' sin paquetes (o especifique una solución).

Sorry it is in spanish, unmet dependencies.

This is the file /etc/apt/sources.list

deb http://5556009:ZFKIM2DS83F@software.virtualmin.com/debian/ virtualmin-etch main deb http://ftp.de.debian.org/debian/ stable main non-free contrib deb-src http://ftp.de.debian.org/debian/ stable main non-free contrib deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free deb-src http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free

deb http://security.debian.org/ stable/updates main contrib non-free

Are you using Debian Etch (4.0) or Lenny (5.0)?

I notice your support request mentions Lenny, but your sources file has references to Etch in it. One way to know for sure is to type:

cat /etc/debian_version

It also looks like your kernel update isn't installing, it may require manually running apt to see if any other dependencies are required.

If you type:

apt-get install linux-image-2.6-686

What output do you receive?

cat /etc/debian_version = 5.0.4

Output of apt-get install linux-image-2.6-686

dl111:~# apt-get install linux-image-2.6-686 Leyendo lista de paquetes... Hecho Creando árbol de dependencias
Leyendo la información de estado... Hecho linux-image-2.6-686 ya está en su versión más reciente. Tal vez quiera ejecutar `apt-get -f install' para corregirlo: Los siguientes paquetes tienen dependencias incumplidas: linux-image-2.6-686: Depende: linux-image-2.6.26-2-686 pero no va a instalarse E: Dependencias incumplidas. Intente 'apt-get -f install' sin paquetes (o especifique una solución).

Unmet dependencies

What happens if you run this command:

apt-get -f install

dl111:~# apt-get -f install Leyendo lista de paquetes... Hecho Creando árbol de dependencias
Leyendo la información de estado... Hecho Corrigiendo dependencias... Listo Se instalarán los siguientes paquetes extras: linux-image-2.6.26-2-686 Paquetes sugeridos: linux-doc-2.6.26 Se instalarán los siguientes paquetes NUEVOS: linux-image-2.6.26-2-686 0 actualizados, 1 se instalarán, 0 para eliminar y 104 no actualizados. 1 no instalados del todo o eliminados. Se necesita descargar 0B/20,2MB de archivos. Se utilizarán 59,9MB de espacio de disco adicional después de esta operación. ¿Desea continuar [S/n]? s Abortado.

S = Y

It does not work, Abortado = Abort

What Can I do?

The question there is case sensitive... so rather than "s", type in "S".

This message now:

2.6.26-2-686). This will not work unless the boot loader is configured ↑
│ to use an initrd. ▒
│ ▒
│ An initrd image is a kernel image that expects to use an INITial Ram ▒
│ Disk to mount a minimal root file system into RAM and use that for ▒
│ booting. ▒
│ ▒
│ The boot loader must be configured to use such images and the system ▒
│ will not boot until this is done. ▒
│ ▒
│ This message will appear for any new kernel installation unless the ▒
│ following is added to /etc/kernel-img.conf: ▒
│ ▮
│ "do_initrd = Yes"

I freaked out because I don't have physical access to the server, will boot up correctly if I continue?

Joe's picture
Submitted by Joe on Wed, 04/14/2010 - 16:14 Pro Licensee

So, since this is completely unrelated to Virtualmin...we probably aren't the best people to be asking about this particular problem. ;-)

I'd probably recommend you do some reading about Debian's bootup stuff, and googling about why it's doing this, and possibly asking in a Debian newbie forum about what it means and why it's happening, rather than trusting our opinion on this. (Though Eric is extremely experienced with Debian/Ubuntu systems, and may have seen this before...I haven't. I have no idea what's happening or why.)

Yeah, I'm stalling on an answer because I'm a bit baffled; I haven't seen anything like that before. Typically those things just install happily and silently :-)

I was going to dig around a little for any ideas on why that's occurring, but as Joe mentioned, you may also want to try asking on some Debian forums, they may have some thoughtful insight there :-)

Okay, so yeah, something is wrong with the update of the kernel on your system; I'm not entirely certain why, though it may be related to the way bootup is setup on your server.

Did you perform the initial Debian installation, or did your ISP do that? And what was initially installed, Debian 4 or 5?

Also, what are the contents of your /etc/kernel-img.conf file?

Since right now it is working fine although I don't have all the features I am going to wait until the dedicated server contract expires, then I will get a new dedicated server with a fresh debian install. My ISP usually install the server with Webmin, any insight about what should I ask in order to make the best virtualmin possible?

Thanks.

Typically, an installation doesn't run into any of the trouble you're seeing. I have a suspicion that part of the problem is that one or more upgrades from previous Debian versions may have taken place, and the default boot methods may have changed across one of those upgrades.

So, a typical Debian installation should work just fine -- and once your ISP has you setup with a new server, you can pop Virtualmin on there, and you should be in good shape!

Thanks a lot for the help.