1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.4 Unexpected database error - too many connections

Discussion in 'Troubleshooting and Problems' started by MarkMark, Sep 17, 2015.

  1. MarkMark

    MarkMark Member

    What I don't understand is that this is happening when I have either one or no users online (we are a very small board).

    Any idea why?
  2. Brogan

    Brogan XenForo Moderator Staff Member

    It's a limit imposed by your host so you would need to contact them and ask them to increase the limit.
  3. MarkMark

    MarkMark Member

    Even if I don't actually have anyone online? Also, if I look at the server error log, there is nothing there?
  4. Brogan

    Brogan XenForo Moderator Staff Member

    Guests and bots will also count.

    If you are seeing that with no registered members online, the limit must be very low.

    Only your host can resolve it.
  5. MarkMark

    MarkMark Member

    Ok, thanks. Haven't had any issues until today, and have had lots online at the same time before. Will speak to host.
  6. MarkMark

    MarkMark Member

    Sorry to be a pain but just a quick question.

    My host is looking into the problem, but what confuses me is that, despite the errors, nothing shows up in my error log in the admin area - shouldn't there be some detail in here?
  7. Brogan

    Brogan XenForo Moderator Staff Member

    It's an error connecting to the mysql server, so occurs before the XF code runs.
  8. Wesker

    Wesker Well-Known Member

    We also had this issue frequently on our old server. We had to restart mySQL through SSH but it's never recommended to restart mySQL unless you have no choice as it can cause a table to be corrupt upon mySQL restarting.
  9. Jeremy P

    Jeremy P Well-Known Member

    @Wesker, this is controlled by the MySQL 'max_connections' setting. If you are running your own server, you can raise this value if the current value is troublesome. However, OP is using a shared/managed host, so that isn't relevant.

    Additionally, it is possible to shutdown/restart MySQL gracefully. I've only ever seen corruption from killing it unexpectedly (ie via killall or OOM).

Share This Page