-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 9.10
-
Fix Version/s: 10.2
-
Component/s: nuxeoctl start/stop/admin
-
Tags:
When jar are missing on nxserver/bundles tomcat fails to start nuxeo but logs are missing.
Using nuxeoctl start it waits for the start that never comes, 0 error in all the available logs.
Using nuxeoctl console an error is displayed, but the cause is unknown.
2018-02-22 09:05:50,284 INFO [application] jsf.core.injection.provider_generic_web_configured 2018-02-22 09:05:51.865 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file 2018-02-22 09:05:51.867 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/nuxeo] startup failed due to previous errors 2018-02-22 09:05:52.461 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 12145 ms
We should not hide the "appropriate container log file"
The above pb without cause can be seen when using a S3 binarystore and when the nuxeo-core-binarymanager-common-10.1-SNAPSHOT.jar is missing.
Starting a stock nuxeo without nuxeo-core-10.1-SNAPSHOT.jar is also hiding the SEVERE logs, but at least there are some ERRORs
2018-02-22 10:27:36,764 ERROR [localhost-startStop-1] [javax.enterprise.resource.webcontainer.jsf.config] Critical error during deployment: java.lang.NoClassDefFoundError: Lorg/nuxeo/ecm/core/lifecycle/LifeCycleService;
