Crashed Main Node

Next topic

Author	Message
Lars Henning Müller	Sunday 04 December 2005 11:56:52 pm Hi everybody, I think my main node is crashed. Two users were logged in with the same user an edited the main node at the same time. One of these users canceled the edit modus. Now when I want to login at the admin page, I´m getting the error message "Kernel 20 - the requested page couldnt displayed"! So I think my main node is crashed. Does anybody knows what I can do, to get my main node back? Is there a possibillity instead of a DB-dump?
Gurudutt Verma	Tuesday 06 December 2005 2:08:52 am Hi Lars This shouldn't be a problem, Could you provide more debug output, error log from /var/log directory. can you access user site ??
Lars Henning Müller	Tuesday 06 December 2005 6:11:19 am Yes I can access the user site. The error.log isnt really helpful because it shows me data from may 2005 :( I have set ín the site.ini.append.php the [SiteAccessSettings] "CheckValidity" from false to true and had done the setup wizzard again. I have choosen to "Leave the data and do nothing" in the databasechoise! So I have my old data again. Now I can access the admin interface and I can see the content actually :) But I´m getting the same message as before when I want to add, edit something or just want to switch to the setup or design-link. So I have my RootNode ID 2 again but the message still says : - The address was misspelled. Try changing the URL - The name of the module was misspelled. Try changing the URL - There is no <"root node name"> module available on this site. - The site is using URL matching to determine which siteaccess to use, but the name of the siteaccess is missing from the URL. Try to add the name of the siteaccess, it should be specified before the name of the module.

Author

Message

Sunday 04 December 2005 11:56:52 pm

Hi everybody,

I think my main node is crashed. Two users were logged in with the same user an edited the main node at the same time. One of these users canceled the edit modus.
Now when I want to login at the admin page, I´m getting the error message "Kernel 20 - the requested page couldnt displayed"!
So I think my main node is crashed.
Does anybody knows what I can do, to get my main node back? Is there a possibillity instead of a DB-dump?

Gurudutt Verma

Tuesday 06 December 2005 2:08:52 am

Hi Lars

This shouldn't be a problem,

Could you provide more debug output, error log from /var/log directory.

can you access user site ??

Lars Henning Müller

Tuesday 06 December 2005 6:11:19 am

Yes I can access the user site.

The error.log isnt really helpful because it shows me data from may 2005 :(

I have set ín the site.ini.append.php the [SiteAccessSettings] "CheckValidity" from false to true and had done the setup wizzard again. I have choosen to "Leave the data and do nothing" in the databasechoise! So I have my old data again.

Now I can access the admin interface and I can see the content actually :) But I´m getting the same message as before when I want to add, edit something or just want to switch to the setup or design-link. So I have my RootNode ID 2 again but the message still says :

- The address was misspelled. Try changing the URL
- The name of the module was misspelled. Try changing the URL
- There is no <"root node name"> module available on this site.
- The site is using URL matching to determine which siteaccess to use, but the name of the siteaccess is missing from the URL. Try to add the name of the siteaccess, it should be specified before the name of the module.

eZ debug

Timing:	Jan 19 2025 04:27:54
Script start
Timing:	Jan 19 2025 04:27:54
Module start 'layout'
Timing:	Jan 19 2025 04:27:54
Module start 'content'
Timing:	Jan 19 2025 04:27:54
Module end 'content'
Timing:	Jan 19 2025 04:27:54
Script end

Main resources:

Total runtime	0.6545 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0070	590.1250	153.4375
Module start 'layout'	0.0070	0.0036	743.5625	39.3594
Module start 'content'	0.0106	0.6422	782.9219	504.5938
Module end 'content'	0.6528	0.0017	1,287.5156	12.1875
Script end	0.6544		1,299.7031

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.5311	16	0.0002
Check MTime	0.0014	0.2070	16	0.0001
Mysql Total
Database connection	0.0009	0.1381	1	0.0009
Mysqli_queries	0.6064	92.6485	57	0.0106
Looping result	0.0005	0.0825	55	0.0000
Template Total	0.6237	95.3	2	0.3119
Template load	0.0019	0.2892	2	0.0009
Template processing	0.6218	95.0118	2	0.3109
Template load and register function	0.0002	0.0315	1	0.0002
states
state_id_array	0.0014	0.2182	1	0.0014
state_identifier_array	0.0008	0.1182	2	0.0004
Override
Cache load	0.0015	0.2305	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.1351	2	0.0004
Fetch class attribute name	0.0009	0.1354	4	0.0002
XML
Image XML parsing	0.0007	0.1105	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0011	4	0.0000
General
dbfile	0.0008	0.1251	16	0.0001
String conversion	0.0000	0.0017	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs