Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory #2761

Open
8 tasks done
ilike2burnthing opened this issue Dec 12, 2023 · 3 comments

Comments

@ilike2burnthing
Copy link
Contributor

ilike2burnthing commented Dec 12, 2023

Is there a pinned issue for this?

  • I have read the pinned issues and could not find my issue

Is there an existing or similar issue/discussion for this?

  • I have searched the existing issues
  • I have searched the existing discussions

Is there any comment in the documentation for this?

  • I have read the documentation, especially the FAQ and Troubleshooting parts

Is this related to a provider?

  • I have checked the provider repo for issues
  • My issue is NOT related to a provider

Are you using the latest release?

  • I am using the latest release

Have you tried using the dev branch latest?

  • I have tried using dev branch

Docker run config used

If you can't replicate this issue I can provide Portainer screenshots.

Current Behavior

Open Transmission in browser when using Flood UI, or refresh page, and error appears in log. Affects dev and latest back to 5.3.0; 5.2 is the latest unaffected build.

Checking the container, 5.2 has config.json, whereas 5.3.0 and onwards have config.json.defaults.

Expected Behavior

config.json exists

How have you tried to solve the problem?

Manually creating the file resolves the issue, but that's not exactly a great fix.

Log output

[2023-12-12 07:31:26.476] ERR utils.cc:105 Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory (2) (utils.cc:105)

HW/SW Environment

- OS: Asustor ADM x86_64
- Docker: 23.06

Anything else?

No response

@pkishino
Copy link
Collaborator

I see the same issue here..
nothing regarding flood has changed what I see, only transmission version up.. no time to dig into this for a while now though

@ilike2burnthing
Copy link
Contributor Author

ilike2burnthing commented Dec 13, 2023

This commit from @defkev / @johman10 appears to be the cause of the issue - johman10/flood-for-transmission@edb6e11

@defkev
Copy link

defkev commented Dec 14, 2023

If my memory serves me right the final verdict here was to hardcode the defaults in an exportable module and load any customization from config.json (if present) and soft fail if that doesn't work (e.g. not present as in your case)

config.json.defaults mever gets loaded and only serves as a skeleton/template/starting point, e.g.: mv config.json.defaults config.json

[2023-12-12 07:31:26.476] ERR utils.cc:105 Couldn't read '/opt/transmission-ui/flood-for-transmission/config.json': No such file or directory (2) (utils.cc:105)

Assuming this is logged by transmission-daemon (utls.cc) the error makes no sense as flood's config.json is loaded by your browser when accessing the frontend (http://host:9091) not transmission.

Edit:
I just pulled a fresh copy of johman10/flood-for-transmission on my seed box, copied my custom config.json and everything is working as expected.

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

No branches or pull requests

3 participants