-
Notifications
You must be signed in to change notification settings - Fork 81
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
stdout pipe shows nothing #50
Comments
some progress, it now gives me this
|
Is this stock MySQL? |
First time trying this and run into the same issue. However, I am using MariaDB 10.0.21. By any chance, do you know is there any difference that can affect mypipe running? Do you know what is the best way to turn on debugging? Thank you! |
Hi @mardambey Steps I have done are the following: 1.) Edit my.cnf
2.)
4.) Package
5.) Added permissions for mypipe:mypipe into MariaDB 6.) Run
and then I see the log:
I tried to do some changes in the database but I see nothing in stdout. Do you have any ideas what could potentially happen? Thanks! |
@kubum the main difference here is MariaDB. I haven't tried mypipe against it recently, and I think it did not work properly last time I tried it. I'll have to give it a try and let you know, unless you can repeat the above steps for a "stock" MySQL server and let us know what you find out. Another thing I noticed in your logs was:
I wonder why mypipe can't find out the binary log file name. Usually, this looks like this:
Thanks for following up! |
I am encountering a similar situation. application.conf
I am using the containers within this project. Kafka, MySQL, and Zookeeper
|
I had the same problem and commenting out shutdown seemed to fix it
|
same problem, comment shutdown to work. |
I have mysql setup with binlog and format = row
my application.conf:
all I see when i start mypipe is that is is connected, but it keep loosing the connection:
in my mysql i have a table users, but when updating it and adding new entries, i see nothing in the stdout
any one experiences this ?
The text was updated successfully, but these errors were encountered: