[Supratik]

'carlos wrote:

OpenSuSE 11.3 x64bit -last MySQL- sqlyog 8,61

I use the installer at cli

./sja: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

I tried:

zypper wp libstdc++.so.5

Loading repository data…

Reading installed packages…

S | Name | Type | Version | Arch | Repository

–+

---

+

---

+

---

+

---

+

---

| libstdc++33 | package | 3.3.3-22.1 | x86_64 | openSUSE-11.3-Oss

| libstdc++33 | package | 3.3.3-22.1 | x86_64 | openSUSE-11.3 11.3-1.82

| libstdc++33 | package | 3.3.3-22.1 | i586 | openSUSE-11.3-Oss

| libstdc++33-32bit | package | 3.3.3-22.1 | x86_64 | openSUSE-11.3-Oss

but i have the last version installed:

libstdc++ 4.4….

Must i need the

compat-libstdc++ ???

Thanks for the answer or solution possibilities

Yes, you need to have compat-libstdc++-5.x.x installed in your system.

You will find this package in your distribution disc.

Do let us know if there is anything else we can do for you.

Warm Regards

Supratik

[Supratik]

'Doug wrote on '27:

Yes the SSH server and mysql server are running on the same machine (however they are on separate machines from the system running monyog).

I can connect to the system from anything OTHER than the ssh connection of monyog using the host name (including the command line ssh client from the system running monyog).

nslookup returns the correct name.

cat /etc/issue

Welcome to openSUSE 11.1 – Kernel r (l).

uname -a

Linux HOSTNAME 2.6.27.48-0.3-default #1 SMP 2010-09-20 11:03:26 -0400 x86_64 x86_64 x86_64 GNU/Linux

The ssh/mysql server has not changed at all (nor has the underlying monyog system) the only update was to monyog itself.

Thanks for the information.

We request you to create a support ticket [url=”http://http://webyog.com/support/ttx.cgi”%5Dhere%5B/url%5D to prevent disclosure of

sensitive information that we may require during our investigation.

Can you please perform the following troubleshooting steps in the system running MONyog and reply us back in our support ticket system.

1. Can you please try to connect to the SSH server from the system on which MONyog is running using the SSH command as shown below and reply us back

with the verbose output

ssh -v -v -v user@server-hostname

2. Please create a entry in your /etc/hosts file as shown below and try to connect using MONyog.

IP-SSH-Server SSH-Server-hostname

Please let us know if you are still facing the issue.

We look forward to your reply.

[Supratik]

Hi,

Can you please provide us some more details so that we can effectively investigate on this issue.

1) Is you SSH server and MySQL server are on the same machine ?

2) Are you able to establish a SSH connection to your server from any SSH client like PUTTY or Linux ssh command using the same hostname ?

3) If you run the command “nslookup [SSH hostname]” does it return the expected IP address ?

(Please replace with the real hostname in place of SSH hostname)

4) What is the O.S in which your SSH server is running ?

Please let us know the output of the following command depending upon the O.S type.

i) For Linux

cat /etc/issue

uname -a

ii) For Solaris

cat /etc/release

uname -a

iii) For MAC

sw_vers

[Supratik]

Hi Carlos,

Thank you for your interest in MONyog (MySQL Monitor and Advisor).

Quote:

1. Is it mean that MONyog can't be running on FreeBSD 7.x ?

Yes, Currently MONyog does not support FreeBSD. We may support in the future depending on the number of user

requests and time required.

Quote:

2. where is MONyog.ini? It could not be found in the directory where MONyog is extracted.

The file “MONyog.ini” will be created automatically in the MONyog installation folder on the first run.

If you are unable to run MONyog in your FreeBSD system then no MONyog.ini will be created.

Please let me know if you have any other questions or concerns.

Warm Regards

Supratik

[Supratik]

Hi MatthewSibson,

The plink binary which you have downloaded from the link provided in Step 4 of my second post is Ver: 0.58.

We have upgraded our SQLyog PLINK to 0.60 and we are not supporting the previous version (Ver: 0.58) of

PLINK from SQLyog 8.5 onwards.

Can you please download the latest PLINK (0.60) binary from here and replace it with the PLINK in your

SQLyog installation folder. If PLINK crashes it will create a crash dump as explained in my last post.This will help us to nail down the issue.

If you have “User Account Control” ON please run SQLyog using administrator privilege.

Please let me know if you have any questions or concerns.

We look forward to your reply.

Warm Regards

Supratik

[Supratik]

Hi MatthewSibson,

We are including two more steps here.

1. Please download this new SQLyog PLINK from here

and replace it with the PLINK in the installation folder.

2. Now try to connect to your server. If PLINK crashes it will create a crash dump in the format “SQLyog_plink_60_Dump_XXX.dmp” (XXX represents sequence) and “SQLyog_plink.log”.

Please upload both the files in the Support Ticket which you need to create as requested in the previous post.

Warm Regards

Supratik

[Supratik]

Hi MatthewSibson,

Quote:

When I tried the latest build of the previous release, SSH tunneling worked just fine. However, after a reboot today plink now crashes when attempting a tunneled connection. This situation is not fixed by using the new release either. No idea if this information is useful but:

Can you please tell me what is the previous version of SQLyog you are using ?

We will require some information to find the root cause of the issue.

1. Are you using Password based or Key based authentication method to connect to your server ?

2. Is it happing when you are connecting to a particular server or all the servers ?

3. Is it reproducible even after you restart once again ?

4. Please download the SQLyog PLINK from here and replace it with the PLINK in the installation folder.

Are you able to connect to your server using this replacement PLINK.

Can you please create a support ticket for SQLyog from here.

You may reply in the ticket with the information requested above. We will continue any further discussion in the ticket system.

We look forward to your reply.

Warm Regards

Supratik

[Supratik]

We think that the issue with Windows 7 and Linux/Wine are similar.

We have fixed this issue in the latest SQLyog-8.5.2.0-n3 not released build.

Please download the binary from here and let us know if it is working fine in your environment.

Warm Regards

Supratik

[Supratik]

Hi,

We really appreciate you for reporting the issue to us.

Quote:

And when I tried to send a response to [email protected], Google was kind of enough to inform me the mail server rejected it:

---

Delivery to the following recipient failed permanently:

[email protected]

Technical details of permanent failure:

Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550-5.1.1 The email account that you tried to reach does not exist. Please try

550-5.1.1 double-checking the recipient's email address for typos or

550-5.1.1 unnecessary spaces. Learn more at

550 5.1.1 http://mail.google.c….py?answer=6596 2si6931435qwi.39 (state 14).

---

The mail failed to deliver because we do not have any email account with name [email protected] in our organization, instead we use [email protected].

Quote:

This could be the cause of the email being marked as spam, too (Google does a reverse check on the sender's email).

We do have Reverse DNS configured for our domain webyog.com.

We would greatly appreciate if you can post the original content of the email (“show original”) in a text file. (Refer to the screenshot: attached)

Warm Regards

Supratik

[Supratik]

'BLAISE wrote on '19:

I'm interested to know if it is possible to change the baseUrl ?

Actually, you can call MonYog via myserver:5555, and I want to configure it to call it via myserver:5555/MyService/MonYog

I want to map it behind a proxypass and it is easier for me to use proxypass

In apache I want to do something like:

ProxyPass http://myserver:5555/MyService/MonYog

Thanks,

Bruno

Hi Bruno,

You may refer our MONyog FAQ Section.

13. How can I access MONyog pages proxying through Apache webserver?

Regards

Supratik

[Supratik]

'Othmar' wrote on '15:

Have try localhost but no success.

I have also test another host (abcde) but on error message always 'localhost' was displayed.

If i disable SSH the error message box contains the entry from MYSQL host. If SSH enabled always 'localhost' was displayed.

Othmar

Hi,

Can you please provide us with a temporary connection of your MySQL server, you may create a ticket in our support system for privacy.

Can you please provide us the following details.

1. What is the SQLyog version you are using ?

2. Are you able to connect if you are using “127.0.0.1” instead of “localhost” ?

[Supratik]

Currently MONyog do not provide any option to bind MONyog to a single interface like “lo” (local loopback). You can only block its port accessible from outside the interface.

Warm Regards,

Supratik

[Supratik]

You may set the iptables/firewall rules to prevent access MONyog except 127.0.0.1.

If you are in Linux you may use the following command to set the iptables rule to block all request other than localhost.

iptables -A INPUT -p tcp –dport 5555 -j DROP

iptables -A INPUT -p tcp –dport 5555 -i lo -j ACCEPT

If you are in windows and if your firewall is enabled you may use the following command.

netsh firewall add portopening TCP 5555 “MONyog” ENABLE CUSTOM 127.0.0.1

If your windows firewall is not enabled you may enable it using the following command

netsh firewall set opmode enable

Please let me know if this solves your problem. If you have any further questions or concerns please let me know.

Regards

Supratik

[Supratik]

Hi,

This is an issue with the the freeSSHD server. We are able to reproduce it and we are working on this issue.

I request you to create a support ticket in http://webyog.com/support/ttx.cgi.

As a temporary workaround you may create a SSH tunnel manually using the plink.exe using the following command.

plink.exe -ssh -l “username” -pw “password” -L 3310:localhost:3306 -P 22 “RemoteHost”

Once you are able to create the SSH tunnel try to connect MySQL server from localhost using the port 3310.

you may refer the screenshot below. Please let me know if you have any questions.

Regards

Supratik

[Supratik]

SQLyog uses Plink for SSH connections and if Pageant is running it will use Pageant to authenticate. I think

if this error is appearing for a SQLyog connection it may also appear for the other applications that uses keys

from Pageant key list.

Can you please provide me with few details..

1) In your present setup did you get the same error for WinSCP and Putty anytime ?

2) Does all your SSH connections uses Pageant to authenticate ?

3) Are you specifying the key that's required for the authentication in the session configuration in WinSCP or Putty for any connection?

Quote:

Can you look at integrating pageant support into the next SQLyog version? It is quite an essential tool for unix administrators…

We will discuss on this feature, to have an option in SQLyog whether to obtain keys from Pageant or not.

Regards

Supratik

[Author]

Posts