PQexecPrepared: ERROR: incorrect binary data format in bind parameter 2

[Allan Wind]

***@pawan:~$ /usr/sbin/indexer -Eblob
indexer[11912]: Converting to blob
indexer[11912]: Loading URL list
indexer[11912]: Converting intag00
indexer[11912]: PQexecPrepared: ERROR: incorrect binary data
format in bind parameter 2

and here is the postgres log event:

2010-06-08 04:08:10 UTC ERROR: incorrect binary data format in
bind parameter 2
2010-06-08 04:08:10 UTC STATEMENT: INSERT INTO bdict (word,
secno, intag) VALUES($1, $2::integer, $3)
2010-06-08 04:08:10 UTC LOG: unexpected EOF on client connection

This is with mnogosearch 3.3.8 against postgres 8.4.4. Any
ideas?


/Allan

[Alexander Barkov]

Hi Allan,

Post by Allan Wind
indexer[11912]: Converting to blob
indexer[11912]: Loading URL list
indexer[11912]: Converting intag00
indexer[11912]: PQexecPrepared: ERROR: incorrect binary data
format in bind parameter 2
2010-06-08 04:08:10 UTC ERROR: incorrect binary data format in
bind parameter 2
2010-06-08 04:08:10 UTC STATEMENT: INSERT INTO bdict (word,
secno, intag) VALUES($1, $2::integer, $3)
2010-06-08 04:08:10 UTC LOG: unexpected EOF on client connection
This is with mnogosearch 3.3.8 against postgres 8.4.4. Any
ideas?

Thanks for reporting!

I need some more information:

- What is your OS?

I found this information on
https://fedoraproject.org/wiki/Infrastructure/Search

Post by Allan Wind
On x86_64 architecture, the x86_64 binary fails when indexing a crawl
with the error "indexer[21272]: PQexecPrepared: ERROR: incorrect binary
data format in bind parameter 2." The tarball refuses to cross-compile
to 32-bit architecture, despite tweaking the ./configure options.
Compiling on a 32-bit machine and moving the binaries to the 64-bit
machine works.

Are you using x86_64 binary? If so, can you please try this suggestion?

- What is "indexer -S" output?

- Please add DebugSQL=yes into your DBAddr command, so it looks about
like this:
DBAddr pgsql://root@/dbname/?DebugSQL=yes
or
DBAddr pgsql://root@/dbname/?DBMode=blob&DebugSQL=yes

then run "indexer -Eblob -v6 &>LOG.txt"

and send LOG.txt output to ***@mnogosearch.org.

Thanks!

Post by Allan Wind
/Allan

[King, Stefan]

The raidset didn't survive very well when the drive was pulled,
most of the data was backed up, but not all, natch. I have a mnogosearch
index of all the directories there, which seems to have a pretty good
idea
of what is inside most of the files. (unfortunately, local side cache
directive was turned off :() I am wondering how to get the most
complete
dump possible of a few of the files out of the mnogo database. Any
ideas?

Stefan

[Alexander Barkov]

Hi Stefan,

Post by King, Stefan
The raidset didn't survive very well when the drive was pulled,
most of the data was backed up, but not all, natch. I have a mnogosearch
index of all the directories there, which seems to have a pretty good
idea
of what is inside most of the files. (unfortunately, local side cache
directive was turned off :() I am wondering how to get the most
complete
dump possible of a few of the files out of the mnogo database. Any
ideas?

If you use CachedCopy, then you can try to restore some information.

You need to do:

SELECT sval FROM urlinfo WHERE sname='CachedCopy';

and then process each record in a way similar to what
UdmCachedCopyUnpack() does. See the file store.c in
the mnoGoSearch sources.

Post by King, Stefan
Stefan
---------------------------------------------------------------------

[Allan Wind]

I run Debian Unstable:

***@pawan:~$ cat /etc/debian_version
squeeze/sid

Linux pawan 2.6.33.2 #1 SMP Thu Apr 8 03:28:55 UTC 2010 x86_64
GNU/Linux


/Allan

[Alexander Barkov]

Hi Allan,

I suggest to try this workaround:
https://fedoraproject.org/wiki/Infrastructure/Search

Or please send send the information I requested in the previous e-mail.

Thanks!

Post by Allan Wind
squeeze/sid
Linux pawan 2.6.33.2 #1 SMP Thu Apr 8 03:28:55 UTC 2010 x86_64
GNU/Linux
/Allan

[Allan Wind]

Post by Alexander Barkov
https://fedoraproject.org/wiki/Infrastructure/Search

Unfortunately I do not have a 32 bit machine available to
cross-compile on.

Post by Alexander Barkov
Or please send send the information I requested in the previous e-mail.

Sorry, what information was it that you requested again? I must
have overlooked it.


/Allan

[Alexander Barkov]

Hi,

Post by Allan Wind

Post by Alexander Barkov
https://fedoraproject.org/wiki/Infrastructure/Search

Unfortunately I do not have a 32 bit machine available to
cross-compile on.

Post by Alexander Barkov
Or please send send the information I requested in the previous e-mail.

Sorry, what information was it that you requested again? I must
have overlooked it.
/Allan
- What is your OS?
I found this information on
https://fedoraproject.org/wiki/Infrastructure/Search

Post by Alexander Barkov
On x86_64 architecture, the x86_64 binary fails when indexing a crawl
with the error "indexer[21272]: PQexecPrepared: ERROR: incorrect binary
data format in bind parameter 2." The tarball refuses to cross-compile
to 32-bit architecture, despite tweaking the ./configure options.
Compiling on a 32-bit machine and moving the binaries to the 64-bit
machine works.

Are you using x86_64 binary? If so, can you please try this suggestion?
- What is "indexer -S" output?
- Please add DebugSQL=yes into your DBAddr command, so it looks about
or
then run "indexer -Eblob -v6 &>LOG.txt"

[Allan Wind]

Hi Alexander,

Thanks again for your help and patience.

Post by Alexander Barkov
- What is your OS?

Debian Linux (unstable)

***@pawan:~$ cat /etc/debian_version
squeeze/sid

***@pawan:~$ uname -a
Linux pawan 2.6.33.2 #1 SMP Thu Apr 8 03:28:55 UTC 2010 x86_64
GNU/Linux

Post by Alexander Barkov
Are you using x86_64 binary? If so, can you please try this suggestion?

Yes:

***@pawan:/home/allan# file /usr/sbin/indexer
/usr/sbin/indexer: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked (uses shared libs), for GNU/Linux
2.6.18, stripped

Post by Alexander Barkov
- What is "indexer -S" output?

# indexer -Edrop
# indexer -Ecreate
# indexer -Eblob
...
indexer[10207]: Converting to blob
indexer[10207]: Loading URL list
indexer[10207]: Converting intag00
indexer[10207]: Converting intag01
indexer[10207]: Converting intag02
indexer[10207]: Converting intag03
indexer[10207]: Converting intag04
indexer[10207]: Converting intag05
indexer[10207]: Converting intag06
indexer[10207]: Converting intag07
indexer[10207]: Converting intag08
indexer[10207]: Converting intag09
indexer[10207]: Converting intag0A
indexer[10207]: Converting intag0B
indexer[10207]: Converting intag0C
indexer[10207]: Converting intag0D
indexer[10207]: Converting intag0E
indexer[10207]: Converting intag0F
indexer[10207]: Converting intag10
indexer[10207]: Converting intag11
indexer[10207]: Converting intag12
indexer[10207]: Converting intag13
indexer[10207]: Converting intag14
indexer[10207]: Converting intag15
indexer[10207]: Converting intag16
indexer[10207]: Converting intag17
indexer[10207]: Converting intag18
indexer[10207]: Converting intag19
indexer[10207]: Converting intag1A
indexer[10207]: Converting intag1B
indexer[10207]: Converting intag1C
indexer[10207]: Converting intag1D
indexer[10207]: Converting intag1E
indexer[10207]: Converting intag1F
indexer[10207]: Total converted: 0 records, 0 bytes
indexer[10207]: PQexecPrepared: ERROR: incorrect binary data format in bind parameter 2
# indexer -S
***@pawan:/home/allan# indexer -S

Database statistics [2010-06-25 12:11:56]

Status Expired Total
-----------------------------
-----------------------------
Total 0 0

Post by Alexander Barkov
- Please add DebugSQL=yes into your DBAddr command, so it looks about
or

Did the latter.

Post by Alexander Barkov
then run "indexer -Eblob -v6 &>LOG.txt"

It does not look that interesting but I will send that off in a sec:

indexer[10262]: Writting '#ts'
indexer[10262]: PQexecPrepared: ERROR: incorrect binary data format in bind parameter 2


/Allan

[Alexander Barkov]

Hi Allan,

Post by Allan Wind
Hi Alexander,
Thanks again for your help and patience.

Thank you for your patience too.

Post by Allan Wind

Post by Alexander Barkov
- What is your OS?

Debian Linux (unstable)
squeeze/sid
Linux pawan 2.6.33.2 #1 SMP Thu Apr 8 03:28:55 UTC 2010 x86_64
GNU/Linux

Post by Alexander Barkov
Are you using x86_64 binary? If so, can you please try this suggestion?

/usr/sbin/indexer: ELF 64-bit LSB executable, x86-64, version 1
(SYSV), dynamically linked (uses shared libs), for GNU/Linux
2.6.18, stripped

Post by Alexander Barkov
- What is "indexer -S" output?

# indexer -Edrop
# indexer -Ecreate
# indexer -Eblob
...
indexer[10207]: Converting to blob
indexer[10207]: Loading URL list
indexer[10207]: Converting intag00
indexer[10207]: Converting intag01
indexer[10207]: Converting intag02
indexer[10207]: Converting intag03
indexer[10207]: Converting intag04
indexer[10207]: Converting intag05
indexer[10207]: Converting intag06
indexer[10207]: Converting intag07
indexer[10207]: Converting intag08
indexer[10207]: Converting intag09
indexer[10207]: Converting intag0A
indexer[10207]: Converting intag0B
indexer[10207]: Converting intag0C
indexer[10207]: Converting intag0D
indexer[10207]: Converting intag0E
indexer[10207]: Converting intag0F
indexer[10207]: Converting intag10
indexer[10207]: Converting intag11
indexer[10207]: Converting intag12
indexer[10207]: Converting intag13
indexer[10207]: Converting intag14
indexer[10207]: Converting intag15
indexer[10207]: Converting intag16
indexer[10207]: Converting intag17
indexer[10207]: Converting intag18
indexer[10207]: Converting intag19
indexer[10207]: Converting intag1A
indexer[10207]: Converting intag1B
indexer[10207]: Converting intag1C
indexer[10207]: Converting intag1D
indexer[10207]: Converting intag1E
indexer[10207]: Converting intag1F
indexer[10207]: Total converted: 0 records, 0 bytes
indexer[10207]: PQexecPrepared: ERROR: incorrect binary data format in bind parameter 2
# indexer -S
Database statistics [2010-06-25 12:11:56]
Status Expired Total
-----------------------------
-----------------------------
Total 0 0

Post by Alexander Barkov
- Please add DebugSQL=yes into your DBAddr command, so it looks about
or

Did the latter.

Post by Alexander Barkov
then run "indexer -Eblob -v6 &>LOG.txt"

indexer[10262]: Writting '#ts'
indexer[10262]: PQexecPrepared: ERROR: incorrect binary data format in bind parameter 2

Can you please rebuild mnogosearch with additional --with-debug flag to
configure?

So the new build commands will look about like this:
./configure --with-pgsql --with-debug
make
make install


Then please run "indexer -Eblob -v6 &>LOG.txt" again,
it will print all SQL queries to the LOG file,
so we'll see which query generates this error.


I think this is a small bug which will be easy to fix.

Thanks!

Post by Allan Wind
/Allan