Clovertech

hciconnstatus errors

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › hciconnstatus errors

  • Creator
    Topic
  • January 3, 2006 at 2:29 pm #48232
    Anonymous
    Participant

      Happy New Year everyone!

      Our server crashed last night – and it took me several hours to get it back up and get our interfaces functioning again.

      Now, this morning, we find that on at least one of our sites, hciconnstatus doesn’t work.  We get the error:

      bgerror failed to handle background error.

         Original error: unmatched open brace in list

         Error in bgerror: invalid command name “bgerror”

      Error: can’t wait for variable “someBogusVariable”:  would wait forever

         while executing

      “vwait someBogusVariable”

         (procedure “hciEventLoop” line 3)

         invoked from within

      “hciEventLoop                   “

         (procedure “main” line 52)

         invoked from within

      “main $argc $argv”

         (file “/qdx/qdx5.3/integrator/bin/hciconnstatus” line 149)

      I have cleared the stats using hcimsiutil -R, and have even tried initializing the databases.  Any input on our error?

    • Creator
      Topic
    Viewing 3 reply threads
    • Author
      Replies
      • January 5, 2006 at 4:35 pm #58085
        Anonymous
        Participant

          FYI – another reboot of the server fixed the problem.  Not sure what was hosed up, but the extra reboot got it.

        • February 28, 2006 at 8:43 pm #58086
          Ben Hochstedler
          Participant

            I get the same error occassionally when running hciprocstatus (run once a minute to watchdog processes):

            Quote:

            bgerror failed to handle background error.

              Original error: broken pipe

              Error in bgerror: invalid command name “bgerror”


            Although I don’t get the other error messages that hciconnstatus produced.  I too have found that rebooting is required to clear the condition.

            Have you seen the problem happen again?

            What OS did it happen on?

            Any further clues what caused it?

            I’m running:

            Windows 2000 Server SP4

            QDX 5.2

            btw, I submitted another post before I found this thread.

          • March 7, 2006 at 7:50 pm #58087
            Scott Folley
            Participant

              I am guessing somewhat but I believe what you have is a cmd_port file that still exists and hitting a port that is listening but is not an actual cloverleaf port.  A “proper” shutdown during the reboot cycle and the elimination of a process actually listening on that port is probably what is cleaning things up.  It is likely that you would do fine by doing a manual cleanup of all cmd_port, pid, and wpid files associated with the site.  Just my 2 cents, hope it helps.

            • March 7, 2006 at 8:05 pm #58088
              Ben Hochstedler
              Participant

                Thanks for the reply.  I’ll have to look into that as the possible root cause.

                I’ve identified two workarounds for the problem:

              • Don’t read the output from hciprocstatus – just look at the exit code and use -p and -e options (the bgerror in tcl happens because of a pipe failure–if there’s no redirection of its stdout/stderr, the bgerror does not occur)

              • Add file to the site to force hciprocstatus to exit with the following tcl proc:

                • Quote:

                proc bgerror err {

                   exit 69

                }

          • Author
            Replies
            • Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.