• Register
    • Help

    striker  0 Items
    Currently Supporting
    • Home
    • News
    • Forum
    • Wiki
    • Support
      • Manage Subscriptions
      • FAQ
      • Support For
        • VaultWiki 4.x Series
        • VaultWiki.org Site
    • What's New?
    • Buy Now
    • Manual
    • 
    • Support
    • VaultWiki 4.x Series
    • Bug
    • read error on connection in /library/Redis/lib/Credis/Client.php on line 1104

    1. Welcome to VaultWiki.org, home of the wiki add-on for vBulletin and XenForo!

      VaultWiki allows your existing forum users to collaborate on creating and managing a site's content pages. VaultWiki is a fully-featured and fully-supported wiki solution for vBulletin and XenForo.

      The VaultWiki Team encourages you to join our community of forum administrators and check out VaultWiki for yourself.

    Issue: read error on connection in /library/Redis/lib/Credis/Client.php on line 1104

    • Issue Tools
      • View Changes
    1. issueid=4915 February 15, 2017 9:12 PM
      Alfa1 Alfa1 is offline
      Distinguished Member
      read error on connection in /library/Redis/lib/Credis/Client.php on line 1104

      I have thousands of these:
      Code:
      CredisException: read error on connection - library/Redis/lib/Credis/Client.php:1104 
      Generated By: Unknown Account, A moment ago
      Stack Trace
      #0 /library/Redis/Cm/Cache/Backend/Redis.php(376): Credis_Client->__call('hget', Array)
      #1 /library/Zend/Cache/Core.php(329): Cm_Cache_Backend_Redis->test('xf_data_vw_atta...')
      #2 /vault/core/model/datastore/xf.php(29): Zend_Cache_Core->test('xf_data_vw_atta...')
      #3 /vault/core/model/datastore/xf.php(108): vw_Datastore_Model_XF->_isset('vw_attach_usage')
      #4 /library/vw/XenForo/CodeEventListener.php(59): vw_Datastore_Model_XF->db_fetch(Array)
      #5 /library/XenForo/CodeEvent.php(90): vw_XenForo_CodeEventListener::init_dependencies(Object(XenForo_Dependencies_Public), Array)
      #6 /library/XenForo/Dependencies/Abstract.php(215): XenForo_CodeEvent::fire('init_dependenci...', Array)
      #7 /library/XenForo/CssOutput.php(594): XenForo_Dependencies_Abstract->preLoadData()
      #8 /css.php(12): XenForo_CssOutput::run()
      #9 {main}
      Request State
      array(3) {
        ["url"] => string(84) "https://forum.com/css.php?css=xenforo,form,public&style=2&dir=LTR&d=1487206330"
        ["_GET"] => array(4) {
          ["css"] => string(19) "xenforo,form,public"
          ["style"] => string(1) "2"
          ["dir"] => string(3) "LTR"
          ["d"] => string(10) "1487206330"
        }
        ["_POST"] => array(0) {
        }
      }
    Issue Details
    Issue Number 4915
    Issue Type Bug
    Project VaultWiki 4.x Series
    Category General
    Status Not a Bug
    Priority 2 - Fatal / Database Errors
    Affected Version 4.0.16
    Fixed Version (none)
    Milestone (none)
    Software DependencyXenForo 1.x
    License TypePaid
    Users able to reproduce bug 0
    Users unable to reproduce bug 0
    Attachments 0
    Assigned Users (none)
    Tags (none)




    1. February 16, 2017 8:59 AM
      pegasus pegasus is offline
      VaultWiki Team
      It seems like there is an issue with the Redis configuration or the Redis instance if Zend Cache cannot read from it. VaultWiki doesn't do anything special here. It doesn't communicate directly with Redis. VaultWiki is asking XenForo's cache object, which happens to be a Zend Cache, "Hey, do you have a key 'vw_attach_usage' in your storage?" Zend Cache passes this question along to Redis.

      Maybe your Redis instance crashed while you were away?
      Reply Reply
    2. February 19, 2017 10:02 AM
      pegasus pegasus is offline
      VaultWiki Team
      Per your other thread, indeed your Redis instance crashed. This was a post-crash error message that occurred because XenForo tried to read from Redis after Redis was already gone. In the case of this specific error message at least, it is a coincidence that the cache entry being requested has a key name that starts with 'vw_'; that just happened to be the next value requested after the crash.

      Your Redis logs will be more useful to you here, and since a crash was involved, you will probably need to talk to Redis developers and provide them with a backtrace from the crash. Then they will be able to give you more information about what caused it, and they will also be able to patch Redis so that it doesn't crash in that situation again.
      Reply Reply
    3. February 24, 2017 11:47 AM
      Alfa1 Alfa1 is offline
      Distinguished Member
      I have fixed this by upgrading redis and changing the redis settings.
      Reply Reply
    4. July 22, 2017 9:07 AM
      Alfa1 Alfa1 is offline
      Distinguished Member
      Unfortunately, this was not fixed with the upgrade. It is indeed not a vaultwiki bug. However, xenforo 2 will have redis built in, so it may be a good idea for VW to anticipate on that.
      Reply Reply
    + Reply

    Assigned Users
    Loading Please Wait
    Tags
    Loading Please Wait
    • Contact Us
    • License Agreement
    • Privacy
    • Terms
    • Top
    All times are GMT -4. The time now is 11:15 PM.
    This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Learn more… Accept Remind me later
  • striker
    Powered by vBulletin® Version 4.2.5 Beta 2
    Copyright © 2025 vBulletin Solutions Inc. All rights reserved.
    Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2025 DragonByte Technologies Ltd.
    Copyright © 2008 - 2024 VaultWiki Team, Cracked Egg Studios, LLC.