Version 8.8.1.6 - fix for finished markets, login window and more

I also got the gateway errors at that time. It was probably an issue with the API.

16:01:47	Error while refreshing the market "Greyhound Racing / SIS / Hove 20th Oct / 16:08 Hove 20th Oct - A6 500m". Gateway Time-out
16:02:08	Error while refreshing the market "Greyhound Racing / SIS / Hove 20th Oct / 16:08 Hove 20th Oct - A6 500m". Gateway Time-out
16:02:11	Error while refreshing the market "Greyhound Racing / SIS / Hove 20th Oct / 16:08 Hove 20th Oct - A6 500m". Gateway Time-out

Hi Oxa
Update from me: 8.8.1.7 been running all day with no problems. Like several other reports I did get the gateway timeout errors at 16:01 and the program just carried on fine after. Otherwise all good.

Hello all!

Thank you again for all your useful input!

I got the Gateway errors too, and around the same time: they are an indication of a temporary break in service. They are different to the "Empty response from the server" errors you were getting before. The fact that the program did not freeze after that and kept going is a good sign.

I'm glad that life (MF Pro-wise) is getting back to normal (well, you can't call it normal in all other respects I'm afraid).

Hi Oxa,

I've had an issue using 8.8.1.7 about an hour ago. The triggers on one of my instances stopped running at 09:51 then the program crashed completely at 10:02.

This is my one of my trigger logs when they stopped working...

09:51:45	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:45	Checking condition and Market's Minutes Before the Off is less than 1.
09:51:45	Condition is: FALSE.
09:51:45	Remaining conditions in the block will not be checked.
09:51:46	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:46	Checking condition and Market's Minutes Before the Off is less than 1.
09:51:46	Condition is: FALSE.
09:51:46	Remaining conditions in the block will not be checked.
09:51:47	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:48	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:49	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:50	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:51	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:52	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".
09:51:53	Checking market "Greyhound Racing / AUS / Rock (AUS) 21st Oct / 09:56 Rock (AUS) 21st Oct - R2 407m Nvce".

This is the crash error from Windows Event Viewer...
Faulting application name: feeder8.exe, version: 8.8.1.7, time stamp: 0x5f8c76f4
Faulting module name: feeder8.exe, version: 8.8.1.7, time stamp: 0x5f8c76f4
Exception code: 0xc0000005

My other instance stayed working, but there's been some of the "Unknown Path" errors...

06:49:01	Checking market "Unknown Path07:14 Asct (AUS) 21st Oct - R2 1400m Mdn".
06:49:01	Checking condition or Market's Matched Volume is greater than 3000.
06:49:01	Condition is: FALSE.
06:49:01	Checking condition or Market's Minutes Before the Off is less than 5.75.

Reggie

Ive been getting some of old errors again today, insufficient fund error,error while refreshing market-bad request and bad gateway errors

Quote from: COLING on 21 Oct 2020, 11:15

Ive been getting some of old errors again today, insufficient fund error,error while refreshing market-bad request and bad gateway errors

I'm not sure they're old.
The "Insufficient Funds" error is still what it is -- the alert of not enough funds in your account. I don't think it was mentioned before in connection with the recent issues. It was "Error while refreshing funds", wasn't it?

The "Bad Gateway" is also different -- it is a temporary break in service, it usually clears on its own after a few minutes.

Could you attach the extract from your Program Log please?

hi thanks, the insufficient funds is worry me, the bets used to show on the log as massive lay bets, for example it trys to lay 1000 pounds at odds of 500, ive got dutch lay amount to lose set at 200, ive been running this trigger for over 4 years with no problem, trouble is the amounts dont show on log anymore just get the insufficient funds error, i enclose the bad request errors

The TOO_MANY_REQUESTS is an error that comes up when you are trying to refresh too many markets at a too frequent refresh rate. See question 5 here:

http://marketfeeder.co.uk/learn/articles/highlights/10-03-2020/

Quote

for example it trys to lay 1000 pounds at odds of 500, ive got dutch lay amount to lose set at 200

You can check the log of that dutching trigger to see what kind of bets it's sending off. The amounts will be in the trigger log, not the Program Log.

Cheers,it was trying to lay 500 pounds on all the outsiders therefore massive liability and insufficient funds, iv egot round it by adding a condition only bet if probable losers stake is under 30, just wondered why it has started to happen, nevr happened before

Quote

just wondered why it has started to happen, nevr happened before

Check what's in the amount of the betting trigger. If you're using a loss recovery, then each next bet can increase very speedily.

But this is off-topic, please create a new trigger request if you need help with a particular set of triggers.

I upgraded to the latest version a few days ago.

All has been good until just now. At about 1830 I loaded tomorrows UK horse racing markets. I've just checked MFP and have seen that the first 9 races, 1240-1425 are all marked as finished. These were not being monitored.

Interestingly I have a 2nd instance of MFP running, again I loaded the markets at 1830 and they are set to be monitored at 30s refresh and non of them are showing finished.

event_finished is zero for all events.

I've attached screen shots.

Thanks

Mike

Quote from: mikejcshaw on 23 Oct 2020, 00:03

I upgraded to the latest version a few days ago.

...
Thanks

Mike

Hello Mike!

Could you please attach the Program Log for the instance where the markets are showing as finished?

Please see attached log, (without bets)
Thanks
Mike

Quote from: mikejcshaw on 23 Oct 2020, 06:27

Please see attached log, (without bets) Thanks Mike

There are no error messages in the log, nothing that could indicate any problem with those markets. You're saying that they were not being monitored, so I'm not sure how they could be deemed "Finished" without refreshing them once. Do you add markets manually or using Market Locator? Are settings in both profiles identical?

I probably need more details from you, but it would be better to discuss them in private. Could you PM me with the answers, and I'll PM you back please?

Hi - I've updated to 8.8.1.6 and am still expereinceing the greyed out markerts issue. Here's a screenshot of two profiles I have running simultaneously (pretty well the same settings) and at some point after not long starting the session several markets got greyed out on one but not the other...

Correction - settings are exactly the same!

Version 8.8.1.6 - fix for finished markets, login window and more

Hello Guest