Forums / Install & configuration / Kernel error 50

Kernel error 50

Author Message

Tomas Ahlbeck

Saturday 04 September 2004 4:55:36 pm

When I try to log in after installing EZPublish I get this message:
kernel (50)

* No database connection could be made, the system might not behave properly.

Very strange, since in the installation process it said System OK and so on.

I have not been able to change safe mode from on to off yet, but that can't be the problem, can it?

Can I eventually fix this in some config file on the server?

Tomas Ahlbeck

Sunday 05 September 2004 3:01:16 am

Hi.

Sorry, found many other entries here in the Forum about this, but nothing that made any change with my problem.
have used shell access to change permissions, also looked in the database. The database is installed, so that is not the problem.
All accessess are 777 as suggested.
Will now make a new clean install. if it does not work - is it something on the server side?
maybe EZPublish can't run on my ISP?
(It ought to though, they have similar services for their customers)

****
OK, I tried the new install, same problem. Does not work. Kernel 50 error again.
anyone has an idea what to do that i have not done already (see above) ?
No point in uninstalling and installing.
GGod thing though - I managed to move parts of my PostNuke database in to EZPublish database. Don't know if it worked though since EZPublish cabn't findthe database ;-)

/TA

Ole Morten Halvorsen

Monday 06 September 2004 7:40:14 am

Could you try setting <b>DebugOutput=enabled</b> in your site.ini? This will hopefully give you some more information about what's wrong.

Ole M.

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

Tomas Ahlbeck

Monday 06 September 2004 11:06:29 am

Hi Ole and also Terje.
I have found the error now. The webinstaller did not create the db-settings in site.ini, but I have done that now. Also i ran debug and found a lot of yellow and red lines. Phew....

Anyway - now i will try to find forum entries on the problem that followed - that there is only possible to enter the admin pages,not the visitors pages.

But that problem will be solved too, sooner or later ;-)

Thanks guys.

Ole Morten Halvorsen

Thursday 09 September 2004 12:51:16 am

Tomas,

Glad everything worked out.

Ole M.

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

eZ debug

Timing: Jan 19 2025 09:09:46
Script start
Timing: Jan 19 2025 09:09:46
Module start 'content'
Timing: Jan 19 2025 09:09:46
Module end 'content'
Timing: Jan 19 2025 09:09:46
Script end

Main resources:

Total runtime0.0264 sec
Peak memory usage2,048.0000 KB
Database Queries4

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0074 588.9453180.8438
Module start 'content' 0.00740.0123 769.789197.7578
Module end 'content' 0.01980.0065 867.546974.7031
Script end 0.0263  942.2500 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00228.4122120.0002
Check MTime0.00103.9415120.0001
Mysql Total
Database connection0.00072.496210.0007
Mysqli_queries0.003713.861440.0009
Looping result0.00000.114020.0000
Template Total0.006022.610.0060
Template load0.00093.338310.0009
Template processing0.005119.278110.0051
Override
Cache load0.00062.256610.0006
General
dbfile0.00186.7652100.0002
String conversion0.00000.034430.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs