Suwayomi / docker-tachidesk

Run Suwayomi-Server in a docker container
Mozilla Public License 2.0
214 stars 55 forks source link

Deployment fails when : is in Backup Time variable. #90

Closed TylerRudie closed 5 months ago

TylerRudie commented 5 months ago

Deployment fails when : is in Backup Time variable. No : this error disappears.

2024-02-07 21:44:12.031459-06:00Caused by: com.typesafe.config.ConfigException$Parse: /home/suwayomi/.local/share/Tachidesk/server.conf: 53: Expecting end of input or a comma, got ':' (if you intended ':' to be part of a key or string value, try enclosing the key or value in double quotes, or you may be able to rename the file .properties rather than .conf

TrueNAS-SCALE-23.10.1.1 Chart Version: 5.0.2

CrispySteak commented 5 months ago

I was also having issues with this (two separate configs). I think it is because of quotes not being there for some reason, either in the source server-reference.conf (https://github.com/Suwayomi/Suwayomi-Server/blob/master/server/src/main/resources/server-reference.conf) or due to an issue in (https://github.com/Suwayomi/docker-tachidesk/blob/main/scripts/startup_script.sh)

Version for reference:

The properties that run into issues are:

full logs of one case (extensionRepos):

2024-02-18 20:25:42.766890-05:00Suwayomi data location inside the container: /home/suwayomi/.local/share/Tachidesk
2024-02-18 20:25:42.954616-05:0020:25:42.952 [main] ERROR suwayomi.tachidesk.server.ServerSetup -- unhandled exception
2024-02-18 20:25:42.954641-05:00java.lang.ExceptionInInitializerError: null
2024-02-18 20:25:42.954648-05:00at suwayomi.tachidesk.server.ServerSetupKt.applicationSetup(ServerSetup.kt:91)
2024-02-18 20:25:42.954654-05:00at suwayomi.tachidesk.MainKt.main(Main.kt:14)
2024-02-18 20:25:42.954669-05:00at suwayomi.tachidesk.MainKt.main(Main.kt)
2024-02-18 20:25:42.954675-05:00Caused by: com.typesafe.config.ConfigException$Parse: /home/suwayomi/.local/share/Tachidesk/server.conf: 27: Expecting end of input or a comma, got ':' (if you intended ':' to be part of a key or string value, try enclosing the key or value in double quotes, or you may be able to rename the file .properties rather than .conf)
2024-02-18 20:25:42.954683-05:00at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseError(ConfigDocumentParser.java:201)
2024-02-18 20:25:42.954689-05:00at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseError(ConfigDocumentParser.java:197)
2024-02-18 20:25:42.954694-05:00at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseObject(ConfigDocumentParser.java:535)
2024-02-18 20:25:42.954699-05:00at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parse(ConfigDocumentParser.java:648)
2024-02-18 20:25:42.954707-05:00at com.typesafe.config.impl.ConfigDocumentParser.parse(ConfigDocumentParser.java:14)
2024-02-18 20:25:42.954713-05:00at com.typesafe.config.impl.Parseable.rawParseValue(Parseable.java:262)
2024-02-18 20:25:42.954718-05:00at com.typesafe.config.impl.Parseable.rawParseValue(Parseable.java:250)
2024-02-18 20:25:42.954723-05:00at com.typesafe.config.impl.Parseable.parseValue(Parseable.java:180)
2024-02-18 20:25:42.954731-05:00at com.typesafe.config.impl.Parseable.parseValue(Parseable.java:174)
2024-02-18 20:25:42.954736-05:00at com.typesafe.config.impl.Parseable.parse(Parseable.java:301)
2024-02-18 20:25:42.954741-05:00at com.typesafe.config.ConfigFactory.parseFile(ConfigFactory.java:793)
2024-02-18 20:25:42.954746-05:00at com.typesafe.config.ConfigFactory.parseFile(ConfigFactory.java:807)
2024-02-18 20:25:42.954754-05:00at xyz.nulldev.ts.config.ConfigManager.getUserConfig(ConfigManager.kt:52)
2024-02-18 20:25:42.954762-05:00at xyz.nulldev.ts.config.ConfigManager.loadConfigs(ConfigManager.kt:72)
2024-02-18 20:25:42.954771-05:00at xyz.nulldev.ts.config.ConfigManager.<init>(ConfigManager.kt:29)
2024-02-18 20:25:42.954781-05:00at xyz.nulldev.ts.config.GlobalConfigManager.<init>(ConfigManager.kt:166)
2024-02-18 20:25:42.954790-05:00at xyz.nulldev.ts.config.GlobalConfigManager.<clinit>(ConfigManager.kt)
2024-02-18 20:25:42.954806-05:00... 3 common frames omitted
CrispySteak commented 5 months ago

The workaround is as below:

Syer10 commented 5 months ago

Should be fixed in the latest image.