BrianD Legend  Posts: 302 Joined: 2/23/2013 Location: Grand Rapids, MI  User Profile | Mark: I did have problems Monday but not TP/IB gateway/execution issues. Problems were because my server rolled over and died due to lack of storage (fortunately Monday AM trades were submitted before server blew up). I think logging of Monday's trades dealt my server's last hand. However, I had no execution problems. After I created a new AWS instance and re-loading TP/IBG, all OV positions were reconnected without problem too. BTW, building a new AWS instance is not the only way to address lack of disk capacity (e.g. delete files, etc.) but that's the avenue I chose for a clean platform because I'm surprised the capacity was used, so I can now watch to assure the log file capacity is released. I case you don't know, to check disk capacity, open server's Windows Explorer, right click on your "Local disk (C:)" and click on Properties. If you are out of "Free Space", that's what has caused my server failure. Otherwise, Steve's point of RAM may be something to look at too. Also, I'm running 3 TP/IBG. Have run as many as 4 but not recently. And I am keeping TP Logging to 1 week in each TP. [Edited by BrianD on 7/29/2016 5:09 PM] | |
