At about 8:13 EST today I had a problem which I've seen before.
I get a SERVER DISCONNECTED message, 5 minutes later my application detects that time-stamp messages have stopped and tries to re-connect. The application re-connects locally, but always gets SERVER DISCONNECTED on re-connection, and no time-stamp messages.
This continues until IQFeed is restarted.

The pattern seems to be that IQFeed gets disconnected from it's server, most of the time it's able to re-connect, but sometimes something goes wrong and it's toast until a re-start. I try to re-connect locally, but the lack of time-stamp messages seems to indicate things have gone south.

Does IQFeed create any logs which may help to diagnose the problem, any advice in general?

It's currently doing the same thing on my account right now if anybody is interested.
Disconnected at 11:34:53.

Tried a different track this time, instead of stopping and starting IQFeed I went to the IQQuoteWatch application, which was working. When I looked at the logs of my other apps they had all magically reconnected and started working. So it seems the IQQuoteWatch connection got it working again.

Edited by Craig on Apr 30, 2014 at 01:57 PM

Craig, there was a network issue with Level 3 near our datacenters (not affecting us directly but affecting network connections coming into our datacenters that go through that hop)around that time today which caused some customers to be unable to maintain connection to our servers. Our logs show that you did get connected long enough to at least authenticate ~20 times today since ~11:36 which indicates that IQConnect was at least trying to connect like it should have been during the outage. Not long before your post, we got a notification that Level3 had replaced some faulty hardware and the hop should have been working again.

As a result, I'm not sure if this is exactly the same issue you reported previously but it is at the very least more information for us to go on in terms of trying to track the issue down.

What should one do with a SERVER DISCONNECTED message?
Do I sit there and wait for IQFeed to reconnect or do I initiate a new physical connection?

You should not need to do anything (unless you told the feed to disconnect). IQConnect is designed to automatically reconnect to the servers as soon as possible and re-watch any symbols you were previously watching.

Ok, will monitor the situation.

Any updates on this?

Hello Craig,

This was fixed prior to Steve's post I think, were you still having issues?

Tim

Hi Tim,
No more issues.
I was referring to the post above "As a result, I'm not sure if this is exactly the same issue you reported previously but it is at the very least more information for us to go on in terms of trying to track the issue down."

Understood, no other issues were reported that day, so I think it is safe to assume the issue was with the hardware between our locations. It could have possibly been a more localized ISP issue, but that seems unlikely given the time of the problem and the time of resolution matching up to that of the reported time frame for the Level 3 outage.

Tim

Cool, Ta.

At approximately 13:00 today, I stopped receiving timestamps.
My application re-connected to IQFeed a number of times, but to no avail, on each re-connect there where no timestamps. I restarted IQFeed and everything started working.
Did something else happen today?

Very quiet today actually, I only show 2 login attempts that reached us today for your ID and both succeeded.

At 12:54:47 I show you reconnected to us
and at
14:47:14 it appears that was where you restarted the software. As to the why, I do not know, since none of the other attempts made it through the cloud to our servers I have no logs to help me explain it and the restart would have cleared any logging that might have been being done on your end.

Tim

What should I do next time to help diagnose the problem?

(Interesting you saw no log-ins, my application tried to log in numerous times, each time I got the start up messages, just no subsequent time stamps).
Edited by Craig on May 16, 2014 at 02:20 PM

I would probably start with your ISP, just given that the signal is not reaching us. Since it is being held up somewhere between you and I they will probably be able to help with that more than us.

You could try contacting our service department though the next time it occurs and they may be able to walk you through some of the troubleshooting steps they use regularly.

Tim

Sorry, I think we posted past each other.
So the IP,CUST,KEYOK etc messages don't come from your server?

That could be coming from the IQConnect App instead of the actual servers, but you could enable logging of the admin in the diagnostics app. If that is turned on, we could verify that the data has actually stopped and the connect method is being called as expected.

Tim

Ok, will do.

So it looks like this is caused by a version compatibility issue or a network problem at DTN.

I am sorry you are having issues, I have replied in your original thread and sent emails in regards to this matter, but given that your issue is unrelated to these posts, (Craig's issue was resolved to my knowledge with a fix in 5.1.3.1), I will be using email primarily going forward. We can report any new issues found in a separate thread so that it is less confusing to others that might benefit from what we find.

Tim