Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28373

nuxeoctl hangs on failure with strict mode

    XMLWordPrintable

    Details

    • Release Notes Summary:
      nuxeoctl stops on failure with strict mode
    • Backlog priority:
      750
    • Team:
      PLATFORM
    • Sprint:
      nxplatform 11.1.26, nxplatform 11.1.27
    • Story Points:
      3

      Description

      Run a nuxeoctl start while elasticsearch is down.
      The output reports errors:
      1. Components failures: ElasticSearchComponent, NXAuditEventsService and UIDGeneratorService start failure:

      2019-12-04T08:59:33,545 ERROR [main] [org.nuxeo.runtime.model.ComponentManager] Component service:org.nuxeo.elasticsearch.ElasticSearchComponent notification of application started failed: java.io.IOException: elasticsearch: Name or service not known
      2019-12-04T08:59:33,579 ERROR [main] [org.nuxeo.runtime.model.ComponentManager] Component service:org.nuxeo.ecm.platform.audit.service.NXAuditEventsService notification of application started failed: null
      java.lang.NullPointerException: null
      2019-12-04T08:59:34,338 ERROR [main] [org.nuxeo.runtime.model.ComponentManager] Component service:org.nuxeo.ecm.core.uidgen.UIDGeneratorService notification of application started failed: null
      java.lang.NullPointerException: null
      

      And the bulkIndex computation is also failing (2 threads = 2 errors)

      2. The Nuxeo startup is in failure

      2019-12-04T08:59:35,634 ERROR [main] [org.nuxeo.runtime.osgi.OSGiRuntimeService] Nuxeo Platform Started
      ======================================================================
      = Component Loading Status: Pending: 0 / Missing: 0 / Unstarted: 3 / Total: 694
        - service:org.nuxeo.ecm.core.uidgen.UIDGeneratorService
        - service:org.nuxeo.ecm.platform.audit.service.NXAuditEventsService
        - service:org.nuxeo.elasticsearch.ElasticSearchComponent
      ======================================================================
      2019-12-04T08:59:35,635 ERROR [main] [org.nuxeo.osgi.OSGiAdapter] Error during Framework Listener execution : class org.nuxeo.runtime.osgi.OSGiRuntimeService
      java.lang.IllegalStateException: Startup aborted due to previous failures (strict mode)
      	at org.nuxeo.runtime.osgi.OSGiRuntimeService.printStatusMessage(OSGiRuntimeService.java:473) ~[nuxeo-runtime-11.1-SNAPSHOT.jar:?]
      	at org.nuxeo.runtime.osgi.OSGiRuntimeService.startComponents(OSGiRuntimeService.java:452) ~[nuxeo-runtime-11.1-SNAPSHOT.jar:?]
      	at org.nuxeo.runtime.osgi.OSGiRuntimeService.frameworkEvent(OSGiRuntimeService.java:462) ~[nuxeo-runtime-11.1-SNAPSHOT.jar:?]
      
      2019-12-04T08:59:35,638 ERROR [main] [org.nuxeo.runtime.deployment.NuxeoStarter] Exception during startup
      java.lang.IllegalStateException: Startup aborted due to previous failures (strict mode)
      	at org.nuxeo.runtime.osgi.OSGiRuntimeService.printStatusMessage(OSGiRuntimeService.java:473) ~[nuxeo-runtime-11.1-SNAPSHOT.jar:?]
      

      3. nuxeoctl timeout

      Server started with process ID 1260.
      .................................................................................................................................................................................................................................................................................................
      Starting process is taking too long - giving up.
      

      But the server is still running:

      nuxeo@nuxeo:/$ nuxeoctl status
      ...
      Server is running with process ID 1260.
      

      Attached server.log and thread dump after nuxeoctl start gives up.

        Attachments

        1. server.log
          44 kB
          Benoit Delbosc
        2. threaddump.txt
          29 kB
          Benoit Delbosc

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 2 hours
                  2d 2h