Discuss

discuss@lists.centos.org

34753 discussions

mysql can't connect from localhost -strange behavior
by Tim Dunphy 30 Mar '15

30 Mar '15

Hey all, I've been having some trouble creating a mysql user that can connect to the database from localhost. It's always been a straight forward thing to do in the past, so its time for a sanity check, if you guys don't mind. Ok, so here's the actual command with actual simplified password that I'm using. It's on localhost so I don't think it's a security threat unless someone gets access to the box itself. mysql> grant all privileges on ftp.* to 'proftpd'@'localhost' identified by 'testpattern'; Query OK, 0 rows affected (0.35 sec) Here's what it looks like when you select it from the mysql database: mysql> select User,Host,Password from user where User like 'proftpd'; +---------+-----------+-------------------------------------------+ | User | Host | Password | +---------+-----------+-------------------------------------------+ | proftpd | localhost | *2EE931CA39652F1ED359A3A36961511B387E74A9 | +---------+-----------+-------------------------------------------+ 1 row in set (0.00 sec) And here's my attempt to connect with the password shown. Which is something I don't usually do, but am doing now to demonstrate what's going on: [root@ops:~] #mysql -uproftpd -ptestpattern -h localhost ERROR 1045 (28000): Access denied for user 'proftpd'@'localhost' (using password: YES) OK, so as I've said this should work! The database I'm trying to give the user access to does also exist: mysql> show databases like 'ftp'; +----------------+ | Database (ftp) | +----------------+ | ftp | +----------------+ 1 row in set (0.34 sec) I checked the error log for mysql and didn't find any clues there: [root@ops:~] #grep log /etc/my.cnf log-error=/var/log/mysqld.log [root@ops:~] #tail /var/log/mysqld.log InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 150329 13:30:34 InnoDB: Waiting for the background threads to start 150329 13:30:35 InnoDB: 5.5.42 started; log sequence number 6071094973 150329 13:30:35 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 150329 13:30:35 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 150329 13:30:35 [Note] Server socket created on IP: '0.0.0.0'. 150329 13:30:35 [Note] Event Scheduler: Loaded 0 events 150329 13:30:35 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.5.42' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi Does anybody out there have any idea why this isn't working? Thanks Tim -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B

5 6

headless VirtualBox on Centos
by Boris Epstein 30 Mar '15

30 Mar '15

Hello listmates, I am wondering if there is a set of scripts/utilities for automatically starting and running headless (no X11) VM's using VirtualBox omn a CentOS 6 server. VNC/RDP access to the VM's would be fine. Any help much appreciated. Cheers, Boris.

7 10

RAID1 bootloader configuration on CentOS 6.x and 7
by Niki Kovacs 29 Mar '15

29 Mar '15

Hi, The CentOS wiki sports a page about setting up software RAID1 on CentOS 5.x. There's a section about making both members of the RAID1 bootable by setting up GRUB on both disks. Now I wonder how this should be done on CentOS 6.x and 7. I have two sandbox machines in my office, one running a minimal CentOS 6.6, the other one with a CentOS 7 installation. Correct me if I'm wrong, but I guess the setup on CentOS 6.6 is similar to the one described on the wiki page for CentOS 5.x, something like: grub> device (hd0) /dev/sda grub> device (hd1) /dev/sdb grub> root (hd0,0) grub> setup (hd0) grub> root (hd1,0) grub> setup (hd1) grub> quit Now how would that work with the new GRUB2 under CentOS 7? Or maybe it's already installed on both disks, but how would I know that? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 1

Why is irqbalance not balancing?
by Steve Snyder 29 Mar '15

29 Mar '15

I am running irqbalance with default configuration on an Atom 330 machine. This CPU has 2 physical cores + 2 SMT (aka Hyperthreading) cores. As shown below the interrupt for the eth0 device is always on CPUs 0 and 1, with CPUs 2 and 3 left idle. But why? Maybe irqbalance prefers physical cores? My understanding, though, is that the even-numbered CPUs are the physical cores, with the odd-numbered one being the SMT cores. If this understanding is correct, it means that irqbalance is toggling between a single physical core and its SMT sibling. Any thoughts on why irqbalance is not using all 4 CPUs to distribute the eth0 interrupts? Thanks. --------------------- # cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 717 568 0 0 IO-APIC-edge timer 1: 0 2 0 0 IO-APIC-edge i8042 8: 26 33 0 0 IO-APIC-edge rtc0 9: 0 0 0 0 IO-APIC-fasteoi acpi 12: 1 3 0 0 IO-APIC-edge i8042 17: 11409 11661 0 0 IO-APIC-fasteoi ahci 18: 264 424 0 0 IO-APIC-fasteoi snd_hda_intel 20: 0 0 0 0 IO-APIC-fasteoi ohci_hcd:usb2 21: 0 0 0 0 IO-APIC-fasteoi ohci_hcd:usb3 22: 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1 24: 686292451 685980205 0 0 PCI-MSI-edge eth0

3 2

reboot causes mapping failures after update to Centos 7
by Stephen 29 Mar '15

29 Mar '15

Hi, I perform the initial update of about 200 packages then when I reboot I get three options instead of two. One is the Core 7 and the other is x86 what do those mean? Also after this the journal returns mapping errors and ext4 errors Best, Steve

1 0

Using LVM to implement RAID
by Fred Smith 29 Mar '15

29 Mar '15

Hi all! I've recently noticed that recent versions of LVM include RAID capabilities, so that one could presumably implement (e.g.) RAID-1 without having to use Linux Software RAID. Given the complexity of LBM, I'm wondering how practical and how safe this is (compared to Linux Software RAID), and also if anyone here knows more about it than I do (which isn't much), and especially if anyone here has actually used it?? I'd appreciate any feedback from y'all! :) Thanks, Fred. -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven." ------------------------------ Matthew 7:21 (niv) -----------------------------

5 7

Netflix
by Bob Hepple 28 Mar '15

28 Mar '15

Now that netflix is in Australia, I wouldn't mind giving it a burl. It's working fine on my fedora-21 lappy with chrome-40 but not on our centos-6 mythtv setup even with chrome-41. I understand the difference might be the version of NSS - fedora-21 has 3.17 while centos is stuck at 3.16. Other than that, I'm flumoxed. Anyone got netflix running on centos-6? Cheers Bob

6 8

Update on CentOS7.1
by Zatorski, Richard 28 Mar '15

28 Mar '15

Several questions about the upcoming release: 1. Will this be happening WW14? If not, is there an ETA? 2. We have our next minor release that’s dependent on CentOS7.1. Are there currently any ISOs available so we can do a risk build? We have an extensive automation farm and doing manual upgrades is not an option. Thanks, (RAZ)

1 0

CentOS-announce Digest, Vol 121, Issue 12
by centos-announce-request＠centos.org 28 Mar '15

28 Mar '15

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://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. CEBA-2015:0748 CentOS 6 amanda BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 27 Mar 2015 12:33:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2015:0748 CentOS 6 amanda BugFix Update Message-ID: <20150327123304.GA28854(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2015:0748 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0748.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6028eb7fd61883f440b98464a64e4ea9046b940fb71ca21910403d76d1ec1f9a amanda-2.6.1p2-9.el6_6.i686.rpm 2c557073b814d230142f85675e1c78ba67fec4183e992cccff4162b93c966eee amanda-client-2.6.1p2-9.el6_6.i686.rpm e5570b2e80028795ed5f268dcb34a3b5022e7465fe47c66895b68e36a8af0ef7 amanda-devel-2.6.1p2-9.el6_6.i686.rpm 8a5e03ecf50c24896af164da8b36d5bf78b04691b2f85ba6a85a04d6f22f5d47 amanda-server-2.6.1p2-9.el6_6.i686.rpm x86_64: 6028eb7fd61883f440b98464a64e4ea9046b940fb71ca21910403d76d1ec1f9a amanda-2.6.1p2-9.el6_6.i686.rpm d19eaa701f1fe55b3c0033f8f4414df1dbe8c5ae8ee32506bf5ac3e5af9003f3 amanda-2.6.1p2-9.el6_6.x86_64.rpm 86e3197db4736f91e94fdf0f08680ca033702a20f782a56749c4075c6cd48689 amanda-client-2.6.1p2-9.el6_6.x86_64.rpm e5570b2e80028795ed5f268dcb34a3b5022e7465fe47c66895b68e36a8af0ef7 amanda-devel-2.6.1p2-9.el6_6.i686.rpm 68795396230ee7a605494eee4d313c7e801cbd4f633f8c94857c876876be6323 amanda-devel-2.6.1p2-9.el6_6.x86_64.rpm f20dfaf4ef7d20e3047b6ce595bfa79322480b361579a165c49d6449e11fd9fb amanda-server-2.6.1p2-9.el6_6.x86_64.rpm Source: f90d2d6f8ae8b0b8acd9be349b67bb3f94dc898aa353a263c4306ff261de333f amanda-2.6.1p2-9.el6_6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 121, Issue 12 ************************************************

1 0

Upgrade centos 6 to 7
by Timothy Murphy 28 Mar '15

28 Mar '15

I read at <http://wiki.centos.org/TipsAndTricks/CentOSUpgradeTool> "Warning: use of this tool is currently not recommended as several system-critical packages are of a higher version number in CentOS 6.6 than they are in CentOS 7 so those do not get upgraded correctly. This renders yum and several other system tools non-functional." Is that still the position? If so, is it likely to change in the near future? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss