[OpenSIPS-Users] debuild error on MediaProxy 2.3.4

Dan Pascu dan at ag-projects.com
Tue Jun 2 10:45:07 CEST 2009


On 2 Jun 2009, at 10:33, Dan Pascu wrote:

> On 2 Jun 2009, at 00:41, Dan Pascu wrote:
>
>>
>> On 1 Jun 2009, at 16:11, Jeff Pyle wrote:
>>
>>> Dan,
>>>
>>> It did not exit cleanly:
>>>
>>> # python -c "from mediaproxy.interfaces.system import _conntrack"
>>> Traceback (most recent call last):
>>> File "<string>", line 1, in <module>
>>> ImportError: cannot import name _conntrack
>>>
>>>
>>
>> I do not know what the matter is. The file is there and python has
>> its directory in the path, so it should be able to find it. Maybe it
>> has troubles loading it. Was it built using the same version of
>> python?
>
> There's another thing that comes to mind. Maybe there is more than one
> _conntrack.so module on your disk and it tries to load the wrong one.
> Try using locate _conntrack.so or find / -name _conntrack.so to see if
> it comes up with more than one result.


And a third thing, do you happen to try to start/run it from the  
source directory, where you built it? Because if so, it will find the  
mediaproxy package in that directory before the one that was installed  
by the debian package, however the one in the source directory doesn't  
have _conntrack.so in the right place (or at all), so it's not found.  
This problem should be easy to spot. Run the following commands and  
watch the output. The first one will tell you from where it imports  
the mediaproxy module. The second one will tell you if there is a  
_conntrack.so file in that place:

$ python -c "import sys, mediaproxy; print sys.modules['mediaproxy']"
<module 'mediaproxy' from '/var/lib/python-support/python2.5/ 
mediaproxy/__init__.pyc'>
$ ls /var/lib/python-support/python2.5/mediaproxy/interfaces/system/
__init__.py  __init__.pyc  _conntrack.so
$

--
Dan






More information about the Users mailing list