[pettergulbra]

Hi

I have an problem with the WOL option.
I have enabled it in the settings, OE settings and made sure the right info is in the wakonlan.xml file.
The server wakes up as it should if other stuff is sending the "magic" packet to lan, with MAC and IP 192.168.1.255 (IP out form head could be wrong)
IP of the server is 192.168.1.2 and the IP of the Chromebox with OE is 192.168.1.4

I have made three logs;
Restart of Chromebox with server on: http://pastebin.com/u9QUMehp
Restart of Chromebox with server off: http://pastebin.com/Sm8JHGLn
Resuming from standby with server off: http://pastebin.com/8ErKjzFu

If more info is needed, please say so. I will do what I can :-)

[sovaby]

$ sudo ethtool eth0 | grep -i wake-on
Supports Wake-on: pumbg
Wake-on: d

d - disabled
g - enabled

On terminal
Enable magic packet on the card
Enable every time at boot

#!/bin/bash
ethtool -s eth0 wol g
exit

Wake on lan - wakeonlan 01:23:45:67:89:ab If the same subnet
or wakeonlan -i 192.168.1.2 -p 7 01:23:45:67:89:ab If different
-p optional port. default 9

[t4_ravenbird]

Your logs are fine but shows no attempt to use anything on the server 192.168.1.2 so then wake-on-lan function will not kick in.

Kodi will not - and should not - try to start server just because Kodi is starting up or resuming from suspend-mode, it will only try to wake server when you actually need it (when you try to use a MySQL server or a file on a file-server)

Did you try to play or otherwise access a file on the server, if not please do so and if server is not woken and thus the file fails to play please make a log of that

Edit :
I see now that your smb-shares are set up by name while in the wakeonlan.xml settings it is by ipaddress. The safest way is to use only ipaddress and not rely on DNS lookups or at least you need to have an entry in wakeonlan.xml for the server by name as it is given in the 'declaration of sources'.
This should be auto-detected and auto-generated by Kodi when you enabled the wakeup-option so I dont understand why it is missing. Try to go into settings and disable the wake-option, exit settings, go back and re-enable it. That should kick a new discovery and generation of wakeonlan.xml

[pettergulbra]

$ sudo ethtool eth0 | grep -i wake-on
Supports Wake-on: pumbg
Wake-on: d

d - disabled
g - enabled

On terminal
Enable magic packet on the card
Enable every time at boot

#!/bin/bash
ethtool -s eth0 wol g
exit

Wake on lan - wakeonlan 01:23:45:67:89:ab If the same subnet
or wakeonlan -i 192.168.1.2 -p 7 01:23:45:67:89:ab If different
-p optional port. default 9

Do not understand what you want to tell me?

Your logs are fine but shows no attempt to use anything on the server 192.168.1.2 so then wake-on-lan function will not kick in.

Kodi will not - and should not - try to start server just because Kodi is starting up or resuming from suspend-mode, it will only try to wake server when you actually need it (when you try to use a MySQL server or a file on a file-server)

Did you try to play or otherwise access a file on the server, if not please do so and if server is not woken and thus the file fails to play please make a log of that

Edit :
I see now that your smb-shares are set up by name while in the wakeonlan.xml settings it is by ipaddress. The safest way is to use only ipaddress and not rely on DNS lookups or at least you need to have an entry in wakeonlan.xml for the server by name as it is given in the 'declaration of sources'.
This should be auto-detected and auto-generated by Kodi when you enabled the wakeup-option so I dont understand why it is missing. Try to go into settings and disable the wake-option, exit settings, go back and re-enable it. That should kick a new discovery and generation of wakeonlan.xml

I have now tried to turn it off, then remove the wakeonlan.xml file to. So it should start over. But nothing happens, just get an error, something like: Can`t find MAC address for KONTOR.

Here ar two logs:
KodiLogOld: http://pastebin.com/CpubbjPL
KodiLog: http://pastebin.com/QYCgjDm6

Thanks for the help so far. :-)

[t4_ravenbird]

Mac discovery will fail if KONTOR is turned off. You need to enable wake-on-lan at a time when the server is reachable.
If mac discovery fails when KONTOR is on then please make a log during that sequence

[pettergulbra]

Hi

Here are the log when turning it of and on again with the server on: http://pastebin.com/hfhmRq55
And here are an log for a restart with the server on: http://pastebin.com/WUn6zTN0

Still the message with MAC problem. Still works to wake it from other computers, inkcl an Chromebook with this addon:
https://chrome.google.com/webstore/detai...nfo-dialog

[t4_ravenbird]

09:17:33 T:139997361444608 ERROR: Unable to lookup host: 'KONTOR'
09:17:33 T:139997361444608 ERROR: DoWork - can't determine ip of 'KONTOR'
09:17:33 T:139997361444608 ERROR: OnJobComplete - Mac discovery failed for host 'KONTOR'

You are using a server by name, not ipaddress. Depending on a lot if networking details on your LAN it can be difficult for the network stack to figure out the ipaddress from the hostname which is required for this discovery.
If you have already communicated with the server I am puzzled that it fails - can you try again and make sure to;
1 start server
2 start kodi and navigate to a file on the server (start a movie by navigating the shaed files for instance)
3 do discovery

*
Alternatively ; reconfigure your sources to not use 'KONTOR' but rather use '192.168.1.2' which is much safer

*
Alternatively ; in your old wakeonlan.xml where you had an entry for '192.168.1.2' , duplicate this entry and replace '192.168.1.2' with 'KONTOR' so you have two entries.

[pettergulbra]

Now I have changed to IP addresses in the sources, passwords and wakeonlan xml`s.
Still it can`t wake the machine, but I do not get the MAC error, as I can see.
I can browse for the files under "files explorer", and play them (it would show in the log?)
But can`t access from the library, the files does not exist, it says..

Log: http://pastebin.com/dLgXesYQ

Wakeonlan: http://pastebin.com/8Zzk2WN7
Sources: http://pastebin.com/gt8RwRSu
Passwords: http://pastebin.com/CXatbi5C

Code:

<advancedsettings>
  <useddsfanart>true</useddsfanart>
  <samba>
    <clienttimeout>40</clienttimeout>
  </samba>
  <network>
    <disableipv6>true</disableipv6>
  </network>
  <videolibrary>
    <importwatchedstate>true</importwatchedstate>
    <importresumepoint>true</importresumepoint>
    <cleanonupdate>true</cleanonupdate>
  </videolibrary>
   <video>
    <usetimeseeking>true</usetimeseeking>
    <timeseekforwardbig>180</timeseekforwardbig>
    <timeseekbackwardbig>-180</timeseekbackwardbig>
   </video>
  <loglevel>1</loglevel>
</advancedsettings>

Can`t use pastbine anymore, paste the limit :-\

If I use this on my Chromebook, it works like an charm:

[t4_ravenbird]

11:16:00 T:140272867555200 NOTICE: WakeOnAccess [192.168.1.2] trigged by accessing : smb://192.168.1.2/
11:16:00 T:140272867555200 NOTICE: WakeOnAccess success exit, server already running

Good, progress, now wake-on-lan has kicked in and tried to wake server but found it was already running so did not do anything.
If it can not wake server when it is sleeping, please post a log of that also

btw:the screenshot is using another ip?

[pettergulbra]

Why it is using another IP I can`t answer for, but I think it has something to do with that it just broadcast it on the whole network and the right MAC pics it up?

Suddenly it just worked :-)
I did not do anything else, just rebooted everything once ore twice. Hope it keeps this way.

Very much thank you! :-)

Petter

[t4_ravenbird]

Excellent glad to hear

[vnser]

I had the same issue on LibreELEC 8.0 (KODI 17.0)
I had to solve it by adding IP-HostName record in /storage/.config/hosts.conf before I found your easy and useful solution.
Thank you much!

[Aexelphone]

Your logs are fine but shows no attempt to use anything on the server 192.168.1.2 so then wake-on-lan function will not kick in.

Kodi will not - and should not - try to start server just because Kodi is starting up or resuming from suspend-mode, it will only try to wake server when you actually need it (when you try to use a MySQL server or a file on a file-server)

Did you try to play or otherwise access a file on the server, if not please do so and if server is not woken and thus the file fails to play please make a log of that

Edit :
I see now that your smb-shares are set up by name while in the wakeonlan.xml settings it is by ipaddress. The safest way is to use only ipaddress and not rely on DNS lookups or at least you need to have an entry in wakeonlan.xml for the server by name as it is given in the 'declaration of sources'.
This should be auto-detected and auto-generated by Kodi when you enabled the wakeup-option so I dont understand why it is missing. Try to go into settings and disable the wake-option, exit settings, go back and re-enable it. That should kick a new discovery and generation of wakeonlan.xml

Hey Guys, ive Gott pretty mich the Same problem. Can you tell me how to Set Up my smb-shares by ip-adress instead oft host-name?

Thanks in advance

[wsnipex]

you edit the media source in kodi, replacing the host name with the IP

[Aexelphone]

Thanks a lot:-)