pujitm
Members
-
Joined
-
Last visited
Solutions
-
pujitm's post in Can’t sign into Connect as of today. was marked as the answer@elibosley can confirm/deny, but I believe this was an infra issue on our end.
-
pujitm's post in error writing to /var/log/unraid-api/unraid-api.log.1: No space left on device was marked as the answerOh! This actually looks simple. Your var/log only has 57M available, but /var/log/unraid-api contains ~68M of logs, which is more than that, so it doesn't have enough space to copy it (as part of logrotate).
Short term, you can delete the log files inside /var/log/unraid-api. The log output location was recently changed to /var/log/graphql-api.log recently for compatibility with the diagnostics tool. We also fixed an issue that generated a crap ton of logs.
Long-term, if you have long-uptimes and this issue persists, you could look into increasing the amount of ram allocated to /var/log. I found another forum post talking about it, and there seem to be many results on google as well.
-
pujitm's post in [Bug] UI cannot be interacted with after checking for update. was marked as the answerfixed in the connect plugin's latest release
-
pujitm's post in Latest release causing errors in logrotate was marked as the answerhey guys, the connect plugin's next release will fix this. sorry to keep yall hanging on such an annoying issue. we'll try to get it out for ya this week or early next week.
Edit: just shipped the release. 🤞
-
pujitm's post in pubkey ssh auth stopped working after updating to 2025.02.20.0835 Unraid Connect was marked as the answerfixed in today's release
-
pujitm's post in 2025.02.06.2108 -- can't clear notification count was marked as the answeri'm working on a fix, @kaiguy! in the meantime, you can run `unraid-api restart` from the terminal to reset notification counts.
