[Bug]: Lidarr is not ready, sleeping until valid response...parse error: Invalid numeric literal at line 1, column 10

[itsgiff]

Describe the bug Getting errors in logs about lidarr not being ready

To Reproduce Steps to reproduce the behavior:

1. Fresh image with new config.xml
2. new apikey generated
3. Errors in log
4. deemix dl doesn't start
5. See error

Expected behavior I get tons on wonderful .flac's from deemix

Log Data From Audio.txt:

2023-01-26 15:42:27 :: Audio :: 1.0.306 :: Lidarr is not ready, sleeping until valid response...
2023-01-26 15:47:22 :: Audio :: 1.0.306 :: -----------------------------------------------------------------------------
2023-01-26 15:47:22 :: Audio :: 1.0.306 ::  |~) _ ._ _| _ ._ _ |\ |o._ o _ |~|_|_|
2023-01-26 15:47:22 :: Audio :: 1.0.306 ::  |~\(_|| |(_|(_)| | || \||| |_|(_||~| | |<
2023-01-26 15:47:22 :: Audio :: 1.0.306 ::  Presents: lidarr-extended (1.0.306)
2023-01-26 15:47:22 :: Audio :: 1.0.306 ::  Docker Version: amd64-1.0.34
2023-01-26 15:47:22 :: Audio :: 1.0.306 ::  May the beats be with you!
2023-01-26 15:47:22 :: Audio :: 1.0.306 :: -----------------------------------------------------------------------------
2023-01-26 15:47:22 :: Audio :: 1.0.306 :: Donate: https://github.com/sponsors/RandomNinjaAtk
2023-01-26 15:47:22 :: Audio :: 1.0.306 :: Project: https://github.com/RandomNinjaAtk/docker-lidarr-extended
2023-01-26 15:47:22 :: Audio :: 1.0.306 :: Support: https://github.com/RandomNinjaAtk/docker-lidarr-extended/discussions
2023-01-26 15:47:22 :: Audio :: 1.0.306 :: -----------------------------------------------------------------------------
2023-01-26 15:47:27 :: Audio :: 1.0.306 :: 
2023-01-26 15:47:27 :: Audio :: 1.0.306 :: Lift off in...
2023-01-26 15:47:28 :: Audio :: 1.0.306 :: 5
2023-01-26 15:47:29 :: Audio :: 1.0.306 :: 4
2023-01-26 15:47:30 :: Audio :: 1.0.306 :: 3
2023-01-26 15:47:31 :: Audio :: 1.0.306 :: 2
2023-01-26 15:47:32 :: Audio :: 1.0.306 :: 1
2023-01-26 15:47:33 :: Audio :: 1.0.306 :: To kill script, use the following command:
2023-01-26 15:47:33 :: Audio :: 1.0.306 :: kill -9 274
parse error: Invalid numeric literal at line 1, column 10
2023-01-26 15:47:35 :: Audio :: 1.0.306 :: Lidarr is not ready, sleeping until valid response...
parse error: Invalid numeric literal at line 1, column 10
2023-01-26 15:47:36 :: Audio :: 1.0.306 :: Lidarr is not ready, sleeping until valid response...
parse error: Invalid numeric literal at line 1, column 10
2023-01-26 15:47:37 :: Audio :: 1.0.306 :: Lidarr is not ready, sleeping until valid response...
parse error: Invalid numeric literal at line 1, column 10
2023-01-26 15:47:38 :: Audio :: 1.0.306 :: Lidarr is not ready, sleeping until valid response...

From Lidarr.txt:

2023-01-26 15:42:25.8|Fatal|ConsoleApp|Failed to bind to address http://[::]:8686: address already in use. This can happen if another instance of Lidarr is already running another application is using the same port (default: 8686) or the user has insufficient permissions

Docker Info:

• Docker Version: Docker version 20.10.3, build 55f0773 (Synology)
• Extended Script Version : Audio.sh 1.0.306

Additional context

[RandomNinjaAtk]

Try to setup linuxserver lidarr docker develop tag and see if it works.

This is the same as that, so if it doesn't work there, then it's a problem upstream.

Edit: Another thought, if your using vpn, that could be why.

[itsgiff]

Not entirely sure how to do that. Do I just add your scripts after the fact?

[RandomNinjaAtk]

Try the next update after it builds, I switched it to use localhost for api call, instead of loopback address. I don't have any faith that it will make a difference, but its worth a try....

This seems like it's isolated to your particular configuration, so I'm not sure how much I could help to resolve it.... If it was a wide spread problem, everyone would be reporting it...

Edit:

After reviewing your steps to reproduce, did you manually generate a new api key? If you did, maybe that is the cause... but a simple container restart would resolve that....

[itsgiff]

I did manually update the api key as well.

[RandomNinjaAtk]

Did you restart the container after updating the key?

[itsgiff]

Yes

[itsgiff]

Welp - I deleted the config.xml again and it worked. I compared the two config files and found these differences:

• the UrlBase was blank
• the LaunchBrowser setting is set to true.

Strange but it's completing the scripts and working as intended.

bad config:

<Config>
  <LogLevel>Info</LogLevel>
  <Port>8686</Port>
  <UrlBase>/</UrlBase>
  <BindAddress>*</BindAddress>
  <SslPort>6868</SslPort>
  <EnableSsl>False</EnableSsl>
  <ApiKey>xxx</ApiKey>
  <AuthenticationMethod>Forms</AuthenticationMethod>
  <Branch>develop</Branch>
  <LaunchBrowser>False</LaunchBrowser>
  <UpdateMechanism>Docker</UpdateMechanism>
  <SslCertPath></SslCertPath>
  <SslCertPassword></SslCertPassword>
  <InstanceName>Lidarr</InstanceName>
</Config>

working config:

<Config>
  <LogLevel>info</LogLevel>
  <UrlBase></UrlBase>
  <UpdateMechanism>Docker</UpdateMechanism>
  <BindAddress>*</BindAddress>
  <Port>8686</Port>
  <SslPort>6868</SslPort>
  <EnableSsl>False</EnableSsl>
  <LaunchBrowser>True</LaunchBrowser>
  <ApiKey>xxx</ApiKey>
  <AuthenticationMethod>Forms</AuthenticationMethod>
  <Branch>develop</Branch>
  <SslCertPath></SslCertPath>
  <SslCertPassword></SslCertPassword>
  <InstanceName>Lidarr</InstanceName>
</Config>