Discuss

discuss@lists.centos.org

11 participants
34747 discussions

upgrading Mysql 5.0.95
by Mark Weaver 20 Mar '17

20 Mar '17

Hi All, I'm getting things ready to upgrade my aging installation of MySQL 5.0.95 on my CentOS 5 LAMP server. With the impending EOL date of 3.31 fast approaching my sense of doom and urgency is increasing. I see that the necessary packages are available in @base and @updates - mysql51 and mysql55 respectively but from all the information I've read on the matter so far I'm left with a few questions I don't yet have answers to.' What I've done so far and thankfully was able recover from: 1. installed and enabled to epel repo - ran yum remove mysql - this command wanted to remove a few things I wanted to keep in place like dovecot and a few php53 packages. I didn't want to have to go back and clean up any messes that would create. So, I used the rpm -e --nodeps command to remove the MySQL packages. - because this was a redhat repo it installed the binaries in a total different place AND tossed all my existing data directories. and yes I spit coffee all over my laptop screen and yes, I did have data dir backups and a dump of MySQL data. HOLY CRAP! 2. removed the epel packages - disabled this repo - for ever at least for now... 3. reinstalled the old MySQL 5.0.95 packages - because I was hyper-ventilating - reset roots password - imported all the databases from the dump and checked my web apps - everything working again. - I did have to recreate the mysql.servers table to be able to flush privileges. I understand that mysql51 is available in @base for the sole purpose of upgrading old MySQL and mysql55 is in updates for getting to 5.5, however here is where things get a little fuzzy for me: Steps for Upgrading (as I understand them): 1. Take a dump of all mysql database using mysqldump --add-drop-database --all-databases 2. Stop mysql services 3. make a backup of data directories: /var/lib/mysql (but its not _supposed_ to remove the data directories.) 3. yum remove mysql mysql-server (again, it will include a few things I don't want removed. so, i'll have to use rpm -e --nodeps and list the packages for removal then issue yum clean all.' 4. yum install mysql51 5. start mysql service 6. run command mysql_upgrade... (here's where things start getting fuzzy) Question #1: is this command to be run from the commandline or should I log into mysql as root user and run the command? Question #2: at this point I will have mysql 5.1 installed and running but to get up to 5.5 am I expected to yum remove 5.1 and then yum install 5.5 from @updates and repeat steps 5 and 6 OR simply run the command yum update mysql51* to catch all already installed mysql51 packages to and then run the mysql_update command to bring data up to date with the current mysql install? THank you for your kind attention... -- Mark

4 7

Up to date guide/information Sendmail SMTP Auth
by Mark Weaver 19 Mar '17

19 Mar '17

Hello all, I've been googling my brains out since yesterday looking for up-to-date information on this matter, and have found information that is anywhere from 15 to 5 years old. I'd really like some information that much more up to date on the subject. Specifically configuring Sendmail SMTP authentication (_no smart host stuff_). I've got Sendmail 8.14 installed on a CentOS 7.3 server. Also installed: - Cyrus-sasl - Dovecot - Openssl Essentially everything I need except the working knowledge for the process. If someone knows where I might locate this information it would be greatly appreciated. thanks Mark

5 17

Centos-6.8 fsck and lvms
by James B. Byrne 18 Mar '17

18 Mar '17

I have a CentOS-6.8 system which has a suspected HHD failure. I have booted it into rescue mode from a CentOS-6.5 minimal install CD in order to run fsck -c on it. The system hosts several vms. I have activated the lvs associated with these vm using pvscan -s ; vgscan ; vgchange -ay. An lvscan shows the lvs as ACTIVE. None are mounted. When I try to run fsck on any of them I see the following error: fsck from util-linux-ng.2.17.2 e2fsck 1.41.12.(17-May-2010) fsck.ext2: No such file or directory while trying to open /dev/vg. . . The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> Trying to find alternate super-blocks proves futile: dump2fs /dev/sda2 | grep -i superblock dump2fs 1.41.12 (17-May-2010) dump2fs: Bad magic number in super-block while trying to open /dev/sda2 Couldn't find valid filesystem superblock The file systems on this host were all created as type ext4 and all are lvs with the exception of /boot, which is not an lv and has its own partition on /dev/sda1. I infer that the HDD is gone the way of all flesh; or ferrite as the case may be. But, my ignorance on this is profound so if I am missing some form of recovery step I would appreciate some guidance on how to proceed. Thanks, -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@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

2 1

Re: [CentOS] [CentOS-announce] CEBA-2017:0392 CentOS 7 polkit BugFix Update
by Leonard den Ottolander 18 Mar '17

18 Mar '17

On Fri, 2017-03-03 at 13:26 +0000, Johnny Hughes wrote: > CentOS Errata and Bugfix Advisory 2017:0392 > > Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0392.html > 33395736c057583471a3e8d3554adb014d0d4cd167aa03bad5099c02faad1d38 polkit-0.112-11.el7_3.src.rpm Note that this update fixes neither the memory leak in the options parsing of the setuid binary pkexec, nor does it fix the memory leaks in pkcheck. https://googleprojectzero.blogspot.nl/2014/08/the-poisoned-nul-byte-2014-ed… https://bugs.freedesktop.org/show_bug.cgi?id=99626 https://bugzilla.redhat.com/show_bug.cgi?id=1418278 https://bugzilla.redhat.com/show_bug.cgi?id=1418287 https://bugzilla.redhat.com/show_bug.cgi?id=1418824 https://bugzilla.redhat.com/show_bug.cgi?id=1418825 Attached is a fix for these. Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

1 0

Re: [CentOS] frozen bubble for C7
by Scott Robbins 18 Mar '17

18 Mar '17

On Sat, Mar 18, 2017 at 07:16:08AM +0000, Miguel Medalha wrote: > > > > > Can't find perl(compress::bzip2) anywhere. > > Are you looking for this? (first hit on Google) > > http://search.cpan.org/~rurban/Compress-Bzip2-2.25/lib/Compress/Bzip2.pm > > Or this? > > ftp://195.220.108.108/linux/centos/7.3.1611/os/x86_64/Packages/perl-IO-Compress-2.061-2.el7.noarch.rpm > _______________________________________________ Definitely not the second one, as that makes no difference, (nor does having perl-Compress-Raw-Bzip2 which seemed a possibility. As for the first one you list, I see it is a Bzip2.pm and I note that I have that in a few different places, but frozen-bubble doesn't install for me. So, TL;DR Nope. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

1 0

CentOS-announce Digest, Vol 145, Issue 7
by centos-announce-request＠centos.org 18 Mar '17

18 Mar '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2017:0527 Moderate CentOS 6 tomcat6 Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 17 Mar 2017 14:19:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0527 Moderate CentOS 6 tomcat6 Security Update Message-ID: <20170317141939.GA39564(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0527 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0527.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f64287823394f3d9d740b227a937b1de4ce02fbb1ae8889739b05ed65c940d00 tomcat6-6.0.24-105.el6_8.noarch.rpm d0591d641d9b3108a67690f13904d4e2365e8c5a8934eda37078e28e22ecb009 tomcat6-admin-webapps-6.0.24-105.el6_8.noarch.rpm edfa8cf02e4ef510fefd95b3d20fbac303a21d0db2102cf7d54b74aad8167551 tomcat6-docs-webapp-6.0.24-105.el6_8.noarch.rpm 60f0a75029377fd15564dd2f22ab6d13bc92883d72e262c55058d602e2528da1 tomcat6-el-2.1-api-6.0.24-105.el6_8.noarch.rpm 2c65091e26bb0bc15e257f2b4551fc5273b0593d29c40a3b9c6fcbc17cf81d23 tomcat6-javadoc-6.0.24-105.el6_8.noarch.rpm 27fb7034a285f3251ce6b436795ad8ab2035e7f21c26e82d01200bfb50bc8061 tomcat6-jsp-2.1-api-6.0.24-105.el6_8.noarch.rpm a54a224d39d3f4fd84209fa80b2854c59e239dd62b66f9126d4465550ade826d tomcat6-lib-6.0.24-105.el6_8.noarch.rpm 9821af169505129d5db326cd237121850c4238f9bc1da963ba8ae4fc2678e11f tomcat6-servlet-2.5-api-6.0.24-105.el6_8.noarch.rpm 4e3673601b91c8466cf84702176570e572ff786c083e59e0ad2bf609d06a4e79 tomcat6-webapps-6.0.24-105.el6_8.noarch.rpm x86_64: f64287823394f3d9d740b227a937b1de4ce02fbb1ae8889739b05ed65c940d00 tomcat6-6.0.24-105.el6_8.noarch.rpm d0591d641d9b3108a67690f13904d4e2365e8c5a8934eda37078e28e22ecb009 tomcat6-admin-webapps-6.0.24-105.el6_8.noarch.rpm edfa8cf02e4ef510fefd95b3d20fbac303a21d0db2102cf7d54b74aad8167551 tomcat6-docs-webapp-6.0.24-105.el6_8.noarch.rpm 60f0a75029377fd15564dd2f22ab6d13bc92883d72e262c55058d602e2528da1 tomcat6-el-2.1-api-6.0.24-105.el6_8.noarch.rpm 2c65091e26bb0bc15e257f2b4551fc5273b0593d29c40a3b9c6fcbc17cf81d23 tomcat6-javadoc-6.0.24-105.el6_8.noarch.rpm 27fb7034a285f3251ce6b436795ad8ab2035e7f21c26e82d01200bfb50bc8061 tomcat6-jsp-2.1-api-6.0.24-105.el6_8.noarch.rpm a54a224d39d3f4fd84209fa80b2854c59e239dd62b66f9126d4465550ade826d tomcat6-lib-6.0.24-105.el6_8.noarch.rpm 9821af169505129d5db326cd237121850c4238f9bc1da963ba8ae4fc2678e11f tomcat6-servlet-2.5-api-6.0.24-105.el6_8.noarch.rpm 4e3673601b91c8466cf84702176570e572ff786c083e59e0ad2bf609d06a4e79 tomcat6-webapps-6.0.24-105.el6_8.noarch.rpm Source: c645432afdc6023fe17ffcb90158a66e3742e6201fc27806cae722102c226ab9 tomcat6-6.0.24-105.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 145, Issue 7 ***********************************************

1 0

lock out account after 3 failures
by Ian Diddams 18 Mar '17

18 Mar '17

I’m looking to configure a centos 7 server to lock out anaccount after 3 login failures. I’ve followed this https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht… Section2.1.9.5 Account Locking And even rebooted the serverbut it doesn’t lock my test account out. login as: test test@X’s password: Access denied test@X's password: Access denied test@X's password: Access denied test@X's password: Access denied test@X's password: Last failed login: Wed Mar 15 15:44:37 GMT 2017 fromXXXXXX on ssh:notty There were 4 failed login attempts since the lastsuccessful login. Last login: Wed Mar 15 15:14:05 2017 from YYYYYYYYYYYYY [test]$ Meanwhile the secure log also shows Mar 15 15:44:27 testbox sshd[4051]: pam_unix(sshd:auth): authenticationfailure; logname= uid=0 euid=0 tty=ssh ruser= rhost=YYYYYYYY user=test Mar 15 15:44:29 testbox sshd[4051]: Failed password fortest from X port 57118 ssh2 Mar 15 15:44:29 testbox sshd[4051]: Failed password fortest from X port 57118 ssh2 Mar 15 15:44:33 testbox sshd[4051]: Failed password fortest from X port 57118 ssh2 Mar 15 15:44:35 testbox sshd[4051]:pam_faillock(sshd:auth): Consecutive login failures for user test accounttemporarily locked Mar 15 15:44:37 testbox sshd[4051]: Failed password fortest from X port 57118 ssh2 Mar 15 15:44:44 testbox sshd[4051]: Accepted password fortest from X port 57118 ssh2 Mar 15 15:44:44 testbox sshd[4051]:pam_unix(sshd:session): session opened for user test by (uid=0) Ie I can deliberately mangle the password three times,secure log shows the account has been locked out, but then I can immediatelystill log in. Has anybody a link to a configuration that works?cheers ian

3 3

Re: [CentOS] frozen bubble for C7
by Miguel Medalha 18 Mar '17

18 Mar '17

> > Can't find perl(compress::bzip2) anywhere. Are you looking for this? (first hit on Google) http://search.cpan.org/~rurban/Compress-Bzip2-2.25/lib/Compress/Bzip2.pm Or this? ftp://195.220.108.108/linux/centos/7.3.1611/os/x86_64/Packages/perl-IO-Compress-2.061-2.el7.noarch.rpm

1 0

laptop editing
by Michael Hennebry 17 Mar '17

17 Mar '17

How does one put centos on a laptop? My understanding that laptops no longer come with optical drives. Booting from an install disk would be difficult. >From https://wiki.centos.org/HowTos/Laptops : Preparation tasks Repartition your harddisk Backup your Master Boot Record (MBR) Modifying your bootloader My understanding is that most laptops have at most one harddisk. Can it really be unmounted for partitioning? -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

6 7

PXE vmlinuz kernel doesn't recognize memory in Intel NUC?
by Locane 17 Mar '17

17 Mar '17

Hello all! I'm hoping someone can help. I'm having 2 issues; first: When trying to load a CentOS LiveCD via PXE on an Intel NUC (NUC6CAY), I get: "Not enough memory to load specified image". The image is 1.1 gigs, and there is 16 gigs of memory in the NUC. To combat this, I found this forum post <https://www.centos.org/forums/viewtopic.php?t=1398> which suggested using the "mem=" kernel parameter to manually set it. The next problem I get is one of two things: On a normal working system, I get the dots loading in PXE, then it freezes on "ready." forever On the NUC, I get a sqaushfs crash saying that the image is unusable. My questions are: Has anyone successfully used the "mem=" parameter in a PXE environment? I wasn't even aware that drivers were necessary for a kernel image to read RAM; I'd thought this was something that was just inherent. Does the CentOS PXE kernel need to be updated?

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss