ID: 646865 in SUN CLUSTER 3.2

I have installed  Cluster DB(Postgres). Week ago I  started to received  the

" ID 646865 daemon.notice Monitor probe time of 30.29 seconds is 100.96 percent of Probe ".


SUN Microsoft  recommend to consider  increasing the  value of Probe_timeout.
I want to know why it gives me this error now ,after 6 months after I installed the servers and if is any other solution.

Regards

IB
IonelBoeriuAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

yuzhCommented:
please have a look at the following doc to see if you can fix it:
http://www.scribd.com/doc/6181544/Sun-Cluster-Error-Messages-Guide-for-Solaris-OS 
http://dlc.sun.com/pdf/820-2560/820-2560.pdf  (same doc in PDF format)
check your configuration against:
http://docs.sun.com/app/docs/doc/819-5578/cacjgdbc?a=view
if you need more help, post your exact OS version and details error messages.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IonelBoeriuAuthor Commented:
Yuzh,
Thanks for help.

On the document it says to increase the monitor probe time (right now is 60 sec).
My question is why it gives me the error now? I installed the computers on March.
You know why it triggers this error, and also let say I increase the value after few months will be not trigger the same error?
I attached the postgres configuration too take a look.
Thanks
Bellow  is the  error I received

04:33 PM  192.168.xx.xx  Notice  SC[SUNW.gds:6,PgeGroup,RS-PGS2,gds_probe]: [ID 646865 daemon.notice] Monitor probe time of 18.00 seconds is 59.98 percent of Probe timeout.  


Pgs-83.txt
0
yuzhCommented:
It has some thing to do with the database (the loads and the way you setup the system),  you beed to the load of the system, have a look at the follow page to see if it can help you to figure it out
http://planets.sun.com/PostgreSQL/group/PostgreSQL/?page=1 
0
IonelBoeriuAuthor Commented:
Since I cannot play much with the production cluster/postgres, I am  going to schedule a Maintenance Window to failover and restart both nodes, hoping for a fresh state after restart.
Can you please advise me what data  I need in order to contribute to the analysis/resolution of the problem.

Thanks ,

IB
0
IonelBoeriuAuthor Commented:
Not really a solution
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.