-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
MySQL died after PHP send data to it. #8
Comments
He is version: '2'
services:
pinba2:
image: alexanderilyin/pinba2:fedora-25-v2.3.2
container_name: pinba2
restart: always
ports:
- "3002:3002/udp"
- "3306:3306/tcp"
build:
context: .
dockerfile: Dockerfile |
Guys I've tried to rebuild it with your latest changes: After it, MySQL crashes on start:
Here is you you can reproduce it:
Here is used version: '2'
services:
pinba2:
image: alexanderilyin/pinba2:latest
container_name: pinba2
restart: always
ports:
- "3002:3002/udp"
- "3306:3306/tcp"
build:
context: .
dockerfile: Dockerfile |
Just stumbled on this issue by accident, sorry! |
Tried your tables quickly, but was unable to reproduce (though i'm not using the container, just local build) - will try again tomorrow. |
Also, please try in mysql
it should start dumping all received packed info to log |
was able to reproduce with Dockerfile built container. suspect issues with build itself. |
@anton-povarov I'm not sure if I can help anyhow on the current stage, so I'm planning to work on automation for functional tests so we can have regression tests using one of these services: The main problem I'm not sure what is the right way to distribute PHP extension. I'm building it right now from sources, but was thinking about packing it in for PECL or for Ubuntu/Alpine. |
the top frame is completely broken, although the jump to the hash function seems legit and registers seem to be fine. And calling the function from debugger seems fine as well. currently i suspect that the cause is that we're building with src rpm, but injecting the pinba module to pre-build fedora rpm. Will try and investigate more today. The quicker fix for you might be to build mysql/mariadb from official downloaded source (that's what we do internally at Badoo anyway). |
@alexanderilyin please try this branch, fixes the issue for me. |
@anton-povarov only today I had time to check it one more time, and it worked on dev environment. There is only one unexpected thing so far:
P. S.Test data was delivered successfully from both CLI and FPM SAPI using old pinba extension, but I'm not sure what is causing |
@anton-povarov I need some help with porting MySQL configuration options from Pinba1 to Pinab2:
Could you please confirm that my assumptions are correct? |
Regarding "Standard Input Code" - no idea what that is, pinba definitely never sets anything like this by itself. Might be a bug, but there are no strings like this anywhere in source code. Regarding settings: your assumptions are correct.
|
is this |
More info about 'Standard input code' in the script_name Pinba extension sends this script_name to a server after run a script /usr/lib/php/sessionclean on Linux systems. The script runs by a cron (at least on systems like Debian) |
Here is what I got in logs
After it, MySQL could not start and docker container goes in crush loop:
Following SQL was applied to MySQL. It was generated using https://github.com/badoo/pinba2/blob/master/scripts/convert_mysqldump.php
Tables like
request
,tag
,timer
,timertag
,info
andstatus
were not converted by script and were not created in new MySQL.Here are details about used PHP version
and
pinba
extention:MySQL crushed after first fpm request was processed. Please send help.
The text was updated successfully, but these errors were encountered: