blog documentation FAQ followers forum marketplace services youtube

CRI: Query Error since updating to 5.3.0b9

The Jamroom Network » Forum » Using Jamroom » Page » CRI: Query Error since updating to 5.3.0b9
iamtimbo
@iamtimbo
10 years ago
301 posts
Hello, all, hope you had a good Christmas.....

Since updating the System Core to 5.3.0b9, I can no longer log in, or carry out updates to any other modules. Almost anything, including an integrity check, generates the following error:

CRI: Query Error: Data too long for column 'session_data' at row 1

Any thoughts....?

updated by @iamtimbo: 04/10/16 12:01:14PM
iamtimbo
@iamtimbo
10 years ago
301 posts
Still locked out - can I run an integrity check from 'outside', somehow?
douglas
@douglas
10 years ago
2,797 posts
I've seen this error message when I had a bad config.php file for a skin, if you've mad any modifications to your skins config.php file, try reverting them back and see if that fixes it for you.

If you didn't, and your using a cloned or custom skin, you might try going into your database and switching the skin to a unmodified default skin to see if that fixes your issue.

The active skin is set in the jr_jrcore_settings > jrCore > active_skin

Hope this helps!


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos
iamtimbo
@iamtimbo
10 years ago
301 posts
Hi, Douglas,

Thank you for that - I certainly haven't done anything to the files - it happened after the update.

I am using the Slate skin, that I've modified various templates for, but not a custom one, per se. Unfortunately, if I try to change the skin in the ACP, I just get the error as above.....

Tim
douglas
@douglas
10 years ago
2,797 posts
You'll want to change the active_skin in your database using phpMyAdmin or whatever your hosting control panel has setup to modify your MySQL database.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos
iamtimbo
@iamtimbo
10 years ago
301 posts
Ah - sorry - misunderstood. I'll have a look. Not delved in there before....
iamtimbo
@iamtimbo
10 years ago
301 posts
Hi, there - I managed to change that value - much simpler than I imagined, and the site loaded up in the Elastic skin, as I'd specified. I thought I'd run an integrity check at that point, but once again, I got the Query Error as above.

I have returned the site to the Slate skin to keep up appearances.....not sure what my next move should be, though.

EDIT: I have inadvertently discovered that this only affects me as an admin - normal site users are unaffected it seems.
updated by @iamtimbo: 12/28/15 04:28:09PM
michael
@michael
10 years ago
7,768 posts
iamtimbo:....not sure what my next move should be, though....

Go back to the root cause:
Quote: CRI: Query Error: Data too long for column 'session_data' at row 1

Is there any error information in the debug log, activity log, error log? is there a ! mark next to that in the activity log with more information.

Need to track the clues given back to the source of the problem to locate the issue.

Alternatively: Outline steps that we can take here to see the issue, so we can fix it here.
iamtimbo
@iamtimbo
10 years ago
301 posts
Hi, @michael and @douglas, sorry for the lack of information above. It's been four months since I last had the time to spend on my site, and clearly I've had Jamroom brain fade.....

Looking at the Activity and Error logs (I can't access the Debug log, as it generates the error), it looks to me that on certain occasions the system seems to want to list all profiles linked to my admin one; I have over 43,000, and I guess that's too much for it as of this update!

I've added a screenshot of the log detail - it continues in that vein for pages and pages....
image.jpg
image.jpg  •  735KB


updated by @iamtimbo: 12/29/15 01:53:23AM
brian
@brian
10 years ago
10,148 posts
The session_data field can only hold up to 64K of data - this error means that MORE than 64K of data is trying to be saved in your session table for YOUR session.

For the next beta release I've made it so it can handle up to 16 megabytes of data - that should be enough to handle your unique situation.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
iamtimbo
@iamtimbo
10 years ago
301 posts
Thanks, Brian, that makes sense. My mum always said I was special....

As I won't be able to do the jrCore update through the marketplace, I assume I can do it through FTP?
iamtimbo
@iamtimbo
9 years ago
301 posts
Hi there again - Happy New Year!

Just wondering if there is a temporary workaround for this, as at the moment I can't do anything very much on the site that doesn't cause the error. If nothing else, I need to be editing profiles, and it won't allow me to do that at the moment.

Cheers!
brian
@brian
9 years ago
10,148 posts
iamtimbo:
Hi there again - Happy New Year!

Just wondering if there is a temporary workaround for this, as at the moment I can't do anything very much on the site that doesn't cause the error. If nothing else, I need to be editing profiles, and it won't allow me to do that at the moment.

Cheers!

Update to the latest User Accounts module and this should be fixed. If you can't log in then you'll need to manually go into your MySQL and change the "session_data" column in the jr_jruser_session table from "TEXT" to "MEDIUMTEXT".

Let me know if that helps.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
iamtimbo
@iamtimbo
9 years ago
301 posts
Thanks ever so much, Brian!