Output spam when executing arcpy functions

[JasonGreenlaw]

I've been working with ArcGIS Server 10.1 beta, prerelease, and now final (Red Hat Enterprise Linux, if that matters) for several months and have noticed the same issue with all three when executing ArcPy functions using the python interpreter packaged with the software (<AGS install dir>/tools/python).

I have an ArcSDE 10.1 Enterprise Geodatabase on top of a PostgreSQL 9.0 database, and whenever I execute an arcpy function that imports data into the geodatabase, e.g.:

arcpy.Append_management(...)

or

arcpy.MosaicToNewRaster_management(...)

...I get many lines of extra output as follows:

...
column number 38 is out of range 0..37
column number 38 is out of range 0..37
column number 38 is out of range 0..37
column number 38 is out of range 0..37
column number 38 is out of range 0..37
column number 38 is out of range 0..37
...

The commands all seem to succeed, so I'm not sure where these messages are coming from. 

Other than using grep or otherwise postprocessing the command output, is there any way to suppress these messages?

[JeffBurton]

I'm seeing the same.
Did you ever sort out what it is?
It's annoying because it causes my except clauses to run when there does not seem to be anything wrong.

[JasonGreenlaw]

No, I never found the cause.  I'm sure it's just internal to arcpy, and perhaps specific to Linux and/or PostgreSQL connections.  As far as I can tell there's no way to suppress it from STDERR. 

It's not as big of an issue for me any more though -- now I'm running all arcpy functions in a new process (using subprocess.check_output) and capturing both STDERR and STDOUT output, which I don't print out unless I'm debugging, so it's hidden from view most of the time.