Skip to content

[BUG] settings.json not persisted if rpc port changed #306

Closed
@energywave

Description

@energywave

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When settings are changed in webui they're not persisted after a restart of the container. The settings.json file is not written.

Expected Behavior

Change settings from webui, restart container, refresh the webui and read the same settings you've set before the restart.

I think to have understood what's the problem.
In the s6-overlay finish script you call /usr/bin/transmission-remote without a port and it seems that, if not specified, it assumes 9091 as the default port.
But if the port is not that the --exit argument is not working (silently...) and docker brutally shut down the container, whitout letting transmission-daemon the possibility to save settings.json.
I've understood that the file is persisted when the daemon closes.
As a programmer I must say that this way is dangerous as you never know if the process will be gracefully shut down or not. And in that case you'll loose all the settings the user changed.

Steps To Reproduce

  1. change rcp-port in settings, something other that 9091
  2. open webui using the new port and change some settings
  3. restart the container (I'm using TrueNas Scale and there I stop and then start again the "app")
  4. refresh the webui
  5. you have to find the same settings you've set at point 2

Environment

- OS: TrueNas Scale ElectricEel-24.10.2.1
- How docker service was installed: internal, I don't know

CPU architecture

x86-64

Docker creation

It's here: https://github.com/truenas/apps/blob/master/ix-dev/community/transmission/templates/docker-compose.yaml

Container logs

No inherent log records found.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions