none
CcpManagement Errors RRS feed

  • Question

  • Now our cluster is working again; however, I still get some errors in the Logs.
    I want to know if it's something to worry about, and what does these errors mean.. Any idea?


    2008/02/04 11:34:58 [Change] [Error] Failed to persist change Updating configuration of compute node 'CLUSTER\ENC3BLADE15'., eefdad23-b765-44d9-8106-ec4caf8e26b3, The attempt to read or update the store failed.  
    2008/02/04 11:35:01 [Change] [Error] Failed to persist change Marking the compute node CLUSTER\ENC1BLADE11 for discovery so that its configuration will be updated in the cluster management model., 384015dd-cb4b-4a36-8a81-ec86c15e68dd, The attempt to read or update the store failed.  
    2008/02/04 11:35:05 [Change] [Error] Failed to persist change Updating configuration of compute node 'CLUSTER\ENC3BLADE05'., 08554c75-9600-40e8-ab13-ec92d0f6a9c4, The attempt to read or update the store failed.  
    2008/02/04 11:35:09 [Change] [Error] Failed to persist change Discovering the configuration of node 'CLUSTER\ENC4BLADE09'. , b6b766fc-0b91-4857-b5cc-ec6a8428cf69, The attempt to read or update the store failed.  
    2008/02/04 11:35:12 [Change] [Error] Failed to persist change Marking the compute node CLUSTER\ENC4BLADE11 for discovery so that its configuration will be updated in the cluster management model., b744d06b-2b85-42c2-88c3-ecbdb7573aae, The attempt to read or update the store failed.  
    2008/02/04 11:35:12 [CcpManagement] [Error] Archive timer failed The attempt to read or update the store failed.  
    2008/02/04 11:35:12 [CcpManagement] [Error] Archive timer failed The attempt to read or update the store failed.  
    2008/02/04 11:35:12 [CcpManagement] [Error] Archive timer failed The attempt to read or update the store failed.  
    2008/02/04 11:35:12 [CcpManagement] [Error] Archive timer failed The attempt to read or update the store failed.  
    2008/02/04 11:35:12 [CcpManagement] [Error] Archive timer failed The attempt to read or update the store failed.  

    Lorenzo


    Monday, February 4, 2008 11:06 AM

Answers

  • If this happens intermittently, it most likely points to a connectivity issue.  The configuration update is scheduled to run at regular intervals though, so it should still update at some point.  However, if this is persistent on these nodes, then further investigation would be necessary.

     

    Also, you'll note that you had five [Change] [Error] entries.  These five entries are in relation to the five [CcpManagement] [Error] entries at the end.  The archive timer is used to schedule when to "store" information about the nodes.  Once the timer resets, it will try updating the information again (hence why persistency is key to knowing if there is a problem).

     

    Thanks,

    Jarred Clore

    Tuesday, February 12, 2008 10:41 PM