@scottalanmiller that's weird, we do use graceful-fs which should handle that automatically
It's possible in done cases this doesn't apply before an operation is executed. When did you encounter an issue?
Seeing this in my log every 30 minutes, thus far it's happened at 12:30 - 13:00 - 13:30 - 14:00 & 14:30
2014-10-31T12:30:00.898Z - error: WRONGTYPE Operation against a key holding the wrong kind of value
2014-10-31T13:00:00.897Z - error: WRONGTYPE Operation against a key holding the wrong kind of value
Running latest master, doesn't break the forum, assuming it's to do with redis saving?
Is there a full stack trace available?
@julian That's all it gives me. There's unrelated warns around them, like the Twitter issue I sent you, and some spam be gone "registration was denied" warns. But no details as to what it could be.
I'll run nodebb in development mode for the 15:30 err, and see if it offers any more details.
EDIT: Nope, that's all I get.
Poss Poss related?
Happened at the same time as moving these two topics: (moving lots of topics into a new category)
[Fri, 31 Oct 2014 17:08:50 GMT] - a_5mith(uid 1) moved topic (tid 1932) [Fri, 31 Oct 2014 17:08:50 GMT] - a_5mith(uid 1) moved topic (tid 1984)
I don't know why I keep asking people for stack traces when Redis explodes. They're almost always useless because of all of the redis library method calls.
If it's happening every 30mins thats probably the notifications prune function.
Can you check out the type of the key
notifications it should be a zset.
redis-cli type notifications
localhost:6379> type notifications set
Yeah that should be a
zset once of the previous upgrades updates that. You can fix it manually by deleting it by
del notifications but you will lose some notifications.
localhost:6379> del notifications (integer) 1 localhost:6379> type notifications none
This looking good now?
Yeah now go create a notification on the forum and recheck the type it should be zset.
@baris Yep, that's the ticket, cheers buddy. Can be marked as solved.