wget: bad port #197

david007co · 2024-02-14T04:27:01Z

david007co
Feb 14, 2024

I am getting the error and the scripts are not being able to download anything.

What am I doing wrong?

Please see my logs here:

2024-02-14 04:22:59 :: Audio :: 2.32 :: Lift off in...
2024-02-14 04:22:59 :: Audio :: 2.32 :: 5
2024-02-14 04:23:00 :: Audio :: 2.32 :: 4
2024-02-14 04:23:01 :: Audio :: 2.32 :: 3
2024-02-14 04:23:03 :: Audio :: 2.32 :: 2
2024-02-14 04:23:04 :: Audio :: 2.32 :: 1
2024-02-14 04:23:05 :: Audio :: 2.32 :: Add Deezer Top Artists is disabled (enable by setting addDeezerTopArtists=true)
2024-02-14 04:23:05 :: Audio :: 2.32 :: Add Deezer Top Album Artists is disabled (enable by setting addDeezerTopAlbumArtists=true)
2024-02-14 04:23:05 :: Audio :: 2.32 :: Add Deezer Top Track Artists is disabled (enable by setting addDeezerTopTrackArtists=true)
2024-02-14 04:23:05 :: Audio :: 2.32 :: Add Deezer Related Artists is disabled (enable by setting addRelatedArtists=true)
2024-02-14 04:23:05 :: Audio :: 2.32 :: Download Location: /config/extended/downloads/audio
2024-02-14 04:23:05 :: Audio :: 2.32 :: Output format: native
2024-02-14 04:23:05 :: Audio :: 2.32 :: Output bitrate: lossless
2024-02-14 04:23:05 :: Audio :: 2.32 :: Download Quality Check Disabled (enable by setting: requireQuality=true
2024-02-14 04:23:05 :: Audio :: 2.32 :: Preferred audio lyric type: both
2024-02-14 04:23:05 :: Audio :: 2.32 :: Tidal Country Code set to: US
2024-02-14 04:23:05 :: Audio :: 2.32 :: Replaygain Tagging Enabled
2024-02-14 04:23:05 :: Audio :: 2.32 :: Match Distance: 5
2024-02-14 04:23:05 :: Audio :: 2.32 :: Beets Tagging Enabled
2024-02-14 04:23:05 :: Audio :: 2.32 :: Beets Matching Threshold 10%
2024-02-14 04:23:05 :: Audio :: 2.32 :: Failed Download Attempt Theshold: 6
2024-02-14 04:23:05 :: Audio :: 2.32 :: DEEZER :: Verifying deemix configuration
2024-02-14 04:23:06 :: Audio :: 2.32 :: DEEZER :: ARL Token: Configured
2024-02-14 04:23:06 :: Audio :: 2.32 :: DEEZER :: Configuring deemix client
wget: bad port ''
wget: bad port ''
2024-02-14 04:23:07 :: Audio :: 2.32 :: FINDING MISSING ALBUMS :: sorted by date
2024-02-14 04:23:07 :: Audio :: 2.32 ::  Missing Albums Found!
2024-02-14 04:23:07 :: Audio :: 2.32 :: Getting Missing Album IDs
./run: line 997: [: -ge: unary operator expected
wget: bad port ''
2024-02-14 04:23:08 :: Audio :: 2.32 :: FINDING CUTOFF ALBUMS sorted by date
2024-02-14 04:23:08 :: Audio :: 2.32 ::  CutOff Albums Found Found!
2024-02-14 04:23:08 :: Audio :: 2.32 :: Getting CutOff Album IDs
./run: line 1037: [: -ge: unary operator expected
2024-02-14 04:23:08 :: Audio :: 2.32 :: Script end...
2024-02-14 04:23:08 :: Audio :: 2.32 :: Script sleeping for 15m...

Answered by RandomNinjaAtk

Mar 21, 2024

@david007co

The problem was probably a bug from a container update, see here: #212

It should now be fixed, so a simple container restart should fix the issue....

View full answer

RandomNinjaAtk · 2024-02-14T11:03:14Z

RandomNinjaAtk
Feb 14, 2024
Maintainer

If you changed the default port of the application, that is probably your problem. Your not supposed to change the port...

5 replies

david007co Feb 14, 2024
Author

I just deleted the container and volumes.
Did it all again with the normal port, but I still get the same error. What could be the problem?

This is my docker compose in case this helps:

---
services:
 lidarr:
   image: lscr.io/linuxserver/lidarr:latest
   container_name: lidarr-ext-test
   environment:
     - PUID=1000
     - PGID=1000
     - TZ=Etc/UTC
   volumes:
     - /home/ubuntu/lidarr-test/config:/config
     - /home/ubuntu/nas/media-test/music:/music #optional
     - /home/ubuntu/nas/media-test/downloads:/downloads #optional
     - /home/ubuntu/lidarr-test/extended-folder-01:/custom-services.d
     - /home/ubuntu/lidarr-test/extended-folder-02:/custom-cont-init.d
   ports:
     - 8686:8686
   restart: unless-stopped

smlgough Feb 15, 2024

I'm seeing the exact same issue on my newly created container.

RandomNinjaAtk Feb 15, 2024
Maintainer

Do you have anything in your wanted - missing or cutoff list?

This is not reproducible on my end... So it has to be some configuration issue on your side. Are any of the other scripts functioning?

Are you using URL base?

smlgough Feb 15, 2024

Hi there, no not using URL base.

Yes, there is items in the wanted list.

I'm just creating another completely fresh container and will this time not make any changes at all e.g. to extended.conf and see if the error is thrown.

smlgough Feb 15, 2024

Yeah, so exactly the same issue. I've set this up numerous times in the past and never had any issues at all.

Extended.conf hasn't been touched this time. I just loaded Lidarr in the browser, added some authentication, added a root folder, then restarted the container.

2024-02-15 12:55:54 wget: bad port ''
2024-02-15 12:55:55 wget: bad port ''
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: FINDING MISSING ALBUMS :: sorted by date
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 ::  Missing Albums Found!
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Getting Missing Album IDs
2024-02-15 12:55:55 ./run: line 997: [: -ge: unary operator expected
2024-02-15 12:55:55 wget: bad port ''
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: FINDING CUTOFF ALBUMS sorted by date
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 ::  CutOff Albums Found Found!
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Getting CutOff Album IDs
2024-02-15 12:55:55 ./run: line 1037: [: -ge: unary operator expected
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Script end...
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Script sleeping for 15m..

RandomNinjaAtk · 2024-02-15T13:00:01Z

RandomNinjaAtk
Feb 15, 2024
Maintainer

Yeah, so exactly the same issue. I've set this up numerous times in the past and never had any issues at all.

Extended.conf hasn't been touched this time. I just loaded Lidarr in the browser, added some authentication, added a root folder, then restarted the container.

2024-02-15 12:55:54 wget: bad port ''
2024-02-15 12:55:55 wget: bad port ''
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: FINDING MISSING ALBUMS :: sorted by date
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 ::  Missing Albums Found!
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Getting Missing Album IDs
2024-02-15 12:55:55 ./run: line 997: [: -ge: unary operator expected
2024-02-15 12:55:55 wget: bad port ''
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: FINDING CUTOFF ALBUMS sorted by date
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 ::  CutOff Albums Found Found!
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Getting CutOff Album IDs
2024-02-15 12:55:55 ./run: line 1037: [: -ge: unary operator expected
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Script end...
2024-02-15 12:55:55 2024-02-15 12:55:55 :: Audio :: 2.32 :: Script sleeping for 15m..

If you did what you said, you would have nothing in your missing/cutoff list, which would be the issue then on a new install...

It's failing at this line:

arr-scripts/lidarr/Audio.service.bash

Line 989 in 92b9f3a

 lidarrMissingTotalRecords=$(wget --timeout=0 -q -O - "$arrUrl/api/v1/wanted/missing?page=1&pagesize=1&sortKey=$searchOrder&sortDirection=$searchDirection&apikey=${arrApiKey}" | jq -r .totalRecords) 

You can manually run the wget command and replace the variables as required to see what is returned...

7 replies

smlgough Feb 15, 2024

I've set it up a few times before with a completely empty Lidarr library, and never seen this error before.

However, you may be right. I've just created another brand new container (just in case), and this time at first Lidarr config I added a few items, and now the error has gone away!

Strange one, but at least it's working now.

RandomNinjaAtk Feb 15, 2024
Maintainer

So might be able to enhance the script to work better in that situation, with only a handful of items... However, I think that wouldn't normally be a very common situation... As I've never run into it... And I imagine most wouldn't...

smlgough Feb 15, 2024

The plot thickens... I removed all artists from Lidarr, so the Wanted list was blank again. Restarted the container and this time, no errors!

As expected, the log just shows 0 missing albums, then sleeps. No idea what the issue was.

2024-02-15 13:44:41 2024-02-15 13:44:41 :: Audio :: 2.32 :: FINDING MISSING ALBUMS :: sorted by date
2024-02-15 13:44:41 2024-02-15 13:44:41 :: Audio :: 2.32 :: 0 Missing Albums Found!
2024-02-15 13:44:41 2024-02-15 13:44:41 :: Audio :: 2.32 :: Getting Missing Album IDs
2024-02-15 13:44:41 2024-02-15 13:44:41 :: Audio :: 2.32 :: FINDING CUTOFF ALBUMS sorted by date
2024-02-15 13:44:41 2024-02-15 13:44:41 :: Audio :: 2.32 :: 0 CutOff Albums Found Found!
2024-02-15 13:44:42 2024-02-15 13:44:42 :: Audio :: 2.32 :: Getting CutOff Album IDs
2024-02-15 13:44:42 2024-02-15 13:44:42 :: Audio :: 2.32 :: Script end...
2024-02-15 13:44:42 2024-02-15 13:44:42 :: Audio :: 2.32 :: Script sleeping for 15m...

smlgough Feb 15, 2024

I think it may be common if people have a 'complete' library and are just using Lidarr and the scripts to download new releases only.

RandomNinjaAtk Feb 15, 2024
Maintainer

it should work fine for 0, just not 1 possibly...

Relevant lines:

arr-scripts/lidarr/Audio.service.bash

Lines 989 to 1028 in 92b9f3a

 lidarrMissingTotalRecords=$(wget --timeout=0 -q -O - "$arrUrl/api/v1/wanted/missing?page=1&pagesize=1&sortKey=$searchOrder&sortDirection=$searchDirection&apikey=${arrApiKey}" | jq -r .totalRecords) 

 log "FINDING MISSING ALBUMS :: sorted by $searchSort" 

 amountPerPull=1000 

 page=0 

 log "$lidarrMissingTotalRecords Missing Albums Found!" 

 log "Getting Missing Album IDs" 

 if [ $lidarrMissingTotalRecords -ge 1 ]; then 

 offsetcount=$(( $lidarrMissingTotalRecords / $amountPerPull )) 

 for ((i=0;i<=$offsetcount;i++)); do 

 page=$(( $i + 1 )) 

 offset=$(( $i * $amountPerPull )) 

 dlnumber=$(( $offset + $amountPerPull )) 

 if [ "$dlnumber" -gt "$lidarrMissingTotalRecords" ]; then 

 dlnumber="$lidarrMissingTotalRecords" 

 fi 

 log "$page :: missing :: Downloading page $page... ($offset - $dlnumber of $lidarrMissingTotalRecords Results)" 

 wget --timeout=0 -q -O - "$arrUrl/api/v1/wanted/missing?page=$page&pagesize=$amountPerPull&sortKey=$searchOrder&sortDirection=$searchDirection&apikey=${arrApiKey}" | jq -r '.records[].id' | sort > /config/extended/cache/tocheck.txt 

 log "$page :: missing :: Filtering Album IDs by removing previously searched Album IDs (/config/extended/logs/notfound/<files>)" 

 ls /config/extended/logs/notfound/ | sed "s/--.*//" > /config/extended/cache/notfound.txt 

 for lidarrRecordId in $(comm -13 /config/extended/cache/notfound.txt /config/extended/cache/tocheck.txt); do 

 if [ ! -f /config/extended/logs/notfound/$lidarrRecordId--* ]; then 

 touch "/config/extended/cache/lidarr/list/${lidarrRecordId}-missing" 

 fi 

 done 

 rm /config/extended/cache/notfound.txt /config/extended/cache/tocheck.txt 

 lidarrMissingRecords=$(ls /config/extended/cache/lidarr/list 2>/dev/null | wc -l) 

 log "$page :: missing :: ${lidarrMissingRecords} albums found to process!" 

 wantedListAlbumTotal=$lidarrMissingRecords 

 if [ ${lidarrMissingRecords} -gt 0 ]; then 

 log "$page :: missing :: Searching for $wantedListAlbumTotal items" 

 SearchProcess 

 rm /config/extended/cache/lidarr/list/*-missing 

 fi 

 done 

 fi

duloo0 · 2024-03-21T18:02:55Z

duloo0
Mar 21, 2024

Is there a fix that doesn't involve reinstalling the container? I've been downloading for a week straight and suddenly seem to have the same problem.


2024-03-21 13:56:17 :: Audio :: 2.32 :: Add Deezer Top Album Artists is disabled (enable by setting addDeezerTopAlbumArtists=true)

2024-03-21 13:56:17 :: Audio :: 2.32 :: Add Deezer Top Track Artists is disabled (enable by setting addDeezerTopTrackArtists=true)

2024-03-21 13:56:17 :: Audio :: 2.32 :: Add Deezer Related Artists is disabled (enable by setting addRelatedArtists=true)

2024-03-21 13:56:17 :: Audio :: 2.32 :: Download Location: /data/lidarr-extended/audio

2024-03-21 13:56:17 :: Audio :: 2.32 :: Output format: native

2024-03-21 13:56:17 :: Audio :: 2.32 :: Output bitrate: lossless

2024-03-21 13:56:17 :: Audio :: 2.32 :: Download Quality Check Disabled (enable by setting: requireQuality=true

2024-03-21 13:56:17 :: Audio :: 2.32 :: Preferred audio lyric type: both

2024-03-21 13:56:17 :: Audio :: 2.32 :: Tidal Country Code set to: US

2024-03-21 13:56:17 :: Audio :: 2.32 :: Replaygain Tagging Enabled

2024-03-21 13:56:17 :: Audio :: 2.32 :: Match Distance: 5

2024-03-21 13:56:17 :: Audio :: 2.32 :: Beets Tagging Enabled

2024-03-21 13:56:17 :: Audio :: 2.32 :: Beets Matching Threshold 90%

2024-03-21 13:56:17 :: Audio :: 2.32 :: Failed Download Attempt Theshold: 6

2024-03-21 13:56:18 :: Audio :: 2.32 :: TIDAL :: Verifying tidal-dl configuration

2024-03-21 13:56:18 :: Audio :: 2.32 :: TIDAL :: No default config found, importing default config "tidal.json"
./run: line 273: tidal-dl: command not found

2024-03-21 13:56:18 :: Audio :: 2.32 :: TIDAL :: ERROR :: Loading client for required authentication, please authenticate, then exit the client...

2024-03-21 13:56:18 :: Audio :: 2.32 :: TIDAL :: Purging album list cache...

2024-03-21 13:56:18 :: Audio :: 2.32 :: FINDING MISSING ALBUMS :: sorted by date

2024-03-21 13:56:18 :: Audio :: 2.32 ::  Missing Albums Found!

2024-03-21 13:56:18 :: Audio :: 2.32 :: Getting Missing Album IDs

2024-03-21 13:56:18 :: Audio :: 2.32 :: FINDING CUTOFF ALBUMS sorted by date

2024-03-21 13:56:18 :: Audio :: 2.32 ::  CutOff Albums Found Found!

2024-03-21 13:56:18 :: Audio :: 2.32 :: Getting CutOff Album IDs

2024-03-21 13:56:18 :: Audio :: 2.32 :: Script end...

2024-03-21 13:56:18 :: Audio :: 2.32 :: Script sleeping for 15m...```

2 replies

RandomNinjaAtk Mar 21, 2024
Maintainer

@david007co
Double check you followed the setup/install instructions correctly. Basically it looks like the init script did not run, which installs all the dependencies and the error your receiving about not the command tidal-dl indicates that it did not run...

Script: https://github.com/RandomNinjaAtk/arr-scripts/blob/main/lidarr/scripts_init.bash

If you restart the container and watch the containers logs, you should see it install packages during the startup, if its not doing that, that is the problem. Which would be likely caused by a misconfiguration or something else on your end....

RandomNinjaAtk Mar 21, 2024
Maintainer

@david007co

The problem was probably a bug from a container update, see here: #212

It should now be fixed, so a simple container restart should fix the issue....

Answer selected by RandomNinjaAtk

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

wget: bad port #197

{{title}}

Replies: 3 comments 14 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

wget: bad port #197

Replies: 3 comments · 14 replies

RandomNinjaAtk Feb 14, 2024 Maintainer

david007co Feb 14, 2024 Author

RandomNinjaAtk Feb 15, 2024 Maintainer

RandomNinjaAtk Feb 15, 2024 Maintainer

RandomNinjaAtk Feb 15, 2024 Maintainer

RandomNinjaAtk Feb 15, 2024 Maintainer

RandomNinjaAtk Mar 21, 2024 Maintainer

RandomNinjaAtk Mar 21, 2024 Maintainer

Replies: 3 comments 14 replies

RandomNinjaAtk
Feb 14, 2024
Maintainer

david007co Feb 14, 2024
Author

RandomNinjaAtk Feb 15, 2024
Maintainer

RandomNinjaAtk
Feb 15, 2024
Maintainer

RandomNinjaAtk Feb 15, 2024
Maintainer

RandomNinjaAtk Feb 15, 2024
Maintainer

RandomNinjaAtk Mar 21, 2024
Maintainer

RandomNinjaAtk Mar 21, 2024
Maintainer