There is the article about it: METATRADER 5 ON LINUX
and it should be log file (in Metatrader 5 - log file) ... what is written in log file? (if you write to the service desk for example so they will also ask about log file).
How much I understand there are not something special.
Please find logs attacked.
Yes, nothing special in the logs ...You can write to the service desk describing the issue (and attach log files to the ticket) - just hope they will work on Monday after holiday so they can review the situation.
Or - may be some user (who are computer specialist for example) can help here ... may be - the memory is not enough in PC ...
Since you tried on two separate operating systems this seems to indicate it is a hardware problem.
Have you kept an eye on the system resource monitor just before it shuts down ?
Did you try on windows ?
On windows all working well with no interrupts.
Could you please share more details what could be wrong with hardware?
I am using VPS with CentOs 6.
I see well you did not mention that it is running on VPS in your first post so i was under the impression that you were using CentOS without VPS.
Unfortunately it's not possible to use the tester agent on a VPS.
Unfortunately it's not possible to use the tester agents on a VPS.
i'm running lots of metatrader instances and tester agents on server linux machines (debian / ubuntu)
I had the same issue - but it's mostly a problem with wine:The metatester.exe is a gui application where you manage windows-services that run in the background. These services are closed (killed) by wine, if no other windows-window application is running (a visible window running in wine).It seems like the metatester window dissapears after a while (eg. 20 minutes ;-) - i think someone build in a timer there (i have no idea why ;-)
so the solution is simple: open a other window from wine
i have a "DISPLAY=:0 wine notepad" in rc.local so wine is started and a window is visible (so the agent-services are started) - you just have to keep the notepad window open
hope this helps you
and some of my machines are virtual (xen instances) - they're also running fine (i also had some tests in a virtualbox-vm - also no problem)
why shouldn't that work in a vps ??