Network issues since Dec update

[Blinkz]

Ah ok, well I couldn’t see any other log where it went? Where should the component logging end up?

Also not sure why the above code is half disappeared, altho I’m writing this on an iPhone which doesn’t help.

[fzinken]

@Blinkz

As I said I don’t have a problem accessing any of the shares or the files, just that the connection is so slow that HD content is unplayable due to jerkyness. The same file on a usb plays no issue.

My sincere apologies we had many threads with people having access problems after the update that I didn’t checked the details of your problem and thought you can not access.

So let’s reset ourselves and start from scratch:

1. Disable all component specific logging and the debug logging
2. Check you network throughput between OSMC and Windows with iperf3
3. Try to copy a file via filemanager (Setttings → Filemanager) and time the duration to estimate the throughput

[Beam]

I had similar problems. Try SMB mount from commandline (mount.cifs) and play movie from that mounted directory.

[Blinkz]

Thanks fzinken. All logging cancelled and below is the results:

I ran iperf3 from osmc to both the server and to my PC, with each both being client and server. It gives a fairly consistent 93-95Mbit/s.

However trying to copy a file from the server to OSMC is much slower. I tried a number of different files and used both the SD card and USB drive and only averaged around 1-1.5Mb/s (both timed and from the speed estimate in kodi)

Thanks Beam for your input, how would I mount a Smb share from the cli? Isn’t CIFS part of smbv1? or am I getting confused (easily done!)

[fzinken]

@Blinkz

However trying to copy a file from the server to OSMC is much slower. I tried a number of different files and used both the SD card and USB drive and only averaged around 1-1.5Mb/s (both timed and from the speed estimate in kodi)

I am still wondering how that can be related to the December Update.
Anyhow maybe try the fstab based mount as @Beam suggested.
Details are here

Configuring fstab based Samba share mounts

This tutorial is to help those who are using Samba (also known as CIFS, SMB or Windows Networking). It assumes that you already are sharing media files on a Windows Server or Desktop. Why use /etc/fstab instead of Kodi’s built in SMB client? The Kodi client in current versions (17.x and older) is slow. Using /etc/fstab is faster, and not really that hard to setup. EDIT: 11/1/2019 While improvements were made in Kodi 18.x, using fstab will still be faster. Preparation: You will need to know …

[Blinkz]

Well it was all working fine before the update, however I will try to mount one of the shares and see if the performance is better, although its not ideal as I have a Mysql database and if I change all the shares its a going to be a pain to have to rescan all of the media!

[fzinken]

@Blinkz

although its not ideal as I have a Mysql database

Well first check if it makes a difference. If it works with fstab mounting that you can use path substitution to match the Database entry
http://kodi.wiki/view/Path_substitution

[Blinkz]

Hey guys. Sorry for the delay,I’ve been away with work.

I’ve had a good play around with lots of different settings and I’ve found that it was to do with an add on that I’ve been using. I use Watchdog to keep all the media updated, I found disabling this fixed the issue. On further investigation it turns out my wife had plugged in the old Rpi2 to watch some tv and so we had two devices constantly checking the sources for updates. As such the strain of this meant SD shows played ok but the HD didn’t have the bandwidth. Thanks for all your help though!

On a separate issue osmc popped up saying that an update has failed to install and to post on the forums. Shall I open a new thread for it?

I tried using the cli but that had an error as well.

[fzinken]

@Blinkz

On a separate issue osmc popped up saying that an update has failed to install and to post on the forums. Shall I open a new thread for it?

I tried using the cli but that had an error as well.

Yes open new thread and add grab-logs -A output

[shkval]

Recently i had face some similar issue, after read your thread it could be related with WatchDog since i use it as well and yesterday i noticed it was taking a lot to update just a couple of Movies/TVSeries

My thread is in case is useful too: SMB issue since last upgrade - #18 by Tom_Doyle

[Laurence_Burke]

@shkval

Recently i had face some similar issue, after read your thread it could be related with WatchDog since i use it as well and yesterday i noticed it was taking a lot to update just a couple of Movies/TVSeries

My thread is in case is useful too: SMB issue since last upgrade

Thanks for sharing the link I will check and hope it helps.