News:

RAID is not a replacement for a backup! Here's why.

Main Menu

Throttle respawn issue with mac

Started by parallax, December 07, 2011, 01:41:29 PM

Previous topic - Next topic

parallax

I have a mac intel running 10.6.8, NAS Nav2 2.40, airport router (hardwired to Buffalo), and Buffalo LinkStation GL1000 that keeps generating:

 

12/7/11 11:30:57 AM com.apple.launchd.peruser.501[169] (jp.buffalo.NASPower) Throttling respawn: Will start in 50 seconds
12/7/11 11:31:05 AM NasNaviHelper[258] OK. Complete to scan drives.
12/7/11 11:31:05 AM NasNaviHelper[258] execute: <NASListModeCommandAfter: 0x501060> end
12/7/11 11:31:05 AM NasNaviHelper[258] execute: <NASListModeCommand: 0x500400> end
12/7/11 11:31:47 AM NasNavigator2[56051] execute: <NASListModeCommand: 0x62f9f0> start
12/7/11 11:31:47 AM NasNavigator2[56051] execute: <NASListModeCommandPrepare: 0x65be80> start
12/7/11 11:31:48 AM NasNavigator2[56051] execute: <NASListModeCommandPrepare: 0x65be80> end
12/7/11 11:31:48 AM NasNavigator2[56051] execute: <NASListModeCommandMain: 0x605c90> start
12/7/11 11:31:48 AM NasNavigator2[56051] 00:16:01:C5:58:F6
12/7/11 11:31:48 AM NasNavigator2[56051] execute: <NASListModeCommandMain: 0x605c90> end
12/7/11 11:31:48 AM NasNavigator2[56051] execute: <NASListModeCommandAfter: 0x661760> start
12/7/11 11:31:55 AM NasNaviHelper[258] execute: <NASListModeCommand: 0x500320> start
12/7/11 11:31:55 AM NasNaviHelper[258] execute: <NASListModeCommandPrepare: 0x5036d0> start
12/7/11 11:31:55 AM NasNaviHelper[258] execute: <NASListModeCommandPrepare: 0x5036d0> end
12/7/11 11:31:55 AM NasNaviHelper[258] execute: <NASListModeCommandMain: 0x501060> start
12/7/11 11:31:55 AM NasNaviHelper[258] 00:16:01:C5:58:F6
12/7/11 11:31:55 AM NasNaviHelper[258] execute: <NASListModeCommandMain: 0x501060> end
12/7/11 11:31:55 AM NasNaviHelper[258] execute: <NASListModeCommandAfter: 0x500da0> start
12/7/11 11:31:58 AM NasNavigator2[56051] OK. Complete to scan drives.
12/7/11 11:31:58 AM NasNavigator2[56051] execute: <NASListModeCommandAfter: 0x661760> end
12/7/11 11:31:58 AM NasNavigator2[56051] execute: <NASListModeCommand: 0x62f9f0> end
12/7/11 11:31:58 AM com.apple.launchd.peruser.501[169] (jp.buffalo.NASPower) Throttling respawn: Will start in 50 seconds

 

every minute.

 

I've checked the NAS files called by the launchd agents and they all seem installed correctly and the program content refs are in place and work. So why the constant errors?

 

i.e.:

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd" target="_blank">http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>jp.buffalo.NASPower_pla</string>
<key>ProgramArguments</key>
<array>
<string>/Library/PrivilegedHelperTools/NasNavigator2.app/Contents/MacOS/NasNavigator2</string>
<string>-list</string>
<string>active</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>KeepAlive</key>
<true/>
<key>ThrottleInterval</key>
<integer>60</integer>
<key>LimitLoadToSessionType</key>
<array>
<string>LoginWindow</string>
</array>
</dict>
</plist>

 

 

 

What do I need the 

jp.buffalo.NASPower_pla.plist

jp.buffalo.NASPower.plist

files for? Can I just delete them? or is there a setting I can change. The Buffalo does not have a physical manual/auto switch on the back that I can see, just a push button.

 

I realize these errors aren't seriously comromising the sytem, but they are annoying, cloying and need to go away so I can see if real problems are cropping up with I check once a week.


jrab

I don't know either, but I think it started appearing after the last update., either the firmware (1.56) or Nas software. I would love to get it cleaned up too.

 

thanks 

jrab


demeeder

Did you ever figure out what this was?  I don't get the throttle spawn error, but do get this every minute:

 

6/26/12 10:25:37.072 PM NasNaviHelper: execute: <NASListModeCommand: 0x1871c0> start
6/26/12 10:25:37.072 PM NasNaviHelper: execute: <NASListModeCommandPrepare: 0x16d3f0> start
6/26/12 10:25:37.073 PM NasNaviHelper: execute: <NASListModeCommandPrepare: 0x16d3f0> end
6/26/12 10:25:37.073 PM NasNaviHelper: execute: <NASListModeCommandMain: 0x1871b0> start
6/26/12 10:25:37.074 PM NasNaviHelper: 00:1D:73:A4:1F:EF
6/26/12 10:25:37.074 PM NasNaviHelper: execute: <NASListModeCommandMain: 0x1871b0> end
6/26/12 10:25:37.075 PM NasNaviHelper: execute: <NASListModeCommandAfter: 0x174c40> start
6/26/12 10:25:47.080 PM NasNaviHelper: OK. Complete to scan drives.
6/26/12 10:25:47.081 PM NasNaviHelper: execute: <NASListModeCommandAfter: 0x174c40> end
6/26/12 10:25:47.081 PM NasNaviHelper: execute: <NASListModeCommand: 0x1871c0> end

 

Seems a bit excessive, but not sure if it is normal.

 

Appreciate the assist.

 


buffalotekalou

Hello,

 

  this message is not an error, it's just a feature.

When you ask your NAS to power on "Automatically", the job you see in the log is in charge of telling the NAS to stay awake. When you stop your mac or you put it to sleep, your NAS will shut down shortly after, because it does not receive this "keep alive" signal from your Mac.

 

Best Regards,

 

Olivier


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 170 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1048KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]