IT46508: NO GUI LOGIN AFTER REBOOT BECAUSE OF VIRGO SERVICE START ERROR <UR0002E> USER REGION FAILED WHILE DEPLOYING INITIAL ARTIFACTS

APAR status

• Closed as Permanent restriction.

Error description

• The IBM Storage Protect Plus login screen is not available after
  a reboot. There is no login available because the virgo service
  is down as seen with the command :
     systemctl status virgo -l
  virgo.service - The Virgo Web Server from EclipseRT
     Loaded: loaded (/usr/lib/systemd/system/virgo.service;
             enabled; vendor preset: disabled)
     Active: inactive (dead) since <timestamp>; <Duration> ago
       Docs: https://eclipse.org/virgo/documentation/
    Process: 13512 ExecStop=/opt/virgo/bin/shutdown.sh -immediate
                   (code=exited, status=0/SUCCESS)
    Process: 4766 ExecStart=/opt/virgo/bin/start-spp-virgo.sh
                  (code=exited, status=0/SUCCESS)
  Main PID: 4766 (code=exited, status=0/SUCCESS)
  ...
  .. <UR0002E> User region failed while deploying initial
               artifacts. Shutting down.
  .. <KE0010I> Shutdown initiated.
  .. <TC0002I> Stopping Tomcat.
  .. <TC0003I> Stopped Tomcat.
  .. : The Server could not be reached, it may already be stopped.
  .. : virgo.service: Succeeded.
  For this APAR to apply, in the appliance virgo log found in
  /opt/virgo/serviceability/logs, the following messages will be
  seen upon startup.
  Example for one bundle :
  .. <DE0004I> Starting bundle 'com.syncsort.dp.xsb.service.
               schedule.impl' version '3.16.0'.
  ...
  .. <KE0100W> Reference '&scheduleProvider' in bundle
               'com.syncsort.dp.xsb.service.schedule.impl'
               version '3.16.0' is waiting for service with filter
               '(objectClass=com.syncsort.dp.xsb.scheduleprovider.
               ScheduleProvider)'.
  ...
  .. <AG0000E> Application context creation failure for bundle
               'com.syncsort.dp.xsb.service.schedule.impl' version
               '3.16.0'. org.springframework.beans.factory.
               BeanCreationException: Error creating bean with
               name 'scheduleConfigForInit' defined in URL
               ¢bundleentry://308.fwk1507066820/META-INF/spring/
               app-context.xml!: Invocation of init method failed;
               nested exception is com.syncsort.dp.xsb.persistence
               .dao.XSBDAOException: org.springframework.data.
               mapping.model.MappingInstantiationException:
               Failed to instantiate java.util.SimpleTimeZone
               using constructor NO_CONSTRUCTOR with arguments
  and finally failing Tomcat start as seen in /var/log/messages :
  .. <UR0002E> User region failed while deploying initial
               artifacts. Shutting down.
  .. <KE0010I> Shutdown initiated.
  .. <TC0002I> Stopping Tomcat.
  .. <TC0003I> Stopped Tomcat.
  This will happen if there is a SLA defined with a start date
  that is incorrectly stored in IBM Storage Protect Plus.
  IBM Storage Protect Plus Versions Affected:
  IBM Storage Protect Plus 10.1.x
  Additional Keywords: SPP, SPPLUS, TS016521143,  ISPPSUP-4984,
                       techdoc-7159719
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * BM Spectrum Protect Plus 10.1.15.2 and later                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * If the SLA start date is set to a higher date (for example,  *
  * the 2099 start date on some SLA), the SPP server fails to    *
  * start after Virgo is restarted/SPP reboot with the below     *
  * error -                                                      *
  * 	org.springframework.data.mapping.model.MappingInstantiation *
  * Exception: Failed to instantiate java.util.SimpleTimeZone    *
  * using constructor NO_CONSTRUCTOR with arguments              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The problem is resolved by resetting the date field using a
  database query.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels