Page 1 of 1

MAC discovery failed

Posted: 23 Feb 2017, 15:20
by sylvio2000
I started with a fresh profile of MrMC.

I scraped my movie folder and wanted to enable "try to wakeup remote servers on access". But I only get the message "MAC discovery failed for Medien-Server". The server definitely worked at this moment.
So I copied the wakeonlan.xml in the userdata folder and restarted MrMC. Nothing changed.

Then I installed and configured the nextpvr addon and it works! But even when the server wakes up the MAC discovery failed.

So this means that only if I install a pvr client my server wakes up :shock:. I think there must be something wrong ;)

I would like to give you a log, but I dont know how to reproduce this.

my wakeonlan.xml looks like this

Code: Select all

<onaccesswakeup>
    <netinittimeout>20</netinittimeout>
    <netsettletime>500</netsettletime>
    <wakeup>
        <host>192.168.178.15</host>
        <mac>D0:50:99:16:A3:D3</mac>
        <pingport>0</pingport>
        <pingmode>0</pingmode>
        <timeout>300</timeout>
        <waitonline>40</waitonline>
        <waitonline2>40</waitonline2>
        <waitservices>5</waitservices>
    </wakeup>
</onaccesswakeup>

Re: MAC discovery failed

Posted: 23 Feb 2017, 15:23
by davilla
follow -> debuglog

Re: MAC discovery failed

Posted: 23 Feb 2017, 15:33
by sylvio2000
Yes of course. But what shall I do if debugging is enabled?

Shall I activate the "try to wakeup remote servers on access" option? Shall I delete my wakeonlan.xml? Shall I disable the pvr client? ;)

Re: MAC discovery failed

Posted: 23 Feb 2017, 16:36
by davilla
replicate the failure, then grab mrmc.log. it might show more details about why it failed.

Re: MAC discovery failed

Posted: 23 Feb 2017, 16:37
by sylvio2000
OK.
I deleted the wakeonlan.xml, disabled tv and disabled "try to wakeup remote servers on access". I then enabled debugging and restarted MrMC.
Then I enabled "try to wakeup remote servers on access" and the failure message appeared.

http://pastebin.com/wFpRMHat

Re: MAC discovery failed

Posted: 26 Feb 2017, 21:26
by davilla
fixed for pending 3.0.1