Skip to content

Conversation

@MCozhusheck
Copy link

Libtor does not accepts uppercase path for logging which results in error. In my case this path contains directory UPPERCASE but while processing it's transformed into lowercase which is invalid.

Sep 11 12:16:37.000 [warn] Couldn't open file for 'Log err file /home/maciej/uppercase/libtor/tor.log': No such file or directory
Sep 11 12:16:37.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
Sep 11 12:16:37.000 [err] Reading config failed--see warnings above.

Same problem when used relative path containing uppercase too:

Sep 11 12:52:10.726 [warn] Path for ControlPortWriteToFile (./UPPERCASE/mainnet/libtor/base_node/data/control_port) is relative and will resolve to /home/maciej/projects/tari/tari/target/release/./UPPERCASE/mainnet/libtor/base_node/data/control_port. Is this what you wanted?
Sep 11 12:52:10.726 [warn] Path for DataDirectory (./UPPERCASE/mainnet/libtor/base_node/data) is relative and will resolve to /home/maciej/projects/tari/tari/target/release/./UPPERCASE/mainnet/libtor/base_node/data. Is this what you wanted?
Sep 11 12:52:10.726 [warn] Fixing permissions on directory ./UPPERCASE/mainnet/libtor/base_node/data
Sep 11 12:52:10.000 [warn] Couldn't open file for 'Log err file ./uppercase/mainnet/libtor/base_node/tor.log': No such file or directory
Sep 11 12:52:10.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
Sep 11 12:52:10.000 [err] Reading config failed--see warnings above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant