| View previous topic :: View next topic |
| Author |
Message |
netshade
Tux's lil' helper
Joined: 02 Jan 2004
Posts: 88
Location: Sweden
|
 Posted: Wed Sep 11, 2024 7:49 am Post subject: Redis server hangs. |
 |
|
I have no idea where I should ask this question or how to figure out the issue but since it happened on two of my Gentoo-servers I figure I'd start here.
I don't have any ideas where to look for info regarding this and can't figure out what is wrong so I'm sorry for a very confused post and if it's already solved somewhere I will be grateful for any hints.
It all started on my second server, after a reboot I can't seem to connect to Redis instance running. First I thought it was just a hickup and ignored the issue by just pointing everything using redis to my first host. (Tried restarting the service but got no errors and needed the services running.)
The day before yesterday the same issue occured on my first host. A reboot and redis is dead.
Running just hangs the prompt. No feedback, no errors, it just does nothing and I can't find any logs (which probably is my fault and a lack of knowledge).
Tried restarting the service and the log returns:
| Code: | sep 10 15:08:02 server.com systemd[1]: Started A persistent key-value database
...
A start job for unit redis.service has finished successfully. |
That doesn't help, at all. So I tried running the exec manually with a reference to the config-file which results in a hanging prompt.
Stopped that and removed the config with the same result.
On one of the hosts I keyworded redis and updated it but still the same result. What I noticed was that I had to add jemalloc to use-flags as well and did so.
Also tried | Code: | | dmesg/journalctl -k |
So, my first question is, where or how do I start figuring this out?
I usually solve most of my issues reading logs and backtracing what I did but in this case the logs give nothing and google is giving me a hard time finding anything. It could be me being terrible at googling as well.
_________________
From where the shadows turn into nightmare, netshade greets you... |
|
| Back to top |
|
 |
Banana
Moderator
Joined: 21 May 2004
Posts: 1727
Location: Germany
|
|
| Back to top |
|
|
Zucca
Moderator
Joined: 14 Jun 2007
Posts: 3695
Location: Rasi, Finland
|
| Posted: Wed Sep 11, 2024 2:08 pm Post subject: |
|
|
I'd try to make redis output debugging messages. Maybe those reveal more.
You should be able to pass extra command line parameters to it by | Code: | | systemctl edit <redis.service> |
... if my memory serves me correctly.
_________________
..: Zucca :..
| My gentoo installs: | init=/sbin/openrc-init
-systemd -logind -elogind seatd |
| Quote: | | I am NaN! I am a man! |
|
|
| Back to top |
|
|
netshade
Tux's lil' helper
Joined: 02 Jan 2004
Posts: 88
Location: Sweden
|
| Posted: Thu Sep 12, 2024 7:11 am Post subject: |
|
|
| Zucca wrote: | I'd try to make redis output debugging messages. Maybe those reveal more.
You should be able to pass extra command line parameters to it by | Code: | | systemctl edit <redis.service> |
... if my memory serves me correctly. |
I was looking into that but the process freezes before it outputs anything. (Tried running redis-server with debug-flag from command line.)
I can however add another thing I found yesterday.
The "redis-cli"-client doesn't work if I try other servers as well. Spun up a container with redis on the first host so I could get my services back up and running and using "redis-cli" pointing to it gives the same result as when trying the native server while connections from services and apps work.
Back to the drawing board.
_________________
From where the shadows turn into nightmare, netshade greets you... |
|
| Back to top |
|
|
|
Other Things Gentoo
