igbinary_unserialize_header warning that keeps appearing

  • Resolved carlcs

    (@carlcs)


    5 years ago

    we kept seeing this warning and no amount of clearing the object cache helped and we had to disable the redis object cache. what’s this error exactly?

    igbinary_unserialize_header: expected at least 5 bytes of data, got X byte(s)

    X is usually 1 but sometimes 2

    we’re using PhPRedis 5.0.2. the settings we have in our wp-config.php are

    define( 'WP_REDIS_SCHEME', 'tls' );
define( 'WP_REDIS_DATABASE', intval( 1, 10 ) );
define( 'WP_REDIS_PORT', intval( 6379, 10 ) );
define( 'WP_REDIS_HOST', 127.0.0.1 );
define( 'WP_REDIS_IGBINARY', true );

    thanks

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    I’d try upgrading to the latest version of igbinary and phpredis, restart the servers and then flush your cache. If that doesn’t help, just use the default serializer.

    If you have space issues and NEED to use the igbinary then consider using the business edition.

    Thread Starter carlcs

    (@carlcs)

    thank you

    although i think for now, we’ll probably forgo using this. We had an issue in Woocommerce processing refunds that disappeared when this was removed

    thanks

    Thread Starter carlcs

    (@carlcs)

    also, how do i use the default serializer? just remove this line?

    define( 'WP_REDIS_IGBINARY', true );

    i removed just that line before and it crashed our site. so i should remove that line, clear the redis object cache via command line, then try again?

    thanks

    Plugin Author Till Krüss

    (@tillkruess)

    You need to clear your cache after doing that.

    Plugin Author Till Krüss

    (@tillkruess)

    It’s optimized for WooCommerce ????

    Thread Starter carlcs

    (@carlcs)

    thank you. i will test when i have an open window for testing

    Thread Starter carlcs

    (@carlcs)

    thanks for the tip. clearing the object cache after removing

    define( 'WP_REDIS_IGBINARY', true );

    eliminated our previous issues with reverting back to the default serializer. observing for further issues now

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘igbinary_unserialize_header warning that keeps appearing’ is closed to new replies.