-
Notifications
You must be signed in to change notification settings - Fork 40
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
Lack of connectivity to MariaDB on a NAS #263
Comments
Thanks. This looks like a fairly specialized application, could this be a firewall of sorts (on the Synology or elsewhere) that interferes here? Can you please try connecting using the |
Thanks, I opened |
Thanks. Did you use the MySQL or MariaDB version of It seems that RemoDB is doing something differently, I haven't found sources for RemoDB though. Would an SSH tunnel work for you? |
Thanks, using However after starting
whereas via ssh:
which is slightly different. Do you mean an ssh tunnel in the R script? Would you mind to elaborate a little on that? |
Can you try installing the MariaDB monitor on Ubuntu and try it there? For an SSH tunnel, you would connect to the device via |
Hi
Thanks for maintaining both DBI and RMariaDB!
I have a problem connecting to a MariaDB on a Synology NAS. It doesn't work at all using
RMariaDB::MariaDB
and just unsatisfactory usingRMySQL::MySQL()
.I first asked a question on Stack Overflow which at least brought me a small step further, but nothing more.
So, according to the documentation, I have tried this:
But I get the error
The port is correct, since otherwise I get:
The driver also appears to be available:
Then tried with the
RMySQL::MySQL()
driver, which actually works but it almost takes forever (207 secs):Curiously it's always around 207 secs. Before you ask, the database actually just has tiny dimensions 86x4.
I'm not sure if it is a Synology, a Network, a Linux, or a problem related to your packages, but maybe you have an idea what's going on and can help?
Here my specs:
Cheers!
The text was updated successfully, but these errors were encountered: