Hi Surender,
My point is this:
The main purpose of the immloader is to load the imm as fast as possible (a
cluster restart is *the* archetypical
high-availability problem, if there is any). If the loading fails due to a
corrupt imm.xml file then the only priority
for the imm-loader is to clearly report that there _is_ a problem with the
file. It must not waste time/complexity/risk
on trying to do detailed diagnosis of exatly _what_ the error in the file is.
Currently the syslog printouts porvide the unambiguous reporting that make it
plain and simple to understand
when there is a problem with loading the imm.xml file.
The detailed analysis of what the problem is with an imm.xml file will have to
be done off-line using tools like immxml-validate.
So what you could do is to apply that tool to the corrupt file. If that tool
does not report clearly enough what the problem is,
then you could write a ticket on immxml-validate.
/AndersBj
________________________________
From: surender khetavath [mailto:[email protected]]
Sent: den 30 september 2014 19:38
To: [email protected]
Subject: [tickets] [opensaf:tickets] #1145 IMM incorrect/irrelevant logging
during loading with modified/corrupt xml file
when you dump an object to xml, which doesn't have implementer set either to
class or object, then the implementer attribute is NOT dumped in to xml file.
I edited the xml file VERY carefully. NO syntax error nor any tags missing.
I didnot add ANOTHER implementer name. Just added the first one by editing the
dumped xml file.
Yes, if i revert the edited tags, the load works properly.
The multivalued error is not for the object information that i edited.Instead
it is for different object.
Attaching test.xml
To reproduce do
immcfg -f test.xml
immdump /tmp/imm.xml ( this xml does not have implementer attributed dumped )
Edit the dumped imm.xml and add the implementer attribute tags as said above.
Now load this new imm.xml
Attachment: test.xml (1.6 kB; text/xml)
________________________________
[tickets:#1145]<http://sourceforge.net/p/opensaf/tickets/1145> IMM
incorrect/irrelevant logging during loading with modified/corrupt xml file
Status: invalid
Milestone: 4.3.3
Created: Tue Sep 30, 2014 01:57 PM UTC by surender khetavath
Last Updated: Tue Sep 30, 2014 04:18 PM UTC
Owner: nobody
Changeset : 5918
Test:
Create a class and object
dump to xml file
Edit the xml file to include the below tags under the object DN
<attr>
<name>SaImmAttrImplementerName</name>
<value>IMPL</value>
</attr>
i.e From :
<object class="accessclass">
<dn>accessdnvalue</dn>
<attr>
<name>SaImmAttrClassName</name>
<value>accessclass</value>
</attr>
</object>
TO :
<object class="accessclass">
<dn>accessdnvalue</dn>
<attr>
<name>SaImmAttrClassName</name>
<value>accessclass</value>
</attr>
<attr>
<name>SaImmAttrImplementerName</name>
<value>IMPL</value>
</attr>
</object>
Now upload this modified xml file, with RepositoryInit pointing to load from
XML file.
Below is the ERR_INVALID_PARAM is observed and the reason being "it is not
multivalued attribute, and multiple values provided in create call"
Sep 30 19:06:41 SC-1 osafimmnd[12018]: NO ERR_INVALID_PARAM: attr
'logStreamSystemLowLimit' is not multivalued yet multiple values provided in
create call
Sep 30 19:06:41 SC-1 osafimmloadd: ER Failed to create object err: 7, class:
OpenSafLogConfig, dn: 'logConfig=1'. Check for duplicate attributes, or trace
osafimmloadd
Sep 30 19:06:41 SC-1 osafimmloadd: NO Failed to create object - exiting
Sep 30 19:06:41 SC-1 osafimmnd[12018]: NO Ccb 2 ABORTED (IMMLOADER)
Sep 30 19:06:41 SC-1 osafimmnd[12018]: WA Hard close of admin owner IMMLOADER
id(2)=> Loading must have failed
Sep 30 19:06:41 SC-1 osafimmnd[12018]: ER LOADING APPARENTLY FAILED status:1
Sep 30 19:06:41 SC-1 osafimmd[11982]: ER * LOADING FAILED. File(s) possibly
missing, inaccessible or corrupt .. ? **
Sep 30 19:06:41 SC-1 opensafd[11931]: ER Could Not RESPAWN IMMND
Sep 30 19:06:41 SC-1 opensafd[11931]: ER Failed DESC:IMMND
Sep 30 19:06:41 SC-1 opensafd[11931]: ER Trying To RESPAWN
/usr/lib64/opensaf/clc-cli/osaf-immnd attempt #2
Sep 30 19:06:41 SC-1 opensafd[11931]: ER Sending SIGKILL to IMMND, pid=12013
Sep 30 19:06:41 SC-1 osafimmnd[12018]: ER IMMND - Periodic server job failed
Sep 30 19:06:41 SC-1 osafimmnd[12018]: ER Failed, exiting...
Sep 30 19:06:41 SC-1 osafimmd[11982]: WA IMMND coordinator at 2010f apparently
crashed => electing new coord
Sep 30 19:06:41 SC-1 osafimmd[11982]: ER Failed to find candidate for new IMMND
coordinator
Sep 30 19:06:41 SC-1 osafimmd[11982]: ER Active IMMD has to restart the IMMSv.
All IMMNDs will restart
Sep 30 19:06:41 SC-1 osafimmd[11982]: NO Cluster failed to load => IMMDs will
not exit.
In the modified xml file, nothing has been changed w.r.t object
logStreamSystemLowLimit. Yet, the irrelevant error.
________________________________
Sent from sourceforge.net because [email protected] is
subscribed to
https://sourceforge.net/p/opensaf/tickets/<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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
