Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Does not work correctly with HeidiSQL #1161

Closed
Panda58dev opened this issue Jun 8, 2023 · 15 comments
Closed

Does not work correctly with HeidiSQL #1161

Panda58dev opened this issue Jun 8, 2023 · 15 comments
Labels
waiting Waiting for the original poster (in most cases) or something else

Comments

@Panda58dev
Copy link

Panda58dev commented Jun 8, 2023 •
edited by githubmanticore
Loading

Describe the bug
When connecting HeidiSQL (version 12.4.0.6659) to Manticore (dev version), it is not possible to see the list of tables, because when reading the schema, some errors are displayed (in the screenshot).
image

To Reproduce
Steps to reproduce the behavior:

  1. Connect via HeidiSQL to Manticore, via the MariaDB driver.
  2. Try to open the database.

Expected behavior
Throws a mistake

Describe the environment:

  • Manticore version dev (docker);
  • Windows 10 WSL;
@tomatolog
Copy link
Contributor

could you provide dockerized case where DB and connection to Manticore is set?

@sanikolaev
Copy link
Collaborator

I can see a few old images https://hub.docker.com/search?q=heidisql

@sanikolaev
Copy link
Collaborator

Try version 6.2.0. Should be fixed there. Feel free to reopen if the issue persists.

@zhdanau
Copy link

zhdanau commented Aug 5, 2023

Still not work (6.2.0)
image

image

@zhdanau
Copy link

zhdanau commented Aug 5, 2023

Please, re-open this issue.

@sanikolaev sanikolaev reopened this Aug 5, 2023
@sanikolaev
Copy link
Collaborator

Please share /var/log/manticore/searchd.log

@zhdanau
Copy link

zhdanau commented Aug 5, 2023

Nothing about this issue in /var/log/manticore/searchd.log Almost empty.

Only these logs from HeidiSQL maybe useful:

/* [11:28:55.920] SSH: Using username "root". */
[11:29:00.125] SELECT CONNECTION_ID();
[11:29:00.538] SHOW VARIABLES;
/* [11:29:00.732] Characterset: utf8mb4 */
[11:29:01.030] SHOW /*!50002 GLOBAL */ STATUS;
[11:29:01.397] SELECT NOW();
/* [11:29:01.557] Connected. Thread-ID: 144 */
/* [11:29:01.557] Reading function definitions from C:\Program Files\HeidiSQL\functions-mysql.ini */
[11:29:01.714] SHOW TABLES FROM `information_schema`;
/* [11:29:01.871] SQL Error (1064): P01: syntax error, unexpected FROM, expecting $end near 'FROM `information_schema`' */
[11:29:02.027] SHOW OPEN TABLES FROM Manticore WHERE `in_use`!=0;
/* [11:29:02.199] SQL Error (1064): P01: syntax error, unexpected identifier, expecting VARIABLES near 'OPEN TABLES FROM Manticore WHERE `in_use`!=0' */
[11:29:02.344] USE `Manticore`;
/* [11:29:02.502] Entering session "manticore" */
[11:29:02.686] SELECT `DEFAULT_COLLATION_NAME` FROM `information_schema`.`SCHEMATA` WHERE `SCHEMA_NAME`='Manticore';
/* [11:29:02.841] SQL Error (1064): P01: syntax error, unexpected BACKTICKED_SUBKEY, expecting $end near '.`SCHEMATA` WHERE `SCHEMA_NAME`='Manticore'' */
[11:29:03.000] SHOW TABLE STATUS FROM `Manticore`;
/* [11:29:03.158] SQL Error (1064): P01: syntax error, unexpected FROM, expecting $end near 'FROM `Manticore`' */
[11:29:03.316] SHOW FUNCTION STATUS WHERE `Db`='Manticore';
/* [11:29:03.475] SQL Error (1064): P01: syntax error, unexpected identifier, expecting VARIABLES near 'FUNCTION STATUS WHERE `Db`='Manticore'' */
[11:29:03.622] SHOW PROCEDURE STATUS WHERE `Db`='Manticore';
/* [11:29:03.780] SQL Error (1064): P01: syntax error, unexpected identifier, expecting VARIABLES near 'PROCEDURE STATUS WHERE `Db`='Manticore'' */
[11:29:03.937] SHOW TRIGGERS FROM `Manticore`;
/* [11:29:04.095] SQL Error (1064): P01: syntax error, unexpected identifier, expecting VARIABLES near 'TRIGGERS FROM `Manticore`' */
[11:29:04.253] SELECT *, EVENT_SCHEMA AS `Db`, EVENT_NAME AS `Name` FROM information_schema.`EVENTS` WHERE `EVENT_SCHEMA`='Manticore';
/* [11:29:04.411] SQL Error (1064): P01: syntax error, unexpected BACKTICKED_SUBKEY, expecting $end near '.`EVENTS` WHERE `EVENT_SCHEMA`='Manticore'' */
[11:29:04.574] SHOW EVENTS FROM `Manticore`;
/* [11:29:04.732] SQL Error (1064): P01: syntax error, unexpected identifier, expecting VARIABLES near 'EVENTS FROM `Manticore`' */

@sanikolaev
Copy link
Collaborator

Please share more from the log or just attach the full log. It's important to figure out if Buddy is working or not.

@sanikolaev sanikolaev added the waiting Waiting for the original poster (in most cases) or something else label Aug 5, 2023
@zhdanau
Copy link

zhdanau commented Aug 5, 2023 

[Sat Aug  5 08:39:33.841 2023] [5191] watchdog: main process 5192 forked ok
[Sat Aug  5 08:39:33.842 2023] [5192] starting daemon version '6.2.0 45680f95d@230804' ...
[Sat Aug  5 08:39:33.842 2023] [5192] listening on 127.0.0.1:9306 for mysql
[Sat Aug  5 08:39:33.909 2023] [5195] WARNING: secondary library not loaded; secondary index(es) disabled
[Sat Aug  5 08:39:34.037 2023] [5193] last message repeated 5 times
[Sat Aug  5 08:39:34.037 2023] [5193] prereading 6 tables
[Sat Aug  5 08:39:34.070 2023] [5192] WARNING: [BUDDY] no manticore-buddy/bin/manticore-buddy found at '/usr/share/manticore/modules/manticore-buddy/bin/manticore-buddy', disabled
[Sat Aug  5 08:39:34.070 2023] [5192] accepting connections
[Sat Aug  5 08:39:34.835 2023] [5193] preread 6 tables in 0.798 sec

@tomatolog
Copy link
Contributor

the warning said buddy did not start

Could you install all packages (Buddy\extra and maybe MCL) as described at the manual https://manual.manticoresearch.com/Installation/Debian_and_Ubuntu#APT-repository

@zhdanau
Copy link

zhdanau commented Aug 5, 2023

Sorry, but I don't need a Buddy: https://github.com/manticoresoftware/manticoresearch-buddy

Buddy is written in PHP...

It's just that I won't be using HeidiSQL with Manticore :) It's better, than Buddy, I think.

@tomatolog
Copy link
Contributor

tomatolog commented Aug 5, 2023 •
edited
Loading

as it said at the manual https://manual.manticoresearch.com/Introduction#The-benefits-of-C++-and-the-convenience-of-PHP

is utilized for high-level functionality that does not require lightning-fast response times or extremely high processing power

you could check that buddy works for your case and create the ticket to move that functionality into manticoresearch core or move related code on you own by creating PR in the main repository

@zhdanau
Copy link

zhdanau commented Aug 5, 2023

Ok. One moment. I see many errors in log (and they are coming every second), but search works fine:

[Sat Aug  5 12:25:08.413 2023] [27667] WARNING: conn (local)(910), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:08.413 2023] [27667] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:08.719 2023] [27664] WARNING: conn (local)(913), sock=66: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:08.719 2023] [27664] WARNING: send() failed: 32: Broken pipe, sock=66
[Sat Aug  5 12:25:24.864 2023] [27668] WARNING: conn (local)(1013), sock=66: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:24.864 2023] [27668] WARNING: send() failed: 32: Broken pipe, sock=66
[Sat Aug  5 12:25:25.259 2023] [27664] WARNING: conn (local)(1014), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:25.259 2023] [27664] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:30.707 2023] [27665] WARNING: conn (local)(1055), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:30.707 2023] [27665] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:31.170 2023] [27669] WARNING: conn (local)(1056), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:31.170 2023] [27669] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:32.074 2023] [27671] WARNING: conn (local)(1058), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:32.074 2023] [27671] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:32.361 2023] [27669] WARNING: conn (local)(1059), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:32.361 2023] [27669] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:32.489 2023] [27666] WARNING: conn (local)(1060), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:32.489 2023] [27666] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:32.786 2023] [27666] WARNING: conn (local)(1061), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 32 (Broken pipe) return -1
[Sat Aug  5 12:25:32.786 2023] [27666] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:32.800 2023] [27671] WARNING: conn (local)(1062), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:32.800 2023] [27671] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:32.821 2023] [27670] WARNING: conn (local)(1063), sock=66: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:32.821 2023] [27670] WARNING: send() failed: 32: Broken pipe, sock=66
[Sat Aug  5 12:25:33.025 2023] [27669] WARNING: conn (local)(1064), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:33.025 2023] [27669] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:33.475 2023] [27670] WARNING: conn (local)(1065), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 32 (Broken pipe) return -1
[Sat Aug  5 12:25:33.475 2023] [27670] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:33.485 2023] [27670] WARNING: conn (local)(1066), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 32 (Broken pipe) return -1
[Sat Aug  5 12:25:33.485 2023] [27670] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:33.761 2023] [27667] WARNING: conn (local)(1067), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1
[Sat Aug  5 12:25:33.761 2023] [27667] WARNING: send() failed: 32: Broken pipe, sock=38
[Sat Aug  5 12:25:34.085 2023] [27664] WARNING: conn (local)(1068), sock=38: bailing on failed MySQL header, AsyncNetInputBuffer_c::AppendData: error 11 (Resource temporarily unavailable) return -1

@tomatolog
Copy link
Contributor

what warning means that client does not properly close mysql session with mysql quit command or other client does not properly close the session but just closes socket backing current session

Should be no problem but we could move this warning into more verbose level if you provide the reproducible case how this warning got popped

@tomatolog
Copy link
Contributor

I'm closing this ticket as topic seems fixed and there is another issue about network warnings #1337

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
waiting Waiting for the original poster (in most cases) or something else
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tomatolog @zhdanau @sanikolaev @Panda58dev