Conversation
Notices
-
Embed this notice
Mitex Leo (mitexleo@infosec.exchange)'s status on Monday, 12-Feb-2024 06:37:12 JST Mitex Leo -
Embed this notice
Shanie (shanie@mastodon.tails.ch)'s status on Monday, 12-Feb-2024 06:37:11 JST Shanie @mitexleo @dansup @pixelfed You may need syslog (which defaults to debug as per docs) which could be the firehose. Then just try to change the avatar and turn that off because it will fill up quickly. Search for the file name you uploaded in the log (or if that gets omitted, just find the issue manually) and see where the error is.
Hint: it’s usually always permissions.
-
Embed this notice
Mitex Leo (mitexleo@infosec.exchange)'s status on Tuesday, 13-Feb-2024 11:36:59 JST Mitex Leo @shanie @dansup @pixelfed I'm seeing this for the first time. Maybe because of setting log level to "syslog" ?
-
Embed this notice
Shanie (shanie@mastodon.tails.ch)'s status on Tuesday, 13-Feb-2024 11:36:59 JST Shanie @mitexleo @dansup @pixelfed I mean it says that "syslog" is a valid configuration option but apparently it might not be. I see there's an "errorlog" option. Would be nice if these actually meant something to someone other than to the person who programmed it.
-
Embed this notice
Shanie (shanie@mastodon.tails.ch)'s status on Tuesday, 13-Feb-2024 11:37:00 JST Shanie Keep in mind "Invalid log level", first line in your log, is setting the logging to "emergency" level logging which does not default to "debug".
-
Embed this notice
Mitex Leo (mitexleo@infosec.exchange)'s status on Tuesday, 13-Feb-2024 11:37:01 JST Mitex Leo @shanie @dansup @pixelfed Well, I'm still not seeing anything related to the avatar issue. Here's the log file: https://share.internxt.com/sh/file/e884b38f-a333-4ca6-8b4e-c6ff965fcc1e/05578206074cc95203450cf3b89ea489817875de8481d55e8ef48286e38da1b6
-
Embed this notice