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

Awaiting Feedback Error by Member search

Discussion in 'Resolved Bug Reports' started by teletubbi, Aug 15, 2015.

  1. teletubbi

    teletubbi Well-Known Member

    Yesterday i got some error messages in ACP.

    All produced from same member.
  2. imthebest

    imthebest Formerly Super120

    Are you able to reproduce the problem with all add-ons disabled? What version of XF are you using? Do you have Enhanced Search installed?
  3. teletubbi

    teletubbi Well-Known Member

    I am using 1.4.10
    Is been running nearly 6 month. Before this error shows up i did not change anything.
    Elasticsearch is running from today. This message was from yesterday.

    I am digging into it. Looks like it is related to memchached.
  4. teletubbi

    teletubbi Well-Known Member

    I can reproduce it if i use the same string as in the error message.

    http : //www .pattayaforum.net/forums/search/member?user_id=2416

    This is an actual active member.
    But i don`t know where this url comes from.

    If i search for a a particular user i use the name instead of id.
    And i guess other members will do the search in the same way.

    So if i use the username in search it brings me to this member.
  5. Mike

    Mike XenForo Developer Staff Member

    What's your max search results? Higher search results sizes will require more memory usage to do permission filtering.

    Unfortunately though, PHP makes these errors very difficult to debug as there's no backtrace. I can't reproduce it as a guest, so it could be related to something with being logged in (including an add-on) or permissions.
  6. teletubbi

    teletubbi Well-Known Member

    Max per page 100.
    Max all 1000.

    Till now don't have this error again.

    But I can lower the max if this is a suggestion.
  7. Mike

    Mike XenForo Developer Staff Member

    A max of 1000 is potentially quite large -- it is 5 times the default -- and is likely the cause of this. I would experiment with lower values to see if that resolves it.

Share This Page