com.rabbitmq.client.ShutdownSignalException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • -------- Change the TT VM's folder name in VC ----------------- Reproduce Step 1. Create a d/c separate cluster with name 'er' and attached spec file 2. In VC's 'MS and Template' view, change the folder name from 'compute1' to 'compute11'(this folder is under folder 'er') 3. Execute 'cluster limit --name test --activeInstanceNum 2' Expected Result: 3. Command execute failed. Log message could be found in either vhm.log or vhm.xml file in Serengeti server indicate the error Actual Result: 3. Command execute failed. Following message could be found in vhm.log(NO extra info specify the error such as failed to find the VM in VC could be found in vhm.xml) =================================================== 2012 Sep 29 09:18:31.618 [10-EmbeddedVHM] Processing message... 2012 Sep 29 09:18:31.619 [10-EmbeddedVHM] Getting folders... 2012 Sep 29 09:18:31.828 [10-EmbeddedVHM] Finding TT states for compute2 2012 Sep 29 09:18:31.898 [10-EmbeddedVHM] Unexpected error in core VHM 2012 Sep 29 09:18:31.899 [10-EmbeddedVHM] Waiting for message =================================================== --------- Wrong vHadoopUser ------------- Reproduce Step 1. Create a d/c separate cluster with name 'er' and attached spec file 2. Change the value of 'vHadoopUser' from 'root' to 'serengeti'(user 'serengeti''s password is 'password', don't need to chage it) 3. Restart Serengeti service 4. Execute 'cluster limit --name test --activeInstanceNum 2' Expected Result: 4. Command execute failed. Log message could be found in either vhm.log or vhm.xml file in Serengeti server indicate the error Actual Result: 3. Command execute failed. Following message could be found in vhm.log(NO extra info specify the error such as failed to find the VM in VC could be found in vhm.xml) =================================================== 2012 Sep 29 09:35:22.332 [10-EmbeddedVHM] Waiting for message 2012 Sep 29 09:35:30.697 [10-EmbeddedVHM] Processing message... 2012 Sep 29 09:35:30.708 [10-EmbeddedVHM] Getting folders... 2012 Sep 29 09:35:30.950 [10-EmbeddedVHM] Finding TT states for compute2 2012 Sep 29 09:35:31.22 [10-EmbeddedVHM] Unexpected error in core VHM 2012 Sep 29 09:35:31.24 [10-EmbeddedVHM] Waiting for message =================================================== -------------- Shutdown TT node service ------------- Reproduce Step 1. Create a d/c separate cluster with name 'er' and attached spec file 2. Shut down one TT node's service 3. Execute 'cluster limit --name test --activeInstanceNum 2' Expected Result: 3. Command execute failed. Log message could be found in either vhm.log or vhm.xml file in Serengeti server indicate the error Actual Result: 3. Command execute failed. Following message could be found in vhm.log(NO extra info specify the error such as failed to find the VM in VC could be found in vhm.xml) =================================================== 2012 Sep 29 10:55:12.642 [10-EmbeddedVHM] Processing message... 2012 Sep 29 10:55:12.643 [10-EmbeddedVHM] Getting folders... 2012 Sep 29 10:55:12.779 [10-VCConnection] testConnection found VC connection dropped; caller will reconnect 2012 Sep 29 10:55:17.300 [10-EmbeddedVHM] Finding TT states for compute2 2012 Sep 29 10:55:17.358 [10-EmbeddedVHM] Unexpected error in core VHM 2012 Sep 29 10:55:17.361 [10-EmbeddedVHM] Waiting for message Exception in thread "main" com.rabbitmq.client.ShutdownSignalException: connection error; reason: {#method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0), null, ""} at com.rabbitmq.client.QueueingConsumer.handle(QueueingConsumer.java:198) at com.rabbitmq.client.QueueingConsumer.nextDelivery(QueueingConsumer.java:214) at com.vmware.vhadoop.adaptor.rabbit.RabbitAdaptor.blockAndReceive(RabbitAdaptor.java:29) at com.vmware.vhadoop.vhm.EmbeddedVHM.start(EmbeddedVHM.java:69) at com.vmware.vhadoop.vhm.MainController.main(MainController.java:124) java.io.FileNotFoundException: /opt/serengeti/conf/vhmProperties (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:137) at com.vmware.vhadoop.vhm.MainController.readPropertiesFile(MainController.java:44) at com.vmware.vhadoop.vhm.MainController.main(MainController.java:85) 2012 Sep 29 10:56:22.814 [10-EmbeddedVHM] Waiting for message ===================================================
    via by Wei Hu (QE),
  • -------- Change the TT VM's folder name in VC ----------------- Reproduce Step 1. Create a d/c separate cluster with name 'er' and attached spec file 2. In VC's 'MS and Template' view, change the folder name from 'compute1' to 'compute11'(this folder is under folder 'er') 3. Execute 'cluster limit --name test --activeInstanceNum 2' Expected Result: 3. Command execute failed. Log message could be found in either vhm.log or vhm.xml file in Serengeti server indicate the error Actual Result: 3. Command execute failed. Following message could be found in vhm.log(NO extra info specify the error such as failed to find the VM in VC could be found in vhm.xml) =================================================== 2012 Sep 29 09:18:31.618 [10-EmbeddedVHM] Processing message... 2012 Sep 29 09:18:31.619 [10-EmbeddedVHM] Getting folders... 2012 Sep 29 09:18:31.828 [10-EmbeddedVHM] Finding TT states for compute2 2012 Sep 29 09:18:31.898 [10-EmbeddedVHM] Unexpected error in core VHM 2012 Sep 29 09:18:31.899 [10-EmbeddedVHM] Waiting for message =================================================== --------- Wrong vHadoopUser ------------- Reproduce Step 1. Create a d/c separate cluster with name 'er' and attached spec file 2. Change the value of 'vHadoopUser' from 'root' to 'serengeti'(user 'serengeti''s password is 'password', don't need to chage it) 3. Restart Serengeti service 4. Execute 'cluster limit --name test --activeInstanceNum 2' Expected Result: 4. Command execute failed. Log message could be found in either vhm.log or vhm.xml file in Serengeti server indicate the error Actual Result: 3. Command execute failed. Following message could be found in vhm.log(NO extra info specify the error such as failed to find the VM in VC could be found in vhm.xml) =================================================== 2012 Sep 29 09:35:22.332 [10-EmbeddedVHM] Waiting for message 2012 Sep 29 09:35:30.697 [10-EmbeddedVHM] Processing message... 2012 Sep 29 09:35:30.708 [10-EmbeddedVHM] Getting folders... 2012 Sep 29 09:35:30.950 [10-EmbeddedVHM] Finding TT states for compute2 2012 Sep 29 09:35:31.22 [10-EmbeddedVHM] Unexpected error in core VHM 2012 Sep 29 09:35:31.24 [10-EmbeddedVHM] Waiting for message =================================================== -------------- Shutdown TT node service ------------- Reproduce Step 1. Create a d/c separate cluster with name 'er' and attached spec file 2. Shut down one TT node's service 3. Execute 'cluster limit --name test --activeInstanceNum 2' Expected Result: 3. Command execute failed. Log message could be found in either vhm.log or vhm.xml file in Serengeti server indicate the error Actual Result: 3. Command execute failed. Following message could be found in vhm.log(NO extra info specify the error such as failed to find the VM in VC could be found in vhm.xml) =================================================== 2012 Sep 29 10:55:12.642 [10-EmbeddedVHM] Processing message... 2012 Sep 29 10:55:12.643 [10-EmbeddedVHM] Getting folders... 2012 Sep 29 10:55:12.779 [10-VCConnection] testConnection found VC connection dropped; caller will reconnect 2012 Sep 29 10:55:17.300 [10-EmbeddedVHM] Finding TT states for compute2 2012 Sep 29 10:55:17.358 [10-EmbeddedVHM] Unexpected error in core VHM 2012 Sep 29 10:55:17.361 [10-EmbeddedVHM] Waiting for message Exception in thread "main" com.rabbitmq.client.ShutdownSignalException: connection error; reason: {#method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0), null, ""} at com.rabbitmq.client.QueueingConsumer.handle(QueueingConsumer.java:198) at com.rabbitmq.client.QueueingConsumer.nextDelivery(QueueingConsumer.java:214) at com.vmware.vhadoop.adaptor.rabbit.RabbitAdaptor.blockAndReceive(RabbitAdaptor.java:29) at com.vmware.vhadoop.vhm.EmbeddedVHM.start(EmbeddedVHM.java:69) at com.vmware.vhadoop.vhm.MainController.main(MainController.java:124) java.io.FileNotFoundException: /opt/serengeti/conf/vhmProperties (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:137) at com.vmware.vhadoop.vhm.MainController.readPropertiesFile(MainController.java:44) at com.vmware.vhadoop.vhm.MainController.main(MainController.java:85) 2012 Sep 29 10:56:22.814 [10-EmbeddedVHM] Waiting for message ===================================================
    via by Wei Hu (QE),
    • com.rabbitmq.client.ShutdownSignalException: connection error; reason: {#method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0), null, ""} at com.rabbitmq.client.QueueingConsumer.handle(QueueingConsumer.java:198) at com.rabbitmq.client.QueueingConsumer.nextDelivery(QueueingConsumer.java:214) at com.vmware.vhadoop.adaptor.rabbit.RabbitAdaptor.blockAndReceive(RabbitAdaptor.java:29) at com.vmware.vhadoop.vhm.EmbeddedVHM.start(EmbeddedVHM.java:69) at com.vmware.vhadoop.vhm.MainController.main(MainController.java:124)

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,