Thank you Chris for your reply. I guess there must have been some pressing need to present both MySQL users and koha users in the same interface/list. I understand the concept of creating a 2nd super-user and perform any operations from that profile; in fact I had already created such a user so that I could get myself out of trouble should I forget/mistype the kohaadmin pass. I suppose I'll have to log-in to MySQL with the new pass (or as a root) and change the kohaadmin pass back to the previous value. Two more notes to be added to my wishlist: a) There ought to be a clear way to change the kohaadmin password nevertheless, for what good is a password for, if it is known by everyone? b) There should be a warning when someone - with the proper rights - tries to change the kohaadmin password via the administrative interface. Then again it may well be a joke on koha newbies and such a warning would spoil the fun ;-) kind regards, Manos Petridis ----- Original Message -----
From: Chris Cormack <chris@bigballofwax.co.nz> To: Manos Petridis <egpetridis@yahoo.com> Cc: "koha@lists.katipo.co.nz" <koha@lists.katipo.co.nz> Sent: Sunday, August 19, 2012 11:37 AM Subject: Re: [Koha] kohaadmin password change
One further question: I recently changed the kohaadmin password, using the koha admin interface (i.e. for patron #1). This change was necessary in order to be able to perform catalogue-ing off-site, connecting to port 8080 from any Internet-connected browser. I did not change the operating system user password, nor the MySQL user
On 19 August 2012 20:33, Manos Petridis <egpetridis@yahoo.com> wrote: password.
One would expect that patrons and their passwords were stored in the MySQL
koha database itself, so koha functionality would remain as before.
Real patrons are, kohaadmin is not a real patron, but the mysql user.
For help, please send mail to the webmaster (webmaster@koha), giving this error message and the time and date of the error.
when I try the admin interface, and
Software error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /home/koha/kohaclone/C4/Context.pm line 758. Compilation failed in require at /home/koha/kohaclone/C4/Auth.pm line 31. BEGIN failed--compilation aborted at /home/koha/kohaclone/C4/Auth.pm line
Compilation failed in require at /home/koha/kohaclone/mainpage.pl line 25. BEGIN failed--compilation aborted at /home/koha/kohaclone/mainpage.pl line
To my surprise, I can't connect to koha, even from the same LAN. From the server I get the following errors
Software error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /home/koha/kohaclone/C4/Context.pm line 758. Compilation failed in require at /home/koha/kohaclone/C4/Auth.pm line 31. BEGIN failed--compilation aborted at /home/koha/kohaclone/C4/Auth.pm line
Compilation failed in require at /home/koha/kohaclone/opac/opac-main.pl line 22. BEGIN failed--compilation aborted at /home/koha/kohaclone/opac/opac-main.pl line 22. For help, please send mail to the webmaster (webmaster@koha), giving this error message and the time and date of the error.
when I try the OPAC interface.
Have the errors above anything to do with the password change? I repeat, I haven't changed (yet) the operating system user password, nor the MySQL user password, or thet of the MySQL root.
The only time you should ever use the kohaadmin user (which is the mysql user). Is to create a user in Koha, and give it super librarian permissions, and to run the web installer.
Never try to do things in Koha as the mysql user (which is what kohaadmin or whatever user you set up in mysql is).