Error during startup: #5805
Replies: 1 comment 4 replies
-
I'm afraid we do not have much information to reason about this exception. All we can tell There is no RabbitMQ or Erlang version information, no details if this was an upgrade, and so on. I can reproduce this exception if I use the value as is: S = [99,58,47,85,115,101,114,115,47,1045,1074,
1075,1077,1085,1080,1081,47,65,112,112,68,
97,116,97,47,82,111,97,109,105,110,103,47,
82,97,98,98,105,116,77,81,47,108,111,103,47,
114,97,98,98,105,116,64,76,65,80,84,79,80,
45,56,86,72,86,86,80,75,73,46,108,111,103]. and it indeed cannot be formatted as a string any way I try. It includes values such as Looking at the code suggests these lines: i(log_files, State) ->
{State, [list_to_binary(F) || F <- rabbit:log_locations()]}; so the log location path is encoded in a way that is not compatible with supervisor child ID names the runtime supports. Paths with non-ASCII characters are known to be problematic and highly not recommended. This is indeed You can disable the plugin and use Prometheus instead or use an installation and node data directory that only has ASCII characters. That's as much as I can recommend with a single stack trace and no other details to work with. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Beta Was this translation helpful? Give feedback.
All reactions