Jump to content

CrazyC

Members
  • Posts

    5
  • Joined

  • Last visited

  1. Nothing more on this? It's definitely related to Pulseway. If I stop Pulseway on either Mac Mini, the errors go away. There are no SMC errors on my Mac Pro.
  2. The errors stop if I stop Pulseway from running, yes. I should have mentioned that in my first post.
  3. I have the pulseway daemon running on 3 different Macs. 2 are Mac Minis and 1 is a Mac Pro. The 2 Mac Minis have a steady flow of errors like this in their logs: Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:52 ny2 kernel[0]: SMC::smcReadKeyAction ERROR F1Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 Mar 30 20:23:57 ny2 kernel[0]: SMC::smcReadKeyAction ERROR F1Ac kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80220d2000 From some searching I have done it is likely related to a none existent sensor that the daemon is looking for. If I had to guess, I would say it's related to fans. The Mac Mini only has 1 cooling fan in it versus the multiple fans in the Mac Pro. It would probably be good to have the option to specify fan monitoring and even other hardware options. The Daemon could display the current state of any item being monitored and if it's error'ed or someting chosen not to monitor, the user can turn that item off and prevent errors like this in the logs.
  4. Hmm, ok. I will restated my comment about it just doesn't seem fair that Mac Admins are charged the same rate as Windows admins with less than 1/2 the features. This is my only hang up at this point. Some how, I don't see getting a break for that, but it would certainly be a nice thought, maybe even for the first year since there are so many things not available for Macs at the present.
  5. I've been testing Pulseway out for a few weeks now and have about 2 weeks before my trial expires. So far, I really like Pulseway and what it does, but I'm very concerned that there are tons of features for monitioring windows servers and there's quite a bit that can be configured for linux (I haven't dug into this yet), but the OS X daemon seems to be lacking in features. Why can't we monitoring services on Macs? I don't see services or scheduled tasks for Macs. For Mac servers (using Apple's server app) I would think it should be pretty simple to integrate with status off the server app. There are a ton of console commands for "serveradmin" that return status of all aspects of the server and there are numerous controls that can be performed using serveradmin. While I do like what I CAN do with pulseway, I really think us Mac users are getting jipped by being charged the same price as Windows admins that get, what looks like, 10 times the features. In addition, I was looking for notification settings for the port monitoring feature. Is there a way to configure notifications for ports?
×
×
  • Create New...