pixitha

This seems to have happened to me again, after upgrading from 7.1.2, to 7.2.4, the next day after I used it for a bit, I started to get 500s again for the main GUI. So far, fixing the symlink and such has not fixed it like before... edit, I had to manually remove the state folder, before creating the symlink to fix it.

I just got this issue tonight, out of the blue. I've not touched the OS/plugins/dockers in weeks, but the webgui suddenly stopped working today with this exact same error. Missing the symlink to the state. I'm on 7.0.0 as well. Def seems like there might be some sort of bug or errant plugin code.... May 8 00:00:02 towerstor Plugin Auto Update: Checking for available plugin updates May 8 00:00:06 towerstor Plugin Auto Update: Checking for language updates May 8 00:00:06 towerstor Plugin Auto Update: Community Applications Plugin Auto Update finished May 8 01:13:43 towerstor root: /mnt/cache: 82.5 GiB (88530468864 bytes) trimmed on /dev/nvme0n1p1 May 8 02:56:35 towerstor root: /mnt/vms: 211.2 GiB (226770313216 bytes) trimmed on /dev/sdi1 May 8 02:56:37 towerstor root: /var/lib/docker: 32.1 GiB (34504237056 bytes) trimmed on /dev/loop2 May 8 22:39:16 towerstor crond[1834]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 May 8 23:39:01 towerstor crond[1834]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 May 9 00:00:01 towerstor Plugin Auto Update: Checking for available plugin updates May 9 00:00:06 towerstor Plugin Auto Update: Checking for language updates May 9 00:00:06 towerstor Plugin Auto Update: Community Applications Plugin Auto Update finished May 9 00:39:01 towerstor crond[1834]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 This is the only thing in the syslogs

/appdata/freshrss/www/freshrss/extensions

This is a bug from long ago, I get this still, even though it was supposed to have been fixed a while back.