Fwd: Cron <root at coyote> run-parts /etc/cron.daily
Gene Heskett
gene.heskett at verizon.net
Mon May 28 02:09:26 UTC 2007
On Sunday 27 May 2007, Justin W wrote:
>Gene Heskett wrote:
>> On Sunday 27 May 2007, Tony Nelson wrote:
>>> At 9:27 AM -0400 5/27/07, Gene Heskett wrote:
>>>> Hi folks;
>>>>
>>>> I've been trying to make this work, un-sucessfully so far. I've set a
>>>> password yadda yadda, but while I've spent an hour or more reading the
>>>> manpages, nowhere in them did I stumble across a step by step on how to
>>>> create, and initialize, a database called 'bugs'.
>>>>
>>>> Am I going blind in my advanced years, or is this bit of seemingly vital
>>>> info actually on the missing list?
>>>>
>>>> Or better yet, since this is probably the result of an update, what
>>>> package can I have smart remove in order to stop this daily nagging by
>>>> cron?
>>>>
>>>> I also have noted that since this nagging started about 10 days ago,
>>>> that my logwatch report no longer contains a section listing kernel
>>>> bugs. Is this related?
>>>>
>>>> ---------- Forwarded Message ----------
>>>>
>>>> Subject: Cron <root at coyote> run-parts /etc/cron.daily
>>>> Date: Sunday 27 May 2007
>>>> From: Cron Daemon <root at coyote.coyote.den>
>>>> To: root at coyote.coyote.den
>>>>
>>>> /etc/cron.daily/bugzilla:
>>>>
>>>>
>>>> Can't connect to the database.
>>>> Error: Access denied for user 'mysql'@'localhost' (using password: YES)
>>>
>>> This is the relevent part of the message. It says it can't log in to the
>>> mysql database. It needs to log in to the mysql database. It tried to
>>> use a password but it did not work. You should find out why.
>>
>> 1. There is no installed user 'mysql', or at least no home dir
>> /home/mysql exists.
>>
>> 2. There is a password set for the user 'mysql' in the other default
>> script, which I think its reading because the message changed a bit when I
>> did set the password. I also changed the password to match in the
>> /etc/passwd file using the passwd -u mysql command.
>
>MySQL keeps its own database of users and their passwords (by default at
>least. I've never looked into whether that can be changed). Try reading
>up on mysqladmin which can change the MySQL users' passwords so that you
>can be certain you have the right password to log in with.
I did indeed do that, and I can su mysql, but typing the mysql shells name
still that I'm root and disallows the access.
The point is I think moot now because there isn't any use of me running a
bugzilla server that I know of, so I had smart nuke it. As the script that
triggered the error is now gone from /etc/cron.daily, I'd assume that is the
end of it. I don't use mysql for anything else, so I can also stop it.
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)
"Kill the Wabbit, Kill the Wabbit, Kill the Wabbit!"
-- Looney Tunes, "What's Opera Doc?" (1957, Chuck Jones)
More information about the fedora-list
mailing list