Critical Debian Wheezy Virtualmin Gpl Bug in Installer sh

21 posts / 0 new
Last post
#1 Tue, 09/09/2014 - 03:22
leobaker

Critical Debian Wheezy Virtualmin Gpl Bug in Installer sh

This only started happening yesterday on a new install of Debian Wheezy using the Virtualmin gpl installer shell from the official website.

The following packages have unmet dependencies: virtualmin-base : Depends: libsasl2 but it is not installable WARN - apt-get seems to have failed. Are you sure your OS and version is supported? WARN - http://www.virtualmin.com/os-support

FATAL - Fatal Error Occurred: Installation failed: 0 FATAL - Cannot continue installation. FATAL - Attempting to remove virtualmin repository configuration, so the installation can be FATAL - re-attempted after any problems have been resolved. FATAL - Removing temporary directory and files. FATAL - If you are unsure of what went wrong, you may wish to review the log FATAL - in /root/virtualmin-install.log root@ns236697:~# root@ns236697:~# The following packages have unmet dependencies: -bash: The: command not found root@ns236697:~# virtualmin-base : Depends: libsasl2 but it is not installable -bash: virtualmin-base: command not found root@ns236697:~# WARN - apt-get seems to have failed. Are you sure your OS and version is supported? -bash: WARN: command not found root@ns236697:~# WARN - http://www.virtualmin.com/os-support -bash: WARN: command not found root@ns236697:~# root@ns236697:~# FATAL - Fatal Error Occurred: Installation failed: 0 -bash: FATAL: command not found root@ns236697:~# FATAL - Cannot continue installation. -bash: FATAL: command not found root@ns236697:~# FATAL - Attempting to remove virtualmin repository configuration, so the installation can be -bash: FATAL: command not found root@ns236697:~# FATAL - re-attempted after any problems have been resolved. -bash: FATAL: command not found root@ns236697:~# FATAL - Removing temporary directory and files. -bash: FATAL: command not found root@ns236697:~# FATAL - If you are unsure of what went wrong, you may wish to review the log -bash: FATAL: command not found root@ns236697:~# FATAL - in /root/virtualmin-install.log -bash: FATAL: command not found root@ns236697:~#

Tue, 09/09/2014 - 09:27
andreychek

Howdy,

It looks like the Debian libsasl2-2 package may have changed; it previously would be installed when asked to install libsasl2, but it looks like that is no longer the case. That means they likely dropped "libsasl2" from the "Provides" like in the package metadata.

I'll ask Joe to push out a new virtualmin-base version for Debian to correct that, thanks for pointing this out.

-Eric

Tue, 09/09/2014 - 10:03 (Reply to #2)
leobaker

Hello Eric,

What is the ETA on providing the new Virtualmin base for Debian to fix this.

Thanks,

Leo

Tue, 09/09/2014 - 14:39
dutch2005

i've got the same problem...

Just re-installed my vps and it doesnt work :(

Tue, 09/09/2014 - 15:02
andreychek

While I unfortunately don't have a specific time, I just spoke to Joe and he says this is something that will be updated today.

-Eric

Wed, 09/10/2014 - 00:01
andreychek

Okay, it should be all fixed now!

Can you give that a shot and let us know if it works for you?

Thanks!

-Eric

Wed, 09/10/2014 - 07:12 (Reply to #6)
leobaker

Hello Eric,

Thanks so much its all working fine now.

leo

Wed, 09/10/2014 - 07:10
dutch2005

confirming, it works..

Fri, 12/05/2014 - 05:08
garethstorer

I've been struggling for a few days to get Virtualmin installed on a new Cloud server. I've tried Debian 7 32 and 64Bit, CentOS 6 32 and 64 bit and Ubuntu 14.04 64 bit nothing works. I am assuming therefore it's related to the cloud package I am using.

Details are as follows: 512MB RAM 10 GB disk space. As far as I can ascertain it's a Xen server. I do understand that the 64 bit distros would struggle to install on 512MB ram. I'm done searching forums for results and Google has not been my friend, so I am hoping someone can help here.

My alternative is to install Webmin which works perfectly and install Virtualmin manually, however I am always wary of missing something important going the manual route where automatic installations should "handle" most things.

I have attached the virtualmin-install log but I've changed log file extention to allow for uploading. If you need to look at another log file let me know. This install was for Debian 7 32 bit.

uname -a result: Linux vps2 3.2.0-4-686-pae #1 SMP Debian 3.2.41-2 i686 GNU/Linux

Thanks guys.

Fri, 12/05/2014 - 08:44
andreychek

Howdy,

I would definitely recommend using a 32 bit system -- 512MB is a bit on the small end of things now, it's possible that you're seeing some RAM related issues. A 64 bit system would have much less RAM available to it.

But you may also be seeing another issue entirely.

What happens if you run "dpkg --configure -a" now, does that throw an error, or does it work properly?

-Eric

Fri, 12/05/2014 - 09:10
garethstorer

I ran dpkg --configure -a and it seemed to be fine. I've attached the results.

Fri, 12/05/2014 - 09:21 (Reply to #11)
garethstorer

Update...

I can log into Virtualmin but during the post install wizard it throws out an error that mysqld failed to start. On previous occasions when the install also didn't seem to complete correctly the same would happen or the post install would complete but the check configuration run would throw out apache module errors. That was when I tried it on CentOS6 though. This is so weird as I have installed and reinstalled virtualmin so many times without problems, but on other hosting providers. It's just seems to be on this host.

Are there any hardware related questions I can ask them that may shed light on the constant failures?

Fri, 12/05/2014 - 10:34
andreychek

Howdy,

There could be something about the particular VPS image you're using there, or the available resources.

If it's just an issue with MySQL starting though, you may be close... what happens if you try to start MySQL on the command line?

I believe the command on Debian to do that is:

/etc/init.d/mysql restart

Fri, 12/05/2014 - 10:58 (Reply to #13)
garethstorer

Mysql restart failed

Fri, 12/05/2014 - 11:10 (Reply to #14)
garethstorer

Another thing I just realised is that I set up a test VM in virtual box using same specs as my hosting and the install also didn't work as expected. I think I am going to try another test using 1GB ram instead of 512MB just to rule out ram as an issue.

Fri, 12/05/2014 - 12:13
andreychek

Howdy,

Yeah I'd be interested to hear if your 1GB instance works better. MySQL not starting is odd though -- I'd be curious if you see any errors in your logs regarding why that's not starting.

-Eric

Fri, 12/05/2014 - 13:15 (Reply to #16)
garethstorer

deamon.log entries when I did the mysql restart:

Dec 5 21:01:02 vps2 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead. Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [Note] Plugin 'FEDERATED' is disabled. Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: The InnoDB memory heap is disabled Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: Compressed tables use zlib 1.2.7 Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: Using Linux native AIO Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: Initializing buffer pool, size = 128.0M Dec 5 21:01:02 vps2 mysqld: InnoDB: mmap(135987200 bytes) failed; errno 12 Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: Completed initialization of buffer pool Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 InnoDB: Fatal error: cannot allocate memory for the buffer pool Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [ERROR] Plugin 'InnoDB' init function returned error. Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [ERROR] Unknown/unsupported storage engine: InnoDB Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [ERROR] Aborting Dec 5 21:01:02 vps2 mysqld: Dec 5 21:01:02 vps2 mysqld: 141205 21:01:02 [Note] /usr/sbin/mysqld: Shutdown complete Dec 5 21:01:02 vps2 mysqld: Dec 5 21:01:02 vps2 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Dec 5 21:01:16 vps2 /etc/init.d/mysql[19218]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Dec 5 21:01:16 vps2 /etc/init.d/mysql[19218]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed Dec 5 21:01:16 vps2 /etc/init.d/mysql[19218]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Dec 5 21:01:16 vps2 /etc/init.d/mysql[19218]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! Dec 5 21:01:16 vps2 /etc/init.d/mysql[19218]:

Fri, 12/05/2014 - 14:10 (Reply to #17)
garethstorer

surprise surprise

I installed using 1GB of RAM and all went well. Installation completed, and post-installations and config checks all completed without hitch. This was done on a Virtualbox VM.

I am not in a position to increase our VPS hosting to a 1GB RAM account so if anyone can do some tests on their own to confirm that, at present, there certainly seems to be an issue with trying to install Virtualmin on only 512MB RAM. It looks like the low RAM issue only affects the auto install of Virtualmin. As mentioned before I did try go through a manual install after installing Webmin and all seemed to run smoothly. However because I wanted to make sure everything installed correctly I continued pursuing the auto install. I may have to try the manual install again and hope I do it correctly.

Fri, 12/05/2014 - 14:12 (Reply to #18)
garethstorer

just to add to this, it seems clear that while virtualmin runs fine on 512MB RAM it needs 1GB RAM to install so I don;t know if the developers are able to streamline to install process a bit. Of course that's obviously easier said than done.

Fri, 12/05/2014 - 14:22
andreychek

Howdy,

Thanks for reporting your findings regarding the RAM issues!

Do you happen to have the ability to increase your swap space? I'd be curious if increasing that allowed you to perform the installation.

-Eric

Fri, 12/05/2014 - 15:34 (Reply to #20)
garethstorer

I recreated the vps with a 1GB Swap drive. I am pleased to tell you the install completed and all post-install and config checks completed without error.

Thanks for all the help.

Topic locked