Missing WOL and buggy tags (/B) in recent OSMC

Hi folks,

until last year (before the new OSMC came out), whenever I located a resource located on a SMB share (Music, Video etc.) OSMC automatically tried to wake up my NAS - with success.
Now OSMC doesn’t even try it anymore.
Is that a known (and still missing) issue?

Second thing (minor): In several dialogues, e.g. search or result screens, bold headlines show a kind of tag at the end, like /B.
Rather a cosmetical bug, but maybe it can be fixed with the next releases…?

Hi,

logs, showing this issue would be helpful. Also are you running the latest version of osmc?

Is this with OSMC skin, a screenshot or a photo showing this issue would be helpful?

Thanks Tom.

Hi Tom,
thanks for your prompt answer.
Can you help me a bit with the logs issue, I mean which ones and where to find them?
OSMC is V 2017.06-1

About the other /B issue I will take a screen picture.

Thanks again

Hi,

You need to enable debug logging as described in the log provided. Then try and browse to an SMB share, reboot. Upload logs via my MyOSMC, then provide the link. You can then disable debug logging.

Thanks Tom.

Hi Tom,
honestly, IMO the latest OSMC locked down the Linux on my Pi a lot.
E.g. SSH was disabled, which was enabled before I upgraded.
Now I finally found out how to re-enable it, and am now connected via Total Commander again finally.
Since there is no “Enable debug logging” shown in “My OSMC”, please tell me where to browse to in the Linux structure (I guess there is a XML file or something to enable it).

Wait… found how to enable it :wink:

OK, uploaded :wink:
https://paste.osmc.tv/umoniyeyos

About the message when trying SMB, it’s not worth posting a picture. It’s just this (in German):
“invalid argument - network host not reachable”

Hi,

Not sure whats going on with system is enabled by default, I think it can be disabled during the wizard on first boot. Have you installed OSMC via the installer on the website or is this a noobs or multi-distro setup?

Thanks Tom.

I installed it via the installer, in the OSMC surface.
And here an example about the /B thingy :wink:

Hi,

Is this only showing for headers for addons?

Thanks Tom.

I think so, yes.
If it’s in bold, then this occurs

Hi,

SMB shares:

17:26:40.427 T:1461457904   ERROR: SMBDirectory->GetDirectory: Unable to open directory : 'smb://LTB/MP3'
                                        unix_err:'16' error : 'Invalid argument'

Edit: Also post the contents of:

cat /home/osmc/.smb/smb.conf

I think there maybe a network issue at play here, are you able to ping your nas from the pi?

Buggy tags - All addons or just some?

Thanks Tom.

I think there is a misunderstanding, so I try to explain the issue once more:
The problem is not that the NAS is not reachable, that’s expected.
But in the past, means at OSMC versions until last year, when you would access such an offline SMB resource, OSMC would automatically send a Wake on LAN command to the NAS, which is not the case anymore now.

Hmm - good question. In fact it may be only the YouTube addon, but I have to say that it didn’t do that in former OSMC versions.

Hi,

Apologies I did indeed misunderstand, I thought you were issues accessing the samba shares in general. Anyway this may help:

http://kodi.wiki/view/Wake_on_lan

As for buggy headers, I’ve been advised an other user have seen this and it has been flagged to the OSMC skin developer.

Thanks Tom.

Indeed a super hot trance - I found why it still doesn’t work for me:
This option was already switched on, however it tries to wake up my NAS using an old IP address of the Pi (192.168.10.16), which is not valid anymore.
Since I disabled WLAN at the Pi recently and since then only use the physical LAN adapter, I somehow need to tell OSMC the new IP address (192.168.10.18) for using Wake on LAN.
Any ideas how to achieve that?

I doubt that the source IP of the Pi plays any role on this.
Is your NAS any of the below written IPs?

17:27:06.358 T:1958409136  NOTICE: WakeOnAccess - Load settings :
17:27:06.358 T:1958409136  NOTICE: WakeOnAccess - Enabled:TRUE
17:27:06.359 T:1958409136  NOTICE:   -Network init timeout : [20] sec
17:27:06.359 T:1958409136  NOTICE:   -Network settle time  : [500] ms
17:27:06.359 T:1958409136  NOTICE:   Registering wakeup entry:
17:27:06.359 T:1958409136  NOTICE:     HostName        : 192.168.10.18
17:27:06.359 T:1958409136  NOTICE:     MacAddress      : 00:D0:4B:88:ED:92
17:27:06.359 T:1958409136  NOTICE:     PingPort        : 0
17:27:06.359 T:1958409136  NOTICE:     PingMode        : 0
17:27:06.359 T:1958409136  NOTICE:     Timeout         : 300 (sec)
17:27:06.359 T:1958409136  NOTICE:     WaitForOnline   : 40 (sec)
17:27:06.359 T:1958409136  NOTICE:     WaitForOnlineEx : 40 (sec)
17:27:06.359 T:1958409136  NOTICE:     WaitForServices : 5 (sec)
17:27:06.359 T:1958409136  NOTICE:   Registering wakeup entry:
17:27:06.359 T:1958409136  NOTICE:     HostName        : 192.168.10.6
17:27:06.359 T:1958409136  NOTICE:     MacAddress      : 00:D0:4B:88:ED:92
17:27:06.359 T:1958409136  NOTICE:     PingPort        : 0
17:27:06.360 T:1958409136  NOTICE:     PingMode        : 0
17:27:06.360 T:1958409136  NOTICE:     Timeout         : 300 (sec)
17:27:06.360 T:1958409136  NOTICE:     WaitForOnline   : 40 (sec)
17:27:06.360 T:1958409136  NOTICE:     WaitForOnlineEx : 40 (sec)
17:27:06.360 T:1958409136  NOTICE:     WaitForServices : 5 (sec)
17:27:06.360 T:1958409136  NOTICE:   Registering wakeup entry:
17:27:06.360 T:1958409136  NOTICE:     HostName        : 192.168.10.16
17:27:06.360 T:1958409136  NOTICE:     MacAddress      : B8:27:EB:79:46:8F
17:27:06.360 T:1958409136  NOTICE:     PingPort        : 0
17:27:06.360 T:1958409136  NOTICE:     PingMode        : 0
17:27:06.360 T:1958409136  NOTICE:     Timeout         : 300 (sec)
17:27:06.360 T:1958409136  NOTICE:     WaitForOnline   : 40 (sec)
17:27:06.360 T:1958409136  NOTICE:     WaitForOnlineEx : 40 (sec)
17:27:06.360 T:1958409136  NOTICE:     WaitForServices : 5 (sec)

Yep, it’s this one:

Well I am not sure but I doubt that it is correct to have the port as part of the source definition

    <name>ltb video</name>
    <path pathversion="1">smb://192.168.10.6:445/Filme/</path>
    <allowsharing>true</allowsharing>

Have you tried smb://192.168.10.6/Filme/

You mean e.g. at Videos => Files? Yes, works like a charm, but I used the NetBIOS name and not the IP, so I am actually more dynamic here in case of an IP change :wink:
Only WOL doesn’t work anymore…