How to automatically re-start MF Pro after it has frozen?

Hi Oxa

I read this over the weekend:

http://community.marketfeederpro.com/suggestions-6/log-in-to-mfpro-when-betfair-down/msg970/#msg970

I understand your suggestions, trigger, but there might be problems with implementing them: too many things in MF Pro are connected with BF data and maintaining them offline is not such an easy job.

Regarding this one:

> 4. If betfair is down the user is notified by a message pop up window in MFPro, 
> MFPro continues to attempt the login automatically say every 15mins

I have a possible solution. Try creating a task in Windows scheduler, as explained here:

http://www.marketfeederpro.com/solutions/tips-n-tricks/start-command-line/

You can set it to try to be launched every 15 mins and make an attempt to log in. If it fails due to BetFair being down, it will stop connecting for now and will re-try next time.

I will try and set this up for the future when Betfair are carrying out maintenance. A lost day's trading for me as I have to leave for work way before 10am.

Over the last couple of days MF Pro has 'frozen' on me i.e. come home and it is not counting down the seconds and minutes to the events. I have to shut down the program and re start; this clears the hang up and it starts working again.

Would the above 'create a task' work in this situation? What I would like is

- a way to monitor that MF Pro is functioning
- if it isn't (i.e. frozen) then this is detected
- MF Pro closed down
- MF Pro started up again

I am concerned that the create a task approach would open another version of MF Pro on my PC.

Please can you let me know what the best way to do this would be? Thanks a lot.

75again,

for restarting MFPro I use a free Windows scripting tool called: AutoIt . google for  keyword AutoIt. I detect possible frozen MFPro by looking in the action logfile directory. If there is no change within 30 minutes I assume MFPro is frozen, then my script kills MFPro and does a restart. This solution has several disadvantages, but is the only solution I found to kill frozen MFPro.

First Problem: You need to write a new script for every new MFPro version because AutoIt simulates mouse clicks and keystrokes. You need some programming skills to write the script.

Second Problem: Script assumes MFPro frozen when no actions are done within 30 minutes. Sometimes there are no matching conditions for triggers, so MFpro is re-started even if was not frozen. This can lead to a problem: script re-starts MFPro just when MFPro sends new bets into the market, can lead to incomplete dutching.

Third Problem: You should use this script only if your trigger file does not need any information stored in user variables and does not use auto greenup. This information is lost during restart.

So I use my AutoIt script only for pre inplay back / lay dutching.

Hi Martin
Great reply, thanks. I shall investigate - I reckon the First Problem maybe my main issue but I shall give it a whirl.

Thanks again.

Second Problem: Script assumes MFPro frozen when no actions are done within 30 minutes. Sometimes there are no matching conditions for triggers, so MFpro is re-started even if was not frozen. This can lead to a problem: script re-starts MFPro just when MFPro sends new bets into the market, can lead to incomplete dutching.

Regarding your second problem Martin, you could set a dummy trigger to do at least something in the action file every 30 mins such as place a bet at odds of 1000 on the favourite (which hopefully won't get matched) and cancel it again after a couple of seconds, just to keep things ticking over.  If MF pro hangs - AS IT DOES, FAR TOO OFTEN - your software should recognise it and restart.

Hi alfaman,

thank you for this great hint! Now doing a lay bet at 1.01 and cancel every 25 minutes for all selections in all active markets.