It seems that the LOG service performs an unnecessarily broad search (starting
at the root of the IMM database). Instead, it could search the tree below
safApp=safLogService
---
** [tickets:#1313] osaf: opensaf does not start when long dn object is present
in imm.db and cluster is reset**
**Status:** unassigned
**Milestone:** 4.5.1
**Created:** Mon Apr 13, 2015 08:57 AM UTC by Sirisha Alla
**Last Updated:** Thu Aug 13, 2015 07:41 AM UTC
**Owner:** Mathi Naickan
**Attachments:**
-
[slot1.tar.bz2](https://sourceforge.net/p/opensaf/tickets/1313/attachment/slot1.tar.bz2)
(269.6 kB; application/x-bzip)
This is observed on changeset 6377 (46FC Tag). The system is up with single pbe
and 50k objects. Long dns was enabled. There is one long dn object in the
cluster.
Syslog on SC-1:
Apr 9 15:49:14 SLES-64BIT-SLOT1 osafimmnd[10731]: WA Setting attr
longDnsAllowed to 0 in opensafImm=opensafImm,safApp=safImmService not allowed
when long RDN exists inside object:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxattrName_testAdminOwnerClear_SubLevelScope_1011
Now the cluster is reset. Nodes in the cluster fail to come up with the
following reason:
Apr 13 13:04:55 SLES-64BIT-SLOT1 osafimmnd[3439]: NO Persistent Back End OI
attached, pid: 3465
Apr 13 13:04:55 SLES-64BIT-SLOT1 osafimmnd[3439]: NO Implementer connected: 1
(OpenSafImmPBE) <10, 2010f>
Apr 13 13:04:55 SLES-64BIT-SLOT1 osafimmnd[3439]: NO implementer for class
'OpensafImm' is OpenSafImmPBE => class extent is safe.
Apr 13 13:04:55 SLES-64BIT-SLOT1 osafimmpbed: NO Update epoch 20 committing
with ccbId:100000003/4294967299
Apr 13 13:04:56 SLES-64BIT-SLOT1 osafimmnd[3439]: NO PBE-OI established on this
SC. Dumping incrementally to file imm.db
Apr 13 13:05:34 SLES-64BIT-SLOT1 opensafd[3378]: ER Timed-out for response from
LOGD
Apr 13 13:05:34 SLES-64BIT-SLOT1 opensafd[3378]: ER
Apr 13 13:05:34 SLES-64BIT-SLOT1 opensafd[3378]: ER Going for recovery
Apr 13 13:05:34 SLES-64BIT-SLOT1 opensafd[3378]: ER Trying To RESPAWN
/usr/lib64/opensaf/clc-cli/osaf-logd attempt #1
Apr 13 13:05:34 SLES-64BIT-SLOT1 opensafd[3378]: ER Sending SIGKILL to LOGD,
pid=3452
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: Started
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: WA read_logsv_configuration().
All attributes could not be read
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: NO Log config system: high 0
low 0, application: high 0 low 0
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: NO log root directory is:
/var/log/opensaf/saflog
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: NO LOG data group is:
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: NO LGS_MBCSV_VERSION = 4
Apr 13 13:05:49 SLES-64BIT-SLOT1 osaflogd[3500]: saImmOmSearchInitialize
FAILED, rc = 13
Apr 13 13:06:29 SLES-64BIT-SLOT1 opensafd[3378]: ER Timed-out for response from
LOGD
Apr 13 13:06:29 SLES-64BIT-SLOT1 opensafd[3378]: ER Could Not RESPAWN LOGD
Apr 13 13:06:29 SLES-64BIT-SLOT1 opensafd[3378]: ER
Apr 13 13:06:29 SLES-64BIT-SLOT1 opensafd[3378]: ER Trying To RESPAWN
/usr/lib64/opensaf/clc-cli/osaf-logd attempt #2
Apr 13 13:06:29 SLES-64BIT-SLOT1 opensafd[3378]: ER Sending SIGKILL to LOGD,
pid=3495
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: Started
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: WA read_logsv_configuration().
All attributes could not be read
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: NO Log config system: high 0
low 0, application: high 0 low 0
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: NO log root directory is:
/var/log/opensaf/saflog
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: NO LOG data group is:
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: NO LGS_MBCSV_VERSION = 4
Apr 13 13:06:44 SLES-64BIT-SLOT1 osaflogd[3546]: saImmOmSearchInitialize
FAILED, rc = 13
Apr 13 13:07:24 SLES-64BIT-SLOT1 opensafd[3378]: ER Timed-out for response from
LOGD
Apr 13 13:07:24 SLES-64BIT-SLOT1 opensafd[3378]: ER Could Not RESPAWN LOGD
Apr 13 13:07:24 SLES-64BIT-SLOT1 opensafd[3378]: ER
Apr 13 13:07:24 SLES-64BIT-SLOT1 opensafd[3378]: ER FAILED TO RESPAWN
Apr 13 13:07:24 SLES-64BIT-SLOT1 osaffmd[3419]: exiting for shutdown
Apr 13 13:07:24 SLES-64BIT-SLOT1 osafimmd[3429]: exiting for shutdown
Apr 13 13:07:24 SLES-64BIT-SLOT1 osafimmnd[3439]: NO No IMMD service => cluster
restart, exiting
Apr 13 13:07:24 SLES-64BIT-SLOT1 osafimmpbed: WA PBE lost contact with parent
IMMND - Exiting
Apr 13 13:07:24 SLES-64BIT-SLOT1 osafrded[3410]: exiting for shutdown
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782513] TIPC: Disabling bearer
<eth:eth0>
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782518] TIPC: Lost link
<1.1.1:eth0-1.1.4:eth0> on network plane A
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782521] TIPC: Lost contact with
<1.1.4>
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782526] TIPC: Lost link
<1.1.1:eth0-1.1.3:eth0> on network plane A
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782527] TIPC: Lost contact with
<1.1.3>
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782534] TIPC: Left network mode
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782551] NET: Unregistered
protocol family 30
Apr 13 13:07:24 SLES-64BIT-SLOT1 kernel: [ 1630.782554] TIPC: Deactivated
Apr 13 13:07:24 SLES-64BIT-SLOT1 opensafd: Starting OpenSAF failed
syslog, imm and logd traces are attached.
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
