When I run Checking Configuration it does not see Logrotate version correctly, system says it has version 3.7 on, but as you can see below I have posted results from the check and says version must be above 3.6
Checking Configuration
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active .. Mail server Postfix is installed and configured.
Apache is installed.
Webalizer is installed.
Apache is configured to host SSL websites.
MySQL is installed and running.
ProFTPd is installed.
The Logrotate program appears to be version , but Virtualmin requires version 3.6 or above in order to support multiple log files in the same section.
.. your system is not ready for use by Virtualmin.
Please help
Are you sure you're running the latest version of Webmin? A bug just like this was fixed a couple of months ago.
If so, then it's still misdetecting the version in some circumstances. You'll want to file a bug...but you'll need to provide a bit more information in order for it to get fixed. Jamie will need to know the OS and version, as well as the output of "logrotate -v"
--
Check out the forum guidelines!
This sounds like a Virtualmin bug, but I don't recall seeing it before.
I could login to your system myself to take a look - you can send me login details at jcameron@virtualmin.com
--
Check out the forum guidelines!
HI
Great to get such a quick responce.
Its running Webmin 1.410 on CentOS Linux 5, not sure what version of virtualmin is on the server.
I asked the system to update all installed components that had newer versions and have had the problem ever since.
It was a clean installation, had added nothing to the system.
Hmm...That's weird. Everybody's running CentOS 5 (it's by far the most popular OS for Virtualmin, even on our own servers), and we're not seeing this issue.
What's the output of "logrotate -v" on your system?
--
Check out the forum guidelines!
Iam new at this,
it is running on a VPS hosted for me.
Their techie said he has no idea why its doing it.
I can email you my login if it will help you to see for your self.
Or you could just run the command (login on the command line, or use the Command Shell in Webmin, if you're nervous about ssh):
logrotate -v
And tell us what it says. This one aint rocket surgery. ;-)
--
Check out the forum guidelines!
Here is the responce
> logrotate -v
logrotate 3.7.4 - Copyright (C) 1995-2001 Red Hat, Inc.
This may be freely redistributed under the terms of the GNU Public License
Usage: logrotate [-dfv?] [-d|--debug] [-f|--force] [-m|--mail command]
[-s|--state statefile] [-v|--verbose] [-?|--help] [--usage]
[OPTION...] <configfile>
Any News yet please I really need to get this server up and running.
I have 30 domains I need to setup.
Jamie email has been sent
Odd, I haven't received it yet. What address did you send it from?
--
Check out the forum guidelines!
Have you had a chance to check yet.
All I am trying to do for now is setup saweb.biz as the main domain
with ns1.saweb.biz and ns2.saweb.biz as my 2 DNS addresses.
Then I need to setup 30 or so domains as virtual servers.
I have now had this VPS for almost 2 weeks and not been able to do a thing yet.
Its prepaid for 3 months so I have a time limit.
Thanx again for all the help so far.
Looking at it now .. your email with the password got put into my spam folder, so I didn't notice it at first.
--
Check out the forum guidelines!
Ok, I see the problem - your system only has 64M of RAM. That is not enough for Virtualmin to do anything, and will cause random failures due to commands it runs dieing due to lack of RAM.
I strongly suggest upgrading your VPS to at *least* 256M, preferably 512M. I'm certainly that this will resolve the problem.
Also, I noticed that your Virtualmin version is quite old. Once you have more RAM, you can update with the command :
yum install wbm-virtual-server wbm-virtual-server-theme webmin usermin
--
Check out the forum guidelines!
no problem let me know how it goes.
I have asked them to otherwise do a new installation of the VPS from scratch.
Then I wont do the all upgrades.
Thanx I will send then here to read the posts
and then see what happens.
Thanx for all the help.
I know that Virtualmin can run with (far) fewer services in 96MB, but 64MB is too tight for pretty much anything except very basic Apache (and no management tools). You'll need plenty of swap space, in either case (and time to wait on things to swap in and out while working).
There is a guide for running Virtualmin on low memory systems, and it's possible to get a pretty full-featured system except AV/spam scanning (which are hugely resource intensive) into 128MB.
http://www.virtualmin.com/documentation/id,virtualmin_on_low_memory_syst...
--
Check out the forum guidelines!
Thanx for the info.
They are going to bump the ram to 128 to see if that helps.
I am also going To disable preloading of Webmin libraries
for now once the server has rebooted.
Yes, turning off preloading will help a lot.
Also, go for 256M if you can - even 128M may be a little to small, depending on what services you are running.
--
Check out the forum guidelines!
The problem is there is a big price jump to go to 256mb
its 4 times what I am paying now.
What annoys me is that they sell this package with the Webmin as an option when theres no real way its going to work with 64MB ram,
as a newbie to VPS I would not know this. But they should.
I mentioned to them I have more than 1 domain before I signed up and
what I planned on doing with this service.
Looks as if I may just run 1 domain here to get used to using
and controling a VPS and Webmin.
Thanx again for all your help
Shane
Well its after 1am here now so time to get some sleep and try again in the morning
<div class='quote'>What annoys me is that they sell this package with the Webmin as an option when theres no real way its going to work with 64MB ram,</div>
Webmin is quite different from Virtualmin in its resource requirements. But, Virtualmin (or Webmin) isn't really where most of the resources are being spent, regardless. Apache is big (depending on modules loaded)...usually much bigger than 64MB. Mail processing requires far more than 64MB. Any one of these services will fit in 64MB, but not all of them...Since Virtualmin is generally used for management of a full hosting stack, it requires a lot of paring down to make it run in a small footprint--it can do it, but the other applications have to be pared back a lot, as well. Without mail or large apps 128MB should be fine (as long as you follow the guide on reducing memory usage, and reduce down to just the services you <i>really</i> need).
It's easiest for us to just say, "get more memory", but a lot of folks don't really need more memory--they just need to adjust their usage down to meet the available memory. Running a single blog, or simple commerce, or whatever, site without email processing is entirely feasible in 128MB. But, as you've noted with 64MB "this town aint big enough for the two of us", where the two would be Virtualmin and just about any other service. The web server is already going to be bumping into that limit.
We do have some plans for a low-memory footprint version of Virtualmin, in the future. Our new VM2 product manages virtualized systems, and realistically, many VPS systems are small. People are shooting for a really low price point with them, and so we need to have some options in place for serving those users. But, it'll be a while...it requires several tweaks to the current model--we have to figure out what to do about mail, since it can't be processed locally on a small system, and we have to figure out the webserver problem...nginx or Lighttpd are possibilities, but they have serious limitations vs. Apache and remove a lot of cool Virtualmin functionality (Analytics, some of the proxy options, Subversion, DAV, etc.), and, of course, we have to build a new Webmin module for whichever webserver we choose, which is a very large endeavor.
--
Check out the forum guidelines!
Looks like I might just have to bite the bullet and go for the 256MB option or find a more affrodable 256mb package, due to my exchange rate to US$ being R8 to $1, I am trying to stay under $15 pm for now.
Have you got any suggesions, looking at around
10 GB Disk Space 256 MB RAM 1Mbps Unmetered Traffic,
the disk space I think is not so critical as I only need around
2 gig or so for my use.
Also regarding the low memory option your working on.
I use a program on my own server to sort my mail so I just use a catch all configuration which sends all email for said domain to me.
This takes the pressure of the web-server, maybe you could suggest a similar setup for use with this package you working on.
Even Windows exchange should be able to handle it.
Regards
Shane
Hi
Post fix keeps giving an error.
What is the best one to use for the mail side of the server, with the best memory requirements for its facilities.
The error I keep getting is:
Failed to start service : Failed to query Postfix config command to get the current value of parameter process_id_directory:
I can take another look at your system if you like - how much memory did you end up going with?
--
Check out the forum guidelines!
Well I have just created my first Virtualmin Virtual Servers.
So far so good, memory has ben upgraded to 128 for now and going to see how it goes.
I could not find the setting to stop the libraries from being preloaded in Virtualmin
Also could not find the details that where mentioned in the manual changing of it, so just added "preload_mode=0" to the end of the list that was there in miniserv.conf.
I also follwed the suggestion about reducing the Reduce Apache memory usage
Thanx guys for all the help.
Regards Shane
It seems the first reboot did not pick up the memory upgrade, but it did work on the second one.
Thanx for all the help so far.
I have updated Virtualmin to 3.46 Gpl
and Webmin was also updated to Webmin 1.410
so far all seems to be working okay.
Will definitly be back if I get stuck.
I would really like to complement you guys on a well run support site and an awesome software package.
Thanx for everything.
Cool, glad you got it all working!
--
Check out the forum guidelines!
Me to.
I guess that ends this thread.
Thanx again for all the help.
https://bugs.gentoo.org/show_bug.cgi?id=621850
I ran across this in gentoo and submitted a fix upstream.