[CentOS-announce] CESA-2012:0125 Moderate CentOS 4 glibc Update
CentOS Errata and Security Advisory 2012:0125 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0125.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
c40f7a3d1091ec0ce10233b49f58cfaf8a9a59380e44fe61303b3e22124a345c
glibc-2.3.4-2.57.i386.rpm
0cd5a29747b75107645f7593bcfbea4150ab09b81fde25251ffb99e2335a9d9a
glibc-2.3.4-2.57.i686.rpm
777342a29d5119a54948b15b42dca4b38ab458b2756287504736c538daf4218b
glibc-common-2.3.4-2.57.i386.rpm
1da90467a7f9a0c502c10621914adc7141801bb420af5a4daac63e2c4011c2f5
glibc-devel-2.3.4-2.57.i386.rpm
4c4815c05c4c8221434e644adce61639a9d3b3ee0485ca7d9665da5fce55a48f
glibc-headers-2.3.4-2.57.i386.rpm
d82703d3f2aef5ea8d02e3ec34b00c8e4bbfc77acf9c3fa42ef7df6d725698ff
glibc-profile-2.3.4-2.57.i386.rpm
7ccfd9542eeb6cd39cbc21512b0ebef1580f24638951078cd43ff7c8e12c3fd3
glibc-utils-2.3.4-2.57.i386.rpm
e097a2fee2201835a8c6484e2ab75c7be6a7252c12f3a267a30ef268d460e658
nptl-devel-2.3.4-2.57.i386.rpm
5a57d7429d04740e3f445a954ecfed2b6d5e251cadf3a4c2f10b7b9307d2fe8e
nptl-devel-2.3.4-2.57.i686.rpm
9a4f1fb8d99c4374d18214a0c91d33691a7d3a0611f933cb175d201719f9868a
nscd-2.3.4-2.57.i386.rpm
x86_64:
0cd5a29747b75107645f7593bcfbea4150ab09b81fde25251ffb99e2335a9d9a
glibc-2.3.4-2.57.i686.rpm
51b5c9bd1edd6b7fe5fdc4041ed1643040f263c28f53574d9d05bc06133665c5
glibc-2.3.4-2.57.x86_64.rpm
01140b88c80d3ce839401863d0b9fcc36af1ee4cb9d06b1bb29b60482fb8c89f
glibc-common-2.3.4-2.57.x86_64.rpm
1da90467a7f9a0c502c10621914adc7141801bb420af5a4daac63e2c4011c2f5
glibc-devel-2.3.4-2.57.i386.rpm
8924ccfee2a8376bdc9a330be8bd0060e030b62b1a003570dd6723844c3c5f09
glibc-devel-2.3.4-2.57.x86_64.rpm
cf013d0c5ab9560d690051f334fb0c311a9d4d74c3cfd68fa15eab0beb68cfc7
glibc-headers-2.3.4-2.57.x86_64.rpm
4c1037e641c56dc67595f6d859bffab54abe6f739bcad036b93d7c517719f013
glibc-profile-2.3.4-2.57.x86_64.rpm
774846ce4a93f60d6a5d8837c24d6b51e98b953a7a4e88bdcc94ad6be58e0519
glibc-utils-2.3.4-2.57.x86_64.rpm
245417fe4d7d3536a47cc05e09d7200195e250881d3f8e628c62a4d8f85afb45
nptl-devel-2.3.4-2.57.x86_64.rpm
ef0447e007436d3d06fe912edfd7067f08c6e5f68ff871af2365cdd9d45c557d
nscd-2.3.4-2.57.x86_64.rpm
Source:
b05896a97fe1fd5f75bb117ef9f21f9ad239442f76862c1c607f3a8d2083ac77
glibc-2.3.4-2.57.src.rpm
--
Tru Huynh
CentOS Project { http://www.centos.org/ }
irc: tru_tru, #cen...@irc.freenode.net
___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2012:0126 Moderate CentOS 5 glibc Update
CentOS Errata and Security Advisory 2012:0126 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0126.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
490a1c39e8d95240f11fc11e080b264d237244e3943dbece83f29665c5650b13
glibc-2.5-65.el5_7.3.i386.rpm
a743515f16ef94e620e886ce7b0421097ea8e9c5237c191146f3febd469a628f
glibc-2.5-65.el5_7.3.i686.rpm
93f45c442e308c0a1257fbd3f35d145c6d4def3c8eaf8d70a3fd78871a61ef56
glibc-common-2.5-65.el5_7.3.i386.rpm
f1528565a36be720abe89ec7e886a3bd8b541fa477dae2a3e9eb28b75ab5fcf2
glibc-devel-2.5-65.el5_7.3.i386.rpm
6e48064b2e532068094992f3735ea27e1fe1cc7552e0757eda65fd0685ccace8
glibc-headers-2.5-65.el5_7.3.i386.rpm
0121d1004b8df564e4ad717e55de16d2c3bcdae987bab39c87d19da2eefb652c
glibc-utils-2.5-65.el5_7.3.i386.rpm
f437b270582fcd0154b5ad5558d810418999dc4966e224c6314e47427e9a58ff
nscd-2.5-65.el5_7.3.i386.rpm
x86_64:
a743515f16ef94e620e886ce7b0421097ea8e9c5237c191146f3febd469a628f
glibc-2.5-65.el5_7.3.i686.rpm
96db45269c391c4433cdd4fa229fc24089384736a9d8abf0b8d18b216617828d
glibc-2.5-65.el5_7.3.x86_64.rpm
79a4ff7acbf4a5d7b357b18bf4b0f69d849c48da84c307a42c51b16beb7d8ab5
glibc-common-2.5-65.el5_7.3.x86_64.rpm
f1528565a36be720abe89ec7e886a3bd8b541fa477dae2a3e9eb28b75ab5fcf2
glibc-devel-2.5-65.el5_7.3.i386.rpm
e035b75fa8e160492695a800c4e78e9a9e9701041ea7c68e2e940e4d037ba989
glibc-devel-2.5-65.el5_7.3.x86_64.rpm
deb552161b54fe208e73882c8f8f06d080795689a6426d5e0c7af5a87f45ad51
glibc-headers-2.5-65.el5_7.3.x86_64.rpm
180606d44619c891bc4b2a2d6042e5952f10e7ada4557ca3b6955c04479dd2eb
glibc-utils-2.5-65.el5_7.3.x86_64.rpm
9049b8fc19f95bcc4ab8165e6c70939d3746d34b536e4ad76481382e892e4673
nscd-2.5-65.el5_7.3.x86_64.rpm
Source:
93d253b3e488536e20bd169b26213fb61a8b2e6c4aeb9ba4148db660473754e8
glibc-2.5-65.el5_7.3.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2012:0127 Moderate CentOS 5 mysql Update
CentOS Errata and Security Advisory 2012:0127 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0127.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
c107ad358ee0ed46c46a1a3910797148f764dbebc602162791def81fc87b5bd1
mysql-5.0.95-1.el5_7.1.i386.rpm
5f80bdc58a281a817b422c054319bc00e57138321201ec7129c6ae86ac8367f7
mysql-bench-5.0.95-1.el5_7.1.i386.rpm
3c347c2a5a921160434390ad0467a6c62dfa41948d964f5e793586aa7ce90b2f
mysql-devel-5.0.95-1.el5_7.1.i386.rpm
d5d419f091cde15a7b0fc89ef5f6d58589787b808a53d922bf34491f45318059
mysql-server-5.0.95-1.el5_7.1.i386.rpm
01b7bf42572d27f50f113ec36efe8759886169bde2ec066c3d6e3b05d1479086
mysql-test-5.0.95-1.el5_7.1.i386.rpm
x86_64:
c107ad358ee0ed46c46a1a3910797148f764dbebc602162791def81fc87b5bd1
mysql-5.0.95-1.el5_7.1.i386.rpm
a019c33ab0e76e05f54faef6c2b2b5885a7b1e793a3cb762daeec8e1aab56e11
mysql-5.0.95-1.el5_7.1.x86_64.rpm
b7725565d8c65b0e9101c465afa340ed6be889850835dba2db59b7d830811d7d
mysql-bench-5.0.95-1.el5_7.1.x86_64.rpm
3c347c2a5a921160434390ad0467a6c62dfa41948d964f5e793586aa7ce90b2f
mysql-devel-5.0.95-1.el5_7.1.i386.rpm
aab476c29efca0df7b0ee1fb790516d336f1b2e41f3415ac66943bdb797312f3
mysql-devel-5.0.95-1.el5_7.1.x86_64.rpm
90527e6805c2d8d61789679f553079580f1e1deb81a64de28aac383106605991
mysql-server-5.0.95-1.el5_7.1.x86_64.rpm
314a67e3aea6cfe65822ded0c74d93cb9fe950e7c151d816ecff9bf07a127b08
mysql-test-5.0.95-1.el5_7.1.x86_64.rpm
Source:
b75f06e06bbc2708e21e74a7fc3cc1fb990d2a571e42aedacbfb9b0631fc38c9
mysql-5.0.95-1.el5_7.1.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
___
CentOS-announce mailing list
CentOS-announce@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS] Dovecot problems
On 2/12/2012 2:09 PM, Alexander Dalloz wrote: Am 12.02.2012 20:01, schrieb Steve Campbell: Actually, I'm having problems with pop and imap. I changed mailservers this weekend, going from a Centos 3 box to a Centos 6 box. The Centos 3 box used the old standard imap and pop servers. We use horde for our webmail. The pop3 mailboxes (mbox) were in /var/spool/mail and the imap folders were in /home/user/mail, which horde took care of. So 2 classes of users? As John has annotated, mixing POP3 and IMP4 use is not advised at all. Not really two classes of users. Most of the users use pop for retrieving email. Horde is our webmail app, and it reads the mailbox, but creates and manages the imap folders in user's home directory. This has worked fine in the past, allowing users to read mail from their desktop using pop, and if desired, using horde to read mail from elsewhere. If they want to be able to see read email from outside the building, they set their mail client to leave on server. Horde takes care of deleting email from the mbox as well if desired. Upon starting the Centos 6 box, I ran into tons of login and viewing problems. I tried Cyrus for imap, could log in, but couldn't see mail in the imap folders. Using dovecot for pop, I eventually could get logged in, but kept getting the couldn't open INBOX message, so no one could download their email, even though sendmail was delivering it properly. Cyrus-IMAPd is out of the game unless you do a real mail store migration as Cyrus-IMAPd uses his own storage scheme. My preference is to use dovecot as both pop and imap servers. The Centos 3 imap server used an rpm named imap-2002d-12 (at least that's the one I have on that server). I'm not sure how mixing comes into play here, since most people set their smart phones up as imap clients, and they can still view their email when they arrive at work using pop. So here's my question: Can (should) dovecot be used for both imap and pop when considering the above setup of mbox in /var/spool/mail and imap folders in ~/mail? Horde will read the mbox to display new messages in it's screens. Yes. That's good to get an opinion. I'm going to proceed thinking dovecot will do both. There's also an issue to address later of shared stuff I'll have to investigate. We have a few accounts that multiple users use in this manner through imap. They log in as a singular user, but there are issues of deletions and the like that sometimes cause problems. If so, does anyone have a pretty good link to how to make dovecot function using the old Centos pop/imap scheme? Should I try and convert the old mbox files to another format or destination to make this work? See http://wiki.dovecot.org/MailLocation I reviewed that quite a bit during the night. I guess I need to read up on dovecot's definitions, since that INBOX parameter kept throwing me. There really isn't an INBOX to a pop account's mbox, but there is on our imap scheme. So I might have been trying to force the issue. Thanks for any help. It's been a long night, going on about 14 hours now and I'm just getting the old server back to current until I figure this out. Not intended to sound smart ass, but changing a production system the way you do without prior testing isn't that clever. Not taken in any bad way. I had actually tested it pretty well for all the stuff I'm running on it. Sendmail worked as expected. All of the other apps I have running dealing with email worked fine as well. Apps such as MimeDefang, MailScanner, MailWatch, and everything else. I took for granted that pop and imap would work fine since on the old system, they just worked. I had no idea these services had changed so much. So yes, I failed to test the two things that users want most. Egg on my face, for sure. Thanks for the help, and criticism. steve campbell I wish you success. Thanks. Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
Hi, On Mon, Feb 13, 2012 at 2:35 PM, Steve Campbell campb...@cnpapers.com wrote: If so, does anyone have a pretty good link to how to make dovecot function using the old Centos pop/imap scheme? Should I try and convert the old mbox files to another format or destination to make this work? See http://wiki.dovecot.org/MailLocation I reviewed that quite a bit during the night. I guess I need to read up on dovecot's definitions, since that INBOX parameter kept throwing me. There really isn't an INBOX to a pop account's mbox, but there is on our imap scheme. So I might have been trying to force the issue. I would recommend using Maildir format instead of mbox format. Maildir seems to be the default for most IMAP servers these days. At least for me Horde + Dovecot (using Maildirs) works nicely. If you cannot get your setup working I would also recommend posting your problem in the Dovecot emailing list, which I've heard being active and helpful. Best, Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] init/upstart issue? ypbind and autofs
Lars Hecking writes: Lars Hecking writes: One problem I have with custom CentOS 6 installation is that NIS auto.* maps are not available. According to boot.log, ypbind starts before autofs, but when I login to the machine, the maps are not available until I issue a service autofs restart. Any pointers on what to check? I guess CentOS doesn't use pid randomisation. autofs does start before ybind: root 2107 1 0 16:40 ?00:00:00 automount --pid-file /var/run/autofs.pid root 2517 1 0 16:41 ?00:00:00 /usr/sbin/ypbind root 3009 2976 0 16:43 pts/000:00:00 egrep auto|ypb Another machine I installed interactively (this one is kickstarted) works correctly. Solved. The other machine doesn't have NetworkManager installed. Removed it here and NIS/autofs started working correctly. Why again did RH switch to NM? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
On Mon, Feb 13, 2012 at 6:41 AM, Peter Peltonen peter.pelto...@gmail.com wrote: I reviewed that quite a bit during the night. I guess I need to read up on dovecot's definitions, since that INBOX parameter kept throwing me. There really isn't an INBOX to a pop account's mbox, but there is on our imap scheme. So I might have been trying to force the issue. I would recommend using Maildir format instead of mbox format. Maildir seems to be the default for most IMAP servers these days. Yes, I think dovecot will show INBOX and other folders with imap. if you connect with pop it will only show the contents of INBOX, but from the same INBOX that imap would use, so delivery to Maildir should work for everyone. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
did you try doveconf -n -c dovecot.old.conf dovecot.new.conf we also use dovecot for POP as well as IMAP. we are using the maildir storage for mails (one file per one mail). no problem sofar (touch wood). suomi On 02/13/2012 01:35 PM, Steve Campbell wrote: On 2/12/2012 2:09 PM, Alexander Dalloz wrote: Am 12.02.2012 20:01, schrieb Steve Campbell: Actually, I'm having problems with pop and imap. I changed mailservers this weekend, going from a Centos 3 box to a Centos 6 box. The Centos 3 box used the old standard imap and pop servers. We use horde for our webmail. The pop3 mailboxes (mbox) were in /var/spool/mail and the imap folders were in /home/user/mail, which horde took care of. So 2 classes of users? As John has annotated, mixing POP3 and IMP4 use is not advised at all. Not really two classes of users. Most of the users use pop for retrieving email. Horde is our webmail app, and it reads the mailbox, but creates and manages the imap folders in user's home directory. This has worked fine in the past, allowing users to read mail from their desktop using pop, and if desired, using horde to read mail from elsewhere. If they want to be able to see read email from outside the building, they set their mail client to leave on server. Horde takes care of deleting email from the mbox as well if desired. Upon starting the Centos 6 box, I ran into tons of login and viewing problems. I tried Cyrus for imap, could log in, but couldn't see mail in the imap folders. Using dovecot for pop, I eventually could get logged in, but kept getting the couldn't open INBOX message, so no one could download their email, even though sendmail was delivering it properly. Cyrus-IMAPd is out of the game unless you do a real mail store migration as Cyrus-IMAPd uses his own storage scheme. My preference is to use dovecot as both pop and imap servers. The Centos 3 imap server used an rpm named imap-2002d-12 (at least that's the one I have on that server). I'm not sure how mixing comes into play here, since most people set their smart phones up as imap clients, and they can still view their email when they arrive at work using pop. So here's my question: Can (should) dovecot be used for both imap and pop when considering the above setup of mbox in /var/spool/mail and imap folders in ~/mail? Horde will read the mbox to display new messages in it's screens. Yes. That's good to get an opinion. I'm going to proceed thinking dovecot will do both. There's also an issue to address later of shared stuff I'll have to investigate. We have a few accounts that multiple users use in this manner through imap. They log in as a singular user, but there are issues of deletions and the like that sometimes cause problems. If so, does anyone have a pretty good link to how to make dovecot function using the old Centos pop/imap scheme? Should I try and convert the old mbox files to another format or destination to make this work? See http://wiki.dovecot.org/MailLocation I reviewed that quite a bit during the night. I guess I need to read up on dovecot's definitions, since that INBOX parameter kept throwing me. There really isn't an INBOX to a pop account's mbox, but there is on our imap scheme. So I might have been trying to force the issue. Thanks for any help. It's been a long night, going on about 14 hours now and I'm just getting the old server back to current until I figure this out. Not intended to sound smart ass, but changing a production system the way you do without prior testing isn't that clever. Not taken in any bad way. I had actually tested it pretty well for all the stuff I'm running on it. Sendmail worked as expected. All of the other apps I have running dealing with email worked fine as well. Apps such as MimeDefang, MailScanner, MailWatch, and everything else. I took for granted that pop and imap would work fine since on the old system, they just worked. I had no idea these services had changed so much. So yes, I failed to test the two things that users want most. Egg on my face, for sure. Thanks for the help, and criticism. steve campbell I wish you success. Thanks. Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Sound drop out with totem. mplayer Can't open audio device /dev/dsp
Mark LaPierre wrote: Hey all. This morning I found that my audio playback is randomly sprinkled with sound skips and dropouts. I went to /var/log/yum.log and found this: Feb 09 20:18:22 Updated: lame-3.99.4-2.el6.rf.i686 I'm not saying that caused the problem but it's all I could find that changed. When I ls in /dev there is no dsp entry. That would explain why mplayer Can't open audio device /dev/dsp. I don't know why there is no /dev/dsp. MPlayer 1.0rc4-4.4.6 seems you're mixing repos here, that's not the mplayer provided by repoforge AFAIK. this could be part or all of your problem. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
on 2/13/2012 4:35 AM Steve Campbell spake the following: On 2/12/2012 2:09 PM, Alexander Dalloz wrote: Am 12.02.2012 20:01, schrieb Steve Campbell: Actually, I'm having problems with pop and imap. I changed mailservers this weekend, going from a Centos 3 box to a Centos 6 box. The Centos 3 box used the old standard imap and pop servers. We use horde for our webmail. The pop3 mailboxes (mbox) were in /var/spool/mail and the imap folders were in /home/user/mail, which horde took care of. So 2 classes of users? As John has annotated, mixing POP3 and IMP4 use is not advised at all. Not really two classes of users. Most of the users use pop for retrieving email. Horde is our webmail app, and it reads the mailbox, but creates and manages the imap folders in user's home directory. This has worked fine in the past, allowing users to read mail from their desktop using pop, and if desired, using horde to read mail from elsewhere. If they want to be able to see read email from outside the building, they set their mail client to leave on server. Horde takes care of deleting email from the mbox as well if desired. Upon starting the Centos 6 box, I ran into tons of login and viewing problems. I tried Cyrus for imap, could log in, but couldn't see mail in the imap folders. Using dovecot for pop, I eventually could get logged in, but kept getting the couldn't open INBOX message, so no one could download their email, even though sendmail was delivering it properly. Cyrus-IMAPd is out of the game unless you do a real mail store migration as Cyrus-IMAPd uses his own storage scheme. My preference is to use dovecot as both pop and imap servers. The Centos 3 imap server used an rpm named imap-2002d-12 (at least that's the one I have on that server). I'm not sure how mixing comes into play here, since most people set their smart phones up as imap clients, and they can still view their email when they arrive at work using pop. So here's my question: Can (should) dovecot be used for both imap and pop when considering the above setup of mbox in /var/spool/mail and imap folders in ~/mail? Horde will read the mbox to display new messages in it's screens. Yes. That's good to get an opinion. I'm going to proceed thinking dovecot will do both. There's also an issue to address later of shared stuff I'll have to investigate. We have a few accounts that multiple users use in this manner through imap. They log in as a singular user, but there are issues of deletions and the like that sometimes cause problems. If so, does anyone have a pretty good link to how to make dovecot function using the old Centos pop/imap scheme? Should I try and convert the old mbox files to another format or destination to make this work? See http://wiki.dovecot.org/MailLocation I reviewed that quite a bit during the night. I guess I need to read up on dovecot's definitions, since that INBOX parameter kept throwing me. There really isn't an INBOX to a pop account's mbox, but there is on our imap scheme. So I might have been trying to force the issue. Thanks for any help. It's been a long night, going on about 14 hours now and I'm just getting the old server back to current until I figure this out. Not intended to sound smart ass, but changing a production system the way you do without prior testing isn't that clever. Not taken in any bad way. I had actually tested it pretty well for all the stuff I'm running on it. Sendmail worked as expected. All of the other apps I have running dealing with email worked fine as well. Apps such as MimeDefang, MailScanner, MailWatch, and everything else. I took for granted that pop and imap would work fine since on the old system, they just worked. I had no idea these services had changed so much. So yes, I failed to test the two things that users want most. Egg on my face, for sure. Thanks for the help, and criticism. steve campbell I wish you success. Thanks. Steve, I know I'm late to the party, but you are saying your old server was running UWimap ( by the statement of imap-2002d-12)? If so, there is a little bit of work to do in converting old mail if you brought it forward... http://wiki2.dovecot.org/Migration/UW ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Adding Mandarin support - pointers?
I've had a request from one of my users to add Mandarin support. A few quick googles gets me nothing, nor looking for adding language support. Anyone have a pointer to info on adding whatever packages/group packages I need? Thanks in advance. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Adding Mandarin support - pointers?
From: m.r...@5-cent.us m.r...@5-cent.us I've had a request from one of my users to add Mandarin support. A few quick googles gets me nothing, nor looking for adding language support. Anyone have a pointer to info on adding whatever packages/group packages I need? Something like that? yum install @Chinese Support JD ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
Never too late for information. Here's the situation as it stands. The original server is a Centos 3 box, and the new server is a Centos 6 box. They are separate boxes and I can move mail back and forth between the without losing any email (so far). I've got pop3 and imap logging in, but only retrieving pop email, etc. on the new box. The INBOX points to where sendmail deposits it. My config right now stands at: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u protocols = pop3 imap By switching my test account from pop to imap, I can't get emails. I'm not sure if the info in your link is pertinent yet. But now I'm wondering if I need Namespaces configured. Both pop and imap use the same INBOX (/var/spool/mail/%u) but imap doesn't seem to honor the above mail_location). So for now, I'm reading a lot more trying to discover how things aren't working. Thanks steve On 2/13/2012 11:18 AM, Scott Silva wrote: on 2/13/2012 4:35 AM Steve Campbell spake the following: On 2/12/2012 2:09 PM, Alexander Dalloz wrote: Am 12.02.2012 20:01, schrieb Steve Campbell: Actually, I'm having problems with pop and imap. I changed mailservers this weekend, going from a Centos 3 box to a Centos 6 box. The Centos 3 box used the old standard imap and pop servers. We use horde for our webmail. The pop3 mailboxes (mbox) were in /var/spool/mail and the imap folders were in /home/user/mail, which horde took care of. So 2 classes of users? As John has annotated, mixing POP3 and IMP4 use is not advised at all. Not really two classes of users. Most of the users use pop for retrieving email. Horde is our webmail app, and it reads the mailbox, but creates and manages the imap folders in user's home directory. This has worked fine in the past, allowing users to read mail from their desktop using pop, and if desired, using horde to read mail from elsewhere. If they want to be able to see read email from outside the building, they set their mail client to leave on server. Horde takes care of deleting email from the mbox as well if desired. Upon starting the Centos 6 box, I ran into tons of login and viewing problems. I tried Cyrus for imap, could log in, but couldn't see mail in the imap folders. Using dovecot for pop, I eventually could get logged in, but kept getting the couldn't open INBOX message, so no one could download their email, even though sendmail was delivering it properly. Cyrus-IMAPd is out of the game unless you do a real mail store migration as Cyrus-IMAPd uses his own storage scheme. My preference is to use dovecot as both pop and imap servers. The Centos 3 imap server used an rpm named imap-2002d-12 (at least that's the one I have on that server). I'm not sure how mixing comes into play here, since most people set their smart phones up as imap clients, and they can still view their email when they arrive at work using pop. So here's my question: Can (should) dovecot be used for both imap and pop when considering the above setup of mbox in /var/spool/mail and imap folders in ~/mail? Horde will read the mbox to display new messages in it's screens. Yes. That's good to get an opinion. I'm going to proceed thinking dovecot will do both. There's also an issue to address later of shared stuff I'll have to investigate. We have a few accounts that multiple users use in this manner through imap. They log in as a singular user, but there are issues of deletions and the like that sometimes cause problems. If so, does anyone have a pretty good link to how to make dovecot function using the old Centos pop/imap scheme? Should I try and convert the old mbox files to another format or destination to make this work? See http://wiki.dovecot.org/MailLocation I reviewed that quite a bit during the night. I guess I need to read up on dovecot's definitions, since that INBOX parameter kept throwing me. There really isn't an INBOX to a pop account's mbox, but there is on our imap scheme. So I might have been trying to force the issue. Thanks for any help. It's been a long night, going on about 14 hours now and I'm just getting the old server back to current until I figure this out. Not intended to sound smart ass, but changing a production system the way you do without prior testing isn't that clever. Not taken in any bad way. I had actually tested it pretty well for all the stuff I'm running on it. Sendmail worked as expected. All of the other apps I have running dealing with email worked fine as well. Apps such as MimeDefang, MailScanner, MailWatch, and everything else. I took for granted that pop and imap would work fine since on the old system, they just worked. I had no idea these services had changed so much. So yes, I failed to test the two things that users want most. Egg on my face, for sure. Thanks for the help, and criticism. steve campbell I wish you success. Thanks. Steve, I know I'm late to the party, but you are saying your old server was
Re: [CentOS] Adding Mandarin support - pointers?
Greetings, On Mon, Feb 13, 2012 at 10:25 PM, John Doe jd...@yahoo.com wrote: From: m.r...@5-cent.us m.r...@5-cent.us I've had a request from one of my users to add Mandarin support. A few quick googles gets me nothing, nor looking for adding language support. Anyone have a pointer to info on adding whatever packages/group packages I need? Something like that? yum install @Chinese Support Pardon my ignorance: should it be 'yum groupinstall Chinese Support ' ? Just wondering. Haven't done any groupinstall in a while. IIRC, at least for Indian languages, the base and openoffice related RPMs seems to be different Or I am growing too old for these things. -- Regards, Rajagopal ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Adding Mandarin support - pointers?
On Mon, Feb 13, 2012 at 10:34:01PM +0530, Rajagopal Swaminathan wrote: Pardon my ignorance: should it be 'yum groupinstall Chinese Support ' ? As per man yum if the package to be installed starts with '@' it is interpreted as being a group name. John -- You can safely assume you've created God in your own image when it turns out that God hates all the same people you do. -- Anne Lamott (10 April 1954-), American author, Bird by Bird pgpxWJtychvjB.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Adding Mandarin support - pointers?
John Doe wrote: From: m.r...@5-cent.us m.r...@5-cent.us I've had a request from one of my users to add Mandarin support. A few quick googles gets me nothing, nor looking for adding language support. Anyone have a pointer to info on adding whatever packages/group packages I need? Something like that? yum install @Chinese Support As I've never needed to do it before, I had no idea, and was a tad annoyed that my google found nothing in the way of advice or howtos. With that, thanks a lot, John, it worked, as reported by my user. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
On Mon, Feb 13, 2012 at 11:02 AM, Steve Campbell campb...@cnpapers.comwrote: Never too late for information. Here's the situation as it stands. The original server is a Centos 3 box, and the new server is a Centos 6 box. They are separate boxes and I can move mail back and forth between the without losing any email (so far). I've got pop3 and imap logging in, but only retrieving pop email, etc. on the new box. The INBOX points to where sendmail deposits it. My config right now stands at: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u protocols = pop3 imap By switching my test account from pop to imap, I can't get emails. I'm not sure if the info in your link is pertinent yet. But now I'm wondering if I need Namespaces configured. Both pop and imap use the same INBOX (/var/spool/mail/%u) but imap doesn't seem to honor the above mail_location). So for now, I'm reading a lot more trying to discover how things aren't working. I think the uw server had a magic mode where the imap side would merge new stuff in mbox format in /var/spool/mail/user with wherever it stored the imap inbox. With dovecot you'll need to deliver to maildir in the first place and it will see the same thing on pop and imap connections (but only show what it considers the inbox to pop connections). If you need to convert formats or copy between machines, there is a program called imapsync that will connect as a client to two imap servers and sync the folder structure. You could probably also switch to cyrus if you use that to do the copy. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Anyone already tried to backport the latest ASPM kernel patch to 6.2?
Michael Lampe wrote: In other words: my BIOS is broken. But it's broken for all Lenovo Notebooks. So ... It seems mine is particularly broken: The BIOS isn't even lying, it realy disables ASPM! That at least is my conclusion after looking at this https://wiki.edubuntu.org/Kernel/PowerManagementASPM and a closer inspection of 'lspci -vvv'. The backported patch may be correct after all. It may be a candiate for centosplus kernel. If someone else wants to test: I can upload a kernel with this patch applied. -Michael ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] displaying user and group names in chroot sftp
I am testing a chrooted environment for sftp using the internal-sftp subsystem. Now that I seem to have SELinux mostly out of the way, when I do an 'ls -l' after the sftp login I see only numbers for the uids and gids. When I was using scponly I simply had a local version of /etc/passwd and /etc/group but these are evidently not used by the internal sftp subsystem. Is there a way to get the internal sftp subsystem to deliver names instead of the numbers? -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] init/upstart issue? ypbind and autofs
- Original Message - | Lars Hecking writes: | Lars Hecking writes: | |One problem I have with custom CentOS 6 installation is that NIS |auto.* |maps are not available. According to boot.log, ypbind starts |before autofs, |but when I login to the machine, the maps are not available |until I issue |a service autofs restart. | |Any pointers on what to check? | | I guess CentOS doesn't use pid randomisation. autofs does start | before | ybind: | | root 2107 1 0 16:40 ?00:00:00 automount | --pid-file /var/run/autofs.pid | root 2517 1 0 16:41 ?00:00:00 /usr/sbin/ypbind | root 3009 2976 0 16:43 pts/000:00:00 egrep auto|ypb | | Another machine I installed interactively (this one is | kickstarted) works | correctly. | | Solved. | | The other machine doesn't have NetworkManager installed. Removed it | here | and NIS/autofs started working correctly. You don't have to remove NetworkManager you just need to tell the interface not to be managed by NM in order for it to work. | Why again did RH switch to NM? To better support mobile devices like laptops and to make network configuration easier for new GNU/Linux users. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dovecot problems
Hi, On Mon, Feb 13, 2012 at 7:43 PM, Les Mikesell lesmikes...@gmail.com wrote: If you need to convert formats or copy between machines, there is a program called imapsync that will connect as a client to two imap servers and sync the folder structure. You could probably also switch to cyrus if you use that to do the copy. +1 for imapsync, I've migrated many imap accounts from different servers with it. It's available in the rpmforge repositry. Best, Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Removing All Packages From Repository
Is there a way to remove all packages from a certain repository such as RPMFORGE? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] bug in repo affecting perl
I seem to running into the following bug when attempting to perform a yum update: http://bugs.centos.org/view.php?id=5322 I have been skipping perl to move on. However, I am unable to update perl to the latest i386 release due to what appears to be a mistake in the centOS repo. The CentOS mirrors have the following: http://mirrors.kernel.org/centos/5/os/i386/CentOS/perl-5.8.8-32.el5_6.3.i386.rpm http://mirrors.kernel.org/centos/5/os/x86_64/CentOS/perl-5.8.8-32.el5_6.3.x86_64.rpm http://mirrors.kernel.org/centos/5/updates/i386/RPMS/perl-5.8.8-32.el5_7.6.i386.rpm http://mirrors.kernel.org/centos/5/updates/x86_64/RPMS/perl-5.8.8-32.el5_7.6.x86_64.rpm *http://mirrors.kernel.org/centos/5/extras/x86_64/RPMS/perl-5.8.8-32.el5_6.3.i386.rpm* ??? When I run a yum list perl or yum update perl.i386 all I see is 5.8.8-32.el5_6.3 in the extras repo. It seems like this file shouldn't even exist. If I disable the repo my yum finds nothing for the i386 release of perl, even though the RPM is present in the updates directory. Could a maintainer of the repository please put some emphasis on this 2 month old bug? Thanks, --Blake ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Removing All Packages From Repository
on 2/13/2012 12:54 PM Matt spake the following: Is there a way to remove all packages from a certain repository such as RPMFORGE? I have done it by something like rpm -qa|grep rf and cat the list into rpm -U... I don't have the exact incantation near me, but that will get you a start ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Removing All Packages From Repository
On 02/13/2012 09:54 PM, Matt wrote:
Is there a way to remove all packages from a certain repository such
as RPMFORGE?
yum remove $(yum list installed | grep repoforge | awk '{ print $1 }')
where repoforge is the part of the repository name that show up in yum
list
--
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Removing All Packages From Repository
Ljubomir Ljubojevic wrote:
On 02/13/2012 09:54 PM, Matt wrote:
Is there a way to remove all packages from a certain repository such
as RPMFORGE?
yum remove $(yum list installed | grep repoforge | awk '{ print $1 }')
where repoforge is the part of the repository name that show up in yum
list
That's silly:
yum remove $(yum list installed | awk '{if ($0 ~ /repoforge) { print $1;}}')
mark, still awking after all these years.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] MySQL/file system question
Hello listmates, I got a rather strange situation that I can't quite make sense of. OK, I've got a very large data file to sort (hundreds of millions of lines) and I decided to use MySQL for the purpose. I inserted the stuff into a table easily enough. Then I decided to sort it and got stuck as it turned out that MySQL, unless specifically configured to do otherwise, puts temporary files in /tmp which simply was not sufficiently large. Then I changed that directory to a partition that had more space (let's call the new temp driectory /home/big-temp) and now as I am running the query aimed at sorting the data it seems like space, according to the df, is no longer being used up under / (which was there /tmp was) but is now being used up in the right partition ( /home, the large one). Yet /home/big-temp is still empty! So how is that possible? I know there are all kinds of file locking possible depending on the circumstances, file system type, etc - but how can it be that the files, if they exist, are not even visible to ls, even ls -a, even run by root? Thanks in advance for any clarification. Cheers, Boris. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On Mon, 2012-02-13 at 16:45 -0500, Boris Epstein wrote:
Hello listmates,
I got a rather strange situation that I can't quite make sense of. OK, I've
got a very large data file to sort (hundreds of millions of lines) and I
decided to use MySQL for the purpose. I inserted the stuff into a table
easily enough. Then I decided to sort it and got stuck as it turned out
that MySQL, unless specifically configured to do otherwise, puts temporary
files in /tmp which simply was not sufficiently large. Then I changed that
directory to a partition that had more space (let's call the new temp
driectory /home/big-temp) and now as I am running the query aimed at
sorting the data it seems like space, according to the df, is no longer
being used up under / (which was there /tmp was) but is now being used up
in the right partition ( /home, the large one). Yet /home/big-temp is still
empty!
So how is that possible?
Easy. It is using temporary files the *correct* way.
1. Open file
2. Unlink file
3. Use file
4. Close file
This means (a) even if the process abends the resources allocated to the
file are released and (b) an external process can't see [or modify] the
temporary file.
When a file is unlinked it remains 'active' until all references to the
file are released - but the daemon is still holding a reference [because
it is using the file].
There is a file there, but nobody, not even root, can see it.
Actually you can; if you look in /proc/{pid#}/fd ...
--
System Network Administrator [ LPI NCLA ]
http://www.whitemiceconsulting.com
OpenGroupware Developer http://www.opengroupware.us
Adam Tauno Williams
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On Mon, Feb 13, 2012 at 4:58 PM, Adam Tauno Williams awill...@whitemice.org
wrote:
On Mon, 2012-02-13 at 16:45 -0500, Boris Epstein wrote:
Hello listmates,
I got a rather strange situation that I can't quite make sense of. OK,
I've
got a very large data file to sort (hundreds of millions of lines) and I
decided to use MySQL for the purpose. I inserted the stuff into a table
easily enough. Then I decided to sort it and got stuck as it turned out
that MySQL, unless specifically configured to do otherwise, puts
temporary
files in /tmp which simply was not sufficiently large. Then I changed
that
directory to a partition that had more space (let's call the new temp
driectory /home/big-temp) and now as I am running the query aimed at
sorting the data it seems like space, according to the df, is no longer
being used up under / (which was there /tmp was) but is now being used up
in the right partition ( /home, the large one). Yet /home/big-temp is
still
empty!
So how is that possible?
Easy. It is using temporary files the *correct* way.
1. Open file
2. Unlink file
3. Use file
4. Close file
This means (a) even if the process abends the resources allocated to the
file are released and (b) an external process can't see [or modify] the
temporary file.
When a file is unlinked it remains 'active' until all references to the
file are released - but the daemon is still holding a reference [because
it is using the file].
There is a file there, but nobody, not even root, can see it.
Actually you can; if you look in /proc/{pid#}/fd ...
--
System Network Administrator [ LPI NCLA ]
http://www.whitemiceconsulting.com
OpenGroupware Developer http://www.opengroupware.us
Adam Tauno Williams
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Adam, thanks!
I haven't thought of it this way. In fact it matches with this description:
http://dev.mysql.com/doc/refman/5.1/en/temporary-files.html
I can kind of see the advantages; the disadvantages, of course, are that a
major transaction can not be resumed in case the mysqld process is stopped.
Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] QEMU configuration not persistent
Since switching from CentOS 5.7 to CentOS 6.x I find that one of the VMs will not restart upon system reboot. I finally figured out that the video is always set to vmvga after rebooting. In addition the VM's storage always reverts back to IDE from virtio and is set to use the wrong image. It may be related to the fact that I moved the XML files that defined the VMs from the old (CentOS 5.7) /etc/libvirt/qemu directory to the new (CentOS 6.2) /etc/libvirt/qemu directory. The images are stored is the same LVM partitions as they were on the CentOS 5.7 Any ideas why a VM would revert back? I've checked the XML file before rebooting and it always has the correct info in it, until after the reboot. Emmett ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
Easy. It is using temporary files the *correct* way.
1. Open file
2. Unlink file
3. Use file
4. Close file
This means (a) even if the process abends the resources allocated to the
file are released and (b) an external process can't see [or modify] the
temporary file.
When a file is unlinked it remains 'active' until all references to the
file are released - but the daemon is still holding a reference [because
it is using the file].
There is a file there, but nobody, not even root, can see it.
Actually you can; if you look in /proc/{pid#}/fd ...
--
System Network Administrator [ LPI NCLA ]
http://www.whitemiceconsulting.com
OpenGroupware Developer http://www.opengroupware.us
Adam Tauno Williams
In fact, I did look in /proc/{pid#}/fd and found the file names, thanks!
Coud quite figure out the size of those invisible files - but no matter,
hopefully I've got enough room.
Thanks.
Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On Mon, 2012-02-13 at 17:06 -0500, Boris Epstein wrote:
On Mon, Feb 13, 2012 at 4:58 PM, Adam Tauno Williams awill...@whitemice.org
wrote:
On Mon, 2012-02-13 at 16:45 -0500, Boris Epstein wrote:
Hello listmates,
I got a rather strange situation that I can't quite make sense of. OK,
I've
got a very large data file to sort (hundreds of millions of lines) and I
decided to use MySQL for the purpose. I inserted the stuff into a table
easily enough. Then I decided to sort it and got stuck as it turned out
that MySQL, unless specifically configured to do otherwise, puts
temporary
files in /tmp which simply was not sufficiently large. Then I changed
that
directory to a partition that had more space (let's call the new temp
driectory /home/big-temp) and now as I am running the query aimed at
sorting the data it seems like space, according to the df, is no longer
being used up under / (which was there /tmp was) but is now being used up
in the right partition ( /home, the large one). Yet /home/big-temp is
still
empty!
So how is that possible?
Easy. It is using temporary files the *correct* way.
1. Open file
2. Unlink file
3. Use file
4. Close file
This means (a) even if the process abends the resources allocated to the
file are released and (b) an external process can't see [or modify] the
temporary file.
When a file is unlinked it remains 'active' until all references to the
file are released - but the daemon is still holding a reference [because
it is using the file].
There is a file there, but nobody, not even root, can see it.
Actually you can; if you look in /proc/{pid#}/fd ...
I haven't thought of it this way. In fact it matches with this description:
http://dev.mysql.com/doc/refman/5.1/en/temporary-files.html
I can kind of see the advantages; the disadvantages, of course, are that a
major transaction can not be resumed in case the mysqld process is stopped.
If the process is stopped the transaction cannot be resumed for a myriad
reasons; loss of the temporary file is a trivial concern.
--
System Network Administrator [ LPI NCLA ]
http://www.whitemiceconsulting.com
OpenGroupware Developer http://www.opengroupware.us
Adam Tauno Williams
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
If the process is stopped the transaction cannot be resumed for a myriad reasons; loss of the temporary file is a trivial concern. -- System Network Administrator [ LPI NCLA ] http://www.whitemiceconsulting.com OpenGroupware Developer http://www.opengroupware.us Adam Tauno Williams ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos True - although if you somehow track your progress within the transaction making it resumable could be possible. Boris. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] my notes on bond, bridge, network, kvm, host and virtual so far
On 02/07/2012 07:26 PM, Devin Reade wrote: I had a lot of problems with the network stack on VMs, both under VMWare ESXi and Xen where the network would just go numb. After a lot of splunking I determined that it seemed to be related to faulty TCP segment offload. Yeah, wow. You just jogged my memory. Intel 82573(V/L/E) ethernet adapters had a serious bug that would cause TX hangs: http://downloadmirror.intel.com/9180/eng/README.txt 82573(V/L/E) TX Unit Hang Messages Bob, what model cards did you have in your server? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On Mon, Feb 13, 2012 at 4:06 PM, Boris Epstein borepst...@gmail.com wrote: I haven't thought of it this way. In fact it matches with this description: http://dev.mysql.com/doc/refman/5.1/en/temporary-files.html I can kind of see the advantages; the disadvantages, of course, are that a major transaction can not be resumed in case the mysqld process is stopped. I don't think it would make much sense to try to finish a query after a restart since at that point the temp table might not reflect the real data anyway. Have you tried adding an index on the fields in your query so it doesn't have to sort everything when you make the query? Mysql isn't too bright about optimizing 3-table joins, but with one or 2 and pre-indexed fields it shouldn't need much time or extra space. -- Les Mikesell lesmikes...@gmail.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] QEMU configuration not persistent
On 02/13/2012 11:18 PM, Emmett Culley wrote: Since switching from CentOS 5.7 to CentOS 6.x I find that one of the VMs will not restart upon system reboot. I finally figured out that the video is always set to vmvga after rebooting. In addition the VM's storage always reverts back to IDE from virtio and is set to use the wrong image. It may be related to the fact that I moved the XML files that defined the VMs from the old (CentOS 5.7) /etc/libvirt/qemu directory to the new (CentOS 6.2) /etc/libvirt/qemu directory. The images are stored is the same LVM partitions as they were on the CentOS 5.7 Any ideas why a VM would revert back? I've checked the XML file before rebooting and it always has the correct info in it, until after the reboot. Do you shutdown that guest system prior to XML changes? -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS, Mikrotik and CentOS/RHEL/Linux consultant ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] QEMU configuration not persistent
On Mon, 13 Feb 2012, Emmett Culley wrote: Since switching from CentOS 5.7 to CentOS 6.x I find that one of the VMs will not restart upon system reboot. I finally figured out that the video is always set to vmvga after rebooting. In addition the VM's storage always reverts back to IDE from virtio and is set to use the wrong image. It may be related to the fact that I moved the XML files that defined the VMs from the old (CentOS 5.7) /etc/libvirt/qemu directory to the new (CentOS 6.2) /etc/libvirt/qemu directory. The images are stored is the same LVM partitions as they were on the CentOS 5.7 Any ideas why a VM would revert back? I've checked the XML file before rebooting and it always has the correct info in it, until after the reboot. Did you copy the XML file from the 5.7 host to 6.3 host as-is or did you edit it at all during the migration? I've found that I need either to run virsh define $DOM.xml and then start the new domain or run virsh create $DOM.xml and then, once it's running, make a trivial change (usually adding an XML comment) to the configuration via virsh edit $DOM to get things to stick. -- Paul Heinlein heinl...@madboa.com http://www.madboa.com/ ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On 02/13/2012 11:31 PM, Boris Epstein wrote:
In fact, I did look in /proc/{pid#}/fd and found the file names, thanks!
Coud quite figure out the size of those invisible files - but no matter,
hopefully I've got enough room.
ls -l /proc/{pid#}/fd
--
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On Mon, Feb 13, 2012 at 6:53 PM, Ljubomir Ljubojevic off...@plnet.rswrote:
On 02/13/2012 11:31 PM, Boris Epstein wrote:
In fact, I did look in /proc/{pid#}/fd and found the file names, thanks!
Coud quite figure out the size of those invisible files - but no matter,
hopefully I've got enough room.
ls -l /proc/{pid#}/fd
--
Ljubomir Ljubojevic
(Love is in the Air)
PL Computers
Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your
trusty Spiderman...
StarOS, Mikrotik and CentOS/RHEL/Linux consultant
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Ljubomir,
Here we go:
[root@gala ~]# ls -l /proc/18702/fd
total 0
lr-x-- 1 root root 64 Feb 13 18:58 0 - /dev/null
lrwx-- 1 root root 64 Feb 13 18:58 1 - /var/log/mysqld.log
lrwx-- 1 root root 64 Feb 13 18:58 10 - socket:[1245288]
lrwx-- 1 root root 64 Feb 13 18:58 11 - /home/mysql/tmp/ibEvxyKc
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 12 - socket:[1245289]
lrwx-- 1 root root 64 Feb 13 18:58 13 -
/home/mysql/mysql_data/mysql/host.MYI
lrwx-- 1 root root 64 Feb 13 18:58 14 -
/home/mysql/mysql_data/mysql/host.MYD
lrwx-- 1 root root 64 Feb 13 18:58 15 -
/home/mysql/mysql_data/mysql/user.MYI
lrwx-- 1 root root 64 Feb 13 18:58 16 -
/home/mysql/mysql_data/mysql/user.MYD
lrwx-- 1 root root 64 Feb 13 18:58 17 -
/home/mysql/mysql_data/mysql/db.MYI
lrwx-- 1 root root 64 Feb 13 18:58 18 -
/home/mysql/mysql_data/mysql/db.MYD
lrwx-- 1 root root 64 Feb 13 18:58 19 -
/home/mysql/mysql_data/mysql/tables_priv.MYI
lrwx-- 1 root root 64 Feb 13 18:58 2 - /var/log/mysqld.log
lrwx-- 1 root root 64 Feb 13 18:58 20 -
/home/mysql/mysql_data/mysql/tables_priv.MYD
lrwx-- 1 root root 64 Feb 13 18:58 21 -
/home/mysql/mysql_data/mysql/columns_priv.MYI
lrwx-- 1 root root 64 Feb 13 18:58 22 -
/home/mysql/mysql_data/mysql/columns_priv.MYD
lrwx-- 1 root root 64 Feb 13 18:58 23 -
/home/mysql/mysql_data/mysql/procs_priv.MYI
lrwx-- 1 root root 64 Feb 13 18:58 24 -
/home/mysql/mysql_data/mysql/procs_priv.MYD
lrwx-- 1 root root 64 Feb 13 18:58 25 -
/home/mysql/mysql_data/mysql/servers.MYI
lrwx-- 1 root root 64 Feb 13 18:58 26 -
/home/mysql/mysql_data/mysql/servers.MYD
lrwx-- 1 root root 64 Feb 13 18:58 27 -
/home/mysql/mysql_data/mysql/event.MYI
lrwx-- 1 root root 64 Feb 13 18:58 28 -
/home/mysql/mysql_data/mysql/event.MYD
lrwx-- 1 root root 64 Feb 13 18:58 29 - socket:[1245325]
lrwx-- 1 root root 64 Feb 13 18:58 3 - /home/mysql/mysql_data/ibdata1
lrwx-- 1 root root 64 Feb 13 18:58 30 -
/home/mysql/mysql_data/text_sort/local_list.MYI
lrwx-- 1 root root 64 Feb 13 18:58 31 -
/home/mysql/mysql_data/text_sort/local_list.MYD
lrwx-- 1 root root 64 Feb 13 18:58 32 -
/home/mysql/mysql_data/text_sort/local_list_sorted.MYI
lrwx-- 1 root root 64 Feb 13 18:58 33 -
/home/mysql/mysql_data/text_sort/local_list_sorted.MYD
lrwx-- 1 root root 64 Feb 13 18:58 34 -
/home/mysql/mysql_data/text_sort/tar_list.MYI
lrwx-- 1 root root 64 Feb 13 18:58 35 -
/home/mysql/mysql_data/text_sort/tar_list.MYD
lrwx-- 1 root root 64 Feb 13 18:58 36 - /home/mysql/tmp/MYbUgIFT
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 37 - /home/mysql/tmp/MYizt5rL
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 38 - socket:[1249477]
lrwx-- 1 root root 64 Feb 13 18:58 39 - socket:[1340698]
lrwx-- 1 root root 64 Feb 13 18:58 4 - /home/mysql/tmp/ibvjZa8E
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 40 -
/home/mysql/mysql_data/text_sort/local_list.MYD
lrwx-- 1 root root 64 Feb 13 18:58 41 -
/home/mysql/mysql_data/text_sort/local_list_sorted.MYD
lrwx-- 1 root root 64 Feb 13 18:58 5 - /home/mysql/tmp/ib08cXW2
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 6 - /home/mysql/tmp/ibtcHJLq
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 7 - /home/mysql/tmp/ibE0DGCO
(deleted)
lrwx-- 1 root root 64 Feb 13 18:58 8 -
/home/mysql/mysql_data/ib_logfile0
lrwx-- 1 root root 64 Feb 13 18:58 9 -
/home/mysql/mysql_data/ib_logfile1
[root@gala ~]#
Now the files of interest are the ones marked deleted in /home/mysql/tmp .
Now how do I tell what their size is?
Thanks.
Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] oops, or how to bring a datacenter router down with one setting
On 02/10/2012 05:54 AM, Bob Hoffman wrote: Yea, I gave up on bonding, ended up just using eth1. But every tutorial I found had added eth0 and eth1 as interfaces to br0, thus sharing the bridge so to speak. Those tutorials were documenting the manner in which you can set up a transparent Linux firewall. That's not what you want to do with a KVM server. Creating an Ethernet bridge and adding two interfaces to it effectively makes a Linux host into a two-port switch with firewalling. If you connect multiple ports from one switch to ports on a second switch (two bridged Linux Ethernet ports to a switch) you create a switch loop. Switch loops will endlessly replay broadcast traffic (such as ARP), creating a broadcast storm. Yes, that can consume all of a router's CPU cycles quite easily. That is why data centers should always run spanning tree on their switches. STP will shut off ports that get looped. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] QEMU configuration not persistent
On 02/13/2012 03:49 PM, Paul Heinlein wrote: On Mon, 13 Feb 2012, Emmett Culley wrote: Since switching from CentOS 5.7 to CentOS 6.x I find that one of the VMs will not restart upon system reboot. I finally figured out that the video is always set to vmvga after rebooting. In addition the VM's storage always reverts back to IDE from virtio and is set to use the wrong image. It may be related to the fact that I moved the XML files that defined the VMs from the old (CentOS 5.7) /etc/libvirt/qemu directory to the new (CentOS 6.2) /etc/libvirt/qemu directory. The images are stored is the same LVM partitions as they were on the CentOS 5.7 Any ideas why a VM would revert back? I've checked the XML file before rebooting and it always has the correct info in it, until after the reboot. Did you copy the XML file from the 5.7 host to 6.3 host as-is or did you edit it at all during the migration? I've found that I need either to run virsh define $DOM.xml and then start the new domain or run virsh create $DOM.xml and then, once it's running, make a trivial change (usually adding an XML comment) to the configuration via virsh edit $DOM to get things to stick. I did copy the XML files to the 6.2 machine. Then when I found that the VMs would not start because they were set to vmvga video, which doesn't seem to be supported anymore, I changed the XML files to cirrus. Then I tried editing the VM using virsh, but still it doesn't persist. Hmm. There is only one of the VMs that doesn't persist so I'll try using virsh edit again on that one and make a change as you suggest, just in case I never really changed anything for that VM using virsh edit. Thanks, Emmett ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] QEMU configuration not persistent
On 02/13/2012 04:24 PM, Emmett Culley wrote: On 02/13/2012 03:49 PM, Paul Heinlein wrote: On Mon, 13 Feb 2012, Emmett Culley wrote: Since switching from CentOS 5.7 to CentOS 6.x I find that one of the VMs will not restart upon system reboot. I finally figured out that the video is always set to vmvga after rebooting. In addition the VM's storage always reverts back to IDE from virtio and is set to use the wrong image. It may be related to the fact that I moved the XML files that defined the VMs from the old (CentOS 5.7) /etc/libvirt/qemu directory to the new (CentOS 6.2) /etc/libvirt/qemu directory. The images are stored is the same LVM partitions as they were on the CentOS 5.7 Any ideas why a VM would revert back? I've checked the XML file before rebooting and it always has the correct info in it, until after the reboot. Did you copy the XML file from the 5.7 host to 6.3 host as-is or did you edit it at all during the migration? I've found that I need either to run virsh define $DOM.xml and then start the new domain or run virsh create $DOM.xml and then, once it's running, make a trivial change (usually adding an XML comment) to the configuration via virsh edit $DOM to get things to stick. I did copy the XML files to the 6.2 machine. Then when I found that the VMs would not start because they were set to vmvga video, which doesn't seem to be supported anymore, I changed the XML files to cirrus. Then I tried editing the VM using virsh, but still it doesn't persist. Hmm. There is only one of the VMs that doesn't persist so I'll try using virsh edit again on that one and make a change as you suggest, just in case I never really changed anything for that VM using virsh edit. Thanks, Emmett Still doesn't persist. Each time I reboot I have to use virt-manager to change video to cirrus from vmvga, then remove the IDE driver that points to the wrong storage location and add a new virtio storage device pointing to the correct image (an LVM partiiton). After I make the changes I close virt-manager and restart it, then look at the configuration for the non-persistent VM, and my changes are still there and I can run the VM. I did a grep vmvga on the entire /etc/libvirt directory tree and found no references to vmvga. Where can libvirt be getting info to change the xml to vmvga, or the IDE to the wrong location? Emmett ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] MySQL/file system question
On Mon, 2012-02-13 at 18:59 -0500, Boris Epstein wrote: Here we go: [root@gala ~]# ls -l /proc/18702/fd total 0 ... lrwx-- 1 root root 64 Feb 13 18:58 7 - /home/mysql/tmp/ibE0DGCO (deleted) lrwx-- 1 root root 64 Feb 13 18:58 8 - /home/mysql/mysql_data/ib_logfile0 lrwx-- 1 root root 64 Feb 13 18:58 9 - /home/mysql/mysql_data/ib_logfile1 [root@gala ~]# Now the files of interest are the ones marked deleted in /home/mysql/tmp . Now how do I tell what their size is? I wouldn't bother pursuing this angle further; I am not an MySQL admin, but it must provide performance reporting, statistics, and explain information [PostgreSQL does, as do most other database engines]. Check the MySQL docs for how you monitor the utilization of temp spaces. If it can't provide this information choose another solution. It is best not to dig around under engines. Use the tools and let them tell you, otherwise you will build around implementation details. -- System Network Administrator [ LPI NCLA ] http://www.whitemiceconsulting.com OpenGroupware Developer http://www.opengroupware.us Adam Tauno Williams ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] bug in repo affecting perl
Blake Hudson wrote: I seem to running into the following bug when attempting to perform a yum update: http://bugs.centos.org/view.php?id=5322 I have been skipping perl to move on. However, I am unable to update perl to the latest i386 release due to what appears to be a mistake in the centOS repo. The CentOS mirrors have the following: http://mirrors.kernel.org/centos/5/os/i386/CentOS/perl-5.8.8-32.el5_6.3.i386.rpm http://mirrors.kernel.org/centos/5/os/x86_64/CentOS/perl-5.8.8-32.el5_6.3.x86_64.rpm http://mirrors.kernel.org/centos/5/updates/i386/RPMS/perl-5.8.8-32.el5_7.6.i386.rpm http://mirrors.kernel.org/centos/5/updates/x86_64/RPMS/perl-5.8.8-32.el5_7.6.x86_64.rpm *http://mirrors.kernel.org/centos/5/extras/x86_64/RPMS/perl-5.8.8-32.el5_6.3.i386.rpm* ??? why do you think there's a problem? if you have an x86_64 system, you are expected to use x86_64 perl, and that's what you have in the os and updates dir for that arch, with the newer version in updates. Same if you have an i386 system. Apparently centos extras provides the i386 package for people who want that on an x86_64 system, although the version provided is the older one. When I run a yum list perl or yum update perl.i386 all I see is 5.8.8-32.el5_6.3 in the extras repo. It seems like this file shouldn't even exist. If I disable the repo my yum finds nothing for the i386 release of perl, even though the RPM is present in the updates directory. it's not in x86_64 and I bet that's what your arch is. so yum doesn't look in the i386 path. Everything is normal. The only possible bug is that extras could carry the latest i386 package. Could a maintainer of the repository please put some emphasis on this 2 month old bug? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] my notes on bond, bridge, network, kvm, host and virtual so far
=== *Gordon Messmer* wrote On 02/07/2012 07:26 PM, Devin Reade wrote: / I had a lot of problems with the network stack on VMs, both under // VMWare ESXi and Xen where the network would just go numb. After a // lot of splunking I determined that it seemed to be related to // faulty TCP segment offload. / Yeah, wow. You just jogged my memory. Intel 82573(V/L/E) ethernet adapters had a serious bug that would cause TX hangs: http://downloadmirror.intel.com/9180/eng/README.txt 82573(V/L/E) TX Unit Hang Messages Bob, what model cards did you have in your server? = http://www.supermicro.com/products/system/2U/6026/SYS-6026T-NTR_.cfm Intel® 82576 Dual-Port Gigabit Ethernet Controller (though I think this is basically e1000) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
