Automatic WakeOnLan upon accessing MySql or FileShares

  Thread Rating:
  • 4 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
t4_ravenbird Offline
Senior Member
Posts: 183
Joined: Mar 2012
Reputation: 5
Post: #526
(2014-07-15 13:33)Excelsis Wrote:  Ok, this is doing my head in. Advanced WOL works a-ok. Wake on access worked during the betas, but since the final v13 came out, it hasn't worked. I have to disable general WOL access, leaving only Magic Packets being able to wake it up, on my server computer as otherwise it just keeps waking back up right after putting it to sleep.

It seems like XBMC WOA switched from sending a magic packet to a generic wol packet? In any case, is there anyway to fix this?

Sorry for late reply but, no, there has been no change - it is and has always been a magic packet transmission. Please post debug log and I will have a look.

(2014-10-20 18:25)wrxtasy Wrote:  Hi everyone,

At the moment I'm having issues with XBMC and WOL with an iMac.
WOL is very particular on a Mac and I believe has to go via a Bonjour sleep proxy, anyway thats not a problem as my router is an Airport Extreme.

It is also very particular about what it will Wake Up to for file sharing.
NFS Sharing and trying to wake the Mac does not work, however initiating a WOL for a SAMBA share (port 445) from XBMC does work to keep the Mac awake.
I can then access the NFS shares whilst the Mac stays awake.

I have modified the wakeonlan.xml file to pingport 445 for SAMBA.

Is it at all possible to do a spoof WOL and wake up my Mac via port 445 if I select a NFS Share (port 2049) in XBMC ?

Accessing NFS should wake your server, please post log if it does not. The ports used for ping is used only for ping, not wakeup.
(This post was last modified: 2014-10-20 19:01 by t4_ravenbird.)
find quote
wrxtasy Offline
Senior Member
Posts: 111
Joined: Feb 2012
Reputation: 1
Location: Perth, Oz
Post: #527
nfsd status
nfsd service is enabled
nfsd is running (pid 170, 8 threads)

First WOA to a SMB Apple Extreme server is a success

WOA to the Mac via NFS always fails even though it reports success...
Tried -
pingport>2049 and 0

in combo with
pingmode>0 and then 1


Code:
01:58:12 T:3059376672  NOTICE: WakeOnAccess [192.168.1.1] trigged by accessing : smb://192.168.1.1/Big_Box_Office/TV Shows/
01:58:12 T:3059376672  NOTICE: WakeOnAccess success exit, server already running
01:58:12 T:2883683408  NOTICE: Thread JobWorker start, auto delete: true
01:58:28 T:2643006544  NOTICE: Thread BackgroundLoader start, auto delete: false
01:58:30 T:2643006544  NOTICE: Thread JobWorker start, auto delete: true
01:58:31 T:2821715024  NOTICE: Thread BackgroundLoader start, auto delete: false
01:58:40 T:3059376672  NOTICE: WakeOnAccess [Monkeys-iMac.local] trigged by accessing : nfs://Monkeys-iMac.local/Users/WRXTASY/Downloads/
01:58:40 T:3059376672  NOTICE: WakeOnAccess success exit, server already running
02:00:02 T:3059376672  NOTICE: Samba is idle. Closing the remaining connections
02:01:08 T:3059376672   ERROR: GetDirectory - Error getting nfs://Monkeys-iMac.local/Users/WRXTASY/Downloads/
02:01:08 T:3059376672   ERROR: CGUIMediaWindow::GetDirectory(nfs://Monkeys-iMac.local/Users/WRXTASY/Downloads/) failed
find quote
t4_ravenbird Offline
Senior Member
Posts: 183
Joined: Mar 2012
Reputation: 5
Post: #528
OK, I dont know what happens but there are 2 explanations I can think of ;
1. The iMac OS (OSX?) is sleeping but not very deep so it is able to respond to the ping? Just speculating, I dont know those Apples very well (not at all , in fact) Is a mode like that possible on an Apple??
2. WakeOnAccess does a DNS-Lookup to figure out the IP-address and afterwards which network the server must be on (so it knows the magix packet goes out on the right NIC). If DNS-Lookup for some reason returns the ipaddress of another (running) machine then something like this could happen. Could you try to map the NFS-path by servers ip-address instead of name and see if that works? (192.168.1.X instead of 'Monkeys-iMac.local')
find quote
wrxtasy Offline
Senior Member
Posts: 111
Joined: Feb 2012
Reputation: 1
Location: Perth, Oz
Post: #529
Thanks for looking into this, I have tried pretty much everything, I.P. addresses instead of local path names etc.

It appears to be a long running known issue with NFS sleep/wake when running on OS X that Apple knows about and for some reason refuses to fix in at least the last 3 OS X releases.

Its all detailed in these two threads if other Apple users want to know whats going on.

http://forums.macrumors.com/showthread.php?t=1752524
https://discussions.apple.com/thread/415...0&tstart=0
(This post was last modified: 2014-10-21 03:27 by wrxtasy.)
find quote
Post Reply