[FX.php List] Monitoring FM Server 9/10 Advance

Steve Winter steve at bluecrocodile.co.nz
Fri Feb 6 02:03:42 MST 2009


I see what you're saying, however as I said, 99+% of the errors I've  
ever had (aside from a power cut) have been FM related, so running  
this level of diagnostics on the web server on a system has proved to  
be sufficient...

Cheers
Steve


On 6 Feb 2009, at 09:01, Gjermund Gusland Thorsen wrote:

> I am questioning whether or not it's possible for the same node that
> is if I understand you correctly possible to diagnose itself and still
> send an email if something is really wrong.
>
> For my system I do a port scan of port 80 on the FMSA machine and
> simulatenously I do this port scan on the web server, however I do NOT
> perform this portscan from any of those two machines running the
> services.
>
> Was I clear or confusing now?
>
> ggt
>
> 2009/2/6 Steve Winter <steve at bluecrocodile.co.nz>:
>> Hi ggt,
>> I'm not really sure what you mean by 'Now that's a nice idea, but  
>> is it for
>> real?'
>> Almost all of the systems that I'm running are a two-server setup,  
>> which has
>> the web server on one (or more) box(es) talking to the database  
>> server(s) on
>> another box (or boxes), with my 'checking' script running on the web
>> server...
>> In my experience 99% of issues with FileMaker based solutions  
>> (which use
>> Apache as the web server) are caused by a problem on the Database  
>> server,
>> and not the web server... and even on single machine installs, the  
>> system
>> itself is usually 'live' and so a command line based PHP script  
>> will still
>> be able to run and send email...
>> I've frequently had emails from the system to tell me that there's  
>> a problem
>> and been able to resolve it proactively before the client/customer  
>> even
>> knows that there is an issue. Over time, and as FMP has moved to a  
>> much more
>> stable server architecture, the frequency of these messages has  
>> decreased...
>> YMMV
>> Cheers
>> Steve
>>
>> On 6 Feb 2009, at 07:36, Gjermund Gusland Thorsen wrote:
>>
>> Now that's a nice idea, but is it for real?
>>
>> Do people who are shot or sick function realiably?
>>
>> Of course the best way is to listen to the ports on main page for  
>> your
>> FX.php,
>> and if there is no response the webserver should send the mail
>> message, I take for granted in this statement that you have FMSA and
>> web server on two different machines.
>>
>> ggt
>>
>>
>> 2009/2/6 Steve Winter <steve at bluecrocodile.co.nz>:
>>
>> Hi John,
>>
>> FMS itself can send automated emails when it detects any issue with  
>> the
>>
>> server situation...
>>
>> The other thing that I've done is to write a simple php script,  
>> which is
>>
>> then run on a win2k3 server scheduled task every 5 min which  
>> attempts to do
>>
>> a findAny() using fx on a series of database tables which should be
>>
>> accessible... if it fails on any of those, then that PHP script  
>> sends me an
>>
>> email with the name of the table in the message... I also have  
>> similar code
>>
>> in all of the web solutions I develop such that if a user ever  
>> attempts to
>>
>> connect to a db and that call fails then I get an email which tells  
>> me
>>
>> that...
>>
>> All of the above email go into an account which my mobile phone also
>>
>> monitors so that I get notification almost in real time by email  
>> and alert
>>
>> on my mobile...
>>
>> Hope this helps... if you want code examples let me know...
>>
>> Cheers
>>
>> Steve
>>
>> On 5 Feb 2009, at 22:56, criticalsolution at comcast.net wrote:
>>
>> Has anybody written or used any kind of script or app to monitor  
>> FMSA 9 or
>>
>> 10? My client wants a pro-acitive solution to tell tech support  
>> when there
>>
>> is trouble (or not) on an FMServer. I thought that there might be  
>> some ways
>>
>> to do this in FX/PHP?
>>
>> Thank you,
>>
>> John Funk
>>
>> Critical Solution
>>
>> _______________________________________________
>>
>> FX.php_List mailing list
>>
>> FX.php_List at mail.iviking.org
>>
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>> Steve Winter
>>
>> steve at bluecrocodile.co.nz
>>
>> m: +44 77 7852 4776
>>
>> 3 Calshot Court, Channel Way
>>
>> Ocean Village, Southampton SO14 3GR
>>
>> _______________________________________________
>>
>> FX.php_List mailing list
>>
>> FX.php_List at mail.iviking.org
>>
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>> Steve Winter
>> steve at bluecrocodile.co.nz
>> m: +44 77 7852 4776
>> 3 Calshot Court, Channel Way
>> Ocean Village, Southampton SO14 3GR
>>
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list


Steve Winter
steve at bluecrocodile.co.nz
m: +44 77 7852 4776
3 Calshot Court, Channel Way
Ocean Village, Southampton SO14 3GR

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iviking.org/pipermail/fx.php_list/attachments/20090206/b23d889b/attachment.html


More information about the FX.php_List mailing list