gmail sent the previous mail by itself ...

I'm pretty sure that the problem is about escaped text, how backslash
is handled.
I patched EscapeString in 1.2.1 from newer version. However, for some
reason the
patched pkgagent cannot connect to database. The issue is that the
original version
is installed from deb package. I compiled the patched agent in the
virtual environment
from where I copied pkgagent. I have changed PREFIX to PREFIX=/usr
which I think should be correct PREFIX. I've tried to cross cheks
location of all conf files, agents etc and there seem to be no
differences between the virtual server and real server.
But the new pkgagent cannot connect to database. So obviously
there must be some differences how the original
1.2.1 deb package was compiled and how I compile patched 1.2.1 for debian.
What are the differences between makefiles between deb packages and
the default Makefiles? What else could cause the db access problem?

Thanks
Raino

2010/11/17 Bob Gobeille <bob.gobei...@hp.com>:
>
> On Nov 17, 2010, at 7:58 AM, Raino Lintulampi wrote:
>>
>> doing that extremely slow. After two days pkgagent has handled about
>> 40.000 items.
>>
>> Any idea why the situation is now different (it shouldn't be)? And why
>> the execution
>> of pkgagent is so slow?
>
> Hi Raino,
> I've seen this before but don't recall the fix.  There has only been one fix 
> to pkgagent since the 1.2.1 release.  This was a fix for improperly escaped 
> text being written to the database.  If that's the problem, look in 
> fossology.log and you will see errors from pkgagent.
>
> To diagnose:
> 1) look in fossology.log (/var/log/fossology/fossology.log) for errors.
>
> 2) look in the postgresql log file 
> (/var/log/postgresql/postgresql-8.3-main.log - note you may have to replace 
> the version number if you aren't running 8.3)
>
> Usually, those will give us a hint or show the error.
>
> Bob
_______________________________________________
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Reply via email to