... is REJECTED with error "DISCONNECTED"
... is REJECTED with error "DISCONNECTED"
21 Jul 2017, 12:18
Hello,
i have noticed that there are frequent disconnects, which would be "ok", if the connect would work anytime.
But look at the following logs, please (by the way "GETRENNT" is the german word for "DISCONNECTED"):
2017.07.20 12:22:22.086 | Request to amend position PID66731851 (SL: 5836.81) is sent to server
2017.07.20 12:22:22.112 | → Request to amend position PID66731851 (SL: 5836.81) is REJECTED with error "GETRENNT"
2017.07.20 12:22:22.122 | Request to amend position PID66731851 (SL: 5836.82) is sent to server
2017.07.20 12:22:22.123 | → Request to amend position PID66731851 (SL: 5836.82) is REJECTED with error "GETRENNT"
2017.07.20 12:22:31.525 | Request to amend position PID66731851 (SL: 5836.72) is sent to server
2017.07.20 12:22:32.683 | → Request to amend position PID66731851 (SL: 5836.72) is ACCEPTED
2017.07.20 12:22:33.710 | Request to amend position PID66731851 (SL: 5836.66) is sent to server
2017.07.20 12:22:34.024 | → Request to amend position PID66731851 (SL: 5836.66) is ACCEPTED
2017.07.20 12:23:35.106 | Request to amend position PID66731851 (SL: 5836.82) is sent to server
2017.07.20 12:23:35.215 | → Request to amend position PID66731851 (SL: 5836.82) is ACCEPTED
---> seems to be connected again
.... many more logs ....
2017.07.20 14:58:55.415 | Request to amend position PID66664915 (SL: 1.14616) is sent to server
2017.07.20 14:58:55.415 | Request to amend position PID66664915 (SL: 1.14615) is sent to server
2017.07.20 14:58:55.415 | Request to amend position PID66664915 (SL: 1.14614) is sent to server
2017.07.20 14:58:55.415 | Request to amend position PID66664915 (SL: 1.14615) is sent to server
2017.07.20 14:58:55.415 | Request to amend position PID66664915 (SL: 1.14616) is sent to server
2017.07.20 14:59:38.549 | → Request to amend position PID66664915 (SL: 1.14601) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.552 | → Request to amend position PID66664915 (SL: 1.14604) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.553 | → Request to amend position PID66664915 (SL: 1.14607) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.555 | → Request to amend position PID66664915 (SL: 1.14608) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.556 | → Request to amend position PID66664915 (SL: 1.14616) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.557 | → Request to amend position PID66664915 (SL: 1.14625) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.557 | → Request to amend position PID66664915 (SL: 1.14621) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.557 | → Request to amend position PID66664915 (SL: 1.14621) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.557 | → Request to amend position PID66664915 (SL: 1.14618) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.557 | → Request to amend position PID66664915 (SL: 1.14616) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.930 | → Request to amend position PID66664915 (SL: 1.14615) is REJECTED with error "GETRENNT"
2017.07.20 14:59:38.936 | → Request to amend position PID66664915 (SL: 1.14614) is REJECTED with error "GETRENNT"
2017.07.20 14:59:39.217 | → Request to amend position PID66664915 (SL: 1.14615) is REJECTED with error "GETRENNT"
2017.07.20 14:59:39.223 | → Request to amend position PID66664915 (SL: 1.14616) is REJECTED with error "GETRENNT"
2017.07.20 14:59:39.397 | Request to amend position PID66664915 (SL: 1.14622) is sent to server
2017.07.20 14:59:39.405 | → Request to amend position PID66664915 (SL: 1.14622) is REJECTED with error "GETRENNT"
2017.07.20 14:59:39.405 | Request to amend position PID66664915 (SL: 1.14618) is sent to server
2017.07.20 14:59:39.490 | → Request to amend position PID66664915 (SL: 1.14618) is REJECTED with error "GETRENNT"
2017.07.20 14:59:39.492 | Request to amend position PID66664915 (SL: 1.14616) is sent to server
2017.07.20 14:59:39.519 | → Request to amend position PID66664915 (SL: 1.14616) is REJECTED with error "GETRENNT"
... here again many more logs, but ALWAYS with the same error until the next mentioned point...
2017.07.20 15:08:21.581 | → Request to amend position PID66664915 (SL: 1.14725) is REJECTED with error "GETRENNT"
2017.07.20 15:08:21.582 | Request to amend position PID66664915 (SL: 1.14724) is sent to server
2017.07.20 15:08:21.584 | → Request to amend position PID66664915 (SL: 1.14724) is REJECTED with error "GETRENNT"
2017.07.20 15:08:23.259 | Request to amend position PID66664915 (SL: 1.14723) is sent to server
2017.07.20 15:08:23.341 | → Request to amend position PID66664915 (SL: 1.14723) is REJECTED with error "GETRENNT"
2017.07.20 15:08:24.240 | Request to Buy € 48k EURGBP (Price: 0.89523, SL: 119, TP: 241, MR: 2) is sent to server
2017.07.20 15:08:24.772 | → Order OID0 is REJECTED with error "GETRENNT"
2017.07.20 15:08:24.774 | Request to amend position PID66664915 (SL: 1.14725) is sent to server
2017.07.20 15:08:24.776 | → Request to amend position PID66664915 (SL: 1.14725) is REJECTED with error "GETRENNT"
2017.07.20 15:08:24.777 | Request to amend position PID66664915 (SL: 1.14724) is sent to server
2017.07.20 15:08:24.779 | → Request to amend position PID66664915 (SL: 1.14724) is REJECTED with error "GETRENNT"
2017.07.20 15:08:35.144 | Request to amend position PID66664915 (SL: 1.14726) is sent to server
2017.07.20 15:08:35.146 | → Request to amend position PID66664915 (SL: 1.14726) is REJECTED with error "GETRENNT"
2017.07.20 15:08:35.147 | Request to amend position PID66664915 (SL: 1.14736) is sent to server
2017.07.20 15:08:35.149 | → Request to amend position PID66664915 (SL: 1.14736) is REJECTED with error "GETRENNT"
... DURCHGÄNGIG
2017.07.20 15:43:51.390 | Request to amend position PID66664915 (SL: 1.15021) is sent to server
2017.07.20 15:43:52.378 | → Request to amend position PID66664915 (SL: 1.15021) is REJECTED with error "GETRENNT"
2017.07.20 15:43:53.504 | Request to amend position PID66664915 (SL: 1.15019) is sent to server
2017.07.20 15:43:53.525 | → Request to amend position PID66664915 (SL: 1.15019) is REJECTED with error "GETRENNT"
2017.07.20 15:43:53.529 | Request to amend position PID66664915 (SL: 1.15018) is sent to server
2017.07.20 15:43:53.597 | → Request to amend position PID66664915 (SL: 1.15018) is REJECTED with error "GETRENNT"
2017.07.20 15:43:53.631 | Request to amend position PID66664915 (SL: 1.15014) is sent to server
2017.07.20 15:43:53.659 | → Request to amend position PID66664915 (SL: 1.15014) is REJECTED with error "GETRENNT"
.... so from 14:59:38.549 until 15:43:53.659 and THEN there are NO more logs until the following...:
HERE i logged onto the machine at about 2017.07.21 07:45:00 and the login dialog was opened with the message, that login details are invalid. BUT when i click at login, it could be logged in fine. So from 2017.07.20 15:43:53.659 until 2017.07.21 07:45:00.864 when i manually logged in with the dialog like i described my bots were completely disconnected.
2017.07.21 07:45:00.864 | Request to amend position PID66664915 (SL: 1.15119) is sent to server
2017.07.21 07:45:01.259 | → Request to amend position PID66664915 (SL: 1.15119) is ACCEPTED
2017.07.21 07:45:01.390 | Request to amend position PID66664915 (SL: 1.15116) is sent to server
2017.07.21 07:45:01.626 | Request to Sell $ 159k USDCHF (Price: 0.95076, SL: 45, TP: 93, MR: 2) is sent to server
2017.07.21 07:45:01.628 | Request to amend position PID66664915 (SL: 1.15116) is sent to server
2017.07.21 07:45:01.710 | → Request to amend position PID66664915 (SL: 1.15116) is ACCEPTED
2017.07.21 07:45:01.994 | → Request to Sell $ 159k USDCHF (Price: 0.95076, SL: 45, TP: 93, MR: 2) is ACCEPTED, order OID105676684 created (21/07/2017 07:44:55.671 UTC+0)
2017.07.21 07:45:01.998 | → Request to amend position PID66664915 (SL: 1.15116) is ACCEPTED
2017.07.21 07:45:02.347 | → Order OID105676684 is FILLED at 0.95074, position PID66809769 (21/07/2017 07:44:55.763 UTC+0)
2017.07.21 07:45:02.581 | Request to amend position PID66664915 (SL: 1.15117) is sent to server
2017.07.21 07:45:02.772 | Request to amend position PID66664915 (SL: 1.15117) is sent to server
2017.07.21 07:45:02.824 | → Request to amend position PID66664915 (SL: 1.15117) is ACCEPTED
2017.07.21 07:45:03.488 | → Request to amend position PID66664915 (SL: 1.15117) is ACCEPTED
2017.07.21 07:45:07.662 | Request to amend position PID66664915 (SL: 1.15119) is sent to server
2017.07.21 07:45:07.974 | → Request to amend position PID66664915 (SL: 1.15119) is ACCEPTED
2017.07.21 07:45:10.470 | Request to amend position PID66664915 (SL: 1.15121) is sent to server
2017.07.21 07:45:10.860 | → Request to amend position PID66664915 (SL: 1.15121) is ACCEPTED
Please fix / help me with the "Connection is lost"-problem. Although it could not connect again, it should NOT happen, that it stops from trying it, because like i said after i clicked the login button on the dialog with - of course no change in password or account number - the login was processed correctly.
Thank you in advance.
Best regards,
andi21
Replies
andi21
21 Jul 2017, 15:36
Hi Spotware,
thank you for your answer.
Yes i can and will do that.
But if this happens again, probably i will have lost money because of that problem, because my bots are not connected and thus cannot handle positions. Currently that is not that bad, because i am "only" forward-testing (although the statistics could be falsified which is not good, too). But the key is, that if disconnections occur in my opinion cAlgo should not stop trying to reconnect automatically, although if it takes some time, and not show the login dialog, because it thinks something changed etc. and the credentials has to be filled in again.
Best regards,
andi21
@andi21
Spotware
21 Jul 2017, 15:24
Hi andi21,
Thanks for reporting this problem. Can you please send us troubleshooting information so that we can investigate further? Whenever this happens again, please press Ctrl+Alt+Shift+T, type your problem and press Submit. Our technical team will receive all the required information to investigate the problem further.
Best Regards,
cTrader Team
@Spotware