This site is designed to take advantage of CSS. If you are seeing this, CSS must not be available or enabled in your browser. Everything should still work, but won't be as pretty. :)
I can't get the email notification to work, please help.
macosx : 10.6.7
For evaluation purposes I've installed the new Simon 3 on my MacBook Pro.
Now, I tried to install it on my server but get the message: this license is already used.
How can I move my Simon license to another machine?
Having trouble with the new v3 Simon, similar to that previously reported in 2.5.7. This began in my third day of test and setting up. I've been using a PING test, changing the IP from the right one, to a bad one, so that the test alternates between down an up, to verify sending emails, and trying to get twitter and sms to work.
That's a separate issue: although the report is now going through to the FTP site, email has been inconsistent and twitter and SMS have not yet worked. *There are no network problems here, I've been capturing and looking at all packets w/ Wireshark to try to see diagnose problems Simon has been having in sending out messages.
Now, in the last hour or so - after about 20 sec of pinging a non-existant IP the beachball of death comes on, Simon hangs, and eventually, if I don't force quit, will hang the whole machine. After 20 seconds Simon has stopped sending out packets, although the test shows it's still going on, although Simon's timer no longer updates. This is what went on previously with 2.5.7.
I uninstalled Simon and trashed com.dejal.plist, but the re-install of 3 still picks up my tests and SN - so - evidently there's info somewhere else as well, which, if it's munged, may be the problem. AFAIK there's no 'uninstall' - too bad. It would be v. nice to be able to go back to square one when there's a problem without needing to do a treasure hunt to find the rest of Simon's files.
Per David's previous request, I took screen shots, console and process samples, and I'll send the zip in - attached here is the hang dump sent to Apple.
Any thoughts appreciated -
* The need to make a test go up and down to test notifiers is not v. convenient. For my USB thermometer software, the email setup window has a "test" button to send a test message without having to cause a test failure. A similar test button for SMS, twitter, email in Simon setup windows to verify the settings right then and there would be nice. Or perhaps I've overlooked something?
* Also - even when the report function is failing to upload to FTP, it happily reports done and available - even when I could see by the packets that it got an error because the path was typoed. A test button here, that understood when an error is generated, would keep me from having to catch the data stream and look at all the packets to diagnose things.
I have approx 150 tests running.
I have interval checks set to 0 seconds.
I need to test some alerts every 5 minutes and some every 15 minutes.
But once a check has been performed the time to next check comes back at approx 20 minutes.
Is there a way i can increase the concurrency of tests so i can reduce the "next check" frequency?
I was hoping in the next version you could add a column in the tests display to show total downtime since the last reset... even better would be able to pick a time frame (in the last day, week, month, or year), or an available column for each (day, week, month, year).
Last downtime is not really all that useful to me, especially in cases like today where my mail server was having sporadic issues and was off and on... each time it recovered it reset the downtime counter, so it reads that it was only down for a few minutes when it was actually down much longer. But when a client calls and complains their site is "always going down" it would be nice to be able to look and say "your site was only down for a total of 85 minutes in the last year" and shut them up :)
Thanks for a great and helpful app!
Using 3.0.1 (3004).
It hangs (non responding) on OS X 10.5.8 on Dual 2GHZ PPC G5 - any one else have this problem?
Prev 2.x.x. never crashed.
Any idea why?