1. The write permission is not given for mounted shared filesystem where PBE
resides.
2. immnd forked with PBE process
Sep 22 19:33:15.014270 osafimmnd [32038:immnd_proc.c:1506] >> immnd_forkPbe
Sep 22 19:33:15.014276 osafimmnd [32038:immnd_proc.c:1519] TR
exec-pbe-file-path:/usr/lib64/opensaf/osafimmpbed
Sep 22 19:33:15.014284 osafimmnd [32038:immnd_proc.c:1542] NO
pbe-db-file-path:/home/PBE/imm.db VETERAN:0 B:0
Sep 22 19:33:15.014414 osafimmnd [32038:osaf_secutil.c:0065] >>
handle_new_connection
Sep 22 19:33:15.015334 osafimmnd [32038:mds_c_api.c:1605] TR svc UP
process_info EXIST, svc:26 cnt:2, adest:2010fbe536019
Sep 22 19:33:15.015323 osafimmnd [32038:immnd_proc.c:1584] T5 Parent osafimmnd,
successfully forked /home/PBE/imm.db, pid:32091
3. But the ps output is still showing the PBE as immnd library path (may be
struck at fork because of permission issue)
opensaf 32038 1 1 19:32 ? 00:00:19 /usr/lib64/opensaf/osafimmnd
--tracemask=0xffffffff
opensaf 32059 1 0 19:33 ? 00:00:00 /usr/lib64/opensaf/osaflogd
opensaf 32072 1 0 19:33 ? 00:00:00 /usr/lib64/opensaf/osafntfd
opensaf 32079 32072 0 19:33 ? 00:00:00 /usr/lib64/opensaf/osafntfimcnd
active
opensaf 32086 1 0 19:33 ? 00:00:00 /usr/lib64/opensaf/osafclmd
opensaf 32091 32038 0 19:33 ? 00:00:00 /usr/lib64/opensaf/osafimmnd
--tracemask=0xffffffff
4. When rerun-again with write permission to mounted filesystem, the problem is
not seen.
---
** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf
with PBE.**
**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Tue Sep 23, 2014 12:24 PM UTC by Hrishikesh
**Last Updated:** Tue Sep 23, 2014 12:24 PM UTC
**Owner:** nobody
changeset : 5697
Setup : 4 nodes cluster with SLES 64bit.
Problem:
=======
Opensaf is configured with single PBE and 100K objects loaded.
Upon starting opensaf, 100K objects were loaded but PBE process didnot start.
It was also observed that there are two immnd processes spawned and running
Syslog clearly says that "PBE is starting" but it never started successfully
and no error messages observed.
======
Sep 22 19:33:15 SLES-SLOT1 osafimmnd[32038]: NO STARTING PBE process.
Sep 22 19:33:15 SLES-SLOT1 osafimmnd[32038]: NO
pbe-db-file-path:/home/PBE/imm.db VETERAN:0 B:0
Sep 22 19:33:15 SLES-SLOT1 osafimmnd[32038]: NO Implementer connected: 3
(safClmService) <15, 2010f>
Sep 22 19:33:15 SLES-SLOT1 osafimmnd[32038]: NO implementer for class
'SaClmNode' is safClmService => class extent is safe.
Sep 22 19:33:15 SLES-SLOT1 osafimmnd[32038]: NO implementer for class
'SaClmCluster' is safClmService => class extent is safe.
Sep 22 19:33:15 SLES-SLOT1 osafclmna[32097]: Started
Sep 22 19:33:15 SLES-SLOT1 osafclmna[32097]: NO
safNode=SC-1,safCluster=myClmCluster Joined cluster, nodeid=2010f
Sep 22 19:33:15 SLES-SLOT1 osafamfd[32106]: Started
=========
---
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.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
