Announcement

Collapse
No announcement yet.

http 503 timeout on merge topics

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Bug / Issue] http 503 timeout on merge topics

    vBulletin Version
    5.3.3

    PHP Version
    7.1

    MySQL Version
    5.7.19

    Any Addons installed
    1 custom addon, but without is its still broken.

    Does the issue occur in a default style?
    yes

    Does the issue occur using the English language provided?
    yes

    Error message on the screen'
    503
    Browser and Browser version used.
    chrome - Version 62.0.3202.94 (Official Build) (64-bit)

    Did you clear the browser cache and did the error continue?
    yes

    A list of steps that can be used to recreate the issue.
    a. go to a place that some active topics (20/30 each)
    b. select & merge them
    c. get a time out error

    (got +/- '1300000' rows in the node table)

    http://tracker.vbulletin.com/browse/VBV-17990
    Last edited by klaasmidhold; Wed 13th Dec '17, 5:07am. Reason: added bug link

  • #2
    A 503 error is a server side error which indicates the server lacks the resources to process the request. Perhaps your PHP memory limit is set too low to handle the request.

    Comment


    • #3
      Yet, all merge and move actions on posts and topics seem to be very resource consuming in vbulletin5.

      I tend to have server errors when moving or merging more than a few posts or topics, and it takes sometimes around a full minute to do the job, even with a powerfull server (12cpus/24gigs ram).
      There is definitely room for code improvement in this area.

      Comment


      • #4
        How big are these topics that you're merging?

        A timeout can't be controlled by us. They are due to limits on the server. You will need to look at the PHP, MySQL, and Apache error logs to see which timeout is being triggered. Then you should see if you can increase these.

        The number of CPU cores or the memory installed is also pretty irrelevant on a misconfigured server. Each process has limits set for those as well. Different errors will be returned if it were a memory issue.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API - Full / Mobile
        Vote for your favorite feature requests and the bugs you want to see fixed.

        Comment


        • #5
          they have 20 topics each, php mysql and nginx have more than 8gb each and we still get the error

          Comment


          • #6
            Originally posted by klaasmidhold View Post
            they have 20 topics each, php mysql and nginx have more than 8gb each and we still get the error
            Have you checked the php max execution time (default 30 secs) maybe thats where things are breaking once it hits the time limit

            Comment


            • #7
              Originally posted by klaasmidhold View Post
              they have 20 topics each, php mysql and nginx have more than 8gb each and we still get the error
              You're not getting a memory error so the amount of memory assigned is irrelevant in this scenario. You're experiencing a server timeout. Please reread my previous post and respond with the time out values for each component of your server... NGINX, PHP, and MySQL. If you're using NGINX as a passthrough, then you also need to look at Apache's configuration.
              Translations provided by Google.

              Wayne Luke
              The Rabid Badger - a vBulletin Cloud demonstration site.
              vBulletin 5 API - Full / Mobile
              Vote for your favorite feature requests and the bugs you want to see fixed.

              Comment

              Related Topics

              Collapse

              Working...
              X