Forum Replies Created
-
AuthorPosts
-
February 11, 2013 at 9:39 pm in reply to: Aborted_Connects Increasing – Causing High Percentage Of Refused Conne #34166paulohm1Member
I believe we have found that the cause of these aborted_connects is a load balancer in our environment which does a check of the tcp port (3306) on a regular basis. I will post back if I find otherwise.
February 11, 2013 at 5:50 pm in reply to: Aborted_Connects Increasing – Causing High Percentage Of Refused Conne #34165paulohm1MemberI always see connections from monyog in the “processlist” page that have a “command” of “sleep” and a “DB” of “NULL”.
If monyog is using persistent connections and correctly closing those connections, why are some of these connections left open in the “sleep” state?
I have attached an image of one such entry in the processlist page of monyog.
February 11, 2013 at 4:04 pm in reply to: Aborted_Connects Increasing – Causing High Percentage Of Refused Conne #34164paulohm1MemberAlso, my collection interval in MONYog is 2 minutes.
I also have sniffing enabled which “sniffs” every 2 seconds.
February 11, 2013 at 4:00 pm in reply to: Aborted_Connects Increasing – Causing High Percentage Of Refused Conne #34163paulohm1MemberThank you for the response. However, my wait_timeout is set to the default of 28800 seconds.
The only other timeouts I have explicitly set in my.cnf are:
slave_net_timeout=60 and innodb_lock_wait_timeout=50
Could either of these cause the same issue?
paulohm1MemberI was never able to get this setup working as I wanted. I was told by support that they were unable to replicate the issue and that I should attempt to recreate all certificates, but still was unable to fix it. I circumvented the issue by creating a VPN between the two networks and making the connection that way.
paulohm1Member'Mahesh' wrote:Please create a ticket by sending an email to “[email protected]”
We will discuss regarding this in ticket system and if required arrange a screen sharing session.
Thanks, I created the ticket
paulohm1MemberI tried creating the key with cygwin using the following command:
ssh-keygen -b 2048
I copied the .pub key that was created into authorized_keys on the server and copied the private key into monyog, but I am still unable to connect.
However, using the ssh client built into cygwin, I am able to connect using the same user and private key, so I know the public/private key authentication is working.
paulohm1Member'Mahesh' wrote:MONyog supports only standard OpenSSH keys and keys generated using Puttygen or any other tool does not work.
Are there any tools that you recommend to generate standard OpenSSH keys that will work with MONYog? I had previously only ever used PuttyGen and then converted the ppk to OpenSSH, but I guess you're saying that doesn't work?
paulohm1MemberI was able to get the connection to work from MONYog to the DB server when using Password Authentication. So it seems like it is an issue with the format of my private key that I am pasting into Monyog. Am I able to use a key that I generate with Puttygen and then convert to Openssh format using puttygen (this is what I have tried in the past and has not worked)? I am unable to create the key using CopSSH on the DB server for unrelated reasons. Is there anything else I can use to create the keys if puttygen does not work?
paulohm1MemberQuote:Give SSH details username and password should match with Windows authenticationI am using Public/Private key pair with CopSSH (not password authentication). When I select “key” in Monyog, I do not have an option for password. I enter my 'username' and 'passphrase' and this is when I get the error “Failed to connect to SFTP:” without any details as described above.
paulohm1MemberI have tried WinSCP and am able to connect OK.
The SSH server software on the 2008 machine is copSSH, which is a packaging of cygwin.
I will not be able to try password-only authentication until monday, however.
Please let me know if there is anything else I can try.
-
AuthorPosts