ok, just done a scan with logs switched on, after doing all the above (removing advancedsettings, deleting mymusic db):
https://paste.osmc.tv/emekujenis
I can see this message in the log (for every album):
2024-07-21 07:46:37.965 T:3187 error : Unable to lookup host: ‘Acer-mb’
Just checked Hostname on Win command prompt: Acer-MB (is it case sensitive?)
DNS and NetBIOS names are case insensitive. So,
nslookup 192.168.1.99Just a speculation: Perhaps, this is a problem caused by the NetBIOS name and the DNS name for this Windows system is not the same or DNS is not working at all for this name in your environment. Obviously, there is code while scraping which cannot resolve the DNS name. Let’s see what the reverse nslookup test will show.
Addition:
Please, can you also ssh into the Vero and invoke the follwoing commands and show the outputs:
sudo apt update && sudo apt install --reinstall dnsutils -ynslookup 192.168.1.99nslookup Acer-mbsudo apt update && sudo apt install --reinstall nbtscan -ynbtscan 192.168.1.0/24connmanctl services*AO Wired ethernet_1234XYZ_cable)ethernet_... and enterconnmanctl services ethernet_1234XYZ_cableHi,
see below:
(From Win PC):
C:\Users\Malco>nslookup 192.168.1.99
Server: public-dns-a.as9105.net
Address: 79.79.79.79
*** public-dns-a.as9105.net can’t find 192.168.1.99: Non-existent domain
(From Putty connection to Vero):
sudo apt update && sudo apt install --reinstall dnsutils -y
Hit:1 Index of /debian bullseye InRelease
Hit:2 Index of /debian bullseye-updates InRelease
Hit:3 https://security.debian.org bullseye-security InRelease
Hit:4 Index of /osmc/osmc/apt bullseye InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following additional packages will be installed:
bind9-dnsutils
The following NEW packages will be installed:
bind9-dnsutils dnsutils
0 upgraded, 2 newly installed, 0 to remove and 32 not upgraded.
Need to get 672 kB of archives.
After this operation, 911 kB of additional disk space will be used.
Get:1 Index of /debian bullseye/main armhf bind9-dnsutils armhf 1:9.16.48-1 [402 kB]
Get:2 Index of /debian bullseye/main armhf dnsutils all 1:9.16.48-1 [269 kB]
Fetched 672 kB in 0s (2230 kB/s)
Selecting previously unselected package bind9-dnsutils.
(Reading database … 37519 files and directories currently installed.)
Preparing to unpack …/bind9-dnsutils_1%3a9.16.48-1_armhf.deb …
Unpacking bind9-dnsutils (1:9.16.48-1) …
Selecting previously unselected package dnsutils.
Preparing to unpack …/dnsutils_1%3a9.16.48-1_all.deb …
Unpacking dnsutils (1:9.16.48-1) …
Setting up bind9-dnsutils (1:9.16.48-1) …
Setting up dnsutils (1:9.16.48-1) …
osmc@osmc:~$ nslookup 192.168.1.99
** server can’t find 99.1.168.192.in-addr.arpa: NXDOMAIN
osmc@osmc:~$ nslookup Acer-mb
Server: ::1
Address: ::1#53
** server can’t find Acer-mb: NXDOMAIN
osmc@osmc:~$ sudo apt update && sudo apt install --reinstall nbtscan -y
Hit:1 Index of /debian bullseye InRelease
Hit:2 https://security.debian.org bullseye-security InRelease
Hit:3 Index of /debian bullseye-updates InRelease
Hit:4 Index of /osmc/osmc/apt bullseye InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following NEW packages will be installed:
nbtscan
0 upgraded, 1 newly installed, 0 to remove and 32 not upgraded.
Need to get 22.0 kB of archives.
After this operation, 49.2 kB of additional disk space will be used.
Get:1 Index of /debian bullseye/main armhf nbtscan armhf 1.6-3 [22.0 kB]
Fetched 22.0 kB in 0s (56.6 kB/s)
Selecting previously unselected package nbtscan.
(Reading database … 37539 files and directories currently installed.)
Preparing to unpack …/nbtscan_1.6-3_armhf.deb …
Unpacking nbtscan (1.6-3) …
Setting up nbtscan (1.6-3) …
osmc@osmc:~$ nbtscan 192.168.1.0/24
Doing NBT name scan for addresses from 192.168.1.0/24
192.168.1.0 Sendto failed: Permission denied
192.168.1.99 ACER-MB 94:c6:91:93:e4:6b
192.168.1.255 Sendto failed: Permission denied
should be…
sudo apt update && sudo apt install --reinstall dnsutils -y
sorry, yes, realised that, post editted, thanks!
thx and please the ‘connmanctl’ commands (sorry just added this while you were already processing the first commands)
osmc@osmc:~$ connmanctl services
*AO Wired ethernet_900eb327504e_cable
That was the first command to get the name of the connection. You then run…
connmanctl services ethernet_900eb327504e_cable
Oops 
osmc@osmc:~$ connmanctl services ethernet_900eb327504e_cable
/net/connman/service/ethernet_900eb327504e_cable
Type = ethernet
Security = [ ]
State = online
Favorite = True
Immutable = False
AutoConnect = True
Name = Wired
Ethernet = [ Method=auto, Interface=eth0, Address=90:0E:B3:27:50:4E, MTU=1500 ]
IPv4 = [ Method=dhcp, Address=192.168.1.135, Netmask=255.255.255.0, Gateway=192.168.1.1 ]
IPv4.Configuration = [ Method=dhcp ]
IPv6 = [ ]
IPv6.Configuration = [ Method=off ]
Nameservers = [ 192.168.1.1 ]
Nameservers.Configuration = [ ]
Timeservers = [ ]
Timeservers.Configuration = [ ]
Domains = [ lan ]
Domains.Configuration = [ ]
Proxy = [ Method=direct ]
Proxy.Configuration = [ ]
mDNS = False
mDNS.Configuration = False
Provider = [ ]
Many thx. Now, hopefully last tests on your Vero via ssh:
nslookup 192.168.1.99 192.168.1.1nslookup Acer-mb 192.168.1.1nslookup www.google.com 192.168.1.1Thx in advance.
osmc@osmc:~$ nslookup 192.168.1.99 192.168.1.1
** server can’t find 99.1.168.192.in-addr.arpa: NXDOMAIN
osmc@osmc:~$ nslookup Acer-mb 192.168.1.1
Server: 192.168.1.1
Address: 192.168.1.1#53
** server can’t find Acer-mb: NXDOMAIN
osmc@osmc:~$ nslookup www.google.com 192.168.1.1
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
Name: www.google.com
Address: 142.250.178.4
Name: www.google.com
Address: 2a00:1450:4009:815::2004
thx Jim!
Ok, still need another test on the Vero:
nslookup 192.168.1.135 192.168.1.1osmc@osmc:~$ nslookup 192.168.1.135 192.168.1.1
** server can’t find 135.1.168.192.in-addr.arpa: NXDOMAIN
Ok, so to summarize we have:
the Vero is getting an IPv4 address 192.168.1.135 via DHCP
the DHCP information most likely also tells the Vero to use name server 192.168.1.1 (which is also the router/gateway)
obviously this name server at 192.168.1.1 only resolves external IP addresses (??? WHY ???)
So the good question is: what/who is the DHCP server? If it is this router/gateway at 192.168.1.1, why is it configured to give DHCP clients an IP address and advertise itself as a name server, but cannot resolve local IP addresses on the 192.168.1.0/24 network?
Can you log into this DHCP server and check/confirm how it is configured as a name server?
If this DNS problem cannot be solved at all, I strongly recommend using NO names at all, just plain IP addresses. Especially with software stacks that handle NetBIOS and DNS name resolution in parallel… which obviously in this mix causes a problem with Kodi and the scraper used.
The downside is that if the Acer system does not use a fixed IP address but also gets its IP via DHCP and the DHCP server decides to send a different IP, the configuration on the Vero is no longer valid.
Priority should be to fix the name server at 192.168.1.1, which seems to be not configured correctly.
thanks Jim, however I’m struggling to understand this.
“log into this DHCP server and check/confirm how it is configured as a name server”
how would I do the above, not sure what the DHCP server is, is that my router?
Yes, I assume this is your router. Can you tell what brand/model this is?
TalkTalk Fast 5364 apparently…
So, this is something you can give a try, on the Vero try
nslookup acer-mb.lanIn case the the name server knows acer-mb, this could let it resolve the local name instead forwarding the request to outer name servers. But brand and model could be helpful to know.
osmc@osmc:~$ nslookup acer-mb.lan
Server: ::1
Address: ::1#53
** server can’t find acer-mb.lan: NXDOMAIN
