cancel
Showing results for 
Search instead for 
Did you mean: 

Root Cause Analysis (OS and DB - OS Command Console) Connection problem!

Former Member
0 Kudos

Dear Community,

i've got a problem with the Root Cause Analysis OS Command console!

Currently I try to read the System MemStat info from the console, without success!

I've got the following errors:

Error1:

Error to parse the data returns by 'SAPOSCol', cause :com.sap.smd.plugin.remoteos.exception.SAPOSColDataParserException: Unknown Error during the parsing of saposcol output; nested exception is:

java.lang.NullPointerException

Error2:

'SAPOSCol' Service not availbale, detail :com.sap.smd.plugin.remoteos.exception.SAPOScolNotAvailable: SAPOSCol not available (detail output: )

The saposcol service is running, when I look on the server, I've got the correct status:

server:<sid>adm> saposcol -s

**************************************************************

Collector Versions :

running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux

dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16

Shared Memory : attached

Number of records : 5758

Active Flag : active (01)

Operating System : Linux server 2.6.5-7.283-smp #1 SMP Wed Nov 29

Collector PID : 9536 (00002540)

Collector : running

Start time coll. : Wed Apr 23 15:00:58 2008

Current Time : Wed Apr 23 15:12:08 2008

Last write access : Wed Apr 23 15:12:04 2008

Last Read Access : Wed Apr 23 15:12:03 2008

Collection Interval : 10 sec (next delay).

Collection Interval : 10 sec (last ).

Status : free

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 2

Collector in IDLE - mode ? : NO

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 10 sec

**************************************************************

The strange thing is, sometimes it works, sometimes not!

Any Ideas?

System: Solution Manager 4.0 SP Stack 13

Thanks and regards

Sascha

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

saposcol changed to the newest release!

markus_doehr2
Active Contributor
0 Kudos

> running : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux

> dialog : COLL 20.94 700 - v2.00, AMD/Intel x86_64 with Linux, 2007/02/16

I suggest you upgrade your saposcol on the Linux box, it's more than a year old and it's possible, that the SMD client needs a newer version that provides the data you're requesting.

Markus

Former Member
0 Kudos

Hi Markus,

shame on me! - Sometimes the easiest solutions are the best solutions!

Now it works, thank you very much!

Sascha

Former Member
0 Kudos

Hi Community,

I'm still waiting for an idea / solution! - Any suggestions?!

Regards

Sascha