I’ve been using Confluence for years with no issues until updating to v19.1 and changing paths to IP address. I tried Confluence, Embuary, and one other and the delay is identical (> 20 seconds).
@fzinken thanks for your help… Also can you please remove the log link url you copied on your earlier reply to me? I don’t like that personal info floating around. Thx
It might just be a coincidence, but the log shows that connman took over 30 seconds to confirm the presence of an Internet connection. It could be a problem with the LAN, WAN or DNS, but I’d normally expect to see it taking 1 or 2 seconds:
It could be network- or server-related or, at a stretch, a very inefficient search algorithm. Have you checked the network performance to/from the server, using iperf3?
Edit: One other thing. The log is also showing that network flow control is switched on. If true, this can potentially cause networking problems.
Aug 21 13:14:49 OSMC kernel: meson6-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
I’m not familiar with iperf3. FYI, the storage are dedicated NAS units, not managed servers that support third-party applications. The Vero 4k+ is directly wired to the router. The NAS are attached to an unmanaged switch wired to the router. Again, the network configuration hasn’t changed in ~4 years. The only change is the upgrade to Kodi v19 and switching to mapped IP rather than samba.
I disabled the Embuary script and it looks like the library update scanning completes more quickly, but no impact to the original play-delay I originally reported.
I now understand how iperf3 works, but it can’t be installed on my NAS, which precludes the testing the instructions refer to.
There’s nothing in my router settings that would implement flow control. I iterated through every setting and there’s nothing called “flow control” nor are there any settings enabled that look related to that functionality.
Please note that I started the film and realized I forgot to switch the skin to OSMC, so I changed the skin to OSMC and then restarted the film. So the last play instance will be under the OSMC skin.
Also, after reboot, the automatic library update takes a long time. I didn’t time anything, but the system hangs for what felt like minutes before starting to scan the LAN data sources for new content.
TBH, I’m unsure what’s happening on the V4K+. I can point to logs where it’s showing as disabled after the link negotiation has occurred:
Aug 19 08:08:23 xxxxxx kernel: meson6-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
and, as in this case, where it’s enabled. Other than running ethtool once the link has come up, I don’t know how to configure it at boot time on the V4K+.
It’s certainly an option on my managed switch and the V4K+ driver seems to support it.
I just ran more tests. Using a stopwatch, the time from pressing play till a film starts is ~20 to 22 seconds. For the past 3 years, the time from press-play to start ranged from instantly to ~4 seconds.
This is very disconcerting especially when trying to browse short home movie clips that are only 15 seconds long. We have to wait 20 seconds to start watching a 15-second video. Iterating through a directory of 30+ short clips is intolerably long.
I don’t think my NAS supports this and it’s not something I would feel comfortable installing (if it were possible).
I can say with 100% certainty that this is issue is not a NAS setting. My LAN includes four 4-bay NAS, one of which is a different model from the rest. After configuring the units many ago and I haven’t touched them since. Also, one of the first things I did was spot-check videos on several of the units and the results all show the same delay, regardless of data source. The other NAS are not set for scanning on the Vero 4K+, so they won’t show on the log file.
At this moment I would suggest to try a clean Kodi folder with than a baseline config to try if that solves the issue. Alternative or additionally you still can check network with iperf3. Doesn’t need to be with your NAS can be e.g. between the PC and the Vero.
For a clean start (you can refer back afterwards, here are the commands.
Let’s test with Kodi default settings. Enter the following commands with an SSH connection.