Dizkus

Have you tried all of these procedures and you still receive the message, 'Session initialisation failed'? Here's another solution that worked for me.

I tried optimizing and then repairing the 'session_info' table. I tried emptying the table. I tried dropping and creating it. I looked at my 'config.php' file to make sure that the database name, username, and password was correct. It was all correct.

I downloaded the PostNuke Swiss Army Knife (PSAK), and thought that I'd try out those options. When I clicked on 'Theme Reset', it gave me an error: 'Database Error 1226 Occurred -- User 'basecamp_pn' has exceeded the 'max_questions' resource (current value: 50000)'.

That made me think about looking in phpMyAdmin at the list of database users. I decided to delete the database USER that was tied to PostNuke, and then added the user right back in the list as it was before. This seemed to clear or reset this 'max_questions' error--at least temporarily. I can't imagine that it is a permanant solution. Here is a post from another person with this error: http://forums.postnu…xquestions+resource I'll check with my host to see what they say.

At any rate, if all else fails, try deleting and then adding the database user in phpMyAdmin to 'cure' the 'sessions' problem.

I too have been struck by the "Sessions" problem. I am a total rookie and totally stumped. I run two PostNuke sites and am considering copying the sessions_info table from one to the other.

Anyone know if this will cause huge damage. Does anyone know how I do this in phpMyAdmin? Desperate for help on where to start!

The weeks before I was receiving pnSecurity email for Porn posted on the Article Comments, thought it may be a biproduct of the webporn industry? :?

I also started to get the "session initialization failed" error , can anyone please guide me exactly on how to try and repearing the 'session_info' table thru the myphpadmin util?
Thanks

Someone give me this solution..
You can try this.. but remember to delete it after it work..
Try at your own risk..

1. Create new ***.php file




2. Save..upload and run it at your root site...

Tried the above file and still a no go.

Would it be possible to create something in PHP that parses my homepage for the "Session initialisation failed" text, then drops/adds the sessions_info table if it detects the text?

Place the file outside the web root for added security, then you could tell the PHP script to run every hour (or whatever) via a cron job. Maybe it will still run if someone does something like posts "Session initialisation failed" on the forums, but this isn't a very common phrase so it shouldn't be a big deal.

I'm going on a trip for a week, and I'll be unable to check on my site since I won't have internet access. I've had the Session initialisation failed error twice in the past 2 weeks. It's a nasty feeling to wake up in the morning to see that your site (and income stream) has been down for 6 hours... you know it when you check your e-mail and there are 600 messages from your pnForum installation that say "Lost connection to mySQL server during query."

I'm positive it will again be an issue while I'm gone. I obviously want my website to be operational even while I'm away, so I need some sort of failsafe that will keep things operational for me.

edit: better yet, couldn't you just make the site drop/add the sessions_info table instead of producing the "Session initialisation failed" error in the first place?

Just a note for anyone who is still having this problem after trying all the suggestions. I had this problem intermittently for a while and none of the suggestions worked until I saw someone mention a possible query limit from the hosting provider. That was it! Deleting/readding the MySQL database user instantly fixed the problem (until a mass of queries came and I blasted past the limit again).

This is just something you might want to check into. I'm planning to move to another provider, but for now I just created a bunch of users and used the hack to randomize the user each time.

MARKWEST solutions works perfectly in my case.

But is there a way to better secure PN so this wont happen again???

It has happened several times and I am just getting a bit anoyed at this.

Thanks,

--
"I'm an idealist. I don't know where I'm going, but I'm on my way."

HI, I had the same Session initialisation failed issue and resolved it by reapairing the session_info table using phpMyAdmin. The syntax is REPAIR TABLE nuke_session_info

Hope this helps - it worked instantly.