![]() ![]() TBH, I'm not completely surprised that it ended up being system resources. I'm almost certain that this will be useful for other users. I'm really glad to hear that you worked it out and thanks for reporting back to let us know. Still it may be worth posting there? If you do, please feel free to cross post a link to that here. The Canvas Google group has been quite good and contains some really good info, but getting timely assistance for specific issues can be a bit hit and miss sometimes. Canvas have a support Q&A, sort of like forums, although my experience suggests that it's not so great for technical self-hosting related issues. Assuming that the log file is /var/log/redis/redis-server.log then to get just the last 30 lines, do this: tail -30 /var/log/redis/redis-server.logįeel free to post here if you want my 2c on it. I suggest that you recreate the issue, and get the last few lines of the redis log so you can try to see exactly what it's up to. I'm not recommending that you necessarily follow the suggestion to modify /etc/nf, but starting at the log file (probably /var/log/redis/redis-server.log) or checking via journalctl seems like a really good idea! This answer (again on the same Q&A you linked to) sounds like a sensible approach and has quite a few upvotes. Although I suggest that you keep reading before you race off and try that blidly. ![]() See this answer on the Q&A you linked to. According to what I've read now about the setting you tweaked though, that should suppress the error message, but not necessarily fix the underlying issue. Redis can't write to disk? (TBH, seeing as it's intermittent, I'm really not sure but perhaps?). FWIW, you're best referring to a particular answer via clicking the "share" button below the relevant answer and then copy/pasting the URL.Īnyway, I'm no Redis expert, but after doing a but more reading, I'm wondering if it's a permissions issue? I.e. Re the StackOverflow Q&A that you refer to, unfortunately the answer order isn't guaranteed to be the same, and many answers include the command you note. But you beat me to that and it sounds like you've ruled that out. Next I was going to say that it's probably also worth double checking free disk space. The fact that you say that it often works eventually, suggests that it may be some sort of race condition?! Intermittent issues can be notoriously hard to resolve in my experience. Any possible suggestions?Īs always, thank you for your help Jeremy! They have to retry at least 3-4 times before the upload successfully completes. It is causing quite a bit of headache for some teachers trying to upload files onto their courses. Just for good measure, I increased the disk space on the / root directory but I'm still getting the error. However the error still persists even after this. I visited this StackOverflow topic at: and followed the second post and tried disabling the snapshot using "config set stop-writes-on-bgsave-error no". Even uploading small video files in the range of 70-100 MB still triggers this error. I doubled the memory on the server from 8 to 16 and monitored the memory usage at around 20%. What is the Debian command to process the upgrade once it is released?Īs for the Redis error, I ruled out memory usage. Jeremy: That sounds great! I look forward to the patched version very soon. Please check Redis logs for details about the error.'' Commands that may modify the data set are disabled. ![]() caused byĮRR Error running script (call to f_55328419e7888a8fff3c59901e25d48909168320): 30: -MISCONF Redis is configured to save RDB snapshots, but is currently Please check Redis logs for details about the error. Request_parameters: ''''Įxception_message: ''ERR Error running script (call to 30: -MISCONF Redis is configured to save RDB snapshots,īut is currently not able to persist on disk. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |