Config reader module in Sun MC Agent not work in E2900

Hi men,

Have you ever meet this error ?

I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it

Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error

I still haven't patches but all others are OK. :confused:

Please comment me ...

Check in this forum. Might be useful
Sun Management Center - Halcyon Forums

For Solaris 8 and 9 systems:

% /etc/init.d/picld stop

% /etc/init.d/picld start

For Solaris 10 systems:

% svcadm restart svc:/system/picl:default

of course i did but nothing change

Is your OS patched with the latest patch cluster? Whats your kernel patch level?

I didn't check.

There must be some thing error, between E2900 server and SunMC 4.0 because other servers on that site are Ok

Impt thing... so far you did not tell us what Solaris version you're running.. and its release.. This is very crucial to analyse the cause

#uname -a
#cat /etc/release

I understand, i think its really hard for Doctor treatment Patient just by listening the description. :frowning:

I almost hope for someone have experience with this error becuase i think SUNMC and E2900 are not rare.

SUNMC Server's OS is "Solaris 10 8/07 s10s_u4wos_12b SPARC".

You may also need to install some Solaris (kernel) patches.
Note: The following are all server patches. Last Updated: Oct 21, 2008

Solaris 10
127683-03
#127683-03: Sun Management Center 4.0: Patch for Solaris 10
Sun Management Center 4.0: Patch for Solaris 10
Tue Sep 02 07:58:00 MDT 2008

138553-02
#138553-02: Sun Management Center 4.0: PRM Patch for Solaris 10
Sun Management Center 4.0: PRM Patch for Solaris 10
Wed Sep 10 04:15:21 MDT 2008

I have tried these 2 patches but, all none work =_=

Then I suggest you to re-install the platform agent for the Sun MC
For your reading and understanding http://docs.sun.com/app/docs/doc/820-2216/chapter2-1000?l=ko&a=view

when i begin this thread its on 12/08 and now 4/09 .

And i has got an answear for this problem. It's a bug fixed by patch 126798-02 from SunSolve.

Hope this will be useful for someone, mb :>

Great to hear that tien86!