CiviCRM Community Forums (archive)

Now I can't login anymore...into joomla:

Duplicate entry 'j77lq65g7t3b28dstupsot61gksmv9vh' for key 'PRIMARY' SQL=INSERT INTO `jos_session` (`session_id`, `client_id`, `time`) VALUES ('j77lq65g7t3b28dstupsot61gksmv9vhc7r3ssvcqik1rdfb7ma0', 1, 1351472823)
I deleted the DB & website several times, restored, still no chance to log in anymore. I think it's too late for my brain, or god hates me 

YYYYYYYYEEEEEEEEEEEAAAAAAAAHHHHHH 

The upgrade finally worked.

So what were the problems?
- Directory rights in website too restrictive (the script should REALLY check this and warn before the upgrade, or at least give an error, not [] as a message)
- SUPER rights in DB needed, despite MySQL 5.1.49
- Joomla 1.6 has DB table `jos_session` with field session_id varchar(32), while it MUST be varchar(64)

With this it works. Hope this thread helps others. Cheers! 

can u expand a bit more on the directory rights being too restrictive

Until now, the webserver had no rights to write too Joomla and it's subdirs. The system was working for 1-2 years now, this was no problem. But now it seems the upgrade had to write somewhere. When I installed the com_civicrm Extension, there were some on-screen errors about needed rights to some subdirs (e.g. components & plugins), and I fixed all that. The upgrade of files worked then, but obviously the part that installs the DB needed some other right too, and this has not been checked by the installer. As soon as I gave write rights to Apache for all subdirs, the DB upgrade started to run.

also, 4.2 and later have been tested only with j! 2.5. so i dont think we've hit the session_id limit. seems more like a j! issue to me rather than a civi issue

Yes, this is a Joomla issue, I just wanted to document it as a reference for other who might find this thread when they have the same problem.
I'm puzzled though as to why Joomla ever worked before? I had done a dump of the DB, then reinstalled that. It worked before but not afterwards. How could it ever have worked, when the field definition was for 32 chars, but uses more? Very strange.

Anyway, we're on 4.2.4 now, so all good.
Thank you for the great hints and support.