Hi Jon;
I have removed the file and I have navigated to the startup logs but nothing happened, here is the output of /var/log/messages
Apr 10 22:41:20 mesa_syslogd[289]: Watchdog started
Apr 10 22:41:20 mesa_syslogd[289]: Child process started (pid=291)
Apr 10 22:41:20 mesa_syslogd[291]: Started
Apr 10 22:41:20 mesa_syslogd[291]: Loading config
Apr 10 22:41:20 mesa_syslogd[291]: Ready
Apr 10 22:41:20 mesa_syslogd[291]: Warning: Unable to attach to eventsd; event reporting temporarily disabled
Apr 10 22:41:22 mesa_control[290]: Found legacy published snapshot: isam_9.0.7.0_published.snapshot
Apr 10 22:41:24 mesa_config[305]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:41:24 mesa_config[305]: Applying snapshot
Apr 10 22:41:24 mesa_config[305]: Snapshot file: /var/shared/snapshots/isam_9.0.7.0_published.snapshot
Apr 10 22:41:24 mesa_config[305]: Found version within /tmp/tmp.ido6cW/Settings: 9.0.7.0
Apr 10 22:41:24 mesa_config[305]: Found model within /tmp/tmp.ido6cW/Settings: docker
Apr 10 22:41:28 mesa_config[305]: Error: MesaSecureFileMgr::signatureIsValid(): acme error:failed:idup_se_singlebuffer_unprotect:GSS_S_FAILURE:GSS_S_INVALID_PKCS7_MESSAGE
Apr 10 22:41:28 mesa_config[305]: Error: The snapshot file cannot be applied because it has been modified!
Apr 10 22:41:28 mesa_config[305]: GLGSY0010E:: GLG_events:: ||
Apr 10 22:41:31 mesa_config[325]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:41:31 mesa_config[325]: Error: DPWAP0072E The key database, rt_profile_keys, does not exist.
Apr 10 22:41:33 mesa_config[329]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:42:06 mesa_config[501]: Last message repeated 5 times
Apr 10 22:42:06 mesa_config[501]: Error: DPWAP0072E The key database, lmi_trust_store, does not exist.
Apr 10 22:42:08 mesa_config[505]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:42:42 mesa_config[696]: Last message repeated 5 times
Apr 10 22:42:42 mesa_config[696]: Error: DPWAP0072E The key database, embedded_ldap_keys, does not exist.
Apr 10 22:42:44 mesa_config[700]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:43:19 mesa_config[877]: Last message repeated 5 times
Apr 10 22:43:23 mesa_control[892]: Bootstrapping from last known good policies
Apr 10 22:43:23 mesa_control[892]: Adapting policy dir=/etc/policies/
Apr 10 22:43:23 mesa_control[892]: Adapt policy succeeded
Apr 10 22:43:23 mesa_control[892]: Translating policy dir=/etc/policies/ out=/etc/settings.tmp
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/addr_geo/addr_geo1_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/addr_host/addr_host2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/addr_mask/addr_mask2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/addr_range/addr_range2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/address_collection/address_collection2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/responses/email/email2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: Last message repeated 1 times
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/responses/logdb/logdb2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: Last message repeated 1 times
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/responses/rsyslog/rsyslog2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: Last message repeated 1 times
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/responses/snmp/snmp2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: Last message repeated 1 times
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/authdb/authdb4_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/authorization/authorization3_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/felb/felb6_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/hosts/hosts3_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/lmi/lmi2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/snmpd/snmpd2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/common/sysaccount/sysaccount2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/isam/activation/activation3_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/isam/cluster/cluster7_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/isam/dsc/dsc1_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/isam/locale/locale1_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/isam/rsyslog_forwarder/rsyslog_forwarder1_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/events/events2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mga/runtime_profile/runtime_profile13_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mga/runtime_profile/runtime_endpoints2_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/gw_net/gw_net1_2_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/local_admin_configuration/local_admin_configuration4_0_0.xml] validate passed
Apr 10 22:43:23 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/system_alerts/system_alerts2_0_0.xml] validate passed
Apr 10 22:43:24 mesa_translate[901]: XML Schema for [/etc/policies//cml/mesa/device_params/device_params2_0_0.xml] validate passed
Apr 10 22:43:24 mesa_control[892]: Translate policy succeeded
Apr 10 22:43:24 mesa_control[892]: Bootstrapping from settings
Apr 10 22:43:26 mesa_config[908]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:43:26 mesa_config[908]: Bootstrapping
Apr 10 22:43:26 mesa_config[908]: Enabling /etc/marker.custom.appliance_info.show by creating marker file.
Apr 10 22:43:26 mesa_config[908]: Enabling /etc/marker.custom.cli.logs by creating marker file.
Apr 10 22:43:26 mesa_config[908]: Error: Could not open the key database.
Apr 10 22:43:26 mesa_config[908]: Hostname set to isamconfig-111900860-h9t9p
Apr 10 22:43:26 mesa_config[908]: Setting kernel log level: 1
Apr 10 22:43:26 mesa_config[908]: Setting maximum number of core files: 3
Apr 10 22:43:26 mesa_eventsd: Dropping the queue size from 1000 to 10 due to system restrictions.
Apr 10 22:43:26 mesa_eventsd_watchdog[919]: Watchdog started
Apr 10 22:43:26 mesa_config[908]: Trying to start daemon: mesa_syslogd
Apr 10 22:43:26 mesa_eventsd_watchdog[919]: Child process started (pid=920)
Apr 10 22:43:26 mesa_eventsd[920]: Started
Apr 10 22:43:26 mesa_eventsd[920]: Loading config
Apr 10 22:43:26 mesa_eventsd[920]: Ready
Apr 10 22:43:26 mesa_syslogd[289]: Watchdog exiting on SIGTERM (sent by 908), terminating child
Apr 10 22:43:26 mesa_config[908]: Daemon already started but command line changed: mesa_syslogd
Apr 10 22:43:26 mesa_config[908]: Trying to stop daemon: mesa_syslogd_watchdog
Apr 10 22:43:26 mesa_syslogd[291]: Received SIGTERM, exiting
Apr 10 22:43:26 mesa_syslogd[291]: Shutting down
Apr 10 22:43:26 mesa_syslogd[938]: Watchdog started
Apr 10 22:43:26 mesa_syslogd[938]: Child process started (pid=939)
Apr 10 22:43:26 mesa_syslogd[939]: Started
Apr 10 22:43:26 mesa_syslogd[939]: Loading config
Apr 10 22:43:26 mesa_syslogd[939]: Ready
Apr 10 22:43:26 mesa_syslogd[939]: Attached to eventsd; event reporting enabled
Apr 10 22:43:26 mesa_config[908]: XML Schema for [/etc/policies//cml/common/authorization/authorization3_0_0.xml] validate passed
Apr 10 22:43:26 mesa_config[908]: GLGSY9025I:: GLG_events:: |component=mesa_config|
Apr 10 22:43:31 mesa_config[908]: GLGSY9029I:: GLG_events:: ||
Apr 10 22:43:31 mesa_config[908]: FIPS Checksum Results: Success(1747), Modified(0), Missing(0), Errors(0)
Apr 10 22:43:31 mesa_config[908]: Creating certificate database /opt/IBM/wlp/usr/servers/default/certs/lmi.db in FIPS mode
Apr 10 22:43:31 mesa_config[908]: Creating default lmi certificate for isamconfig-111900860-h9t9p in FIPS mode
Apr 10 22:43:41 mesa_config[1022]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:43:43 mesa_config[1028]: Last message repeated 1 times
Apr 10 22:43:57 mesa_config[908]: Starting App Server
Apr 10 22:43:57 su: (to www-data) root on none
Apr 10 22:45:08 mesa_config[1390]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:45:10 mesa_config[908]: Component Liberty enabled FIPS mode.
Apr 10 22:45:10 mesa_config[908]: Reading /proc/provhwinfo
Apr 10 22:45:10 mesa_config[908]: Creating LUM host file for virtual/generic system: /etc/lum/host-info
Apr 10 22:45:10 mesa_config[908]: host-info model: AMV 5100
Apr 10 22:45:10 mesa_config[908]: host-info serial: 515c3e5a-6e36-443e-b72e-87a995d5231a
Apr 10 22:45:10 mesa_config[908]: Executing: sed -i -e 's/^host_type.*/host_type =S v;/' /etc/lum/UpdateTypeNames.config
Apr 10 22:45:10 mesa_config[908]: Prepopulating update history after firmware update
Apr 10 22:45:10 mesa_config[908]: Writing /etc/lum/update-history.yaml
Apr 10 22:45:10 mesa_config[908]: Starting iss-lum
Apr 10 22:45:11 mesa_config[908]: Checking for automatic PAM update after firmware update
Apr 10 22:45:11 iss-lum[1442]: Component LUM enabled FIPS mode.
Apr 10 22:45:11 iss-lum[1442]: Notice: Component LUM enabled FIPS mode.
Apr 10 22:45:11 iss-lum[1442]: Started thread '_asThread-instance' with ID 140034632029952
Apr 10 22:45:11 iss-lum[1442]: Started thread 'LumTaskThread' with ID 140034623637248
Apr 10 22:45:11 iss-lum[1442]: Started thread 'UpdateServicesThread' with ID 140034615244544
Apr 10 22:45:13 mesa_config[1398]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:45:17 rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-41.el7_7.2" x-pid="1452" x-info="http://www.rsyslog.com"] start
Apr 10 22:45:17 mesa_config[908]: XML Schema for [/etc/policies//cml/common/sysaccount/sysaccount2_0_0.xml] validate passed
Apr 10 22:45:17 mesa_control[892]: Bootstrap from settings succeeded
Apr 10 22:45:17 mesa_control[892]: GLGSY0015I:: GLG_events:: ||
Apr 10 22:45:17 mesa_control[892]: Bootstrap succeeded
Apr 10 22:45:18 rsyslogd: rsyslogd's userid changed to 6000
Apr 10 22:45:23 mesa_config[1474]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:45:23 mesa_config[1474]: Error: WGAWA0279E An incorrect user name or password has been supplied.
Apr 10 22:45:23 mesa_config[1474]: GLGSY0021W:: GLG_events:: |user=cfgsvc|
Apr 10 22:45:23 mesa_config[1474]: GLGSY0100W:: GLG_events:: |user=cfgsvc,host=22.249.13.1|
Apr 10 22:45:24 mesa_config[1480]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:45:24 mesa_control[892]: Policy changes have been kept.
Apr 10 22:45:36 mesa_config[1523]: Signature verification passed for file: /usr/sbin/mesa_config
Apr 10 22:45:36 mesa_config[1523]: Error: WGAWA0279E An incorrect user name or password has been supplied.
Apr 10 22:45:36 mesa_config[1523]: GLGSY0021W:: GLG_events:: |user=cfgsvc|
Apr 10 22:45:36 mesa_config[1523]: GLGSY0100W:: GLG_events:: |user=cfgsvc,host=22.249.13.1|
Apr 10 22:45:48 mesa_config[1567]: Signature verification passed for file: /usr/sbin/mesa_config
Also container POD log is still indicating that it's not able to detect a configuration snapshot
2020-04-10T21:41:07+0000: Bootstrapping.... | |
| 2020-04-10T21:41:13+0000: ---- Log files for this container will be written to docker-508b0 |
| / / |
| / |
| 2020-04-10T21:41:13+0000: ---- Creating path: /var/application.logs/docker-508b0/lmi |
| 2020-04-10T21:41:13+0000: ---- Creating path: /var/application.logs/docker-508b0/rsyslog_forwarder |
| 2020-04-10T21:41:14+0000: ---- Creating path: /var/application.logs/docker-508b0/isam_runtime/policy |
| 2020-04-10T21:41:14+0000: ---- Creating path: /var/application.logs/docker-508b0/isam_runtime/user_registry |
| 2020-04-10T21:41:14+0000: ---- Creating path: /var/application.logs/docker-508b0/wrp |
| 2020-04-10T21:41:14+0000: ---- Creating path: /var/application.logs/docker-508b0/system |
| 2020-04-10T21:41:14+0000: ---- Creating path: /var/application.logs/docker-508b0/db |
| Docker detected |
| 2020-04-10T22:41:29+0100: ---- No configuration snapshot detected. Preparing the container |
| 2020-04-10T22:41:29+0100: now. |
| |
| Verifying checksums... Done |
| 2020-04-10T22:45:24+0100: --- Running. |
| 2020-04-10T22:45:24+0100: Log file: /var/application.logs.local/lmi/messages.log |
| [4/10/20 22:45:04:896 BST] 0000002b com.ibm.ws.util I SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation. |
| [4/10/20 22:45:06:080 BST] 0000002d com.ibm.ws.session.WASSessionCore I SESN0176I: A new session context will be created for application key default_host/isam |
| [4/10/20 22:45:06:083 BST] 0000002d com.ibm.ws.util I SESN0172I: The session manager is using the Java default SecureRandom implementation for session ID generation. |
| [4/10/20 22:45:06:088 BST] 0000002b com.ibm.ws.app.manager.AppMessageHelper A CWWKZ0001I: Application xgs_50 started in 24.997 seconds. |
| [4/10/20 22:45:10:181 BST] 00000041 com.ibm.ws.app.manager.AppMessageHelper A CWWKZ0022W: Application isam has not started in 30.098 seconds. |
| [4/10/20 22:45:10:485 BST] 00000027 com.ibm.ws.kernel.feature.internal.FeatureManager A CWWKF0012I: The server installed the following features: [appSecurity-2.0, distributedMap-1.0, el-3.0, jaxrs-2.1, jaxrsClient-2.1, jndi-1.0, json-1.0, jsonp-1.1, jsp-2.3, servlet-4.0, ssl-1.0, usr:isam.cluster_filter-8.0.0, usr:isam.guixml_validators-8.0.0, usr:isam.offering_filter-8.0.0, usr:isam.security_filter-8.0.0, usr:isam.tenant_filter-9.0.0, usr:mesa.registry-8.0.0]. |
Thanks,
Ghiffary Osman I Automation, Integration & Management Services | GTIS Middleware Services
Tel: +1 (201)-499-2880
Mob: +1 (240)- 821-5516
Webex: https://barclays.webex.com/meet/gosman
Email GOsman@barclaycardus.com
Barclays, Barclays Technology
400 Jefferson Park Whippany,NJ 07981, USA
Respect | Integrity | Service | Excellence | Stewardship
Creating opportunities to rise
P Please consider the environment before printing this email
Restricted - External