Thread failure "too many open files" about cdat_info HOT 19 CLOSED

@doutriaux1 Yes, we discussed this last week actually and Ghaleb agreed we should go ahead and remove the logging at this time. I'm looking into removing it

from cdat_info.

ouch... I'll take a look right away. What were you doing?

from cdat_info.

Mutli-linear regression, but using numpy. It is not clear exactly where in the code the error is being generated.

from cdat_info.

do you mind sending me the python code? By email if you don't feel comfortable posting it here.

from cdat_info.

I don't get the error when I switch back to cdat version 2.8

from cdat_info.

yes this bz2 cache thing as been introduced in 2.10

from cdat_info.

Just curious if there are any updates on this? It is preventing me from using the latest version!

from cdat_info.

I'll take a look either today or tomorrow.

from cdat_info.

@mzelinka @doutriaux1 @dnadeau4 @pochedls just wondering what happened with this back in Feb?

from cdat_info.

I have some code in cdat82 that is producing this error (on f = cdms2.open). I believe I am closing all the file handles I open (after reading in the data).

from cdat_info.

@pochedls the cdat_info reference means that some weird logging thing with CDAT is likely causing your issue, if you make sure to set logging to off then this might fix you

from cdat_info.

@muryanto1 @downiec pinging you both as this is a nasty little bug that would benefit from a fix

from cdat_info.

Does UVCDAT_ANONYMOUS_LOG='no' in my bash profile still turn off logging?

from cdat_info.

@pochedls theoretically yes

from cdat_info.

@muryanto1 @downiec Dean really wanted the logging for statisictics purposes. But the server is pretty much broken (and might down Chris Mauzey would know) so it's probably safe to remove this. Double check with Ghaleb though. At least turn it off by default for now.

from cdat_info.

@downiec to be honest I have hit my head against this many times, so removing it altogether is going to prevent a bunch of weird behaviors that slow down or make code bomb - two thumbs up for trim down

from cdat_info.

Marking issue as stale, since there has been no activity in 30 days.

Unless the issue is updated or the 'stale' tag is removed, this issue will be closed in 7 days.

from cdat_info.

I believe this was resolved in the 8.2.1 release by #2 - so a candidate for closure

@downiec

from cdat_info.

@durack1 That's correct anonymous logging was removed, seems like the culprit. Closing as this should not be fixed.

from cdat_info.