CCO Gets "Connection refused" Error in osmosix.log File

Available Languages

Download Options

  • PDF     (346.8 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (435.9 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (175.0 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:March 26, 2018
Document ID:212918

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes the issue specific to the "Connection refused" error from Advanced Message Queuing Protocol (AMQP) server which can be seen in Cisco Connection Online (CCO) osmosix.log file.

    Prerequisites

    Requirements

    Cisco recommends that you have knowledge of these topics:

    • Linux Virtual Machine (VM)
    • CloudCenter

    Components Used

    This document is not restricted to specific software and hardware versions.

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

      

    Problem

    When a VM is deployed or terminated or suspended, the process gets stuck in terminating or suspending state forever. The exception can be found in osmosix.log files from CCO, as shown in the image. 

     Logs from Rabbit Server are as shown in the image.

    Solution

    In order to solve this issue, you need to check all the necessary port that are open for communication between the components.

    This issue was resolved by the addition of proper Domain Name Server (DNS) name in CCO’s and Rabbit's host file as the DNS server was not able to resolve the custom DNS name provided to Rabbit server.

    TAC Authored

    Contributed by Cisco Engineers

    • Vihar Kuruppathukattil
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products