Constant critical errors in system.log #3507

[da Silva]

This error is still a open subject on GitHub...could someone help us please?

Ver: 2.1.5 - Win 7, Apache 2.4, PHP 7.0.16, MySQL 5.7.17

If i click on Stores > Configuration ...The Error screen popup. 

If i click on Products > Catalog...The Error screen popup.

Critical errors constantly logged in var/log/system.log:

[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'global_notices' element cannot be added as child to 'global.notices', because the latter doesn't exist [] []

[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'logo' element cannot be added as child to 'header', because the latter doesn't exist [] []

[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'global.search' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'user' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'menu' element cannot be added as child to 'page.menu', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'breadcrumbs' element cannot be added as child to 'page.breadcrumbs', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'formkey' element cannot be added as child to 'page.formkey', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'page.title' element cannot be added as child to 'main.top', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'messages' element cannot be added as child to 'page.messages', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'page.actions.toolbar' element cannot be added as child to 'page.main.actions', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'legal' element cannot be added as child to 'footer', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'system_messages' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'unread_system_messages' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'notification_window' element cannot be added as child to 'notifications', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'notification.messages' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'header.inner.left' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'header.inner.right' element cannot be added as child to 'header', because the latter doesn't exist [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'logo' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'logo', but their parents are different: 'header' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'user' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'page.actions.toolbar' tries to reorder itself towards '', but their parents are different: 'page.main.actions' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'system_messages' tries to reorder itself towards '', but their parents are different: 'notifications' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'unread_system_messages' tries to reorder itself towards 'system_messages', but their parents are different: 'notifications' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'notification.messages' tries to reorder itself towards 'user', but their parents are different: 'header' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'header.inner.left' tries to reorder itself towards '', but their parents are different: 'header' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'header.inner.right' tries to reorder itself towards 'header.inner.left', but their parents are different: 'header' and '' respectively. [] []
[2017-03-06 17:23:12] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and '' respectively. [] []
[2017-03-06 17:23:33] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2017-03-06 17:23:33] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2017-03-06 17:23:33] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []
[2017-03-06 17:25:01] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2017-03-06 17:25:01] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2017-03-06 17:25:01] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []
[2017-03-06 17:25:26] main.CRITICAL: Broken reference: the 'header' tries to reorder itself towards 'global.notices', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2017-03-06 17:25:26] main.CRITICAL: Broken reference: the 'page.breadcrumbs' tries to reorder itself towards 'notifications', but their parents are different: 'page.wrapper' and 'notices.wrapper' respectively. [] []
[2017-03-06 17:25:26] main.CRITICAL: Broken reference: the 'global.search' tries to reorder itself towards 'notification.messages', but their parents are different: 'header.inner.right' and 'header' respectively. [] []

[Sunil_jangir]

Hello All ,

I am facing this issues also. Can any tell us solutions of this issues. waiting quick resposne

[Ikubod]

This looks to be one of Magento's lovely errors that are mostly ignored. Take a look at the thread for this issue: https://github.com/magento/magento2/issues/3507

It looks like they've finally created a fix for this in 2.3, but until it releases it seems like we're expected to just deal with it. 

If it's not affecting anything working on your website, just pretend that log doesn't exist until you can get updated to 2.3.

Wish I had a better answer for you, but I'm also in the same boat with these errors.

[itmultimobd453]

Hi, have you found any solution for this eventually?

The same in Magento 2.4, they are INFO, not CRITICAL, but it makes the logs unusable.

[chatroomwef409]

Reason 1.
The people keep forgetting to remove "before" or "after" attributes from blocks which have been moved to another parent, so these attributes are no longer needed. Internal ticket in process MAGETWO-5410 and we'll take care of old references in the near future.

Reason 2.
To illustrate we can take
These references generally (if they exist at all) reside typically in default.xml files (so they will be applied to all pages , without exceptions) While the container "sidebar.additional" is added via 2columns-left.xml layout only. Also, on pages on which an alternative layout is employed the reference can lead to nowhere there will be a critical errors logged (while this isn't a problem at all Chatroom ).

The tricky thing is that the situation may be normal case , and developers understand the reasons behind it (if are looking to add a block for a certain container to every page on which the they have the target container, and don't need the block to be added to pages on which the target container is not in use).

Short excerpt from internal ticket the description of which reads: "Stop logging such cases in any way, or perhaps stop marking them as critical (ensure that the issue is not logged using production). It will also be useful for the logged message to provide the URL for the page where target container is lost".