Hello Anders, Sorry, I did not go through the end of your message.
You also have a problem with psql which is, I think, the equivalent of mysql for PostgreSQL. Do you need PostgreSQL? If not, you should deactivate it. For your problem with mysqladmin, most probably specifying the switch --host with the hostname associated with your "binding" will fix the problem. Regards, Bernard On Friday 07 November 2003 15:15, Bernard Clement wrote: > Hello Anders, > > NOTE: I am actually using SuSE 8.2 Pro Edition. However, those CRON jobs > seem to be at the same place irrelevant of the distro (RedHat or SuSE). > Therefore, I doubt that SuSE Linux Standard Server 8 has changed that. > > If the problem occurs once a day then it is within the script > /etc/cron.daily/logrotate > > That script is used to "rotate" the various log files in order that they do > not fill up the hard disk. > > The script logrotate will activate all the scripts in /etc/logrotate.d and > one of them is called mysql. You will find within that script the > activation of mysqladmin that generate the error. > > I cannot really tell what you have to do to have mysqladmin to work > correctly. Probably you will have to specify a user with some kind of > "root" permission. > > I hope that I have been helpful. > > Regards, > > Bernard > > On Friday 07 November 2003 14:47, Anders Norrbring wrote: > > [Second try, the first one rendered a few hints that didn't help] > > > > > > I've set up a new MySQL server on a box with multiple IP addresses, and > > the SQL server only binds to ONE of these addresses. > > > > Also, I've been changing some user rights in the SQL setup, and now I get > > a cronjob error, related to user rights... My big problem is that I > > don't even know where I should start looking for it. > > > > The system and MySQL setup is in all other aspects the distributed > > versions from the SuSE Linux Standard Server 8 distribution, based on > > United Linux 1.0. > > > > The cronjob error mailed to me is the following: > > > > > > SCRIPT: clean_catman, OK. > > SCRIPT: clean_core, OK. > > SCRIPT: do_mandb, OK. > > SCRIPT: logrotate exited with RETURNCODE = 1. > > SCRIPT: ouput (stdout && stderr) follows > > > > /usr/bin/mysqladmin: refresh failed; error: 'Access denied for user: > > '@localhost' (Using password: NO)' > > error running postrotate script > > Reload syslog service..done > > SCRIPT: logrotate > > ------- END OF OUTPUT > > > > > > SCRIPT: slots, OK. > > SCRIPT: ouput (stdout && stderr) follows > > > > psql: could not connect to server: No such file or directory > > Is the server running locally and accepting > > connections on Unix domain socket "/tmp/.s.PGSQL.5432"? > > SCRIPT: slots > > ------- END OF OUTPUT > > > > > > Can somebody please help me out here? If the /usr/bin/mysqladmin tries > > to use a user from localhost (any) then it fails, because "localhost" > > doesn't have access to the SQL server... What user should be granted > > access (and from where) to make this job work correctly? > > > > Anders Norrbring > > > > Norrbring Consulting > > Halmvägen 42 > > SE-691 48 Karlskoga > > SWEDEN > > > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: > > http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
