eZ Community » Forums » Developer » Fatal error while login fixed by itself
expandshrink

Fatal error while login fixed by itself

Fatal error while login fixed by itself

Wednesday 15 December 2010 2:14:53 pm - 6 replies

I had installed and configured ezpublish. After I used it for few days a fatal error screen was displayed when I tried to login. I searched a lot to find a way to resolve this problem. On searching I found that this is a pretty common error that people face and most of the answers asked the user to delete the cache manually etc. I tried all those answers but I couldn't get rid of this error.

And a day later, I try to login and it works. I wonder how the error was fixed all by itself. I am curious to know why this occured and how the error was fixed. Could anyone please let me know?

Thanks.

Modified on Wednesday 15 December 2010 2:18:45 pm by Pavanred

Wednesday 15 December 2010 2:56:33 pm

Could be ezsession table issue, where you had filled up your ezsession table so new sessions couldn't be created and someone or php session gc being triggered somehow manually or automatic that fixed it.
In recent versions there are both scripts and cronjobs to purge sessions manually if your on a Debian/Ubuntu based system where this doesn't work automatically.

Wednesday 15 December 2010 3:51:37 pm

Could be ezsession table issue, where you had filled up your ezsession table so new sessions couldn't be created and someone or php session gc being triggered somehow manually or automatic that fixed it.
In recent versions there are both scripts and cronjobs to purge sessions manually if your on a Debian/Ubuntu based system where this doesn't work automatically.

I had tried that too. One of the answers to a similar thread suggested truncating the ezsession table. I remember truncating the ezsession table but that hadn't helped then.

I am running the latest version of ezpublish (4.4) and I am running it on windows. So, I doubt if this caused the error. Are there any other possible causes for such an error.

Monday 20 December 2010 11:25:10 am

I think i found the reason for this fatal error while login. When the login fails and this error message is dispalyed, the error logged is -

Query error (1146): Table 'ezfind_elevate_configureation' doesn't work. Query : Delete FROM ezfind_elevate_configuration where contentobject_id = '111'

An issue with ezfind causes this error. I can disable the ezfind extension but as I cannot login, I am unable to disable the ezfind extension.

Can anyone tell me which configuration file I have to edit to disable extesnions?

Modified on Monday 20 December 2010 11:26:07 am by Pavanred

Monday 20 December 2010 12:12:50 pm

Why don't you add these tables? They should be in the sql directory of ezfind. I think they were added with the last ezfind upgrade. Probably someone forgot to do this when upgrading.

Monday 20 December 2010 12:36:43 pm

Indeed, the ezfind_elevate_configuration table was added in eZ Find 2.1. One can find the dump in the master branch there :
https://github.com/ezsystems/ezfind/blob/master/sql/mysql/

Cheers,

Monday 20 December 2010 1:47:46 pm

Thanks. This did work. I added the ezfind_elevate_configuration table. This did solve that error but now i get a different one. The error that I get now is -

eZFindElevateConfiguration::pushConfigureationToSolr: An unknown error occured in updateing Solr's elevate configuration.

I searched to find a fix for this error and I found that I need to find an update for Solr too. I am looking for the update. Meanwhile, can help me find an update for solr?

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from