Problem with indexer -Eblob

Discussion:

d***@hodei.net

2014-03-13 16:51:24 UTC

hi
when i try this command, i have an error message : mysql_stmt_execute()
failed: Lost connection to MySQL server during query

here is the result of my command :
------------------------------------------------------------------------------------------------------------------------------------------------------
***@bot:/usr/local/mnogosearch/sbin# ./indexer -Eblob
/usr/local/mnogosearch/etc/indexer.conf
indexer[22039]: Indexing
indexer[22039]: Loading URL list
indexer[22039]: Converting intag00
indexer[22039]: Converting intag01
indexer[22039]: Converting intag02
indexer[22039]: Converting intag03
indexer[22039]: Converting intag04
indexer[22039]: Converting intag05
indexer[22039]: Converting intag06
indexer[22039]: Converting intag07
indexer[22039]: Converting intag08
indexer[22039]: Converting intag09
indexer[22039]: Converting intag0A
indexer[22039]: Converting intag0B
indexer[22039]: Converting intag0C
indexer[22039]: Converting intag0D
indexer[22039]: Converting intag0E
indexer[22039]: Converting intag0F
indexer[22039]: Converting intag10
indexer[22039]: Converting intag11
indexer[22039]: Converting intag12
indexer[22039]: Converting intag13
indexer[22039]: Converting intag14
indexer[22039]: Converting intag15
indexer[22039]: Converting intag16
indexer[22039]: Converting intag17
indexer[22039]: Converting intag18
indexer[22039]: Converting intag19
indexer[22039]: Converting intag1A
indexer[22039]: Converting intag1B
indexer[22039]: Converting intag1C
indexer[22039]: Converting intag1D
indexer[22039]: Converting intag1E
indexer[22039]: Converting intag1F
indexer[22039]: Total converted: 32554167 records, 78081117 bytes
indexer[22039]: Converting url data
indexer[22039]: mysql_stmt_execute() failed: Lost connection to MySQL
server during query
------------------------------------------------------------------------------------------------------------------------------------------------------

have you an idea?

--------------------
my config :

Debian 3.2.51-1 x86_64 GNU/Linux
mnogosearch 3.3.15

---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active.
http://www.avast.com

Alexander Barkov

2014-03-18 02:18:13 UTC

Permalink

Hi,

Post by d***@hodei.net
hi
when i try this command, i have an error message : mysql_stmt_execute()
failed: Lost connection to MySQL server during query
------------------------------------------------------------------------------------------------------------------------------------------------------
/usr/local/mnogosearch/etc/indexer.conf
indexer[22039]: Indexing
indexer[22039]: Loading URL list
indexer[22039]: Converting intag00
indexer[22039]: Converting intag01
indexer[22039]: Converting intag02
indexer[22039]: Converting intag03
indexer[22039]: Converting intag04
indexer[22039]: Converting intag05
indexer[22039]: Converting intag06
indexer[22039]: Converting intag07
indexer[22039]: Converting intag08
indexer[22039]: Converting intag09
indexer[22039]: Converting intag0A
indexer[22039]: Converting intag0B
indexer[22039]: Converting intag0C
indexer[22039]: Converting intag0D
indexer[22039]: Converting intag0E
indexer[22039]: Converting intag0F
indexer[22039]: Converting intag10
indexer[22039]: Converting intag11
indexer[22039]: Converting intag12
indexer[22039]: Converting intag13
indexer[22039]: Converting intag14
indexer[22039]: Converting intag15
indexer[22039]: Converting intag16
indexer[22039]: Converting intag17
indexer[22039]: Converting intag18
indexer[22039]: Converting intag19
indexer[22039]: Converting intag1A
indexer[22039]: Converting intag1B
indexer[22039]: Converting intag1C
indexer[22039]: Converting intag1D
indexer[22039]: Converting intag1E
indexer[22039]: Converting intag1F
indexer[22039]: Total converted: 32554167 records, 78081117 bytes
indexer[22039]: Converting url data
indexer[22039]: mysql_stmt_execute() failed: Lost connection to MySQL
server during query
------------------------------------------------------------------------------------------------------------------------------------------------------
have you an idea?

Try this:

select @@max_allowed_packet;

If the maximum packet size is small enough, try to increase it in
the server side.

If this does not help, then compile mnogoseearch again by adding
--with-debug to the configure command line,
then add "DebugSQL=yes" parameter into DBAddr, like this:

DBAddr mysql://***@localhost/test/?DebugSQL=yes

and run "indexer -Eblob 2>LOG.txt".

It will print all SQL queries to the log file.
Check the last few lines in the log.

Post by d***@hodei.net
--------------------
Debian 3.2.51-1 x86_64 GNU/Linux
mnogosearch 3.3.15
---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant
parce que la protection avast! Antivirus est active.
http://www.avast.com
_______________________________________________
General mailing list
http://lists.mnogosearch.org/listinfo/general

d***@hodei.net

2014-03-18 11:07:59 UTC

Permalink

Hi
Thanks for your help
If i take select @@max_allowed_packet;
i have this result :

+----------------------+
| @@max_allowed_packet |
+----------------------+
| 16777216 |
+----------------------+
1 row in set (0.00 sec)

So, after i have recompile mnogoseearch 3.3.15 by adding --with-debug
i have run make and make install
i have add DebugSQL=yes in indexer.conf at the end of line DBAddr
mysql://root:***@localhost/test/?dbmode=blob&DebugSQL=yes
and i have run indexer -Eblob 2>LOG.txt
the message in LOG.txt is :
----------------------------------------------
indexer[13250]: Indexing
indexer[13250]: Loading URL list
----------------------------------------------

the process terminated on the console by 'Killed' message

i do not understand nothing ?
is my databases corrupted ?
can you help me ?

Post by Alexander Barkov
Hi,

If the maximum packet size is small enough, try to increase it in
the server side.
If this does not help, then compile mnogoseearch again by adding
--with-debug to the configure command line,
and run "indexer -Eblob 2>LOG.txt".
It will print all SQL queries to the log file.
Check the last few lines in the log.

---
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active.
http://www.avast.com