Answering my own question:
Do debug such problems, set the following log categories to DEBUG:
[code]
<category name="info.magnolia.importexport">
<priority value="DEBUG" />
</category>
<category name="info.magnolia.init">
<priority value="DEBUG" />
</category>
[/code]
Then, in the log look for two things:
1. Just when Magnolia starts up, it prints out, what config files it is using.
Look for something like this:
[code]Property sources loaded: [DefaultMagnoliaConfigurationProperties with
sources:
[SystemPropertySource]
[ServletContextPropertySource from
WEB-INF/config/adnmac127.dyn.adnovum.ch/magnolia.properties]
[ServletContextPropertySource from
WEB-INF/config/twint-portal-author/magnolia.properties]
[ServletContextPropertySource from WEB-INF/config/default/magnolia.properties]
[ModulePropertiesSource from modules [core, dam, ui-framework, activation,
device-detection, nevis, ocm, rendering, rest-integration, scheduler,
task-management, ui-mediaeditor, imaging, rest-services, templating,
dam-templating, templating-jsp, ui-admincentral, adminInterface, groovy, mail,
messages-app, pages, rest-tools, sample-app, security-app, tools,
ui-contentapp, backup, cache, contacts, diff, form, about-app, dam-jcr, data,
inplace-templating, public-user-registration, resources, rssaggregator,
dam-app, enterprise, forum, advanced-cache, commenting, exchange-transactional,
standard-templating-kit, categorization, content-translation-support,
dependencies, google-analytics, google-sitemap, multisite, theme-pop,
demo-project, shop, twint-portal, twint-portal-shop, webapp]]
[InitPathsPropertySource][/code]
(I rearranged the output a bit for better readability.)
2. After all modules have bootstrapped their stuff, Magnolia outputs where it's
trying to load its data from. Look for something like this:
[code]
trying to initialize repositories from:
/full/path/to/bootrap/folder/in/WEB-INF/bootstrap/common
/full/path/to/bootrap/folder/in/WEB-INF/bootstrap/samples
[/code]
This should hopefully be enough info to tell you what's wrong. In my case, it
was the an Ansible deployment script which added an other magnolia.properties
file ruining my perfectly well working configuration :-(
Seriously, who is using Ansible and most of all why would you add a
magnolia.properties file in Ansible when Magnolia already comes with all you
need to configure multiple environments in a single webapp?! ;-)
Sorry for the waste of bandwidth. Maybe this will help me 2 years from now when
I google for a bootstrap problem and find my own post again (would not be the
first time).
-will
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=be2b5eae-facb-49ba-95bd-8affb93a7ec2
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------
