in progress redis issue

soaringeagle
@soaringeagle
2 months ago
3,230 posts
redis just caused a panic attack!
i added some css to the skins html.css that was suposed to be a beveled customized scrollbar (webkit) when i didn't see the desired result i simply removed the code
thats when the panic set in cause the index page stopped loading css at all
i tried restoring the totaly non customized css still nothing restarted litespeed upgraded litespeed downgraded litespeed finaly shut off redis use in acp and the page loaded again
had to then restart mariadb and redis and renice them

i could then re-enable the site to use redis
i do use full page caching
just adding and removing valid css shouldn't cause 1 page and 1 page only to stop loadijng css
scared the hell out of me cause my month long trip meant i couldn't cover the backup costs and didn't have an active backup and wont till next wednsday

ps did you see my other post a few days ago maybe a week ago about the pending images checkboxes being missing since a recent update (beta core, don't mind helping you test)


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

updated by @soaringeagle: 04 Sep 2019 11:20:14AM
soaringeagle
@soaringeagle
2 months ago
3,230 posts
ok remember i said i was having a long term issue with my siitemap crawler not finishing and it seemed to be malformed image urls
months of testing (and upgraded internet speed) i found that if i ran it flat out 25 crawler threads it finished usualy
then i found errors in the activity log
related to redis
i think the isdsues been redis all along (wil do a test today with redis disabled)

[30-Aug-2019 11:02:32 America/New_York] PHP Fatal error:  Uncaught RedisException: read error on connection in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php:922 [4]
Stack trace: [16]
#0 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php(922): Redis->hGetAll('a4703m7') [1]
#1 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/cache.php(655): _jrRedis_redis_cache_maintenance() [6]
#2 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/misc.php(1305): jrCore_cache_maintenance() [6]
#3 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/include.php(899): jrCore_ten_minute_maintenance_worker(Array) [6]
#4 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/misc.php(302): jrCore_process_exit_listener(Array, Array, Array, Array, 'process_exit') [6]
#5 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/util.php(733): jrCore_trigger_event('jrCore', 'process_exit', Array) [6]
#6 /var/www/vhosts/dreadlock in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php on line 922 [4]
#0 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php(922): Redis->hGetAll('a4703md') [1]
[30-Aug-2019 14:43:55 America/New_York] PHP Fatal error:  Uncaught RedisException: read error on connection in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php:946 [2]
#0 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php(946): Redis->exec() [2]
#6 /var/www/vhosts/dreadlockssite.com/ht in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php on line 946 [2]
#0 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php(922): Redis->hGetAll('a4703mb') [1]
#0 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php(922): Redis->hGetAll('a4703m6') [1]
[30-Aug-2019 17:04:23 America/New_York] PHP Fatal error:  Uncaught RedisException: read error on connection in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php:546 [5]
#0 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php(546): Redis->exec() [5]
#1 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/cache.php(407): _jrRedis_redis_delete_all_cache_entries(NULL, NULL) [5]
#2 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/index.php(5489): jrCore_delete_all_cache_entries() [5]
#3 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/module.php(293): view_jrCore_cache_reset_save(Array, Array, Array) [5]
#4 /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/router.php(182): jrCore_run_module_view_function('view_jrCore_cac...') [5]
  thrown in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrRedis-release-1.1.4/include.php on line 546 [5]
[30-Aug-2019 18:12:00 America/New_York] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 4718592 bytes) in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/mysql.php on line 543 [1]
[30-Aug-2019 18:12:00 America/New_York] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 1105920 bytes) in /var/www/vhosts/dreadlockssite.com/httpdocs/modules/jrCore-release-6.4.0b8/lib/misc.php on line 252 [1]



--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
michael
@michael
2 months ago
7,050 posts
Why do you need redis if you have litespeed? both are caches, seems like one or the other would do.
soaringeagle
@soaringeagle
2 months ago
3,230 posts
redis is database cache you suggested beccause my database was so huge. litespeed private cache barely gets any hits public cache dont work will with multiple sites it does get alot of static file hits


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
brian
@brian
2 months ago
9,894 posts
michael:
Why do you need redis if you have litespeed? both are caches, seems like one or the other would do.

Litespeed is a web server, Redis is a data structure server - they are not the same thing at all.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
brian
@brian
2 months ago
9,894 posts
I'm checking this out - none of the Redis accesses should have uncaught exceptions.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
brian
@brian
2 months ago
9,894 posts
The root cause of this is your Redis server (or server) is overloaded and is taking longer than 5 seconds to respond to the Redis command, which causes a READ timeout on the socket.

So right now key functions all expect a true/false return and are not wrapped in a try/catch structure. Since the root cause of these errors is a server failure I will try to add additional try/catches in as I update the module, but it's not a high priority.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

updated by @brian: 04 Sep 2019 11:20:03AM
soaringeagle
@soaringeagle
2 months ago
3,230 posts
ok overloaded is in.. what.. ram
ram use is high because mysqltuner keeps commending i increase innodb cache ..i can't remember the exact 1
but its suggesting i increase it to over 25-28 gigs on a 32 gig ram system
cpu use isnt generally all that high iunless i am trying to run the sitemap crawler at 25 threads
(i used to just ruun it at 2 and lat it take 4 days tio crawl but then they stopped working and hadnt gotten a crawl done in montrhs till i realized it would not stall usualy if i ran it fast enough to complete in just 6 or so hours

before seeing these errors i thought it was a timeout ..i had lowered the interaction timeout since it was way high from when the vid converter and inttegbrity check werent completing (no longer an issue)
i think i reset that to default

what exactly do you mean by "overloaded" and should i just reduce the ram footprint by adjusting a few things in my.cnf
right now it hovers around 70%


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
soaringeagle
@soaringeagle
2 months ago
3,230 posts
update: its confirmed the sitemap crawler issue iu had was from redis all along..wich has been ongoing issue for months!

redis and mariadb are running at highest priorities with litespeed 1 lower
since disabling redis for the 1st time in many months (before june at least) i'm able to get a fill 1 million + page crawl


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

Tags