Uploaded image for project: 'odlparent'
  1. odlparent
  2. ODLPARENT-35

ODL won't boot correctly if dead DNS server is present.

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Resolution: Unresolved
    • None
    • None
    • General
    • None
    • Operating System: All
      Platform: All

    • 5991

    Description

      1. cat /etc/resolv.conf
      2. Using IPTABLES cut each IP address reported in step 1 so that
      traffic sent to them is silently dropped.
      3. /where/your/odl/is/located/bin/start

      These "step 2" actions could also work but they were not tested:

      • Cut only one DNS IP address, make the rest inaccessible (connection
        refused or so on).
      • Configure a DNS server that takes 2 minutes to provide any data.

      The symptoms are that the ODL takes significantly longer to boot and the karaf console becomes inacessible (attempt to connect to the karaf console will result in opened connection whose other end does not respond to anything).

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Unassigned Unassigned
            jbehran@cisco.com Jozef Behran
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: