Harshitkumar Jain | 24 Nov 14:42 2014

CIMPLE website down

Hi team,

 

An advance apology if this mail gets listed at  wrong forum.

 

The CIMPLE website http://www.simplewbem.org/ is down for some time now.

Is there any change in the project, i.e is it being depreciated or is it just a networking issue?

 

Thanks,

Harshit

The information contained in this e-mail message and in any attachments/annexure/appendices is confidential to the
recipient and may contain privileged information. If you are not the intended recipient, please notify the
sender and delete the message along with any attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender specifically states them to be the views of 
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.
Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Toshiba Software India Pvt. Ltd, for any loss or damage arising in any way from its use.

Arunkumar S | 19 Nov 10:05 2014
Picon

Re: Event delivery issue after Provider Crash

Thanks a lot.

The issue got fixed with OP 2.13.0 

Thanks,
Arun

On Tue, Nov 18, 2014 at 9:08 AM, Arunkumar S <arunkumar.krishnan <at> gmail.com> wrote:
Hi Dev,

My intention is not to debug the crash, since it is induced crash.

I am using Pegasus 2.11.1.   I will try 2.13.0 and check if the issue is still reproducible. 

Thanks,
Arun




On Tue, Nov 18, 2014 at 12:31 AM, Devchandra L Meetei <dlmeetei <at> gmail.com> wrote:

Have you tried running the provider in process. If it crashes while running as in process. Getting a BT might help.
Which version of pegasus u r using. There was a related fix in pegasus 2.13

On Nov 18, 2014 7:35 AM, "Arunkumar S" <arunkumar.krishnan <at> gmail.com> wrote:
Hi Karl et al.,

Thanks for your inputs.

Actually, I am trying to unit test my provider against provider crash. 

The test objective is to ensure that Events are delivered properly, once provider is restarted by cimserver after its first crash, as per PEP#: 360

The steps:
1. Induce the provider to have NULL pointer Crash for a specific invokeMethod operation and get message "Lost connection with cimprovagt ..."
2. Generate a hardware event
3. Check whether the CIM Client - Event listener is able to receive that event or not. 

Having looked at the Pegasus and my provider log,   I have confirmed that the provider is getting crashed and then restarted by cimserver, but subsequently the event delivery is failing. 
The CMPI method - CBDeliverIndication for Event delivery is failing.  

My provider has all capabilities combined - Instance, Association, Method and Indication. 
maxFailedProviderModuleRestarts is set to default value =3

Do I need to enable any specific CIM attribute or cimconfig parameter. ?

Thanks,
Arun

On Mon, Nov 17, 2014 at 5:54 AM, Karl Schopmeyer <k.schopmeyer <at> swbell.net> wrote:
Here is an example of a script that would allow running just some oop providers under valgrind

#!/bin/sh
## Original Author: Tim Potter
# move cimprovagt to cimprovagt.real
# move this file to cimprovagt
#
# mv /usr/sbin/cimprovagt /usr/sbin/cimprovagt.real
# cp cimprovagt.wrapper /usr/sbin/cimprovagt

## By default the script doesn't call valgrind - enable it by
## creating a semaphore file of the form /tmp/$MODULE.valgrind where module
## is the module name in the output of "cimprovider -l".

## Or create a file /tmp/LogAll.valgrind which valgrinds all providers.

module=$5

VALGRIND_ARGS="--leak-check=yes --trace-children=yes --log-file=/tmp/$module.valgrind"

if [ -e /tmp/$module.valgrind -o -e /tmp/LogAll.valgrind ]; then
        exec /usr/bin/valgrind $VALGRIND_ARGS \
        /usr/sbin/cimprovagt.real "$ <at> "
else
        exec /usr/sbin/cimprovagt.real "$ <at> "
fi

On 11/16/2014 10:52 PM, Arunkumar S wrote:
Hi,

My provider is encountering a crash occasionally.  The CIM server automatically restarts the provider process. But the events are not delivered after the provider restart.

I have confirmed using cimsub that the event subscription is active. But even then, the events are not delivered to the target system.

But, If I restart the entire cimserver altogether, I can get the event delivered.

Thanks,
Arun







Arunkumar S | 19 Nov 10:02 2014
Picon

(unknown)

Hi All,

My provider has got degraded status. So I have reloaded it using using cimprovider cmd. 
But I could see both "Degraded" and "OK" messages , instead of just only "OK" message in the status column for my provider.

# cimprovider -l -s
MODULE                          STATUS
OperatingSystemModule        OK
ComputerSystemModule        OK
ProcessModule                     OK
ProcessorProviderModule      OK
IPProviderModule                 OK
xxxxxxProvider                    Degraded OK

Cross verified with PG_ProviderModule instance:
# cimcli -n root/PG_InterOp gi PG_ProviderModule.Name=\"xxxxxxProvider\" | grep  OperationalStatus
    OperationalStatus = {3, 2};

Is this expected behavior ?
My OP is 2.13.0

Thanks,
Arun

Arunkumar S | 18 Nov 03:05 2014
Picon

Re: Event delivery issue after Provider Crash

Hi Karl et al.,

Thanks for your inputs.

Actually, I am trying to unit test my provider against provider crash. 

The test objective is to ensure that Events are delivered properly, once provider is restarted by cimserver after its first crash, as per PEP#: 360

The steps:
1. Induce the provider to have NULL pointer Crash for a specific invokeMethod operation and get message "Lost connection with cimprovagt ..."
2. Generate a hardware event
3. Check whether the CIM Client - Event listener is able to receive that event or not. 

Having looked at the Pegasus and my provider log,   I have confirmed that the provider is getting crashed and then restarted by cimserver, but subsequently the event delivery is failing. 
The CMPI method - CBDeliverIndication for Event delivery is failing.  

My provider has all capabilities combined - Instance, Association, Method and Indication. 
maxFailedProviderModuleRestarts is set to default value =3

Do I need to enable any specific CIM attribute or cimconfig parameter. ?

Thanks,
Arun

On Mon, Nov 17, 2014 at 5:54 AM, Karl Schopmeyer <k.schopmeyer <at> swbell.net> wrote:
Here is an example of a script that would allow running just some oop providers under valgrind

#!/bin/sh
## Original Author: Tim Potter
# move cimprovagt to cimprovagt.real
# move this file to cimprovagt
#
# mv /usr/sbin/cimprovagt /usr/sbin/cimprovagt.real
# cp cimprovagt.wrapper /usr/sbin/cimprovagt

## By default the script doesn't call valgrind - enable it by
## creating a semaphore file of the form /tmp/$MODULE.valgrind where module
## is the module name in the output of "cimprovider -l".

## Or create a file /tmp/LogAll.valgrind which valgrinds all providers.

module=$5

VALGRIND_ARGS="--leak-check=yes --trace-children=yes --log-file=/tmp/$module.valgrind"

if [ -e /tmp/$module.valgrind -o -e /tmp/LogAll.valgrind ]; then
        exec /usr/bin/valgrind $VALGRIND_ARGS \
        /usr/sbin/cimprovagt.real "$ <at> "
else
        exec /usr/sbin/cimprovagt.real "$ <at> "
fi

On 11/16/2014 10:52 PM, Arunkumar S wrote:
Hi,

My provider is encountering a crash occasionally.  The CIM server automatically restarts the provider process. But the events are not delivered after the provider restart.

I have confirmed using cimsub that the event subscription is active. But even then, the events are not delivered to the target system.

But, If I restart the entire cimserver altogether, I can get the event delivered.

Thanks,
Arun





Khushboo Sancheti | 17 Nov 19:12 2014

Compiling Open Pegasus 2.13 with CIM 2.41 experimental

Hi,

Has anyone tried to compile Open Pegasus using 2.41 experimental CIM Schema? The latest schema that Open Pegasus 2.13 ships with seems to be CIM 2.36 per the pegasus/Schemas directory.

We are seeing the following issue:

Open Pegasus is compiled using CIM 2.36 schema (that is the default in the 2.13 source RPM).  We then try to register the 2.41 experimental CIM schema using cimmofl.  Cimmofl throws an error in the qualifiers.mof at line 154 complaining about the "Reference" field in qualifiers.mof of CIM 2.41 experimental.

Note: We have not seen this issue with Open Pegasus 2.12-2.


Arunkumar S | 17 Nov 05:52 2014
Picon

Event delivery issue after Provider Crash

Hi,

My provider is encountering a crash occasionally.  The CIM server automatically restarts the provider process. But the events are not delivered after the provider restart.

I have confirmed using cimsub that the event subscription is active. But even then, the events are not delivered to the target system. 

But, If I restart the entire cimserver altogether, I can get the event delivered.  

Thanks,
Arun



Singh, Devendra (UPEL | 11 Nov 07:09 2014
Picon

POODLE vulnerability

Is Open Pegasus impacted due to POODLE vulnerability? Since cimserver can accept connections using SSLV3 and SSLV3 is still not disabled on server side so I think its vulnerable.
Currently we are using 2.11 version of OP. Please share your thoughts on this.

Regards,
Devendra

 

Karl Schopmeyer | 8 Nov 21:09 2014
Picon

Scripts in pegasus-unsupported

I have update one set of scripts in the pegasus-unsupported module and 
committed the first version of a second set.

1. formattrace - A bash/awk script tool to help clean up the traces 
somewhat.  It does several things including:
     - consolidate the multiple traces  from OOP into a single trace 
sorted by time.
     - Change the time on each trace entry from absolute to time 
relative to the start of the output. Thus, all of
       the lines of the log can be read in terms of time from the first 
entry in the output log.  Makes it much easier
       to see time differences in the log
    - Changes the process/thread id to something meaningful (P01:TH01) 
so that it is much easier to trace the
       multiple threads through the dump.
    - Reformat the XML output to that it is easier to read.
    - Marks certain log entries so that they are easy to find.

Remember that that this is an unsupported tool.  I found it useful and 
am making it available to everybody.

2. CHO test scripts.  I created two bash scripts (chosimpletest and 
watchcimserver) and they in the sunsupported
     directory scripts/chotest.   One is to regulary display/save core 
data about the server operation (today it is
     data from repeated execution of the ps command) and the other, 
executes a defined set of clients against
     the server.  Again this is primitive but at least it works and we 
have already used it to locate a number of issues.

I welcome comments, etc.

Note that today this are primarily for developers.

Karl

Devchandra L Meetei | 28 Oct 17:28 2014
Picon

Fwd: [VOTING RESULT] Bug 9903 - Remove the duplicate doc file and related cimcli doc from cimcli/doc

The proposed patch has been accepted
Yes vote: Deleisha
No Vote: None
Abstain vote: None
---------- Forwarded message ----------
From: Devchandra L Meetei <dlmeetei <at> gmail.com>
Date: Tue, Oct 21, 2014 at 8:30 PM
Subject: [VOTE] Bug 9903 - Remove the duplicate doc file and related cimcli doc from cimcli/doc
To: pegasus-architecture <pegasus-architecture <at> opengroup.org>


The proposed patch for bug 9903 is open for voting
http://bugzilla.openpegasus.org/show_bug.cgi?id=9903
Please register votes within 48 hours of initial acceptance period if possible.


--
Warm Regards
--Dev
OpenPegasus Developer

"I'm one of those people that think Thomas Edison and the light bulb changed the world more than Karl Marx ever did,” Steve Jobs



--
Warm Regards
--Dev
OpenPegasus Developer

"I'm one of those people that think Thomas Edison and the light bulb changed the world more than Karl Marx ever did,” Steve Jobs
Arunkumar | 9 Oct 00:58 2014
Picon

OpenPegasus cimserver UTF-8 issue in Windows 7 Russian

Hi,

I am just wondering if anyone has encountered any issue running 
OpenPegasus cimserver binary in Windows 7 Russian edition.

When I run cimserver in that OS, it throws an error saying that the config 
file is not in UTF-8 format, even though its in UTF-8 format.

Even OpenPegasus based CIM tools from HP and EMC are also having the same 
issue. 

Please let me know if I need to ensure any formatting and configuration 
for Windows 7 Russian. 

Thanks in advance.

Arun

Elliot Justice | 22 Sep 19:45 2014

Install duplicate DMTF schema

First some background.
We have clients using software on legacy servers that have OpenPegasus 
installed with versions ranging from 2.6 to 2.11 and we are planning to 
use OpenPegasus to augment one of our existing projects.We operating 
under the assumption that some of the clients may be using OP for some 
in house project. So for testability we would like to install a 
duplicate copy of the DMTF standard schema in a separate namespace so we 
can have some consistency for the project.

So far I've downloaded  and compiled the MOF files into a seperate 
namespace on a test server using 

cimmof -n root/testNamespace CIM_SCHEMA.mof 

which displayed a duplicate class warning (which I expected). I then 
added R/W permissions to the new namespace using 

cimauth -a -u testUser -n root/testNamespace -R -W

and checked if the classes were available using 

cimcli gc -n root/testNamespace CIM_OperatingSystem

However trying to get an instance of a class with

cimcli gi -n root/testNamespace CIM_OperatingSystem 

gives a CIM_ERR_NOT_SUPPORTED error. Upon further investigation I 
realized that no instances of any classes were created when the MOF was 
compiled, so I tried using

cimcli ci -n root/testNamespace CIM_OperatingSystem

but this also gave a CIM_ERR_NOT_SUPPORTED. I feel that I missed a step 
somewhere, or that there is some other recommended way to do this. Can 
anyone provide assistance?


Gmane