It seems like this is possible based on the threads I've read from others but for some reason I'm not having any luck. On the GUI side of things, everything looks fine, but nothing seems to actually connect. The logs seem to support this since it looks like it connects successfully but then immediately complains no clients are connected and begins shutting down. Again, there is no sign of this in the GUI of Diagnostics.exe which will just hang indefinitely without throwing errors or crashing.

It seems like there is a ping issue though since the logs end with "Ping failed: Error: 11010 - Unknown Error."

The machine is a DigitalOcean VPS running Ubuntu 14.04 x64

Any guidance on what sort of black magic I need to use or incantations to mutter while running commands to make this work would be greatly appreciated

Results from traceroute in Diagnostics.exe:

login.interquote.com
Trace route to 66.112.156.213
Hop Min RTT Avg RTT Max RTT IP
1 * * * Error:11010
2 * * * Error:11010
3 * * * Error:11010
4 * * * Error:11010
5 * * * Error:11010
6 * * * Error:11010
7 47 ms 47 ms 47 ms 66.112.156.213


login2.paragonsoftware.net
Trace route to 66.112.148.213
Hop Min RTT Avg RTT Max RTT IP
1 * * * Error:11010
2 * * * Error:11010
3 * * * Error:11010
4 * * * Error:11010
5 * * * Error:11010
6 * * * Error:11010
7 * * * Error:11010
8 * * * Error:11010
9 * * * Error:11010
10 * * * Error:11010
11 * * * Error:11010
12 * * * Error:11010
13 49 ms 49 ms 50 ms 66.112.148.213

Results from ping in Diagnositics.exe:

Pinging login.interquote.com [66.112.156.210] with 32 bytes of data:

Reply from 66.112.156.210: bytes=4 time=48ms TTL=53
Reply from 66.112.156.210: bytes=4 time=48ms TTL=53
Reply from 66.112.156.210: bytes=4 time=48ms TTL=53
Reply from 66.112.156.210: bytes=4 time=52ms TTL=53

Ping statistics for 66.112.156.210:
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 52ms, Average = 49ms


Pinging login2.paragonsoftware.net [66.112.148.210] with 32 bytes of data:

Reply from 66.112.148.210: bytes=4 time=50ms TTL=49
Reply from 66.112.148.210: bytes=4 time=50ms TTL=49
Reply from 66.112.148.210: bytes=4 time=50ms TTL=49
Reply from 66.112.148.210: bytes=4 time=50ms TTL=49

Ping statistics for 66.112.148.210:
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 50ms, Average = 50ms

Hello,

When IQConnect starts up it waits for 30 seconds and if no connections are received it will then close itself. If you look at the launching the feed apps, it will show an example of how you connect to the admin socket to keep the app open while you do other functions.

Once any connection to IQFeed is made, the feed will close itself 5 seconds after the last socket is closed. So, I would just open the admin socket and leave that there for the duration of your apps run. The ping being blocked seems normal in WINE builds by default.

Tim

So when running in wine it's normal that the diagnostics don't actually run?

On WINE, with current IQFeed versions, yes. Much of the diagnostics was designed using a COM interface that WINE does not support. We are looking to remove the pieces in a nearby release to improve this.

Tim

Check out the thread below. I had a similar problem and I found a solution. It may not work but it might be related.

http://forums.dtn.com/index.cfm?page=topic&topicID=4195