programmer has contributed to 35 posts out of 19808 total posts
(0.18%) in 3,892 days (0.01 posts per day).
20 Most recent posts:
After digging in to it, that error is actually one of my internal errors and kind of generic (ie. it can be caused by a number of things). I'm not sure what the IQ client is returning but I am running the latest now 18.104.22.168.
I'm still investigating this. I have a lot of things I need to upgrade including the OS. I managed to get some history pulls yesterday without errors so it obviously CAN work. I'm thinking the problem is probably on my side. Though I'm not sure why this started all of a sudden. Anyway, I'm going to rework some of my code making that error less generic so I can see was is going on in case this happens again.
Thanks for the help!
Thanks for checking. Seems to be working fine now during the day but I just updated from 22.214.171.124 to 126.96.36.199 so I'll see how that goes tonight too.
Looking at version 188.8.131.52 I see: Added support for 64bit (8+ decimals) precision prices in streaming (Level 1) data and History data (as soon as the history servers support rolls out).
Any chance the history servers updated to this new 64bit precision on March 14?
Just trying to figure out what happened. I'll keep testing to make sure the problem is not on my side.
On March 14 all of a sudden I'm getting a lot of "Invalid symbol" errors. For example pulling history for "APPS" returns invalid symbol even though it's not. I'm not sure if they're all NASDAQ but many of them seem to be.
Maybe I need to update my IQFeed client because I think I'm out of date or maybe my machine has been corrupted.
I'm looking in to the issue on my side but figured I would post to ask if something changed.
Looks good. I tried at about 6:45 AM and it was still corrupt which is why I posted but I assume the zip rebuild must be some time later than that. Anyway, it's fixed now. Thanks!
It seems like as of yesterday the symbols archive has been corrupted (ie. invalid zip file). I was hoping it would get fixed when it was rebuilt for today but that doesn't appear to be the case.
I'm talking about the list here:
I'm talking about the list here:
It used to be updated every day but for months it has only been sporadically updated. It currently hasn't been updated since March 17.
Is there a better way to get this list?
*** deleted original message ***
Never mind. I was using IQLink to start IQFeed and apparently you need to use whatever "validated" software (from the list) to start IQFeed.
I think I made a note about this a long time ago but since lost it. I'll make another again so I don't forget.
Edited by programmer on Mar 12, 2016 at 12:11 AM
Just thought I would note that it's easy to recreate the memory leak simply by connecting to any iqfeed socket then disconnect (no command need to be executed). Do it several thousand times and watch the memory usage grow.
Edited by programmer on May 29, 2013 at 08:07 AM
Quote: The one theme I've seen between all of your scenarios is that you are making multiple connections to the feed (not simply maintaining a single connection and making multiple requests). Is this accurate?
That is true for me. It seems to leak around 200 bytes per connection. Not so much by itself but over a long enough time the iqconnect.exe process causes the machine to run out of RAM and I get the out of memory error.
Edited by programmer on May 28, 2013 at 01:59 PM
I'm getting this error too and I'm not making lots of simultaneous socket connections. It seems that over time iqconnect.exe uses more and more memory until it consumes all memory on the machine. If you make a lot of connections for example to pull historical data (NOT simultaneous connections; just sequential) it will use up memory faster.
I believe there is some sort of memory leak in the 184.108.40.206 version of iqconnect.exe.
I think I may have it working. It could be because my filesystem was corrupted. I tried again on a fresh install and now it seems to survive the reboot.
However, it does not seem to work unless you install IQ 4.7 at least once. I'm guessing because a dll (IQ32.dll?) or other components needs to be registered or configured and just copying over IQ32.dll is not enough on a clean new system that never had 4.7 installed.
But like I said, it seems to work right now. Sorry for the noise. Thanks!
What are these "usage statistics" reported with the newer versions of IQFeed?
I apologize if I seem alarmist but you have to understand that I don't like anything that could possibly affect my trading and I definitely don't like software that spies on my system. What is it reporting exactly and why? Can I disable it? "Anonymous" reporting is not an answer because an IP address is usually enough information to connect a user to "statistics".
I'm finding that it still doesn't work. I tried a fresh install of IQFeed 4.9 and QT, copied the IQ32.dll over to the IQFeed install directory. I then start QuoteTracker and it immediately sends me to their "How to install IQFeed" page. QuoteTracker is not able to start or connect to IQFeed.
I then install IQFeed 4.7 and everything works normally. Then I re-installed IQ 4.9 and now 4.9 works with QuoteTracker. Then I reboot and now QuoteTracker no longer works with IQFeed 4.9
This doesn't seem to work very well and is the reason I have been avoiding anything newer than IQFeed 4.7.
OK thanks. If that's the way it would show up in the live stream then I'll just leave it as is.
I was looking through some of the raw data in the platform I use and I noticed that sometimes (fairly rarely) that some of my backfill data has ticks with timestamps that are out of order. For example:
2011-07-11 15:58:34,1315.00,4573299 <-- tick id
You can see the third tick from the bottom has a timestamp that is out of order. The tick ID seems to suggest that the timestamp is incorrect (either that or the tick id is incorrect). I refreshed the data and it stays the same so I believe it's stored on the server this way. It doesn't happen too often but it always happens the same way with the timestamp slightly off but the tick id is in order.
Even though it seems to not happen often, I'm a bit fanatical about having accurate data so I'm wondering if I should manually correct the timestamp or move the ticks to their correct position in the stream?
Edited by programmer on Jul 31, 2011 at 09:25 PM
Yes I have been noticing this as well. It takes more than twice as long as it used to which seems to match up with what you are seeing.
I think it's just a bug in the platform that was introduced with recent updates. I was able to recreate the problem just with last weeks data and it seemed somewhat random.
Sorry for the noise but I think everything is working fine (or will be once they fix it ).
I suppose it could be a bug in the platform. It seems like mostly older dates (a week or two ago) when pulled from historical data.
I'll have to wait till the end of the day so I can pull ticks that old, then I'll try refreshing from a fresh install of the platform and see how that goes. I'm just requesting one symbol at a time. I'm not sure what request the platform uses but I can find out.
I have never seen this before so that's why I was thinking it might be the data itself but now I don't know.
Edited by programmer on Aug 18, 2010 at 11:26 AM
I'm looking at tick data on the @ES# instrument and I'm seeing all sorts of bad data. It may not be just that symbol, it's the only one I have looked at.
Some ticks have dates with bad years like 22010-MM-DD, 202010-MM-DD, 2012010-MM-DD, and 20102010-MM-DD.
I'm also seeing some ticks with an incorrect number of fields like:
That tick has an extra field that shouldn't be there (looks like the volume got duplicated or something).
OK thanks, that link has a lot more useful information in it!
The only thing missing as far as I'm concerned is a comprehensive explanation of "dollar volume." (ie. those symbols that have "$ VOL" in the description)