Hi,
I'm running 5.6.1, and the redis server on port 6379 seems to be being
being killed every so often:
[root@server conf]# grep -i 'Killed Process' /var/log/messages
Jul 18 13:57:41 server kernel: Killed process 9531, UID 492, (redis-server)
total-vm:655908kB, anon-rss:518840kB, file-rss:296kB
Jul 18 13:57:48 server kernel: Killed process 2105, UID 492, (redis-server)
total-vm:655472kB, anon-rss:518980kB, file-rss:240kB
Jul 18 13:57:48 server kernel: Killed process 2457, UID 492, (httpd)
total-vm:825496kB, anon-rss:43428kB, file-rss:552kB
The pf watcher crontab command doesn't seem to restart it - perhaps it
should? (this I've put in /etc/crontab)
*/5 * * * * pf /usr/local/pf/bin/pfcmd service pf watch
Here's a really crappy script to auto start it again: (I've put it
in /usr/local/bin/redischeck
)
#!/bin/bash
/etc/init.d/packetfence-redis-cache status > /dev/null 2>&1
if [[ $? == 3 ]]; then
/etc/init.d/packetfence-redis-cache start > /dev/null 2>&1
fi
Add this to /etc/crontab to run every minute:
* * * * * root /usr/local/bin/redischeck
I've also added these settings to /usr/local/pf/conf/redis_cache.conf to
hopefully stop runaway memory usage:
maxmemory 4G
maxmemory-policy allkeys-lru
Cheers,
David
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
