Re: myqsl dummy needs help

[Bill Crawford]

On Monday 16 February 2009 20:27:04 Gene Heskett wrote:

> To start mysqld at boot time you have to copy
> support-files/mysql.server to the right place for your system
>
> PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
> To do so, start the server, then issue the following commands:
> /usr/bin/mysqladmin -u root password 'new-password'
> /usr/bin/mysqladmin -u root -h coyote.coyote.den password 'new-password'
> 
> Example:
> cd /usr ; /usr/bin/mysqld_safe &
> /usr/bin/mysqladmin -u root password 'new-password'
> /usr/bin/mysqladmin -u root -h coyote.coyote.den password 'new-password'
> /usr/bin/mysqladmin -u root -h localhost password 'new-password'

Try this part?

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Tuesday 17 February 2009, Rick Stevens wrote:
>Gene Heskett wrote:
>
>(snip)
>
>> That of course is based on the "don't get mad, get even" theory. :)
>
>I don't get mad and I don't get even.  I get ahead!  ;-)

ROTFLMAO!  I like that.  Consider it stolen, Rick, thanks.
>--
>- Rick Stevens, Systems Engineer  ri...@nerd.com -
>- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
>--
>-   To err is human, to moo bovine.  -
>--



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Q:  How many IBM CPU's does it take to do a logical right shift?
A:  33.  1 to hold the bits and 32 to push the register.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Tuesday 17 February 2009, Bill Davidsen wrote:
>
>At this point, if you have VM capable hardware, I would suggest using KVM
> and a virtual machine for trial runs on stuff like this. You can make a
> copy-on-write image, and if it gets hosed delete it and start again. Great
> way to avoid the backout process.

I don't have any of the virtual stuffs enabled in my present kernel.  I guess 
its needed for compiz and such, and that eye candy just doesn't pull my 
trigger.

But, lest Craig convince everyone I'm ungrateful, far from it, I thank each 
and every one that tried to help very much.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
When the wind is great, bow before it;
when the wind is heavy, yield to it.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Craig White]

On Tue, 2009-02-17 at 19:03 -0500, Bill Davidsen wrote:
> >>
> >> So how do we fix YAMYSQLFSCKUP?
> > 
> > ignoring that the person whining is the one who deleted the directory in
> > the first place, it should have been obvious to you that you needed to
> > also restore the security contexts on /var/lib/mysql when you recreated
> > it.
> > 
> > Are you having a good time blaming everything else for your troubles?
> > 
> > There are millions of people running mysql without your issues.
> > 
> Fair number of us trying to help Gene without being snotty, too...

responding in kind to his...

Yet Another MYSQL F**kUP

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Bill Davidsen]

Rick Stevens wrote:

Gene Heskett wrote:

(snip)
That of course is based on the "don't get mad, get even" theory. :) 


I don't get mad and I don't get even.  I get ahead!  ;-)


Hopefully it is the head of a hacker, preferably displayed on a pike.

--
Bill Davidsen 
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Bill Davidsen]

Gene Heskett wrote:

On Monday 16 February 2009, Mike Wright wrote:

locate mysql | grep '/bin/' | grep install

/usr/bin/mysql_install_db
/usr/bin/mysql_secure_installation

The secure installer asks me for my root pw then tells me to just press enter
Enter current password for root (enter for none):
ERROR 2002 (HY000): Can't connect to local MySQL server through 
socket '/var/lib/mysql/mysql.sock' (2)

Enter current password for root (enter for none):

So I ctl-c it and run the install_db, which gets me back to the selinux & its 
used bull food leavings.


Do I need to touch /.autorelabel and reboot?  With 2TB of drives I can't begin 
to describe how painful that 4 hours would be.


Or go file a bug against selinux and mysql?

Frustration reigns supreme here.  If I have to reboot, it might just be to 
Kubuntu-8.10 or a beta of 9.4.


At this point, if you have VM capable hardware, I would suggest using KVM and a 
virtual machine for trial runs on stuff like this. You can make a copy-on-write 
image, and if it gets hosed delete it and start again. Great way to avoid the 
backout process.


Added that (selinux) list to To:  Daniel, your turn, it's 18:05 here, and I've 
been screwing with this since about 18:00 yesterday.  That is long enough 
IMO.  This thread has a now VERY lengthy thread on the fedora list.





--
Bill Davidsen 
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Bill Davidsen]

Craig White wrote:

On Mon, 2009-02-16 at 17:52 -0500, Gene Heskett wrote:

On Monday 16 February 2009, Craig White wrote:

On Mon, 2009-02-16 at 15:51 -0500, Gene Heskett wrote:

On Monday 16 February 2009, Anne Wilson wrote:

On Monday 16 February 2009 20:27:04 Gene Heskett wrote:

No package webmin available.
Nothing to do

I don't think I've ever had webmin from a distro package, but it installs
so easily from the website.

Anne

I found it, installed it, let it do its updates, but a scan for servers
doesn't find mysql cuz it is not running and now won't run.

I had NDI this was going to such a PIMA, but a friend has mythtv running
at his place and it does everything but fix breakfast.

If anyone has any idea how to reset this SOB to absolutely square one,
never having been run, please advise.  Deleting /var/lib/mysql didn't do
it.


you don't delete /var/lib/mysql
you delete /var/lib/mysql/*

mkdir /var/lib/mysql
chown mysql:mysql /var/lib/mysql
service mysqld start

I got to here ^^^ and selinux stuck up its hand & waved at me.
SELinux is preventing mysqld (mysqld_t) "create" to mysql.sock (var_lib_t). 


And recommended I run restorecon -v 'mysql.sock', but:
[r...@coyote rpms]# restorecon -v 'mysql.sock'
restorecon:  stat error on mysql.sock:  No such file or directory

So I go back to the top of the list above and repeat, apparently forever cuz I 
get the same thing when I restart mysqld.


Now, since mysql.sock doesn't exist, because it can't create it, therefore 
restorecon can't do anything about it, WTH do I do next?


So I located the old one in the database, touched a new one, then 
'chown mysql:mysql mysql.sock;restorecon -v mysql.sock'  No errors reported.
But, a 'service mysqld start' eventually fails.  And now the selinux count is 
plus 2 cuz I tried it twice.


So how do we fix YAMYSQLFSCKUP?


ignoring that the person whining is the one who deleted the directory in
the first place, it should have been obvious to you that you needed to
also restore the security contexts on /var/lib/mysql when you recreated
it.

Are you having a good time blaming everything else for your troubles?

There are millions of people running mysql without your issues.


Fair number of us trying to help Gene without being snotty, too...

--
Bill Davidsen 
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Bill Davidsen]

Gene Heskett wrote:

On Monday 16 February 2009, Craig White wrote:


So obviously /tmp doesn't have the right perms.  Or at least I assume (there 
is that word again) that an error 13 is permissions related.  Selinux is in 
targeted mode, enabled, and it isn't fussing.


/tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0   tmp
but nearly everything in it is root:root except the amanda and amanda-debug 
directories.  So I just changed tmp to drwxrwxrwx  But that also didn't change

anything. Or did it, now the log shows this when I restart mysqld:


chmod 1777 /tmp

--
Bill Davidsen 
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Rick Stevens]

Gene Heskett wrote:

(snip)
That of course is based on the "don't get mad, get even" theory. :) 


I don't get mad and I don't get even.  I get ahead!  ;-)
--
- Rick Stevens, Systems Engineer  ri...@nerd.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
-   To err is human, to moo bovine.  -
--

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Tuesday 17 February 2009, Gordon Messmer wrote:
>Gene Heskett wrote:
>> On Tuesday 17 February 2009, Gordon Messmer wrote:
>>> It's not quite that bad.  You can reset by simply removing the contents
>>> of /var/lib/mysql and starting the mysql service.  If you have a
>>> database to save, you can use --skip-grant-tables and resetting any
>>> passwords that you require.
>>
>> I am glad that it worked for you.  I did that 4 times, and each time the
>> restart was foiled by selinux.  Only a total, complete nuke job, cleaning
>> up all the leftovers with rm, succeeded in making a fresh install work.
>
>That is very likely because you removed /var/lib/mysql, and did not
>"restorecon /var/lib/mysql" when you re-created it.
>
>I'm also still curious how your /tmp got its permissions restricted.
>Did you do that intentionally?

Yes, the idea was to make it warn me if somehow, somebody got in and was 
trying to play funnies..  Its back to normal now, in 2 years of using dd-wrt 
as my router, no one I did not give the ssh passwords to has managed that 
feat, but they keep banging on it none-the-less.  The one thing that dd-wrt 
is missing is a portsentry or denyhosts setup.  If everyone ran that, these 
shitheads would have to either find another way, or find another means of 
buying their peanut butter.  Hmmm, could we sell them some of the recalled 
stuff?  That of course is based on the "don't get mad, get even" theory. :) 

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Occam's eraser:
The philosophical principle that even the simplest
solution is bound to have something wrong with it.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gordon Messmer]

Gene Heskett wrote:

On Tuesday 17 February 2009, Gordon Messmer wrote:

It's not quite that bad.  You can reset by simply removing the contents
of /var/lib/mysql and starting the mysql service.  If you have a
database to save, you can use --skip-grant-tables and resetting any
passwords that you require.


I am glad that it worked for you.  I did that 4 times, and each time the 
restart was foiled by selinux.  Only a total, complete nuke job, cleaning up 
all the leftovers with rm, succeeded in making a fresh install work.


That is very likely because you removed /var/lib/mysql, and did not 
"restorecon /var/lib/mysql" when you re-created it.


I'm also still curious how your /tmp got its permissions restricted. 
Did you do that intentionally?


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Tuesday 17 February 2009, Gordon Messmer wrote:
>Gene Heskett wrote:
>> The bottom line would appear to be, if you don't have any databases to
>> save, then yum remove *mysql*, updatedb locate and nuke ANYTHING left
>> behind, then re-install.  If you have a database to save, well, rotsa
>> ruck.  Hope you have backups.
>
>It's not quite that bad.  You can reset by simply removing the contents
>of /var/lib/mysql and starting the mysql service.  If you have a
>database to save, you can use --skip-grant-tables and resetting any
>passwords that you require.

I am glad that it worked for you.  I did that 4 times, and each time the 
restart was foiled by selinux.  Only a total, complete nuke job, cleaning up 
all the leftovers with rm, succeeded in making a fresh install work.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Most people can't understand how others can blow their noses differently
than they do.
-- Turgenev

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gordon Messmer]

Gene Heskett wrote:
The bottom line would appear to be, if you don't have any databases to save, 
then yum remove *mysql*, updatedb locate and nuke ANYTHING left behind, then 
re-install.  If you have a database to save, well, rotsa ruck.  Hope you have 
backups.


It's not quite that bad.  You can reset by simply removing the contents 
of /var/lib/mysql and starting the mysql service.  If you have a 
database to save, you can use --skip-grant-tables and resetting any 
passwords that you require.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Craig White wrote:
>On Mon, 2009-02-16 at 15:38 -0500, Gene Heskett wrote:
>> webmin not available according to yum.
>>
>> Ok, so I rip it out again, only this time I run a script that searches the
>> locate database for mysql and deletes all the leftovers before I
>> reinstall.
>>
>> Would that help?  Something is obviously completely fubar.
>
>
>turned out that I had to start mysqld before running...
>
>mysqladmin - u root password 'new-password'
>
>after that, it was no problem connecting
>
># mysqladmin -u root password 'test'
>[r...@lin-workstation httpd]# mysql -p
>Enter password:
>Welcome to the MySQL monitor.  Commands end with ; or \g.
>Your MySQL connection id is 5
>Server version: 5.0.67 Source distribution
>
>Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
>
>mysql> \q
>Bye
>
>webmin (rpm and/or tarball) is available at http://www.webmin.com
>
>Craig

This time I not only had yum remove anything mysql related, I then ran thru 
the output of a fresh updatedb run, and nuked everything I could find.

Then I had yum install about 50 mysql related packages.  Now it will at least 
start mysqld.
If the root pw is empty I should be able to run something, so I'll start with 
mysqladmin in the gui.  And using the gui, and this machines FQDN, I am 
apparently in.

The bottom line would appear to be, if you don't have any databases to save, 
then yum remove *mysql*, updatedb locate and nuke ANYTHING left behind, then 
re-install.  If you have a database to save, well, rotsa ruck.  Hope you have 
backups.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Been Transferred Lately?

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Gordon Messmer wrote:
>Gene Heskett wrote:
>> See other posts that describe what I did to recover.  Thanks.
>
>I read your other posts, but didn't see that you'd recovered.  Things
>are working now?

Yes, I had yum remove it all, then ran updatedb so I could locate the ghosts 
and nuke them too.  Then I had yum reinstall the whole maryann.  And it 
appears to be working, I can now get a mysql shell just fine.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Our houseplants have a good sense of humous.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gordon Messmer]

Gene Heskett wrote:


See other posts that describe what I did to recover.  Thanks.


I read your other posts, but didn't see that you'd recovered.  Things 
are working now?


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Gordon Messmer wrote:
>Gene Heskett wrote:
>...
>
>> With all due respect Craig, what the hell use is it then when ALL the
>> documentation is wrong?
>
>...
>
>> /tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0  
>> tmp
>
>Well, that's totally wrong.  I'm curious about how permissions on /tmp
>got broken.  That's almost certainly what caused the problem.  My guess
>is that the first time mysql started, it began the initialization
>process for the databases in /var/lib/mysql, but failed partially
>through because of the problem with /tmp.  After that, MySQL will not
>continue trying to initialize, so you've got a bad database.
>
>To correct the problem, you need to make sure that /tmp is in good
>order.  It should look like this:
>
># ls -ldZ /tmp
>drwxrwxrwt  root root system_u:object_r:tmp_t:s0   /tmp/
>
>If it doesn't, then "chmod 1777 /tmp" and "chown root:root /tmp"
>
>Next, delete the contents of /var/lib/mysql.  That directory must also
>exist and must have the correct permissions.  It should look like this:
>
>$ ls -ldZ /va/lib/mysql
>drwxr-xr-x  mysql mysql system_u:object_r:mysqld_db_t  /var/lib/mysql
>
>Once those two directories are fixed, you *should* be able to start
>msyql, and use the cli "mysql" and "mysqladmin" tools without a
>password.  If not, check for new SELinux problems.
>
>And with all due respect, the documentation isn't wrong just because it
>doesn't cover recovery from the specific error condition on your host.

See other posts that describe what I did to recover.  Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"Die?  I should say not, dear fellow.  No Barrymore would allow such a
conventional thing to happen to him."
-- John Barrymore's dying words

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Craig White]

On Mon, 2009-02-16 at 16:16 -0800, Rick Stevens wrote:

> Name calling won't solve anyone's problems, gang.  Let's try to keep
> this a bit more professional, shall we?
> 
> Now, to address the issue, /var/lib/mysql/mysql.sock is a FIFO (actually
> a named pipe), not an actual file and is created when mysqld starts up 
> and deleted when mysql shuts down.  When mysqld is running, it should
> appear as follows:
> 
> # ls -lZ mysql.sock
> srwxrwxrwx  mysql mysql unconfined_u:object_r:mysqld_var_run_t:s0 mysql.sock
> 
> If your /var/lib/mysql/mysql.sock is a regular file (which it would be
> if you used "touch" to create it), first delete the file and run
> "restorecon -v /var/lib/mysql" as root.  Then see if mysql will start
> up.  It may not, because if you "rm -rf /var/lib/mysql", then you also
> destroyed mysql's users, hosts and permissions database which it needs
> to manage things.  You should be able to recover them by running the
> following commands:
> 
>   # mysql# mysql# mysql  
> Or "yum remove mysql*" and reinstall the packages that get removed.

entirely unnecessary Rick...

[r...@lin-workstation httpd]# rm -fr /var/lib/mysql/*  
You have new mail in /var/spool/mail/root  
[r...@lin-workstation httpd]# service mysqld start 
Initializing MySQL database:  Installing MySQL system tables...
090216 17:52:30 [Warning] option 'max_join_size': unsigned value
18446744073709551615 adjusted to 4294967295
090216 17:52:30 [Warning] option 'max_join_size': unsigned value
18446744073709551615 adjusted to 4294967295
OK  

Filling help
tables...   
   
090216 17:52:31 [Warning] option 'max_join_size': unsigned value
18446744073709551615 adjusted to 4294967295
090216 17:52:31 [Warning] option 'max_join_size': unsigned value
18446744073709551615 adjusted to 4294967295
OK  


To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h lin-workstation.azapple.com password
'new-password'

Alternatively you can run:
/usr/bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:
cd /usr ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com
   [  OK  ]
Starting MySQL:[  OK  ]
[r...@lin-workstation httpd]# mysqladmin -u root password 'test'
[r...@lin-workstation httpd]# mysql -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.0.67 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> \q
Bye

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Rick Stevens]

Gene Heskett wrote:

On Monday 16 February 2009, Craig White wrote:

On Mon, 2009-02-16 at 17:52 -0500, Gene Heskett wrote:

On Monday 16 February 2009, Craig White wrote:

On Mon, 2009-02-16 at 15:51 -0500, Gene Heskett wrote:

On Monday 16 February 2009, Anne Wilson wrote:

On Monday 16 February 2009 20:27:04 Gene Heskett wrote:

No package webmin available.
Nothing to do

I don't think I've ever had webmin from a distro package, but it
installs so easily from the website.

Anne

I found it, installed it, let it do its updates, but a scan for servers
doesn't find mysql cuz it is not running and now won't run.

I had NDI this was going to such a PIMA, but a friend has mythtv
running at his place and it does everything but fix breakfast.

If anyone has any idea how to reset this SOB to absolutely square one,
never having been run, please advise.  Deleting /var/lib/mysql didn't
do it.


you don't delete /var/lib/mysql
you delete /var/lib/mysql/*

mkdir /var/lib/mysql
chown mysql:mysql /var/lib/mysql
service mysqld start

I got to here ^^^ and selinux stuck up its hand & waved at me.
SELinux is preventing mysqld (mysqld_t) "create" to mysql.sock
(var_lib_t).

And recommended I run restorecon -v 'mysql.sock', but:
[r...@coyote rpms]# restorecon -v 'mysql.sock'
restorecon:  stat error on mysql.sock:  No such file or directory

So I go back to the top of the list above and repeat, apparently forever
cuz I get the same thing when I restart mysqld.

Now, since mysql.sock doesn't exist, because it can't create it, therefore
restorecon can't do anything about it, WTH do I do next?

So I located the old one in the database, touched a new one, then
'chown mysql:mysql mysql.sock;restorecon -v mysql.sock'  No errors
reported. But, a 'service mysqld start' eventually fails.  And now the
selinux count is plus 2 cuz I tried it twice.

So how do we fix YAMYSQLFSCKUP?


ignoring that the person whining is the one who deleted the directory in
the first place, it should have been obvious to you that you needed to
also restore the security contexts on /var/lib/mysql when you recreated
it.

Are you having a good time blaming everything else for your troubles?

There are millions of people running mysql without your issues.

Craig


With all due respect Craig, it must have done it once, over a year ago, but I 
haven't been using it for anything.  I had yum rpm -e the whole thing which 
took a few other things along with it, then reinstalled the whole maryann.


No change.  If, when it was installed originally, it spit out any such errors, 
I don't after a year, recall them, and selinux has been updated a dozen times 
since the install and my re-enabling selinux.  So lets be realistic and see 
just what the hell we can do about selinux killing mysql instead of your 
usual shoot the messenger attitude.


Name calling won't solve anyone's problems, gang.  Let's try to keep
this a bit more professional, shall we?

Now, to address the issue, /var/lib/mysql/mysql.sock is a FIFO (actually
a named pipe), not an actual file and is created when mysqld starts up 
and deleted when mysql shuts down.  When mysqld is running, it should

appear as follows:

# ls -lZ mysql.sock
srwxrwxrwx  mysql mysql unconfined_u:object_r:mysqld_var_run_t:s0 mysql.sock

If your /var/lib/mysql/mysql.sock is a regular file (which it would be
if you used "touch" to create it), first delete the file and run
"restorecon -v /var/lib/mysql" as root.  Then see if mysql will start
up.  It may not, because if you "rm -rf /var/lib/mysql", then you also
destroyed mysql's users, hosts and permissions database which it needs
to manage things.  You should be able to recover them by running the
following commands:

# mysql https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Craig White wrote:
>On Mon, 2009-02-16 at 17:52 -0500, Gene Heskett wrote:
>> On Monday 16 February 2009, Craig White wrote:
>> >On Mon, 2009-02-16 at 15:51 -0500, Gene Heskett wrote:
>> >> On Monday 16 February 2009, Anne Wilson wrote:
>> >> >On Monday 16 February 2009 20:27:04 Gene Heskett wrote:
>> >> >> No package webmin available.
>> >> >> Nothing to do
>> >> >
>> >> >I don't think I've ever had webmin from a distro package, but it
>> >> > installs so easily from the website.
>> >> >
>> >> >Anne
>> >>
>> >> I found it, installed it, let it do its updates, but a scan for servers
>> >> doesn't find mysql cuz it is not running and now won't run.
>> >>
>> >> I had NDI this was going to such a PIMA, but a friend has mythtv
>> >> running at his place and it does everything but fix breakfast.
>> >>
>> >> If anyone has any idea how to reset this SOB to absolutely square one,
>> >> never having been run, please advise.  Deleting /var/lib/mysql didn't
>> >> do it.
>> >
>> >
>> >you don't delete /var/lib/mysql
>> >you delete /var/lib/mysql/*
>> >
>> >mkdir /var/lib/mysql
>> >chown mysql:mysql /var/lib/mysql
>> >service mysqld start
>>
>> I got to here ^^^ and selinux stuck up its hand & waved at me.
>> SELinux is preventing mysqld (mysqld_t) "create" to mysql.sock
>> (var_lib_t).
>>
>> And recommended I run restorecon -v 'mysql.sock', but:
>> [r...@coyote rpms]# restorecon -v 'mysql.sock'
>> restorecon:  stat error on mysql.sock:  No such file or directory
>>
>> So I go back to the top of the list above and repeat, apparently forever
>> cuz I get the same thing when I restart mysqld.
>>
>> Now, since mysql.sock doesn't exist, because it can't create it, therefore
>> restorecon can't do anything about it, WTH do I do next?
>>
>> So I located the old one in the database, touched a new one, then
>> 'chown mysql:mysql mysql.sock;restorecon -v mysql.sock'  No errors
>> reported. But, a 'service mysqld start' eventually fails.  And now the
>> selinux count is plus 2 cuz I tried it twice.
>>
>> So how do we fix YAMYSQLFSCKUP?
>
>
>ignoring that the person whining is the one who deleted the directory in
>the first place, it should have been obvious to you that you needed to
>also restore the security contexts on /var/lib/mysql when you recreated
>it.
>
>Are you having a good time blaming everything else for your troubles?
>
>There are millions of people running mysql without your issues.
>
>Craig

With all due respect Craig, it must have done it once, over a year ago, but I 
haven't been using it for anything.  I had yum rpm -e the whole thing which 
took a few other things along with it, then reinstalled the whole maryann.

No change.  If, when it was installed originally, it spit out any such errors, 
I don't after a year, recall them, and selinux has been updated a dozen times 
since the install and my re-enabling selinux.  So lets be realistic and see 
just what the hell we can do about selinux killing mysql instead of your 
usual shoot the messenger attitude.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"Open the pod bay doors, HAL."
-- Dave Bowman, 2001

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Craig White]

On Mon, 2009-02-16 at 17:52 -0500, Gene Heskett wrote:
> On Monday 16 February 2009, Craig White wrote:
> >On Mon, 2009-02-16 at 15:51 -0500, Gene Heskett wrote:
> >> On Monday 16 February 2009, Anne Wilson wrote:
> >> >On Monday 16 February 2009 20:27:04 Gene Heskett wrote:
> >> >> No package webmin available.
> >> >> Nothing to do
> >> >
> >> >I don't think I've ever had webmin from a distro package, but it installs
> >> > so easily from the website.
> >> >
> >> >Anne
> >>
> >> I found it, installed it, let it do its updates, but a scan for servers
> >> doesn't find mysql cuz it is not running and now won't run.
> >>
> >> I had NDI this was going to such a PIMA, but a friend has mythtv running
> >> at his place and it does everything but fix breakfast.
> >>
> >> If anyone has any idea how to reset this SOB to absolutely square one,
> >> never having been run, please advise.  Deleting /var/lib/mysql didn't do
> >> it.
> >
> >
> >you don't delete /var/lib/mysql
> >you delete /var/lib/mysql/*
> >
> >mkdir /var/lib/mysql
> >chown mysql:mysql /var/lib/mysql
> >service mysqld start
> 
> I got to here ^^^ and selinux stuck up its hand & waved at me.
> SELinux is preventing mysqld (mysqld_t) "create" to mysql.sock (var_lib_t). 
> 
> And recommended I run restorecon -v 'mysql.sock', but:
> [r...@coyote rpms]# restorecon -v 'mysql.sock'
> restorecon:  stat error on mysql.sock:  No such file or directory
> 
> So I go back to the top of the list above and repeat, apparently forever cuz 
> I 
> get the same thing when I restart mysqld.
> 
> Now, since mysql.sock doesn't exist, because it can't create it, therefore 
> restorecon can't do anything about it, WTH do I do next?
> 
> So I located the old one in the database, touched a new one, then 
> 'chown mysql:mysql mysql.sock;restorecon -v mysql.sock'  No errors reported.
> But, a 'service mysqld start' eventually fails.  And now the selinux count is 
> plus 2 cuz I tried it twice.
> 
> So how do we fix YAMYSQLFSCKUP?

ignoring that the person whining is the one who deleted the directory in
the first place, it should have been obvious to you that you needed to
also restore the security contexts on /var/lib/mysql when you recreated
it.

Are you having a good time blaming everything else for your troubles?

There are millions of people running mysql without your issues.

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Mike Wright wrote:
>locate mysql | grep '/bin/' | grep install
/usr/bin/mysql_install_db
/usr/bin/mysql_secure_installation

The secure installer asks me for my root pw then tells me to just press enter
Enter current password for root (enter for none):
ERROR 2002 (HY000): Can't connect to local MySQL server through 
socket '/var/lib/mysql/mysql.sock' (2)
Enter current password for root (enter for none):

So I ctl-c it and run the install_db, which gets me back to the selinux & its 
used bull food leavings.

Do I need to touch /.autorelabel and reboot?  With 2TB of drives I can't begin 
to describe how painful that 4 hours would be.

Or go file a bug against selinux and mysql?

Frustration reigns supreme here.  If I have to reboot, it might just be to 
Kubuntu-8.10 or a beta of 9.4.

Added that (selinux) list to To:  Daniel, your turn, it's 18:05 here, and I've 
been screwing with this since about 18:00 yesterday.  That is long enough 
IMO.  This thread has a now VERY lengthy thread on the fedora list.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
There appears to be irrefutable evidence that the mere fact of overcrowding
induces violence.
-- Harvey Wheeler

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Craig White wrote:
>On Mon, 2009-02-16 at 15:51 -0500, Gene Heskett wrote:
>> On Monday 16 February 2009, Anne Wilson wrote:
>> >On Monday 16 February 2009 20:27:04 Gene Heskett wrote:
>> >> No package webmin available.
>> >> Nothing to do
>> >
>> >I don't think I've ever had webmin from a distro package, but it installs
>> > so easily from the website.
>> >
>> >Anne
>>
>> I found it, installed it, let it do its updates, but a scan for servers
>> doesn't find mysql cuz it is not running and now won't run.
>>
>> I had NDI this was going to such a PIMA, but a friend has mythtv running
>> at his place and it does everything but fix breakfast.
>>
>> If anyone has any idea how to reset this SOB to absolutely square one,
>> never having been run, please advise.  Deleting /var/lib/mysql didn't do
>> it.
>
>
>you don't delete /var/lib/mysql
>you delete /var/lib/mysql/*
>
>mkdir /var/lib/mysql
>chown mysql:mysql /var/lib/mysql
>service mysqld start

I got to here ^^^ and selinux stuck up its hand & waved at me.
SELinux is preventing mysqld (mysqld_t) "create" to mysql.sock (var_lib_t). 

And recommended I run restorecon -v 'mysql.sock', but:
[r...@coyote rpms]# restorecon -v 'mysql.sock'
restorecon:  stat error on mysql.sock:  No such file or directory

So I go back to the top of the list above and repeat, apparently forever cuz I 
get the same thing when I restart mysqld.

Now, since mysql.sock doesn't exist, because it can't create it, therefore 
restorecon can't do anything about it, WTH do I do next?

So I located the old one in the database, touched a new one, then 
'chown mysql:mysql mysql.sock;restorecon -v mysql.sock'  No errors reported.
But, a 'service mysqld start' eventually fails.  And now the selinux count is 
plus 2 cuz I tried it twice.

So how do we fix YAMYSQLFSCKUP?

Thanks Craig
 
>mysqladmin -u root password 'new-password'
>   ^don't change   ^change
>
>done
>
>Craig



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"In the face of entropy and nothingness, you kind of have to pretend it's not
there if you want to keep writing good code."  -- Karl Lehenbauer

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Craig White]

On Mon, 2009-02-16 at 15:38 -0500, Gene Heskett wrote:

> webmin not available according to yum.
> 
> Ok, so I rip it out again, only this time I run a script that searches the 
> locate database for mysql and deletes all the leftovers before I reinstall.
> 
> Would that help?  Something is obviously completely fubar.

turned out that I had to start mysqld before running...

mysqladmin - u root password 'new-password'

after that, it was no problem connecting

# mysqladmin -u root password 'test'
[r...@lin-workstation httpd]# mysql -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5
Server version: 5.0.67 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> \q
Bye

webmin (rpm and/or tarball) is available at http://www.webmin.com

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gordon Messmer]

Gene Heskett wrote:
...
With all due respect Craig, what the hell use is it then when ALL the 
documentation is wrong?

...

/tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0   tmp


Well, that's totally wrong.  I'm curious about how permissions on /tmp 
got broken.  That's almost certainly what caused the problem.  My guess 
is that the first time mysql started, it began the initialization 
process for the databases in /var/lib/mysql, but failed partially 
through because of the problem with /tmp.  After that, MySQL will not 
continue trying to initialize, so you've got a bad database.


To correct the problem, you need to make sure that /tmp is in good 
order.  It should look like this:


# ls -ldZ /tmp
drwxrwxrwt  root root system_u:object_r:tmp_t:s0   /tmp/

If it doesn't, then "chmod 1777 /tmp" and "chown root:root /tmp"

Next, delete the contents of /var/lib/mysql.  That directory must also 
exist and must have the correct permissions.  It should look like this:


$ ls -ldZ /va/lib/mysql
drwxr-xr-x  mysql mysql system_u:object_r:mysqld_db_t  /var/lib/mysql

Once those two directories are fixed, you *should* be able to start 
msyql, and use the cli "mysql" and "mysqladmin" tools without a 
password.  If not, check for new SELinux problems.


And with all due respect, the documentation isn't wrong just because it 
doesn't cover recovery from the specific error condition on your host.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Mike Wright]

Gene Heskett wrote:

Ok, so I rip it out again, only this time I run a script that searches the 
locate database for mysql and deletes all the leftovers before I reinstall.


Would that help?  Something is obviously completely fubar.


I don't think you have to resort to that.  MySql stores its settings in 
one of its own databases, usually /var/lib/mysql/mysql.


If you really just want to start from scratch and you are sure there are 
no databases you need inside the directory /var/lib/myslq you could 
delete everything in there: "rm -rf /var/lib/mysql/*".


Once that is empty take a look for mysql installers.  e.g.

"locate mysql | grep '/bin/' | grep install"

Execute whichever one seems most promising and you should end up with a 
 brand new out-of-the-box wide open mysql database setup.


Start the mysqld server.

Run mysqladmin and set the root password.

Should be good to go from there.

:m)

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Craig White]

On Mon, 2009-02-16 at 15:51 -0500, Gene Heskett wrote:
> On Monday 16 February 2009, Anne Wilson wrote:
> >On Monday 16 February 2009 20:27:04 Gene Heskett wrote:
> >> No package webmin available.
> >> Nothing to do
> >
> >I don't think I've ever had webmin from a distro package, but it installs so
> >easily from the website.
> >
> >Anne
> 
> I found it, installed it, let it do its updates, but a scan for servers 
> doesn't find mysql cuz it is not running and now won't run.
> 
> I had NDI this was going to such a PIMA, but a friend has mythtv running at 
> his place and it does everything but fix breakfast.
> 
> If anyone has any idea how to reset this SOB to absolutely square one, never 
> having been run, please advise.  Deleting /var/lib/mysql didn't do it.

you don't delete /var/lib/mysql
you delete /var/lib/mysql/*

mkdir /var/lib/mysql
chown mysql:mysql /var/lib/mysql
service mysqld start
mysqladmin -u root password 'new-password'
   ^don't change   ^change

done

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Anne Wilson wrote:
>On Monday 16 February 2009 20:27:04 Gene Heskett wrote:
>> No package webmin available.
>> Nothing to do
>
>I don't think I've ever had webmin from a distro package, but it installs so
>easily from the website.
>
>Anne

I found it, installed it, let it do its updates, but a scan for servers 
doesn't find mysql cuz it is not running and now won't run.

I had NDI this was going to such a PIMA, but a friend has mythtv running at 
his place and it does everything but fix breakfast.

If anyone has any idea how to reset this SOB to absolutely square one, never 
having been run, please advise.  Deleting /var/lib/mysql didn't do it.

Thanks Ann.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The appreciation of the average visual graphisticator alone is worth
the whole suaveness and decadence which abounds!!

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Robert L Cochran wrote:
>The documentation on the MySQL website that I pointed to, and that
>detailed in Paul DuBois' book, absolutely works for all Fedora
>implementations of MySQL. The Fedora distro packagers do not do anything
>"Fedora different" from a standard MySQL installation.
>
>I know from having studied the spec files in Fedora source packages for
>mysql-server and from having to clean up my own messes now and then that
>this is so.
>
>What is important...is to very carefully read and research the
>documentation provided first, before ever doing anything.
>
>Bob
>
>Craig White wrote:
>> On Mon, 2009-02-16 at 14:06 -0500, Gene Heskett wrote:
>>> On Monday 16 February 2009, Craig White wrote:
 
 I think original setup for mysql is for root user via local socket and
 not via localhost so there actually isn't an account for r...@localhost
 thus attempting to connect via tcp/ip as root is doomed to fail out of
 the box.

 Craig
>>>
>>> With all due respect Craig, what the hell use is it then when ALL the
>>> documentation is wrong?
>>>
>>> Now, I just had the bright idea of looking at the mysqld.log after
>>> ripping it all out and putting even more of it back in, and see this:
>>>
>>> [r...@coyote etc]# cat /var/log/mysqld.log
>>> 090216 13:30:36  mysqld ended
>>>
>>> 090216 13:30:45  mysqld started
>>> /usr/libexec/mysqld: Can't create/write to file '/tmp/ibnoIZas' (Errcode:
>>> 13) 090216 13:30:45  InnoDB: Error: unable to create temporary file;
>>> errno: 13 090216 13:30:45 [Note] /usr/libexec/mysqld: ready for
>>> connections. Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock' 
>>> port: 3306  Source distribution
>>>
>>> So obviously /tmp doesn't have the right perms.  Or at least I assume
>>> (there is that word again) that an error 13 is permissions related. 
>>> Selinux is in targeted mode, enabled, and it isn't fussing.
>>>
>>> /tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0  
>>> tmp but nearly everything in it is root:root except the amanda and
>>> amanda-debug directories.  So I just changed tmp to drwxrwxrwx  But that
>>> also didn't change anything. Or did it, now the log shows this when I
>>> restart mysqld:
>>>
>>> 090216 13:51:44  mysqld started
>>> InnoDB: The first specified data file ./ibdata1 did not exist:
>>> InnoDB: a new database to be created!
>>> 090216 13:51:44  InnoDB: Setting file ./ibdata1 size to 10 MB
>>> InnoDB: Database physically writes the file full: wait...
>>> 090216 13:51:45  InnoDB: Log file ./ib_logfile0 did not exist: new to be
>>> created InnoDB: Setting log file ./ib_logfile0 size to 5 MB
>>> InnoDB: Database physically writes the file full: wait...
>>> 090216 13:51:45  InnoDB: Log file ./ib_logfile1 did not exist: new to be
>>> created InnoDB: Setting log file ./ib_logfile1 size to 5 MB
>>> InnoDB: Database physically writes the file full: wait...
>>> InnoDB: Doublewrite buffer not found: creating new
>>> InnoDB: Doublewrite buffer created
>>> InnoDB: Creating foreign key constraint system tables
>>> InnoDB: Foreign key constraint system tables created
>>> 090216 13:51:46  InnoDB: Started; log sequence number 0 0
>>> 090216 13:51:46 [Note] /usr/libexec/mysqld: ready for connections.
>>> Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306 
>>> Source distribution
>>>
>>> Which says one problem seems to be sorted, at the expense of a huge
>>> security hole in /tmp as anyone can do anything there now.
>>>
>>> Ok, so now try a login again:
>>> [r...@coyote /]# mysql -u root -p
>>> Enter password:
>>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>>> password: YES) [r...@coyote /]# mysql -u root -p
>>> Enter password:
>>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>>> password: NO) [r...@coyote /]#
>>>
>>> Seems like this is where I started, isn't it?
>>>
>>> Now that the tmp perms is sorted, I suppose I need to go back and do all
>>> that other stuff again...
>>>
>>> Which I just did, and didn't change a thing.  WTF?
>>> Thanks Craig
>>
>> 
>> after initial installation but before you actually ever start mysqld
>> service...
>>
>> mysqladmin - u root password 'new-password'
>>
>> *might* work after the mysqld service has already been started but if
>> you look at the script involved in /etc/init.d/mysqld, much will happen
>> the first time you start it.
>>
>> You can always stop mysqld service, empty contents of /var/lib/mysql and
>> start the service if you don't care about any of the setup.
>>
>> As for the documentation...it's not wrong but the documentation doesn't
>> account for what the various distributions will do with their
>> initialization scripts.
>>
>> If it's all too much for you, install webmin and use that to
>> create/maintain user accounts in mysql.
>>
>> Craig

webmin not available according to yum.

Ok, so I rip it out again, only this time I run a script that searches the 
locate datab

Re: myqsl dummy needs help

[Anne Wilson]

On Monday 16 February 2009 20:27:04 Gene Heskett wrote:
> No package webmin available.
> Nothing to do

I don't think I've ever had webmin from a distro package, but it installs so 
easily from the website.

Anne


signature.asc
Description: This is a digitally signed message part.
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Robert L Cochran]

The documentation on the MySQL website that I pointed to, and that
detailed in Paul DuBois' book, absolutely works for all Fedora
implementations of MySQL. The Fedora distro packagers do not do anything
"Fedora different" from a standard MySQL installation.

I know from having studied the spec files in Fedora source packages for
mysql-server and from having to clean up my own messes now and then that
this is so.

What is important...is to very carefully read and research the
documentation provided first, before ever doing anything.

Bob



Craig White wrote:
> On Mon, 2009-02-16 at 14:06 -0500, Gene Heskett wrote:
>   
>> On Monday 16 February 2009, Craig White wrote:
>> 
>
>   
>>> 
>>> I think original setup for mysql is for root user via local socket and
>>> not via localhost so there actually isn't an account for r...@localhost
>>> thus attempting to connect via tcp/ip as root is doomed to fail out of
>>> the box.
>>>
>>> Craig
>>>   
>> With all due respect Craig, what the hell use is it then when ALL the 
>> documentation is wrong?
>>
>> Now, I just had the bright idea of looking at the mysqld.log after ripping 
>> it all out and putting even more of it back in, and see this:
>>
>> [r...@coyote etc]# cat /var/log/mysqld.log
>> 090216 13:30:36  mysqld ended
>>
>> 090216 13:30:45  mysqld started
>> /usr/libexec/mysqld: Can't create/write to file '/tmp/ibnoIZas' (Errcode: 13)
>> 090216 13:30:45  InnoDB: Error: unable to create temporary file; errno: 13
>> 090216 13:30:45 [Note] /usr/libexec/mysqld: ready for connections.
>> Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source 
>> distribution
>>
>> So obviously /tmp doesn't have the right perms.  Or at least I assume (there 
>> is that word again) that an error 13 is permissions related.  Selinux is in 
>> targeted mode, enabled, and it isn't fussing.
>>
>> /tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0   tmp
>> but nearly everything in it is root:root except the amanda and amanda-debug 
>> directories.  So I just changed tmp to drwxrwxrwx  But that also didn't 
>> change
>> anything. Or did it, now the log shows this when I restart mysqld:
>>
>> 090216 13:51:44  mysqld started
>> InnoDB: The first specified data file ./ibdata1 did not exist:
>> InnoDB: a new database to be created!
>> 090216 13:51:44  InnoDB: Setting file ./ibdata1 size to 10 MB
>> InnoDB: Database physically writes the file full: wait...
>> 090216 13:51:45  InnoDB: Log file ./ib_logfile0 did not exist: new to be 
>> created
>> InnoDB: Setting log file ./ib_logfile0 size to 5 MB
>> InnoDB: Database physically writes the file full: wait...
>> 090216 13:51:45  InnoDB: Log file ./ib_logfile1 did not exist: new to be 
>> created
>> InnoDB: Setting log file ./ib_logfile1 size to 5 MB
>> InnoDB: Database physically writes the file full: wait...
>> InnoDB: Doublewrite buffer not found: creating new
>> InnoDB: Doublewrite buffer created
>> InnoDB: Creating foreign key constraint system tables
>> InnoDB: Foreign key constraint system tables created
>> 090216 13:51:46  InnoDB: Started; log sequence number 0 0
>> 090216 13:51:46 [Note] /usr/libexec/mysqld: ready for connections.
>> Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source 
>> distribution
>>
>> Which says one problem seems to be sorted, at the expense of a huge security 
>> hole in /tmp as anyone can do anything there now.
>>
>> Ok, so now try a login again:
>> [r...@coyote /]# mysql -u root -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
>> password: YES)
>> [r...@coyote /]# mysql -u root -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
>> password: NO)
>> [r...@coyote /]#
>>
>> Seems like this is where I started, isn't it?
>>
>> Now that the tmp perms is sorted, I suppose I need to go back and do all 
>> that 
>> other stuff again...
>>
>> Which I just did, and didn't change a thing.  WTF?
>> Thanks Craig
>> 
> 
> after initial installation but before you actually ever start mysqld
> service...
>
> mysqladmin - u root password 'new-password'
>
> *might* work after the mysqld service has already been started but if
> you look at the script involved in /etc/init.d/mysqld, much will happen
> the first time you start it.
>
> You can always stop mysqld service, empty contents of /var/lib/mysql and
> start the service if you don't care about any of the setup.
>
> As for the documentation...it's not wrong but the documentation doesn't
> account for what the various distributions will do with their
> initialization scripts.
>
> If it's all too much for you, install webmin and use that to
> create/maintain user accounts in mysql.
>
> Craig
>
>   

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Craig White wrote:
>On Mon, 2009-02-16 at 14:06 -0500, Gene Heskett wrote:
>> On Monday 16 February 2009, Craig White wrote:
>> >
>> >I think original setup for mysql is for root user via local socket and
>> >not via localhost so there actually isn't an account for r...@localhost
>> >thus attempting to connect via tcp/ip as root is doomed to fail out of
>> >the box.
>> >
>> >Craig
>>
>> With all due respect Craig, what the hell use is it then when ALL the
>> documentation is wrong?
>>
>> Now, I just had the bright idea of looking at the mysqld.log after ripping
>> it all out and putting even more of it back in, and see this:
>>
>> [r...@coyote etc]# cat /var/log/mysqld.log
>> 090216 13:30:36  mysqld ended
>>
>> 090216 13:30:45  mysqld started
>> /usr/libexec/mysqld: Can't create/write to file '/tmp/ibnoIZas' (Errcode:
>> 13) 090216 13:30:45  InnoDB: Error: unable to create temporary file;
>> errno: 13 090216 13:30:45 [Note] /usr/libexec/mysqld: ready for
>> connections. Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port:
>> 3306  Source distribution
>>
>> So obviously /tmp doesn't have the right perms.  Or at least I assume
>> (there is that word again) that an error 13 is permissions related. 
>> Selinux is in targeted mode, enabled, and it isn't fussing.
>>
>> /tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0  
>> tmp but nearly everything in it is root:root except the amanda and
>> amanda-debug directories.  So I just changed tmp to drwxrwxrwx  But that
>> also didn't change anything. Or did it, now the log shows this when I
>> restart mysqld:
>>
>> 090216 13:51:44  mysqld started
>> InnoDB: The first specified data file ./ibdata1 did not exist:
>> InnoDB: a new database to be created!
>> 090216 13:51:44  InnoDB: Setting file ./ibdata1 size to 10 MB
>> InnoDB: Database physically writes the file full: wait...
>> 090216 13:51:45  InnoDB: Log file ./ib_logfile0 did not exist: new to be
>> created InnoDB: Setting log file ./ib_logfile0 size to 5 MB
>> InnoDB: Database physically writes the file full: wait...
>> 090216 13:51:45  InnoDB: Log file ./ib_logfile1 did not exist: new to be
>> created InnoDB: Setting log file ./ib_logfile1 size to 5 MB
>> InnoDB: Database physically writes the file full: wait...
>> InnoDB: Doublewrite buffer not found: creating new
>> InnoDB: Doublewrite buffer created
>> InnoDB: Creating foreign key constraint system tables
>> InnoDB: Foreign key constraint system tables created
>> 090216 13:51:46  InnoDB: Started; log sequence number 0 0
>> 090216 13:51:46 [Note] /usr/libexec/mysqld: ready for connections.
>> Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source
>> distribution
>>
>> Which says one problem seems to be sorted, at the expense of a huge
>> security hole in /tmp as anyone can do anything there now.
>>
>> Ok, so now try a login again:
>> [r...@coyote /]# mysql -u root -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: YES) [r...@coyote /]# mysql -u root -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: NO) [r...@coyote /]#
>>
>> Seems like this is where I started, isn't it?
>>
>> Now that the tmp perms is sorted, I suppose I need to go back and do all
>> that other stuff again...
>>
>> Which I just did, and didn't change a thing.  WTF?
>> Thanks Craig
>
>
>after initial installation but before you actually ever start mysqld
>service...
>
>mysqladmin - u root password 'new-password'
>
>*might* work after the mysqld service has already been started but if
>you look at the script involved in /etc/init.d/mysqld, much will happen
>the first time you start it.
>
>You can always stop mysqld service, empty contents of /var/lib/mysql and
>start the service if you don't care about any of the setup.

I didn't, but:

[r...@coyote /]# service mysqld stop
STOPPING server from pid file /var/run/mysqld/mysqld.pid
090216 14:57:46  mysqld ended

Stopping MySQL:[  OK  ]
[1]+  Donemysqld_safe --skip-grant-tables 
--init-file=/tmp/mysql.user
[r...@coyote /]# mysqladmin password 'xxxsanitized'
mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket 
'/var/lib/mysql/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/var/lib/mysql/mysql.sock' 
exists!
[r...@coyote /]# cd /var/lib
[r...@coyote lib]# ls
alternatives  cs dhclient  hal kdm   multipath  pgsql   
 rkhunter  sepolgentexmf  
yum
awstats   davdhcpv6hsqldb  logrotate.status  mysql  php 
 rpcbind   setroubleshoot  vdr
bittorrentdbus   dirmngr   htdig   misc  nfs
PolicyKitrpm   spamassassinwebalizer
bluetooth denyhosts  games iptraf  mlocate   ntp
random-seed  samba sta

Re: myqsl dummy needs help

[Craig White]

On Mon, 2009-02-16 at 14:06 -0500, Gene Heskett wrote:
> On Monday 16 February 2009, Craig White wrote:

> >
> >I think original setup for mysql is for root user via local socket and
> >not via localhost so there actually isn't an account for r...@localhost
> >thus attempting to connect via tcp/ip as root is doomed to fail out of
> >the box.
> >
> >Craig
> 
> With all due respect Craig, what the hell use is it then when ALL the 
> documentation is wrong?
> 
> Now, I just had the bright idea of looking at the mysqld.log after ripping 
> it all out and putting even more of it back in, and see this:
> 
> [r...@coyote etc]# cat /var/log/mysqld.log
> 090216 13:30:36  mysqld ended
> 
> 090216 13:30:45  mysqld started
> /usr/libexec/mysqld: Can't create/write to file '/tmp/ibnoIZas' (Errcode: 13)
> 090216 13:30:45  InnoDB: Error: unable to create temporary file; errno: 13
> 090216 13:30:45 [Note] /usr/libexec/mysqld: ready for connections.
> Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source 
> distribution
> 
> So obviously /tmp doesn't have the right perms.  Or at least I assume (there 
> is that word again) that an error 13 is permissions related.  Selinux is in 
> targeted mode, enabled, and it isn't fussing.
> 
> /tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0   tmp
> but nearly everything in it is root:root except the amanda and amanda-debug 
> directories.  So I just changed tmp to drwxrwxrwx  But that also didn't change
> anything. Or did it, now the log shows this when I restart mysqld:
> 
> 090216 13:51:44  mysqld started
> InnoDB: The first specified data file ./ibdata1 did not exist:
> InnoDB: a new database to be created!
> 090216 13:51:44  InnoDB: Setting file ./ibdata1 size to 10 MB
> InnoDB: Database physically writes the file full: wait...
> 090216 13:51:45  InnoDB: Log file ./ib_logfile0 did not exist: new to be 
> created
> InnoDB: Setting log file ./ib_logfile0 size to 5 MB
> InnoDB: Database physically writes the file full: wait...
> 090216 13:51:45  InnoDB: Log file ./ib_logfile1 did not exist: new to be 
> created
> InnoDB: Setting log file ./ib_logfile1 size to 5 MB
> InnoDB: Database physically writes the file full: wait...
> InnoDB: Doublewrite buffer not found: creating new
> InnoDB: Doublewrite buffer created
> InnoDB: Creating foreign key constraint system tables
> InnoDB: Foreign key constraint system tables created
> 090216 13:51:46  InnoDB: Started; log sequence number 0 0
> 090216 13:51:46 [Note] /usr/libexec/mysqld: ready for connections.
> Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source 
> distribution
> 
> Which says one problem seems to be sorted, at the expense of a huge security 
> hole in /tmp as anyone can do anything there now.
> 
> Ok, so now try a login again:
> [r...@coyote /]# mysql -u root -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: YES)
> [r...@coyote /]# mysql -u root -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: NO)
> [r...@coyote /]#
> 
> Seems like this is where I started, isn't it?
> 
> Now that the tmp perms is sorted, I suppose I need to go back and do all that 
> other stuff again...
> 
> Which I just did, and didn't change a thing.  WTF?
> Thanks Craig

after initial installation but before you actually ever start mysqld
service...

mysqladmin - u root password 'new-password'

*might* work after the mysqld service has already been started but if
you look at the script involved in /etc/init.d/mysqld, much will happen
the first time you start it.

You can always stop mysqld service, empty contents of /var/lib/mysql and
start the service if you don't care about any of the setup.

As for the documentation...it's not wrong but the documentation doesn't
account for what the various distributions will do with their
initialization scripts.

If it's all too much for you, install webmin and use that to
create/maintain user accounts in mysql.

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Markku Kolkka]

Gene Heskett kirjoitti viestissään (lähetysaika maanantai, 16. 
helmikuuta 2009):
> There is no localhost in my /etc/passwd file, do I need to
> adduser first?

MySQL has its own user/password management system that has 
absolutely nothing to do with /etc/passwd, PAM or other Linux 
account management components.

-- 
 Markku Kolkka
 markku.kol...@iki.fi

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Mike Wright wrote:
>mysqladmin password 'secretcode'

mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'


-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I have no doubt that it is a part of the destiny of the human race, 
in its gradual improvement, to leave off eating animals.
-- Thoreau

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Mike Wright wrote:
>Gene Heskett wrote:
>
>
>> /tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0  
>> tmp but nearly everything in it is root:root except the amanda and
>> amanda-debug directories.  So I just changed tmp to drwxrwxrwx  But that
>> also didn't change anything. Or did it, now the log shows this when I
>> restart mysqld:
>
>Hi Gene.  You also need to execute "chmod +t /tmp".  I think your
>permissions should be drwxrwxrwt.

No difference Mike, thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I have no doubt that it is a part of the destiny of the human race, 
in its gradual improvement, to leave off eating animals.
-- Thoreau

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Robert L Cochran wrote:
>http://dev.mysql.com/doc/refman/5.0/en/resetting-permissions.html
>
>http://dev.mysql.com/doc/refman/5.0/en/privilege-system.html
>
All of which assume that the simple mysql shell works.  It doesn't, can't 
connect r...@localhost, error 1045

>Robert L Cochran wrote:
>> There is a 'root'@'localhost' account, but it has no password. For more
>> information see the MySQL knowledgebase at www.mysql.com.
>>
>> Been there, done that.
>>
>> Bob
>>
>> Craig White wrote:
>>> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
 All the heavier-weight database engines have their own user accounts, so
 they can grant or restrict permissions to various databases and tables
 based on who the user is. MySQL does this. Even though mysql has a root
 user that user is totally separate from the OS root account. You can
 also have a mysql user account named mickey even though your host box
 does not have such a user. So think only in terms of the defined MySQL
 users.

 You need to reset the MySQL root user password.

 There may be no password to start with. I wonder what happens if you
 just press enter when prompted for the password. If there is no
 password, then you can set one using mysqladmin. When you first start
 the mysqld server using 'service start mysqld' the syntax of the command
 is explained to you right on the terminal window.

 One more point. If you want to assign a password to a user on a specific
 host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
 at the time someone attempts to log in with that username the actual
 machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
 the user 'mickey' must have a password defined for the localhost machine
 ('mickey'@'localhost').

 To do reset the root password correctly, you can find copious details on
 the MySQL knowledgebase. Go to www.mysql.com and search off their
 knowledgebase. There is a method described for changing the password for
 the root user, but it is fairly complicated. I've used it successfully
 once or twice before when I made a mess of my own mysql root password.

 Another great resource is to read Paul DuBois book "MySQL". It is really
 the bible of all things MySQL. If you intend to use MySQL seriously then
 this book is mandatory purchasing and reading.
>>>
>>> 
>>> I think original setup for mysql is for root user via local socket and
>>> not via localhost so there actually isn't an account for r...@localhost
>>> thus attempting to connect via tcp/ip as root is doomed to fail out of
>>> the box.
>>>
>>> Craig



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
We all agree on the necessity of compromise.  We just can't agree on
when it's necessary to compromise.
-- Larry Wall

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Robert L Cochran wrote:
>That is to say, on the initial installation of a MySQL server, there is
>indeed a 'root'@'localhost' account, but it has no password. See page
>609 of MySQL, Third Edition, by Paul DuBois and read through the next
>several pages.
>
>I just did this for a new MySQL installation on one of my test boxes and
>was able to set the root password with only a little fussiness from
>mysqladmin. I first set the password for localhost, 

There is no localhost in my /etc/passwd file, do I need to adduser first?

>then logged into the 
>mysql server as 'root'@'localhost' and set the password for
>'root'@'my.box.name'. You need to set both these passwords for root.
>Then I tested my login and did a few easy queries such as 'show
>databases;' and I was all set.
>
>Bob
>
>Robert L Cochran wrote:
>> There is a 'root'@'localhost' account, but it has no password. For more
>> information see the MySQL knowledgebase at www.mysql.com.
>>
>> Been there, done that.
>>
>> Bob
>>
>> Craig White wrote:
>>> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
 All the heavier-weight database engines have their own user accounts, so
 they can grant or restrict permissions to various databases and tables
 based on who the user is. MySQL does this. Even though mysql has a root
 user that user is totally separate from the OS root account. You can
 also have a mysql user account named mickey even though your host box
 does not have such a user. So think only in terms of the defined MySQL
 users.

 You need to reset the MySQL root user password.

 There may be no password to start with. I wonder what happens if you
 just press enter when prompted for the password. If there is no
 password, then you can set one using mysqladmin. When you first start
 the mysqld server using 'service start mysqld' the syntax of the command
 is explained to you right on the terminal window.

 One more point. If you want to assign a password to a user on a specific
 host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
 at the time someone attempts to log in with that username the actual
 machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
 the user 'mickey' must have a password defined for the localhost machine
 ('mickey'@'localhost').

 To do reset the root password correctly, you can find copious details on
 the MySQL knowledgebase. Go to www.mysql.com and search off their
 knowledgebase. There is a method described for changing the password for
 the root user, but it is fairly complicated. I've used it successfully
 once or twice before when I made a mess of my own mysql root password.

 Another great resource is to read Paul DuBois book "MySQL". It is really
 the bible of all things MySQL. If you intend to use MySQL seriously then
 this book is mandatory purchasing and reading.
>>>
>>> 
>>> I think original setup for mysql is for root user via local socket and
>>> not via localhost so there actually isn't an account for r...@localhost
>>> thus attempting to connect via tcp/ip as root is doomed to fail out of
>>> the box.
>>>
>>> Craig



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Would you *__really* want to get on a non-stop flight?
-- George Carlin

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Mike Wright]

Gene Heskett wrote:



/tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0   tmp
but nearly everything in it is root:root except the amanda and amanda-debug 
directories.  So I just changed tmp to drwxrwxrwx  But that also didn't change

anything. Or did it, now the log shows this when I restart mysqld:



Hi Gene.  You also need to execute "chmod +t /tmp".  I think your 
permissions should be drwxrwxrwt.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Robert L Cochran wrote:
>That is to say, on the initial installation of a MySQL server, there is
>indeed a 'root'@'localhost' account, but it has no password. See page
>609 of MySQL, Third Edition, by Paul DuBois and read through the next
>several pages.
>
>I just did this for a new MySQL installation on one of my test boxes and
>was able to set the root password with only a little fussiness from
>mysqladmin. I first set the password for localhost, then logged into the
>mysql server as 'root'@'localhost' and set the password for
>'root'@'my.box.name'. You need to set both these passwords for root.
>Then I tested my login and did a few easy queries such as 'show
>databases;' and I was all set.
>
>Bob
>
>Robert L Cochran wrote:
>> There is a 'root'@'localhost' account, but it has no password. For more
>> information see the MySQL knowledgebase at www.mysql.com.
>>
>> Been there, done that.
>>
>> Bob
>>
>> Craig White wrote:
>>> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
 All the heavier-weight database engines have their own user accounts, so
 they can grant or restrict permissions to various databases and tables
 based on who the user is. MySQL does this. Even though mysql has a root
 user that user is totally separate from the OS root account. You can
 also have a mysql user account named mickey even though your host box
 does not have such a user. So think only in terms of the defined MySQL
 users.

 You need to reset the MySQL root user password.

I have done this 5 times now.

 There may be no password to start with. I wonder what happens if you
 just press enter when prompted for the password. If there is no
 password, then you can set one using mysqladmin.

mysqladmin is also being denied access.
[r...@coyote /]# mysqladmin
mysqladmin  Ver 8.41 Distrib 5.0.45, for redhat-linux-gnu on i386
Copyright (C) 2000-2006 MySQL AB
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL license

Administration program for the mysqld daemon.
Usage: mysqladmin [OPTIONS] command command
  -c, --count=#   Number of iterations to make. This works with -i
  (--sleep) only.
  -#, --debug[=name]  Output debug log. Often this is 'd:t:o,filename'.
  -f, --force Don't ask for confirmation on drop database; with
  multiple commands, continue even if an error occurs.
  -C, --compress  Use compression in server/client protocol.
  --character-sets-dir=name
  Directory where character sets are.
  --default-character-set=name
  Set the default character set.
  -?, --help  Display this help and exit.
  -h, --host=name Connect to host.
  -p, --password[=name]
  Password to use when connecting to server. If password is
  not given it's asked from the tty.
  -P, --port=#Port number to use for connection.
  --protocol=name The protocol of connection (tcp,socket,pipe,memory).
  -r, --relative  Show difference between current and previous values when
  used with -i. Currently works only with extended-status.
  -O, --set-variable=name
  Change the value of a variable. Please note that this
  option is deprecated; you can set variables directly with
  --variable-name=value.
  -s, --silentSilently exit if one can't connect to server.
  -S, --socket=name   Socket file to use for connection.
  -i, --sleep=#   Execute commands again and again with a sleep between.
  --ssl   Enable SSL for connection (automatically enabled with
  other flags). Disable with --skip-ssl.
  --ssl-ca=name   CA file in PEM format (check OpenSSL docs, implies
  --ssl).
  --ssl-capath=name   CA directory (check OpenSSL docs, implies --ssl).
  --ssl-cert=name X509 cert in PEM format (implies --ssl).
  --ssl-cipher=name   SSL cipher to use (implies --ssl).
  --ssl-key=name  X509 key in PEM format (implies --ssl).
  --ssl-verify-server-cert
  Verify server's "Common Name" in its cert against
  hostname used when connecting. This option is disabled by
  default.
  -u, --user=name User for login if not current user.
  -v, --verbose   Write more information.
  -V, --version   Output version information and exit.
  -E, --vertical  Print output vertically. Is similar to --relative, but
  prints output vertically.
  -w, --wait[=#]  Wait and retry if connection is down.
  --connect_timeout=#
  --shutdown_timeout=#

Variables (--variable-name=value)
and boolean options {FALSE|TRUE}  Value (after reading options)
- -
count 

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Robert L Cochran wrote:
>There is a 'root'@'localhost' account, but it has no password. For more
>information see the MySQL knowledgebase at www.mysql.com.
>
>Been there, done that.
>
>Bob

So have I Bob, and other than disclosing my /tmp perms weren't as wide open as 
they needed to be, which was denying INNoDB permission to write a scratch 
file, no change.  I even ripped it out and reinstalled even more of it, 
again, no change.

The only way I can access it is with:
mysqld_safe --skip-grant-tables &

So where is this "grant-tables"?

>Craig White wrote:
>> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
>>> All the heavier-weight database engines have their own user accounts, so
>>> they can grant or restrict permissions to various databases and tables
>>> based on who the user is. MySQL does this. Even though mysql has a root
>>> user that user is totally separate from the OS root account. You can
>>> also have a mysql user account named mickey even though your host box
>>> does not have such a user. So think only in terms of the defined MySQL
>>> users.
>>>
>>> You need to reset the MySQL root user password.
>>>
>>> There may be no password to start with. I wonder what happens if you
>>> just press enter when prompted for the password. If there is no
>>> password, then you can set one using mysqladmin. When you first start
>>> the mysqld server using 'service start mysqld' the syntax of the command
>>> is explained to you right on the terminal window.
>>>
>>> One more point. If you want to assign a password to a user on a specific
>>> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>>> at the time someone attempts to log in with that username the actual
>>> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>>> the user 'mickey' must have a password defined for the localhost machine
>>> ('mickey'@'localhost').
>>>
>>> To do reset the root password correctly, you can find copious details on
>>> the MySQL knowledgebase. Go to www.mysql.com and search off their
>>> knowledgebase. There is a method described for changing the password for
>>> the root user, but it is fairly complicated. I've used it successfully
>>> once or twice before when I made a mess of my own mysql root password.
>>>
>>> Another great resource is to read Paul DuBois book "MySQL". It is really
>>> the bible of all things MySQL. If you intend to use MySQL seriously then
>>> this book is mandatory purchasing and reading.
>>
>> 
>> I think original setup for mysql is for root user via local socket and
>> not via localhost so there actually isn't an account for r...@localhost
>> thus attempting to connect via tcp/ip as root is doomed to fail out of
>> the box.
>>
>> Craig



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Eloquence is logic on fire.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Craig White wrote:
>On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
>> All the heavier-weight database engines have their own user accounts, so
>> they can grant or restrict permissions to various databases and tables
>> based on who the user is. MySQL does this. Even though mysql has a root
>> user that user is totally separate from the OS root account. You can
>> also have a mysql user account named mickey even though your host box
>> does not have such a user. So think only in terms of the defined MySQL
>> users.
>>
>> You need to reset the MySQL root user password.
>>
>> There may be no password to start with. I wonder what happens if you
>> just press enter when prompted for the password. If there is no
>> password, then you can set one using mysqladmin. When you first start
>> the mysqld server using 'service start mysqld' the syntax of the command
>> is explained to you right on the terminal window.
>>
>> One more point. If you want to assign a password to a user on a specific
>> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>> at the time someone attempts to log in with that username the actual
>> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>> the user 'mickey' must have a password defined for the localhost machine
>> ('mickey'@'localhost').
>>
>> To do reset the root password correctly, you can find copious details on
>> the MySQL knowledgebase. Go to www.mysql.com and search off their
>> knowledgebase. There is a method described for changing the password for
>> the root user, but it is fairly complicated. I've used it successfully
>> once or twice before when I made a mess of my own mysql root password.
>>
>> Another great resource is to read Paul DuBois book "MySQL". It is really
>> the bible of all things MySQL. If you intend to use MySQL seriously then
>> this book is mandatory purchasing and reading.
>
>
>I think original setup for mysql is for root user via local socket and
>not via localhost so there actually isn't an account for r...@localhost
>thus attempting to connect via tcp/ip as root is doomed to fail out of
>the box.
>
>Craig

With all due respect Craig, what the hell use is it then when ALL the 
documentation is wrong?

Now, I just had the bright idea of looking at the mysqld.log after ripping 
it all out and putting even more of it back in, and see this:

[r...@coyote etc]# cat /var/log/mysqld.log
090216 13:30:36  mysqld ended

090216 13:30:45  mysqld started
/usr/libexec/mysqld: Can't create/write to file '/tmp/ibnoIZas' (Errcode: 13)
090216 13:30:45  InnoDB: Error: unable to create temporary file; errno: 13
090216 13:30:45 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source 
distribution

So obviously /tmp doesn't have the right perms.  Or at least I assume (there 
is that word again) that an error 13 is permissions related.  Selinux is in 
targeted mode, enabled, and it isn't fussing.

/tmp itself is drwxr-xr-x  amanda disk   system_u:object_r:tmp_t:s0   tmp
but nearly everything in it is root:root except the amanda and amanda-debug 
directories.  So I just changed tmp to drwxrwxrwx  But that also didn't change
anything. Or did it, now the log shows this when I restart mysqld:

090216 13:51:44  mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
090216 13:51:44  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
090216 13:51:45  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
090216 13:51:45  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
090216 13:51:46  InnoDB: Started; log sequence number 0 0
090216 13:51:46 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.45'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Source 
distribution

Which says one problem seems to be sorted, at the expense of a huge security 
hole in /tmp as anyone can do anything there now.

Ok, so now try a login again:
[r...@coyote /]# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
YES)
[r...@coyote /]# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
NO)
[r...@coyote /]#

Seems like this is where I started, isn't it?

Now that the tmp perms is sorted, I suppose I need to go back and do all that 
other stuff again...

Which I just did, and di

Re: myqsl dummy needs help

[Robert L Cochran]

With databases, you need to do careful research first and foremost.
Otherwise you make a big mess and it becomes far worse to fix.

http://dev.mysql.com/doc/refman/5.0/en/resetting-permissions.html

Bob


Mike Wright wrote:
> Gene Heskett wrote:
>> On Monday 16 February 2009, Robert L Cochran wrote:
>>> All the heavier-weight database engines have their own user
>>> accounts, so
>>> they can grant or restrict permissions to various databases and tables
>>> based on who the user is. MySQL does this. Even though mysql has a root
>>> user that user is totally separate from the OS root account. You can
>>> also have a mysql user account named mickey even though your host box
>>> does not have such a user. So think only in terms of the defined MySQL
>>> users.
>>>
>>> You need to reset the MySQL root user password.
>>>
>>> There may be no password to start with. I wonder what happens if you
>>> just press enter when prompted for the password. If there is no
>>> password, then you can set one using mysqladmin. When you first start
>>> the mysqld server using 'service start mysqld' the syntax of the
>>> command
>>> is explained to you right on the terminal window.
>>>
>>> One more point. If you want to assign a password to a user on a
>>> specific
>>> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>>> at the time someone attempts to log in with that username the actual
>>> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>>> the user 'mickey' must have a password defined for the localhost
>>> machine
>>> ('mickey'@'localhost').
>>>
>>> To do reset the root password correctly, you can find copious
>>> details on
>>> the MySQL knowledgebase. Go to www.mysql.com and search off their
>>> knowledgebase. There is a method described for changing the password
>>> for
>>> the root user, but it is fairly complicated. I've used it successfully
>>> once or twice before when I made a mess of my own mysql root password.
>>
>> I have now done that procedure twice, setting a different passwd the
>> last time in case mysql has a password length limit less that the
>> size of my root pw.
>>
>> It didn't help, I'm still getting exactly the same error.  How can I
>> nuke it all & start from a truly scratch install?
>
> Hi Gene,
>
> Before you do that I have an idea.
>
> I don't install MySql very often but I seem to recall an alert given
> upon installation advising the use of mysqladmin to set the initial
> root password.  On a clean install the password is the empty string
> (return).
>
> "mysqladmin password 'secretcode'"
>
> After that you use the GRANT command to control access to the rdb.
>
> Hope I'm not all wet here.  Sometimes my CRS gets in the way ;)
>
> Mike Wright
>

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Mike Wright]

Gene Heskett wrote:

On Monday 16 February 2009, Robert L Cochran wrote:

All the heavier-weight database engines have their own user accounts, so
they can grant or restrict permissions to various databases and tables
based on who the user is. MySQL does this. Even though mysql has a root
user that user is totally separate from the OS root account. You can
also have a mysql user account named mickey even though your host box
does not have such a user. So think only in terms of the defined MySQL
users.

You need to reset the MySQL root user password.

There may be no password to start with. I wonder what happens if you
just press enter when prompted for the password. If there is no
password, then you can set one using mysqladmin. When you first start
the mysqld server using 'service start mysqld' the syntax of the command
is explained to you right on the terminal window.

One more point. If you want to assign a password to a user on a specific
host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
at the time someone attempts to log in with that username the actual
machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
the user 'mickey' must have a password defined for the localhost machine
('mickey'@'localhost').

To do reset the root password correctly, you can find copious details on
the MySQL knowledgebase. Go to www.mysql.com and search off their
knowledgebase. There is a method described for changing the password for
the root user, but it is fairly complicated. I've used it successfully
once or twice before when I made a mess of my own mysql root password.


I have now done that procedure twice, setting a different passwd the last time 
in case mysql has a password length limit less that the size of my root pw.


It didn't help, I'm still getting exactly the same error.  How can I nuke it 
all & start from a truly scratch install?


Hi Gene,

Before you do that I have an idea.

I don't install MySql very often but I seem to recall an alert given 
upon installation advising the use of mysqladmin to set the initial root 
password.  On a clean install the password is the empty string (return).


"mysqladmin password 'secretcode'"

After that you use the GRANT command to control access to the rdb.

Hope I'm not all wet here.  Sometimes my CRS gets in the way ;)

Mike Wright

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Robert L Cochran]

http://dev.mysql.com/doc/refman/5.0/en/resetting-permissions.html

http://dev.mysql.com/doc/refman/5.0/en/privilege-system.html




Robert L Cochran wrote:
> There is a 'root'@'localhost' account, but it has no password. For more
> information see the MySQL knowledgebase at www.mysql.com.
>
> Been there, done that.
>
> Bob
>
>
> Craig White wrote:
>   
>> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
>>   
>> 
>>> All the heavier-weight database engines have their own user accounts, so
>>> they can grant or restrict permissions to various databases and tables
>>> based on who the user is. MySQL does this. Even though mysql has a root
>>> user that user is totally separate from the OS root account. You can
>>> also have a mysql user account named mickey even though your host box
>>> does not have such a user. So think only in terms of the defined MySQL
>>> users.
>>>
>>> You need to reset the MySQL root user password.
>>>
>>> There may be no password to start with. I wonder what happens if you
>>> just press enter when prompted for the password. If there is no
>>> password, then you can set one using mysqladmin. When you first start
>>> the mysqld server using 'service start mysqld' the syntax of the command
>>> is explained to you right on the terminal window.
>>>
>>> One more point. If you want to assign a password to a user on a specific
>>> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>>> at the time someone attempts to log in with that username the actual
>>> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>>> the user 'mickey' must have a password defined for the localhost machine
>>> ('mickey'@'localhost').
>>>
>>> To do reset the root password correctly, you can find copious details on
>>> the MySQL knowledgebase. Go to www.mysql.com and search off their
>>> knowledgebase. There is a method described for changing the password for
>>> the root user, but it is fairly complicated. I've used it successfully
>>> once or twice before when I made a mess of my own mysql root password.
>>>
>>> Another great resource is to read Paul DuBois book "MySQL". It is really
>>> the bible of all things MySQL. If you intend to use MySQL seriously then
>>> this book is mandatory purchasing and reading.
>>> 
>>>   
>> 
>> I think original setup for mysql is for root user via local socket and
>> not via localhost so there actually isn't an account for r...@localhost
>> thus attempting to connect via tcp/ip as root is doomed to fail out of
>> the box.
>>
>> Craig
>>
>>   
>> 
>
>   

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Robert L Cochran wrote:
>All the heavier-weight database engines have their own user accounts, so
>they can grant or restrict permissions to various databases and tables
>based on who the user is. MySQL does this. Even though mysql has a root
>user that user is totally separate from the OS root account. You can
>also have a mysql user account named mickey even though your host box
>does not have such a user. So think only in terms of the defined MySQL
>users.
>
>You need to reset the MySQL root user password.
>
>There may be no password to start with. I wonder what happens if you
>just press enter when prompted for the password. If there is no
>password, then you can set one using mysqladmin. When you first start
>the mysqld server using 'service start mysqld' the syntax of the command
>is explained to you right on the terminal window.
>
>One more point. If you want to assign a password to a user on a specific
>host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>at the time someone attempts to log in with that username the actual
>machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>the user 'mickey' must have a password defined for the localhost machine
>('mickey'@'localhost').
>
>To do reset the root password correctly, you can find copious details on
>the MySQL knowledgebase. Go to www.mysql.com and search off their
>knowledgebase. There is a method described for changing the password for
>the root user, but it is fairly complicated. I've used it successfully
>once or twice before when I made a mess of my own mysql root password.

I have now done that procedure twice, setting a different passwd the last time 
in case mysql has a password length limit less that the size of my root pw.

It didn't help, I'm still getting exactly the same error.  How can I nuke it 
all & start from a truly scratch install?

>Another great resource is to read Paul DuBois book "MySQL". It is really
>the bible of all things MySQL. If you intend to use MySQL seriously then
>this book is mandatory purchasing and reading.

That book, if B&N has it, is 60 miles away.

>Bob Cochran
>
>Gene Heskett wrote:
>> On Monday 16 February 2009, Brian Millett wrote:
>>> On Mon, 2009-02-16 at 10:03 -0500, Gene Heskett wrote:
 On Monday 16 February 2009, Steve Searle wrote:
> Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett
>>
>> scrawled:
>> 3.# mysql -u root mysql
>
> 3.# mysql -u root mysql -p
>^^
>
> The -p will cause you to be prompted for root's password.  What you
> have tried does not supply the password.
>
> Steve

 Unforch Steve, same error:

 [r...@coyote etc]# mysql -u root mysql -p
 Enter password:
 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
 password: YES)
 [r...@coyote etc]# mysql -u root mysql -p
 Enter password:
 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
 password: YES)

 in each case I entered my root pw at the prompt.
>>>
>>> That will be the mysql root user, not the system root user.  IF that was
>>> setup installing mythtv, then you need to check the scripts used in the
>>> package that installed mysql.
>>
>> Humm, mythtv was built from the tarball.  mysql was from the F8 rpms. I'll
>> check the mythtv Makefile.  No joy there, and /etc/my.cnf says the
>> user=mysql
>>
>> Do I need to add another user, such as mythtv and assign that user a
>> password? Or assign mysql a password?
>>
>> I did the latter as mysql existed in the passwd file, but the same error
>> results:
>>
>> [r...@coyote etc]# passwd mysql
>> Changing password for user mysql.
>> New UNIX password:
>> Retype new UNIX password:
>> passwd: all authentication tokens updated successfully.
>> [r...@coyote etc]# mysql -u mysql -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'mysql'@'localhost' (using
>> password: YES)
>> [r...@coyote etc]# mysql -u root -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: YES)
>>
>> Does anyone know the default msql passwd so I can set it back?
>>
>> Still bumfuzzled.
>>
>> Thanks.



-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Accuracy, n.:
The vice of being right

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Robert L Cochran]

That is to say, on the initial installation of a MySQL server, there is
indeed a 'root'@'localhost' account, but it has no password. See page
609 of MySQL, Third Edition, by Paul DuBois and read through the next
several pages.

I just did this for a new MySQL installation on one of my test boxes and
was able to set the root password with only a little fussiness from
mysqladmin. I first set the password for localhost, then logged into the
mysql server as 'root'@'localhost' and set the password for
'root'@'my.box.name'. You need to set both these passwords for root.
Then I tested my login and did a few easy queries such as 'show
databases;' and I was all set.

Bob

Robert L Cochran wrote:
> There is a 'root'@'localhost' account, but it has no password. For more
> information see the MySQL knowledgebase at www.mysql.com.
>
> Been there, done that.
>
> Bob
>
>
> Craig White wrote:
>   
>> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
>>   
>> 
>>> All the heavier-weight database engines have their own user accounts, so
>>> they can grant or restrict permissions to various databases and tables
>>> based on who the user is. MySQL does this. Even though mysql has a root
>>> user that user is totally separate from the OS root account. You can
>>> also have a mysql user account named mickey even though your host box
>>> does not have such a user. So think only in terms of the defined MySQL
>>> users.
>>>
>>> You need to reset the MySQL root user password.
>>>
>>> There may be no password to start with. I wonder what happens if you
>>> just press enter when prompted for the password. If there is no
>>> password, then you can set one using mysqladmin. When you first start
>>> the mysqld server using 'service start mysqld' the syntax of the command
>>> is explained to you right on the terminal window.
>>>
>>> One more point. If you want to assign a password to a user on a specific
>>> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>>> at the time someone attempts to log in with that username the actual
>>> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>>> the user 'mickey' must have a password defined for the localhost machine
>>> ('mickey'@'localhost').
>>>
>>> To do reset the root password correctly, you can find copious details on
>>> the MySQL knowledgebase. Go to www.mysql.com and search off their
>>> knowledgebase. There is a method described for changing the password for
>>> the root user, but it is fairly complicated. I've used it successfully
>>> once or twice before when I made a mess of my own mysql root password.
>>>
>>> Another great resource is to read Paul DuBois book "MySQL". It is really
>>> the bible of all things MySQL. If you intend to use MySQL seriously then
>>> this book is mandatory purchasing and reading.
>>> 
>>>   
>> 
>> I think original setup for mysql is for root user via local socket and
>> not via localhost so there actually isn't an account for r...@localhost
>> thus attempting to connect via tcp/ip as root is doomed to fail out of
>> the box.
>>
>> Craig
>>
>>   
>> 
>
>   

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Robert L Cochran]

There is a 'root'@'localhost' account, but it has no password. For more
information see the MySQL knowledgebase at www.mysql.com.

Been there, done that.

Bob


Craig White wrote:
> On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
>   
>> All the heavier-weight database engines have their own user accounts, so
>> they can grant or restrict permissions to various databases and tables
>> based on who the user is. MySQL does this. Even though mysql has a root
>> user that user is totally separate from the OS root account. You can
>> also have a mysql user account named mickey even though your host box
>> does not have such a user. So think only in terms of the defined MySQL
>> users.
>>
>> You need to reset the MySQL root user password.
>>
>> There may be no password to start with. I wonder what happens if you
>> just press enter when prompted for the password. If there is no
>> password, then you can set one using mysqladmin. When you first start
>> the mysqld server using 'service start mysqld' the syntax of the command
>> is explained to you right on the terminal window.
>>
>> One more point. If you want to assign a password to a user on a specific
>> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
>> at the time someone attempts to log in with that username the actual
>> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
>> the user 'mickey' must have a password defined for the localhost machine
>> ('mickey'@'localhost').
>>
>> To do reset the root password correctly, you can find copious details on
>> the MySQL knowledgebase. Go to www.mysql.com and search off their
>> knowledgebase. There is a method described for changing the password for
>> the root user, but it is fairly complicated. I've used it successfully
>> once or twice before when I made a mess of my own mysql root password.
>>
>> Another great resource is to read Paul DuBois book "MySQL". It is really
>> the bible of all things MySQL. If you intend to use MySQL seriously then
>> this book is mandatory purchasing and reading.
>> 
> 
> I think original setup for mysql is for root user via local socket and
> not via localhost so there actually isn't an account for r...@localhost
> thus attempting to connect via tcp/ip as root is doomed to fail out of
> the box.
>
> Craig
>
>   

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Craig White]

On Mon, 2009-02-16 at 11:06 -0500, Robert L Cochran wrote:
> All the heavier-weight database engines have their own user accounts, so
> they can grant or restrict permissions to various databases and tables
> based on who the user is. MySQL does this. Even though mysql has a root
> user that user is totally separate from the OS root account. You can
> also have a mysql user account named mickey even though your host box
> does not have such a user. So think only in terms of the defined MySQL
> users.
> 
> You need to reset the MySQL root user password.
> 
> There may be no password to start with. I wonder what happens if you
> just press enter when prompted for the password. If there is no
> password, then you can set one using mysqladmin. When you first start
> the mysqld server using 'service start mysqld' the syntax of the command
> is explained to you right on the terminal window.
> 
> One more point. If you want to assign a password to a user on a specific
> host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
> at the time someone attempts to log in with that username the actual
> machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
> the user 'mickey' must have a password defined for the localhost machine
> ('mickey'@'localhost').
> 
> To do reset the root password correctly, you can find copious details on
> the MySQL knowledgebase. Go to www.mysql.com and search off their
> knowledgebase. There is a method described for changing the password for
> the root user, but it is fairly complicated. I've used it successfully
> once or twice before when I made a mess of my own mysql root password.
> 
> Another great resource is to read Paul DuBois book "MySQL". It is really
> the bible of all things MySQL. If you intend to use MySQL seriously then
> this book is mandatory purchasing and reading.

I think original setup for mysql is for root user via local socket and
not via localhost so there actually isn't an account for r...@localhost
thus attempting to connect via tcp/ip as root is doomed to fail out of
the box.

Craig

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Robert L Cochran]

All the heavier-weight database engines have their own user accounts, so
they can grant or restrict permissions to various databases and tables
based on who the user is. MySQL does this. Even though mysql has a root
user that user is totally separate from the OS root account. You can
also have a mysql user account named mickey even though your host box
does not have such a user. So think only in terms of the defined MySQL
users.

You need to reset the MySQL root user password.

There may be no password to start with. I wonder what happens if you
just press enter when prompted for the password. If there is no
password, then you can set one using mysqladmin. When you first start
the mysqld server using 'service start mysqld' the syntax of the command
is explained to you right on the terminal window.

One more point. If you want to assign a password to a user on a specific
host machine, such as 'mickey'@'mickeymouse.m1.org' then I believe that
at the time someone attempts to log in with that username the actual
machine name must resolve correctly on dns to 'mickeymouse.m1.org' or
the user 'mickey' must have a password defined for the localhost machine
('mickey'@'localhost').

To do reset the root password correctly, you can find copious details on
the MySQL knowledgebase. Go to www.mysql.com and search off their
knowledgebase. There is a method described for changing the password for
the root user, but it is fairly complicated. I've used it successfully
once or twice before when I made a mess of my own mysql root password.

Another great resource is to read Paul DuBois book "MySQL". It is really
the bible of all things MySQL. If you intend to use MySQL seriously then
this book is mandatory purchasing and reading.

Bob Cochran


Gene Heskett wrote:
> On Monday 16 February 2009, Brian Millett wrote:
>   
>> On Mon, 2009-02-16 at 10:03 -0500, Gene Heskett wrote:
>> 
>>> On Monday 16 February 2009, Steve Searle wrote:
>>>   
 Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett 
 
> scrawled:
>   
> 3.# mysql -u root mysql
>   
 3.# mysql -u root mysql -p
^^

 The -p will cause you to be prompted for root's password.  What you have
 tried does not supply the password.

 Steve
 
>>> Unforch Steve, same error:
>>>
>>> [r...@coyote etc]# mysql -u root mysql -p
>>> Enter password:
>>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>>> password: YES)
>>> [r...@coyote etc]# mysql -u root mysql -p
>>> Enter password:
>>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>>> password: YES)
>>>
>>> in each case I entered my root pw at the prompt.
>>>   
>> That will be the mysql root user, not the system root user.  IF that was
>> setup installing mythtv, then you need to check the scripts used in the
>> package that installed mysql.
>> 
>
> Humm, mythtv was built from the tarball.  mysql was from the F8 rpms. I'll 
> check the mythtv Makefile.  No joy there, and /etc/my.cnf says the user=mysql
>
> Do I need to add another user, such as mythtv and assign that user a 
> password?  
> Or assign mysql a password?
>
> I did the latter as mysql existed in the passwd file, but the same error 
> results:
>
> [r...@coyote etc]# passwd mysql
> Changing password for user mysql.
> New UNIX password:
> Retype new UNIX password:
> passwd: all authentication tokens updated successfully.
> [r...@coyote etc]# mysql -u mysql -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'mysql'@'localhost' (using 
> password: YES)
> [r...@coyote etc]# mysql -u root -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: 
> YES)
>
> Does anyone know the default msql passwd so I can set it back?
>
> Still bumfuzzled.
>
> Thanks.
>
>   

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Matthew Flaschen wrote:
>Gene Heskett wrote:
>> On Monday 16 February 2009, Steve Searle wrote:
>>> Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett 
scrawled:
 3.# mysql -u root mysql
>>>
>>> 3.# mysql -u root mysql -p
>>>^^
>>>
>>> The -p will cause you to be prompted for root's password.  What you have
>>> tried does not supply the password.
>>>
>>> Steve
>>
>> Unforch Steve, same error:
>>
>> [r...@coyote etc]# mysql -u root mysql -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: YES)
>> [r...@coyote etc]# mysql -u root mysql -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: YES)
>>
>> in each case I entered my root pw at the prompt.
>
>Your root password is not MySQL's root password.  However, you can
>change that if you choose (or set whatever pw you want).  See the
>instructions at
>http://www.cyberciti.biz/tips/recover-mysql-root-password.html (though
>there are other methods)
>
>Matt Flaschen

I did all of that sites steps, Matt, with no reported errors, but when I stop 
the special session and restart the regular session, the exact same error is 
returned:
[r...@coyote etc]# /etc/init.d/mysqld stop
STOPPING server from pid file /var/run/mysqld/mysqld.pid
090216 10:53:05  mysqld ended

Stopping MySQL:[  OK  ]
[1]+  Donemysqld_safe --skip-grant-tables
[r...@coyote etc]# /etc/init.d/mysqld start
Starting MySQL:[  OK  ]
[r...@coyote etc]# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
YES)

Thanks Matt.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
We are all worms.  But I do believe I am a glowworm.
-- Winston Churchill

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Brian Millett wrote:
>On Mon, 2009-02-16 at 10:03 -0500, Gene Heskett wrote:
>> On Monday 16 February 2009, Steve Searle wrote:
>> >Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett 
scrawled:
>> >> 3.# mysql -u root mysql
>> >
>> >3.# mysql -u root mysql -p
>> >^^
>> >
>> >The -p will cause you to be prompted for root's password.  What you have
>> >tried does not supply the password.
>> >
>> >Steve
>>
>> Unforch Steve, same error:
>>
>> [r...@coyote etc]# mysql -u root mysql -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: YES)
>> [r...@coyote etc]# mysql -u root mysql -p
>> Enter password:
>> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using
>> password: YES)
>>
>> in each case I entered my root pw at the prompt.
>
>That will be the mysql root user, not the system root user.  IF that was
>setup installing mythtv, then you need to check the scripts used in the
>package that installed mysql.

Humm, mythtv was built from the tarball.  mysql was from the F8 rpms. I'll 
check the mythtv Makefile.  No joy there, and /etc/my.cnf says the user=mysql

Do I need to add another user, such as mythtv and assign that user a password?  
Or assign mysql a password?

I did the latter as mysql existed in the passwd file, but the same error 
results:

[r...@coyote etc]# passwd mysql
Changing password for user mysql.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
[r...@coyote etc]# mysql -u mysql -p
Enter password:
ERROR 1045 (28000): Access denied for user 'mysql'@'localhost' (using 
password: YES)
[r...@coyote etc]# mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
YES)

Does anyone know the default msql passwd so I can set it back?

Still bumfuzzled.

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I need another lawyer like I need another hole in my head.
-- Fratianno

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Matthew Flaschen]

Gene Heskett wrote:
> On Monday 16 February 2009, Steve Searle wrote:
>> Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett scrawled:
>>> 3.# mysql -u root mysql
>> 3.# mysql -u root mysql -p
>>^^
>>
>> The -p will cause you to be prompted for root's password.  What you have
>> tried does not supply the password.
>>
>> Steve
> 
> Unforch Steve, same error:
> 
> [r...@coyote etc]# mysql -u root mysql -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: 
> YES)
> [r...@coyote etc]# mysql -u root mysql -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: 
> YES)
> 
> in each case I entered my root pw at the prompt.

Your root password is not MySQL's root password.  However, you can
change that if you choose (or set whatever pw you want).  See the
instructions at
http://www.cyberciti.biz/tips/recover-mysql-root-password.html (though
there are other methods)

Matt Flaschen

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Brian Millett]

On Mon, 2009-02-16 at 10:03 -0500, Gene Heskett wrote:
> On Monday 16 February 2009, Steve Searle wrote:
> >Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett scrawled:
> >> 3.# mysql -u root mysql
> >
> >3.# mysql -u root mysql -p
> >^^
> >
> >The -p will cause you to be prompted for root's password.  What you have
> >tried does not supply the password.
> >
> >Steve
> 
> Unforch Steve, same error:
> 
> [r...@coyote etc]# mysql -u root mysql -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: 
> YES)
> [r...@coyote etc]# mysql -u root mysql -p
> Enter password:
> ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using 
> password: 
> YES)
> 
> in each case I entered my root pw at the prompt.
> 


That will be the mysql root user, not the system root user.  IF that was
setup installing mythtv, then you need to check the scripts used in the
package that installed mysql.

-- 
Brian Millett - [ Ivanova, "The Geometry of Shadows"]
"If it gets too bad I'll just gnaw it off at the ankle."



signature.asc
Description: This is a digitally signed message part
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Gene Heskett]

On Monday 16 February 2009, Steve Searle wrote:
>Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett scrawled:
>> 3.# mysql -u root mysql
>
>3.# mysql -u root mysql -p
>^^
>
>The -p will cause you to be prompted for root's password.  What you have
>tried does not supply the password.
>
>Steve

Unforch Steve, same error:

[r...@coyote etc]# mysql -u root mysql -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
YES)
[r...@coyote etc]# mysql -u root mysql -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
YES)

in each case I entered my root pw at the prompt.

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The cable TV sex channels don't expand our horizons, don't make us better
people, and don't come in clearly enough.
-- Bill Maher

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: myqsl dummy needs help

[Steve Searle]

Around 02:33pm on Monday, February 16, 2009 (UK time), Gene Heskett scrawled:

> 3.# mysql -u root mysql

3.# mysql -u root mysql -p
^^

The -p will cause you to be prompted for root's password.  What you have
tried does not supply the password.

Steve

-- 
 
(o< www.stevesearle.com
//\ Powered by Fedora
V_/_No MS products were used in the creation of this message

 14:34:52 up 9 days, 15:25,  1 user,  load average: 1.14, 0.68, 0.29


pgpET6tBjTcbH.pgp
Description: PGP signature
-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

myqsl dummy needs help

[Gene Heskett]

Greetings all;

Following the instructs for setting up mythtv, which needs mysql, from the 

1.# /sbin/chkconfig mysqld on
2.# /sbin/service mysqld start
3.# mysql -u root mysql
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: 
NO)

Obviously one cannot administrate a database if even root has no access.

How to proceed is the question?

Thanks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
... I don't like FRANK SINATRA or his CHILDREN.

-- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines