Forums / Install & configuration / eZp 3.3 JUST WON'T RUN after installation - Kernel (50) error (Virtual Host setup)

eZp 3.3 JUST WON'T RUN after installation - Kernel (50) error (Virtual Host setup)

Next topic

Author	Message
Arno van Vulpen	Monday 26 January 2004 4:23:24 pm PLEASE HELP, I'm having the same problem with this 'Kernel (50)' error. While searching "Kernel (50)" returned 61 results, I found NO ANSWERS OR SOLUTIONS ? PLEASE, THIS SEEMS TO BE A MAJOR PROBLEM, CAN YOU HELP TO SOLVE THIS eZ Publish Moderators or ANYONE else ?? Is this a bug in eZ Publish 3.3 ?? Thank you so much in advance for any help! Best regards, Arno
Bård Farstad	Tuesday 27 January 2004 1:12:35 am Arno, the kernel error 50 means that you don't have access to the database. Turn on debug information to get more info about this. You need to check your database settings. --bård Documentation: http://ez.no/doc
Arno van Vulpen	Tuesday 27 January 2004 4:44:57 am Thank you Bård. I tried and succeeded once to get rid of the error, but then it came back again. Any other scripts work great, no problem at all here. Could it perhaps have to do with the memory? It was set at 8 MB for PHP. I changed it though in the .htaccess file, but don't know if that works on my server (which is not my own). I'd like to try the setup once again, last time, to see if it will work now. Two clients of mine want a CMS for their site, and I'm testing if eZ publish is a good option. So far it has only given troubles... :-( * Anyway, could you tell me how to re-install eZ publish 3.3 ?? * Do I need to remove all files and reupload everything again ? Or is there a faster way ? (uploading to USA took over an hour from here!) Thanks again in advance for any replies.
Nick Woods	Tuesday 27 January 2004 5:09:20 am This happend to me - it turned out that the installer couldnt create the site.ini. files due to access permissions (it handles this very badly indeed) if you are on linux just delete the ezpublish directory and reinstall the software. The cd to the ezpublish directory and type this chown -R apache.apache * chmod -r 777 var it may be a bit heavyhanded but it worked for me.
Arno van Vulpen	Tuesday 27 January 2004 5:58:02 am Thanks for the quick help Nick. Do you mean I need to remove and re-upload all files? How can I run the commands you mentioned... I'm using FTP (Dreamweaver MX) ? A normal 777 chmod command here would be: site chmod 777 /public_html/cms When I try chown -R apache.apache * OR site chown -R apache.apache * OR site chown -R apache.apache /public_html/cms/ OR any other variation I get: 500 'SITE CHOWN' not understood Thanks again.
Maarten Holland	Tuesday 27 January 2004 9:34:12 am Sounds like it's a public server and you aren't allowed to change the owner?