Hi all,

I've just rolled out the latest Virtualmin virtual-server module 3.30 to all repositories. I has numerous bugfixes and usabilty enhancements, along with one major feature enhancement.

This version includes support for backups to Amazon's S3 storage service, which provides an extremely reliable and reasonably priced remote backup solution. This feature requires the perl XML::Simple module. Installation of this module is covered below.

Changes since 3.29:

[list]

[*]The cache file used by the lookup-domain.pl program to determine if a mailbox is close to its disk quota is automatically flushed when a user's or domain's quota is changed, which increases the speed at which such changes are detected.[/*]

[*]When renaming a virtual server, an option is available to rename any mailboxes in the domain that contain the old server name.[/*]

[*]A city or locality name can be entered when generating a certificate.[/*]

[*]Added an option to use Spanish to the Joomla script installer.[/*]

[*]Changed the 'PHP Options' page to 'Website Options', and added a field for enabling log writing via a program (to protect against a missing ~/logs directory).[/*]

[*]When restoring template backups, existing templates are no longer deleted. This makes copying templates to new servers easier.[/*]

[*]Added checkboxes and a button on the Server Templates page to delete several at once. [/*]

[*]Fixed the osCommerce script installer, so that the admin module works.[/*]

[*]Virtual server backups can now be made to Amazon's S3 service, which provides online storage (at a price). Similarly, restores can be made from the same service. Before you can use this feature, you must sign up for an account with S3 and get an access key and secret key.[/*]

[*]Each reseller can have an IP address specified for virtual servers with shared address websites under his ownership to be set up on. All DNS records in the servers' domains will use that IP, which allows resellers to appear to have a dedicated server for their customer domains.[/*]

[*]The change IP address page can now modify the IP of name-based servers, if more than one possibility is available (such as from a reseller IP). Similar, the modify-domain.pl program now takes a --shared-ip option to do the same thing.[/*]

[/list]


To upgrade on Red Hat based systems:

yum update wbm-virtual-server

On SUSE systems:

yast -i wbm-virtual-server

On Mandriva systems:

urpmi.update -a

urpmi wbm-virtual-server

And on Debian and Ubuntu systems:

apt-get update
apt-get upgrade webmin-virtual-server

If you plan to use the Amazon S3 backup feature, you will also need the perl XML::Simple module. This is provided in the system repository of most supported systems. For those that do not, I will package it and roll it into our repository over the next couple of days.

To install on Fedora 5/6 and CentOS 4:
yum install perl-XML-Simple

To install on Red Hat Enterprise Linux 4:

up2date perl-XML-Simple

To install on OpenSUSE 10.0:

yast -i perl-XML-Simple

To install on Mandriva:

urpmi perl-XML-Simple

And on Debian/Ubuntu:

apt-get install libxml-simple-perl

Fedora versions below 5 and CentOS/RHEL below 4 do not include this module. I'll package it shortly and add it to our repositories for these systems.

Please let us know of any problems, by filing a bug in the bug tracker.

I tried the Amazon S3 this evening and got to sort of a road block. I installed the libxml-simple-perl fine and reran the backup. I was then prompted with

Backup failed : The Perl module S3::AWSAuthConnection needed to communicate with Amazon's S3 service is not installed

I've searched and cannot seem to come up with the apt package name for this. Also, are there any other packages that might pop up after installing this one that might save some time and another post? :)

I updated from 3.29 to 3.30 this evening on RHEL4
The update caused apache to hang. Stopping/starting httpd failed, and the server required a reboot before web pages were accessible again.

[[Sun Dec 10 19:38:09 2006]] [[notice]] caught SIGTERM, shutting down
[[Sun Dec 10 19:38:10 2006]] [[notice]] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[[Sun Dec 10 19:38:11 2006]] [[notice]] Digest: generating secret for digest authentication ...
[[Sun Dec 10 19:38:11 2006]] [[notice]] Digest: done
[[Sun Dec 10 19:38:11 2006]] [[notice]] LDAP: Built with OpenLDAP LDAP SDK
[[Sun Dec 10 19:38:11 2006]] [[notice]] LDAP: SSL support unavailable
[[Sun Dec 10 19:38:11 2006]] [[error]] (28)No space left on device: Cannot create SSLMutex
Configuration Failed
[[Sun Dec 10 19:39:39 2006]] [[crit]] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock
Configuration Failed

Space is not an issue

Hey Tom,

I'll look into it. I thought only XML::Simple was needed. ;-)

I'll plan to add it to the repository soon, if it's not already in the Debian universe.

Hey Jeff,

[[Sun Dec 10 19:38:11 2006]] [[error]] (28)No space left on device: Cannot create SSLMutex
Configuration Failed
[[Sun Dec 10 19:39:39 2006]] [[crit]] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock
Configuration Failed

Space is not an issue

Space almost certainly is the issue, but it's probably not where you expect it to be. It's something to do with the IPC shared memory on the system. You can run ipcs to see the existing segments. You may be able to free some up by restarting the processes that are eating them (or figuring out what is eating more than it's fair share and fixing it). Feel free to send along the results of this command to the Help! forums, and I'll try to help you figure out what we need to do to fix it.

It could also be that you don't have /dev/shm mounted for some reason. I would think you'd get a different error, though.

Oh, yeah, I'll point out that this has nothing to do with the Virtualmin version--Virtualmin doesn't use any of this memory. On my systems it is mostly used by apache and postgresql.

Joe, here are the results of ipcs

[[#]] ipcs

------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 131072 root 600 33554432 22 dest
0x00000000 163841 root 600 524288 22 dest

------ Semaphore Arrays --------
key semid owner perms nsems
0x00000000 65536 apache 600 1
0x00000000 98305 apache 600 1
0x00000000 262146 apache 600 1
0x00000000 294915 apache 600 1
0x00000000 458756 apache 600 1
0x00000000 491525 apache 600 1
0x00000000 524294 apache 600 1
0x00000000 557063 apache 600 1

------ Message Queues --------
key msqid owner perms used-bytes messages

[[#]] free -m
total used free shared buffers cached
Mem: 4953 3121 1831 0 194 1852
-/+ buffers/cache: 1073 3879
Swap: 4094 0 4094

I'm getting an error when trying to backup using s3...

Starting backup of 1 domains to Amazon S3 bucket chris ..
HTTP/1.0 500 Perl execution failed Server: MiniServ/0.01 Date: Sun, 4 Mar 2007 15:22:15 GMT Content-type: text/html Connection: close

Error - Perl execution failed

syntax error at line 1, column 0, byte 0 at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/XML/Parser.pm line 187

I'm running Fedora 5 and have installed the xml::simple as described above.

Any thoughts?

Chris

I'm getting the same error under centos4

I also have xml::simple installed.


Starting backup of 15 domains to Amazon S3 bucket virtualmin1359 ..

HTTP/1.0 500 Perl execution failed Server: MiniServ/0.01 Date: Sun, 18 Mar 2007 09:21:35 GMT Content-type: text/html Connection: close
Error - Perl execution failed

syntax error at line 1, column 0, byte 0 at /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi/XML/Parser.pm line 187

John

Hi,

Has anyone experienced the above error besides me and Chris?

Or can anyone offer suggestions as to corrective steps I should try?

My keys are ok as I can access my S3 account with the S3 firefox extension and other tools so I'm wondering what I can do to get this working.

This would be the most fantastic way to back up the server.

Thanks,
John Wolgamot

Hey John,

Yeah, there's all kinds of stupid with S3 backups. We're still not installing all of the dependencies, and the remaining missing deps aren't even visible--they're hidden inside the response from the server.

I'm fixing them first thing tomorrow. I'll ping this thread when it's easily resolvable.