This morning I decided to try and make sure our Koha would support Unicode properly, following the instructions at: http://wiki.koha.org/doku.php?id=encodingscratchpad Since upgrading to MySQL 4.1.11 (using the Debian mysql-server-4.1 package) our Koha installation is behaving very strangely. 1. On the intranet I have to log in every time I go to a different page, each time it shows: Login Error You are accessing Koha from a different ip address! Please login again. 2. Only the 'kohaadmin' user (the MySQL user for Koha) seems to be able to log in. 3. Our NPL templates no longer load the stylesheets (both OPAC and intranet). In the HTML source it seems to be trying to load "/opac-tmpl/npl/en/includes/" (the directory the stylesheets are in). 4. Searching behaves normally and I can see the list of borrowers. It seems that Koha is able to connect to the database with at least some success. 5. There are no errors in the OPAC or Koha error logs. Does anyone have any suggestions what might have gone wrong? I have a backup of the MySQL 4.0 database, so I can roll back if necessary but then I'll lose Unicode support. Kevin -- Kevin O'Rourke ICT Coordinator, National Teachers' Institute, Kaduna, Nigeria 062 316972
OK, I've discovered the answer to my own question, it should be useful information for other people out there. The upgrading process from MySQL 4.0 to 4.1 changed the length of text fields!
1.
Login Error
You are accessing Koha from a different ip address! Please login again.
This is because the 'sessions' table had its 'ip' field truncated to 5 characters. The other problems had similar causes. I've got Koha working again by dropping all the tables in the Koha database and re-importing the data from my backup. The 'mysqldump' command defaults to creating backups that don't specify character encodings for the tables, so they've all defaulted to UTF-8 on import. I'm very glad I made that backup! -- Kevin O'Rourke ICT Coordinator, National Teachers' Institute, Kaduna, Nigeria 062 316972
Kevin O'Rourke <lists@...> writes:
OK, I've discovered the answer to my own question, it should be useful information for other people out there. The upgrading process from MySQL 4.0 to 4.1 changed the length of text fields!
Login Error You are accessing Koha from a different ip address! Please login again.
This is because the 'sessions' table had its 'ip' field truncated to 5 characters. The other problems had similar causes. I've got Koha working again by dropping all the tables in the Koha database and re-importing the data from my backup. The 'mysqldump' command defaults to creating backups that don't specify character encodings for the tables, so they've all defaulted to UTF-8 on import. I'm very glad I made that backup!-- Kevin O'Rourke ICT Coordinator, National Teachers' Institute, Kaduna, Nigeria 062 316972
Kevin - THANKS for your post! I ran into the same problem on a fresh install. Not being a MySQL expert how would I correct this problem if I don't have any backup files to leverage? THANKS in advance for any help you can provide! Glen
Glen wrote:
Kevin O'Rourke <lists@...> writes:
OK, I've discovered the answer to my own question, it should be useful information for other people out there. The upgrading process from MySQL 4.0 to 4.1 changed the length of text fields!
I ran into the same problem on a fresh install. Not being a MySQL expert how would I correct this problem if I don't have any backup files to leverage? THANKS in advance for any help you can provide!
Was that a fresh install of Koha, a fresh install of MySQL, or both? You shouldn't get that problem on a fresh Koha install, because it will create the tables with the correct field lengths. If it's a fresh Koha install followed by a MySQL upgrade then without a backup you've probably irretrievably lost some data. It's difficult to tell what, somebody who knows more about Koha's database tables and MySQL might be able to help. If you didn't have much data in your Koha system then I'd recommend reinstalling it _after_ making sure all your MySQL settings are as you want them. Alternatively you may have a slightly different problem from mine but with similar symptoms, if you can maybe describe in detail the steps that got you to where you are now that would help. Kevin -- Kevin O'Rourke ICT Coordinator, National Teachers' Institute, Kaduna, Nigeria 062 316972
Kevin O'Rourke <lists@...> writes:
Was that a fresh install of Koha, a fresh install of MySQL, or both?
You shouldn't get that problem on a fresh Koha install, because it will create the tables with the correct field lengths.
If it's a fresh Koha install followed by a MySQL upgrade then without a backup you've probably irretrievably lost some data. It's difficult to tell what, somebody who knows more about Koha's database tables and MySQL might be able to help.
If you didn't have much data in your Koha system then I'd recommend reinstalling it _after_ making sure all your MySQL settings are as you want them.
Alternatively you may have a slightly different problem from mine but with similar symptoms, if you can maybe describe in detail the steps that got you to where you are now that would help.
Kevin
It was a completely fresh install of Koha and all its pre-requisites on Windows XP SP2; followed the directions in the Koha for Windows install guide. Everything seemed to install OK with the end result being that I could access both the OPAC and the Intranet but on the Intranet I have to re-authenticate every time I try to access a new screen. Also after entering a patron and assigning them a username/password with superlibrarian privileges I'm unable to to login with those credentials to the Intranet. From your initial description it sounds like the same/similar problem. Just don't know how to try and fix it? Any thoughts/ideas would be appreciated. Glen
Glen wrote:
Kevin O'Rourke <lists@...> writes:
Was that a fresh install of Koha, a fresh install of MySQL, or both?
It was a completely fresh install of Koha and all its pre-requisites on Windows XP SP2; followed the directions in the Koha for Windows install guide. Everything seemed to install OK with the end result being that I could access both the OPAC and the Intranet but on the Intranet I have to re-authenticate every time I try to access a new screen. Also after entering a patron and assigning them a username/password with superlibrarian privileges I'm unable to to login with those credentials to the Intranet. From your initial description it sounds like the same/similar problem. Just don't know how to try and fix it? Any thoughts/ideas would be appreciated.
Try using the MySQL command line client (open a command prompt, change to the MySQL bin directory [probably "C:\Program Files\MySQL\MySQL Server 5.0\bin\"])": mysql -u <Koha admin user> -p Enter your Koha admin password. Then type: \u <Koha database name> describe sessions; You should see something like: +-----------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------+--------------+------+-----+---------+-------+ | sessionID | varchar(255) | | PRI | | | | userid | varchar(255) | YES | | NULL | | | ip | varchar(16) | YES | | NULL | | | lasttime | int(11) | YES | | NULL | | +-----------+--------------+------+-----+---------+-------+ 4 rows in set (0.00 sec) The important thing is that the numbers after each field type are the same as shown here. My problem was caused by the MySQL upgrade changing the IP field to length 5, too short for an IP address so the session information couldn't be stored and I had to keep logging in. It sounds like your problem isn't quite the same as mine, more that your Koha install went wrong at some point. Maybe someone with experience of Koha on Windows can help? Kevin -- Kevin O'Rourke ICT Coordinator, National Teachers' Institute, Kaduna, Nigeria 062 316972
THANKS! May try re-installing again in case like you say something fouled on my initial attempt. Glen
Glen a écrit :
It was a completely fresh install of Koha and all its pre-requisites on Windows XP SP2; followed the directions in the Koha for Windows install guide. Everything seemed to install OK with the end result being that I could access both the OPAC and the Intranet but on the Intranet I have to re-authenticate every time I try to access a new screen. Also after entering a patron and assigning them a username/password with superlibrarian privileges I'm unable to to login with those credentials to the Intranet. From your initial description it sounds like the same/similar problem. Just don't know how to try and fix it? Any thoughts/ideas would be appreciated.
Glen
Koha Authentication system relies on Cookies. Does your browser accept them ? My 2 cts. -- Henri-Damien LAURENT
participants (3)
-
Glen -
Henri-Damien LAURENT -
Kevin O'Rourke