Hello,
I'm trying to tunnel to my VPS Trove instance, so that I can test some code
against the production database.
I'm using the following:
ssh -N -L 4177:tdlqt33y3nt.svc.trove.eqiad1.wikimedia.cloud:3306
login.toolforge.org
I've also tried:
ssh -N -L 4177:tdlqt33y3nt.svc.trove.eqiad1.wikimed
I noticed you say it's a VPS as in Cloud VPS project but you attempt to
tunnel via login.toolforge.org.
Maybe try tunneling via bastion.wmcloud.org or primary.bastion.wmcloud.org
as the bastion hosts for the cloud VPS projects.
https://wikitech.wikimedia.org/w/index.php?go=Go&search=bastion.wmcl
When I try tunnelling through bastion.wmcloud.org or
primary.bastion.wmcloud.org I just get:
pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on
'localhost' ([Errno 61] Connection refused)")
I can resolve and connect to the trove instance from toolforge, and as I
mentioned in m
I also have just now tried the command line mysql client through the tunnel
and things seem to work, so maybe it's some Python setting that's causing
the connection to drop?
-Travis
On Fri, Jun 21, 2024 at 12:06 PM Travis Briggs wrote:
> When I try tunnelling through bastion.wmcloud.org or
> pr
There's no fundamental reason why this can't work. I've done similar things:
> ssh -t dev.toolforge.org -L 3306:tools.db.svc.wikimedia.cloud:3306"
Sometimes it takes a few tries to find the right ssh incantation, but port
tunneling is definitely something that works. One thing you might try
Yes I've definitely tunnelled successfully to toolforge DBs, and the wiki
replica databases, before. I've never had a problem with it, but I suspect
the issue is with Trove. Like i said, I can establish the connection and
even query my Trove production db from the mysql command line. But it times
o
