Any Tubex users seen this error ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Wicked 1
    Confirmed User
    • Feb 2003
    • 188

    #1

    Any Tubex users seen this error ?

    An Error Has Occurred
    Could not connect to MySQL database
    The site administrator has been notified of this issue and will look into it as soon as possible
    Could not append data to the error log!

    Any Ideas ?

    Thanks.
  • Babaganoosh
    ♥♥♥ Likes Hugs ♥♥♥
    • Nov 2001
    • 15841

    #2
    Your mysql login information is probably incorrect or mysql isn't running.

    Then the script was unable to add debug information to the error log because either the path or permissions were incorrect.
    I like pie.

    Comment

    • Wicked 1
      Confirmed User
      • Feb 2003
      • 188

      #3
      The strange thing is the script throws back at you the databse name,login and username.

      I considered a typo causing it,so I deleted the existing db,user and password and made another with 100% match to what the script error said.

      Still cannot connect.

      The server has multiple wordpress blogs running on it with no db connection issues.

      Probably right on the path being incorrect for the error reporting as I've found JMB's scripts are not so good at auto detecting paths depending on the sever setup.


      Hmm I'll keep looking for an answer.

      Thanks,

      Comment

      • Babaganoosh
        ♥♥♥ Likes Hugs ♥♥♥
        • Nov 2001
        • 15841

        #4
        That's a pretty dumb error message. Wow. Going to have to test that one out and see if it happens to me. I can't imagine why it would echo the login information.
        I like pie.

        Comment

        • sn0man
          Registered User
          • Oct 2011
          • 5

          #5
          First thing that comes to mind on the topic of the error message output to screen is your php.ini settings.

          Look for "display_errors" in your php.ini

          Make sure it's set to "Off"

          PHP Code:
          display_errors = Off 
          
          If that doesn't stop it from doing that, the script itself is probably recording the error into a variable and echoing it to the screen.

          As for why it's not talking to the DB in the first place, check the log files to see what the true error message is.

          Comment

          • socialcracker
            Confirmed User
            • Oct 2011
            • 52

            #6
            I think it could be incorrect SQL information.. Never really faced such problem !

            Comment

            • pm2000
              Confirmed User
              • Aug 2002
              • 3135

              #7
              never seen it that weird

              Comment

              Working...