Greetings CentOS Team-
Since the list tends to be filled with "things don't work" and "why did you do it this way" and "complaint X", I thought I'd make a small deviation...
I have a production system running on a Dell Poweredge 2650 server. I simply ran 'yum update' and rebooted with no problems. Everything continues to work as rock solid as before.
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
--Tim
On Thu, 2 Apr 2009, Tim Nelson wrote:
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
I agree. I've only updated one server so far (the backup server, which is completely subservient to my will -- unlike development servers with real live users who might complain), but it went very smoothly. Thank you very, very much!
2009/4/2 Paul Heinlein heinlein@madboa.com:
On Thu, 2 Apr 2009, Tim Nelson wrote:
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
I agree. I've only updated one server so far (the backup server, which is completely subservient to my will -- unlike development servers with real live users who might complain), but it went very smoothly. Thank you very, very much!
Updated 4 desktops (kde), 5 servers (one httpd, one postgres (pgdg), one nfsd (not yet rebooted), two aimed at cluster testing). Everything went fine. Still have a couple servers to do. Kudos to CentOS and RH team ! Laurent.
On Thursday 02 April 2009 18:50:30 Paul Heinlein wrote:
On Thu, 2 Apr 2009, Tim Nelson wrote:
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
I agree. I've only updated one server so far (the backup server, which is completely subservient to my will -- unlike development servers with real live users who might complain), but it went very smoothly. Thank you very, very much!
+1
Anne
On Thursday 02 April 2009 19:50, Paul Heinlein wrote:
On Thu, 2 Apr 2009, Tim Nelson wrote:
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
I agree. I've only updated one server so far (the backup server, which is completely subservient to my will -- unlike development servers with real live users who might complain), but it went very smoothly. Thank you very, very much!
+1
Best, :-) Marko
Paul Heinlein wrote:
On Thu, 2 Apr 2009, Tim Nelson wrote:
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
I agree. I've only updated one server so far (the backup server, which is completely subservient to my will -- unlike development servers with real live users who might complain), but it went very smoothly. Thank you very, very much!
+1
Thank you for a job well done, Andy
On Thu, Apr 2, 2009 at 12:05 PM, Tim Nelson tnelson@rockbochs.com wrote:
Greetings CentOS Team-
Since the list tends to be filled with "things don't work" and "why did you do it this way" and "complaint X", I thought I'd make a small deviation...
I have a production system running on a Dell Poweredge 2650 server. I simply ran 'yum update' and rebooted with no problems. Everything continues to work as rock solid as before.
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
--Tim
Had I yum updated on my desktop computer I believe everything would have been fine (as it was on my laptop). But I tried the Update path from the DVD first, without doing any preparation or reading and, though it booted fine, a lot of my programs failed -- even Firefox until I ran yum update. Fortunately I had backed everything up -- and I had a couple issues that made a clean install a good idea anyhow. The clean install went flawlessly.
Only thing... I tried to like the new wallpaper, but eventually Googled and found the old version. I just like the plain CentOS 5 wallpaper better. (Yeah, I'm bland.)
Thanks to everyone.
On 04/02/2009 06:05 PM, Tim Nelson wrote:
Greetings CentOS Team-
Since the list tends to be filled with "things don't work" and "why did you do it this way" and "complaint X", I thought I'd make a small deviation...
I have a production system running on a Dell Poweredge 2650 server. I simply ran 'yum update' and rebooted with no problems. Everything continues to work as rock solid as before.
So, I just wanted to say 'Thank You' to all those who put in such hard work into the CentOS project. The time between releases was not a problem here. If it was, I guess I'd just ask for a refund. :-)
--Tim _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Had the same success with a dozen of xen domUs and a couple of dedicated servers (both i386 & x86_64), although I made sure I updated glibc and yum first, just to stay in the safe side. :)
Great job, Centos team.
I updated two machines yesterday. No problems after reboot so far. Very smooth. Before I was able to update I hit minor annoyances with getting rid of packages I didn't want installed (like linuxwacom) and a perl dependency of a third-party perl package.
Kai
Kai Schaetzl wrote:
I updated two machines yesterday. No problems after reboot so far. Very smooth.
I also updated two servers in the last few days without any problems. I don't think I have ever had such a simple upgrade of any system. I'd like to add my thanks to the Centos team.
Following advice here, I yum-updated glibc, glibc-devel, yum and rpm before upgrading. I don't know if that was really necessary, but it couldn't do any harm.
Timothy Murphy wrote on Sat, 04 Apr 2009 13:26:24 +0100:
I yum-updated glibc, glibc-devel, yum and rpm before upgrading.
I forgot to mention that I did not do this. No problems.
Kai
On Sat, 04 Apr 2009 15:31:19 +0200 Kai Schaetzl wrote:
Timothy Murphy wrote on Sat, 04 Apr 2009 13:26:24 +0100:
I yum-updated glibc, glibc-devel, yum and rpm before upgrading.
I forgot to mention that I did not do this. No problems.
I've upgrade 3 machines so far and had no issues on any of them.
"yum update", reboot, done.
After performing an update from CentOS 5.2 to 5.3 with yum update I have an error with clamav-milter The clamav-milter won't start.
[root@is3 sysconfig]# service clamav-milter restart Stopping Clamav Milter Daemon: [FAILED] Starting Clamav Milter Daemon: clamav-milter: unrecognized option `--local' ERROR: Unknown option passed ERROR: Can't parse command line options [FAILED]
The config of /etc/sysconfig/clamav-milter
CLAMAV_FLAGS=" --config-file=/etc/clamd.conf --local --max-children=10 --outgoing --quiet " SOCKET_ADDRESS="local:/var/run/clamd.socket"
Removing the config lines gives no result. Someone the same problem of an idea?
Kind Regards, Leo Arnts
Leo Arnts wrote on Sun, 5 Apr 2009 09:20:08 +0200:
After performing an update from CentOS 5.2 to 5.3 with yum update I have an error with clamav-milter The clamav-milter won't start.
Can you please start a new thread? (You hijacked an existing thread and just changed the subject.) Add the rpm -q output for clamav-milter and related programs, like clamav and sendmail to your new posting. I doubt that you problem results from the update. clamav-milter is not part of CentOS. Your problem likely was caused by the restart and existed already, maybe some wrong config variable or so.
(Starting Clamav Milter Daemon: clamav-milter: unrecognized option `--local' ERROR: Unknown option passed ERROR: Can't parse command line options)
Kai
Kai wrote:
Leo Arnts wrote on Sun, 5 Apr 2009 09:20:08 +0200:
After performing an update from CentOS 5.2 to 5.3 with yum update I
have
an error with clamav-milter The clamav-milter won't start.
Can you please start a new thread? (You hijacked an existing thread and
just changed the subject.) Add the rpm -q output for clamav-milter and related programs, like
clamav
and sendmail to your new posting. I doubt that you problem results from the update. clamav-milter is not
part
of CentOS. Your problem likely was caused by the restart and existed already, maybe some wrong config variable or so.
(Starting Clamav Milter Daemon: clamav-milter: unrecognized option `--local' ERROR: Unknown option passed ERROR: Can't parse command line options)
Kai
Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com
Hi Kai,
Sorry for the wrong mail to the maillist. I have fixed the problem. With the upgrade of centos 5.2 to 5.3 there is an new clamaav-milter installed wich uses an new set of configuration files. The old config file in /etc/sysconfig isn't deleted with the upgrade. After deleting the configfile there are no problems anymore.
Kind Regards,
Starting Clamav Milter Daemon: clamav-milter: unrecognized option `--local' ERROR: Unknown option passed ERROR: Can't parse command line options
[FAILED]
The config of /etc/sysconfig/clamav-milter
CLAMAV_FLAGS=" --config-file=/etc/clamd.conf --local --max-children=10 --outgoing --quiet "
It sounds like you did an update to clamav-0.95.
IF SO: { You must now do the configuration in /etc/clamav-milter.conf. Leave the sysconfig as CLAMAV_FLAGS=" " . Read the man pages for both clamd.conf and clamav-milter as they have both changed, although the conf files are pretty well documented by themselves. Make sure the sockets in the clamd.conf file is correctly referenced in the clamav-milter.conf file and the milter socket is compatible with what you put in your sendmail.mc file. }
[OT]: { The clamav folks completely rewrote the milter in 0.95 to require sendmail- 13 or higher. For anyone with an old (RHEL/Centos 3.9) distro, clamav- milter-0.95 does not work with sendmail-12. I built and the installed the sendmail-13 rpm from the RHEL4 (Centos4 should also work) src.rpm before building and installing the clamav-0.95 rpm on one old machine. It is now receiving and filtering mail happily (allthough oblivious to its scheduled July date with the hardware recycler). Clamdtop even works with Centos 3.9.
Someone may want to put sendmail-13 in the Centos 3.9 centosplus directory. A "clamav-0.95-for-sendmail-13" could also be put in the rpmforge updates for EL3, although there are probably few customers for that item. }
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Leo Arnts Sent: Sunday, 5 April 2009 5:20 PM To: centos@centos.org Subject: [CentOS] 5.3 Update Problem clamav-milter
After performing an update from CentOS 5.2 to 5.3 with yum update I have an error with clamav-milter The clamav-milter won't start.
[root@is3 sysconfig]# service clamav-milter restart Stopping Clamav Milter Daemon: [FAILED] Starting Clamav Milter Daemon: clamav-milter: unrecognized option `--local' ERROR: Unknown option passed ERROR: Can't parse command line options [FAILED]
The config of /etc/sysconfig/clamav-milter
CLAMAV_FLAGS=" --config-file=/etc/clamd.conf --local --max-children=10 --outgoing --quiet " SOCKET_ADDRESS="local:/var/run/clamd.socket"
Had the same error on upgrade! It appears that ClamAV people have decided to do away with /etc/sysconfig/clamav-milter altogether.
Get rid of the file above and modify /etc/clamav-milter.conf instead and make the necessary changes. Most important is to comment out the "Example" line near the top of that file.
Cheers, AK.
Timothy Murphy wrote:
Kai Schaetzl wrote:
I updated two machines yesterday. No problems after reboot so far. Very smooth.
I also updated two servers in the last few days without any problems. I don't think I have ever had such a simple upgrade of any system.
I have - twice before. Once was when I went from 5.0 to 5.1 and once when I went from 5.1 to 5.2
:D
On Apr 4, 2009, at 9:30 AM, Michael A. Peters wrote:
Timothy Murphy wrote:
Kai Schaetzl wrote:
I updated two machines yesterday. No problems after reboot so far. Very smooth.
I also updated two servers in the last few days without any problems. I don't think I have ever had such a simple upgrade of any system.
I have - twice before. Once was when I went from 5.0 to 5.1 and once when I went from 5.1 to 5.2
One time on an upgrade, some kernel problem prevented my system from booting. Somewhere between 5 and 5.1. I had to stick with the original kernel until some later kernel fixed the problem.
It was around the time the system recognized my video, I believe.
Kernel problems happen. At work, with the upstream vender, one of the 5.1 era kernels didn't handle the Pentium III on one of our systems very well, and would panic in some Athlon power management driver. Later, it too was fixed.
I just upgraded my home system today, and it came up fine.
Kevin Krieser wrote:
On Apr 4, 2009, at 9:30 AM, Michael A. Peters wrote:
Kernel problems happen.
Yes - I've had mixed results with power management with and audio on laptops before in Fedora with kernel updates, but none recently.
Going from Fedora 8 to CentOS 5 broke my thinkpad sleep (it doesn't wake up if you close the lid) - haven't tried lately. That was fixed in Fedora towards end of FC6 lifespan. In F8 it worked quite well (I skipped F7 and only ran F8 long enough to know the poor thing couldn't handle it).
-
Andrew Hull -
Anne Wilson -
Anthony Kamau -
Ben Mohilef -
Frank Cox -
Kai Schaetzl -
Kevin Krieser -
Laurent Wandrebeck -
Leo Arnts -
lucian＠lastdot.org -
Marko Vojinovic -
Michael A. Peters -
Paul Heinlein -
Ron Blizzard -
Tim Nelson -
Timothy Murphy