It uses mysql_root_password
But you need to change the root pw in the logger instance to whatever it is in the main instance.
hrm.
It is. I used the same pwds for both instances.
I'll do it again to make sure i didn't mess it up.
Yeah, the update didn't change anything....
mysql> update user set password=PASSWORD('frankjones') where user='root';
Query OK, 0 rows affected (0.00 sec)
Rows matched: 3 Changed: 0 Warnings: 0
So now I'll go back and see if maybe i made it somethine else in the other instance and just had a major brain fart.
Thanks
Man, I hate to keep posting. I'm really sorry for bugging you guys.
anyway... neither command had any rows to update. AND... I was running without the --skip flag and logged in as logmysql -u root -p mysql
to run those commands and used my password, so I think that the password is totally sorted on the mysql side. I'll reset it again in zmlocalconfig using -f and see if it helps.
Note the 0 rows affected.
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)
mysql> update user set password=PASSWORD('frankjones') where user like 'root%';
Query OK, 0 rows affected (0.00 sec)
Rows matched: 3 Changed: 0 Warnings: 0
You'll need another flush after you manually set the password.
but the update didn't change any rows at all. there were no privileges to flush.
i'll do it again anyway at your request, but am pretty sure that's not the problem
Earlier today I declared you a hero. Now you truly are. That was the last bit. The setting i couldn't find alone. Thanks so freaking much. I'm truly truly amazed by the responsiveness of these forums.
[zimbra@mail ~]$ zmcontrol status
Host mail.tlogic.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
snmp Running
spell Running
There are currently 1 users browsing this thread. (0 members and 1 guests)