Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ERROR: Unable to connect to DB

    I can't log in with the username and password I always used in the past, is the fact that the DB is down mean that the log in credentials are not available either? This seems bad.

  • #2
    Couple of questions? Is your system working or are you experiencing issues? Are you able to access Director? What release are you on? And what credentials are you trying to use?

    Comment


    • #3
      Is this really on the old conference bridge?

      Comment


      • #4
        Yes this is the converged conference bridge. I can't use instant message and when I try to use conference codes it says the call cannot be connected and hangs up. Everything else Shoretel related it working. I'm on 12.3 at the moment, the conference bridge is 7.1 I think.

        check out these errors, I think they are happening because of disk space but I dont know how to navigaet linux to get in there and free up space, or even why there is no space left.

        When I login to the CB (using a defualt username and password the one we used to always use isn't even working):

        Message from [email protected] at Wed May 13 00:24:32 2015 ...

        TBG-SHORECONF sip_log_thsdb: 774 FATAL Startup error: Couldn't open data base connection -- Killing THS

        other messages:
        Getting Private key
        Insufficient disk space; try again later


        Getting Private key
        Insufficient disk space; try again later
        Insufficient disk space; try again later
        returntosender: cannot select queue for acs_alert
        Insufficient disk space; try again later
        returntosender: cannot select queue for postmaster
        putbody: write error: No space left on device
        Error writing control file qft4D6sOY2011713: No space left on device

        Comment


        • #5
          In case anyone else ever has this issue. Once you clear out some hard drive space, the problem goes away. You need to log in to the server via WINSCP or something similar, then go into the logs area and clean house. I just had a heck of a time getting to there even tho I had a feeling that was the issue. I hadn't done this before so I didn't know the root passwords and all that info but once you get that you can fix this pretty easily.

          Comment

          Working...
          X