[Sayan Chaliha]

Hi Rob,

Sorry for all the trouble, but could you try the binary once again? I made a couple of changes to it. Here's the link again:

http://www.webyog.co…5-42.x86_64.rpm

You can expect the same thing — a message like “Allocation failed…” should be logged to MONyog's log this time.

It is very likely that there is some text in your slow log which MONyog isn't being able to parse correctly. When attempting to parse that particular line it gets caught in an infinite loop which is only broken (by the crash) when it tries to allocate a string which is 2.5GB in size.

It would be very helpful if you could upload your slow log file. If you're worried about privacy, let me assure you that we guarantee full privacy on our ticket system — what goes on there stays between the user and us. Moreover, you may definitely remove any information that you deem sensitive from the log.

[Sayan Chaliha]

Hi Rob,

There is a scenario where this same crash can be reproduced if the system is low on memory (such as in a virtualized system). To eliminate that as a possibility, here's a link to a binary: http://www.webyog.com/downloads/betas/not_released/MONyog-3.7.6-1.glibc-2.5-42.x86_64.rpm

This version of MONyog will log an error message in case memory allocation fails (besides the usual abnormal exit procedure).

[Sayan Chaliha]

Also, it looks like you're using CentOS 5.4 x86_64 but just to be doubly sure, could you include the output of

Code:

uname -a

?

[Sayan Chaliha]

Hi Rob,

Initially I missed the signal number — 6 — ie, SIGABRT, the signal sent to the process calling the function 'abort()' to make an abnormal exit. There are a couple of instances in MONyog's source where this function is called and all of them are, one way or the other, related to the filesystem and the system's word-size.

Is there any particular characteristic of your system I'm missing — as in any special settings or the like? I have never seen MONyog signal an abort before.

BTW, besides the log analyzer are the other features of MONyog working?

[Sayan Chaliha]

Hi Rob,

Could you check in MONyog's installation directory for a core dump? It's weird that it's segfaulting when analyzing the slow log: that part of MONyog is very old, and has gone through thorough testing over the years.

You should also check MONyog's log file (you'll find in the installation directory itself).

[Sayan Chaliha]

Hi Paul,

We are looking into this problem and will keep you updated on the progress. Could you also post the contents of MONyog's log (at the time when you were experiencing this problem) here? You can find the log in MONyog's installation directory (a file named MONyog.log).

In the meantime, you should have a look at this article: http://www.watchingthenet.com/how-to-kill-windows-processes-that-wont-die-or-terminat.html

It explains how to kill Windows processes that don't die easily.

[Sayan Chaliha]

Hi Ratheesh,

We'll get rid of this limitation with priority.

Also, I'm moving this discussion to our support system. Issues like these are more easily managed there.

http://webyog.com/support/ttx.cgi?cmd=ticket&key=9316Z1490036918618127238

[Sayan Chaliha]

Hi,

I suppose you are referring to SQLyog. This forum is for MONyog — MySQL monitor. I'll move this topic to the SQLyog forums, and I'm sure you have a reply pretty soon!

[Sayan Chaliha]

Hi Maurice,

I see that you've already enabled system monitoring through SSH, so all you need to do is select 'via SFTP' in “Edit Server” –> 'Log Settings”. This should solve the problem.

BTW, I also replied the same to the ticket you had created. I will close the ticket, and we can continue our discussion here… Is that ok?

[Sayan Chaliha]

'Maurice' wrote on '15:

Log Settings:

Read File From = Local Path

…

Is MONyog running on the same system where the log file is?

[Sayan Chaliha]

Unfortunately, SQLyog is only available for Windows. However, you can still use SQLyog's Job Agent (SJA) on Linux. Moreover, you might want to take a look at Wine… Wine make running Windows software on Linux a breeze.

Also, I was wondering if you have any feedback on the downloads page. We recently had it changed and lots of people seem to be getting confused…

Thanks for your interest in our products!

[Sayan Chaliha]

'Sayan wrote on '12:

The version of RPM of MONyog that you are trying to install is actually compiled on a CentOS 5.4 (x86_64) base system with C/C++ runtimes installed!

PS: I just noticed you tried to install a 64-bit RPM on a 32-bit system. Here's the link to the 32-bit binary:

http://www.webyog.com/downloads/MONyog-3.7.2-0.glibc-2.5-42.i386.rpm

[Sayan Chaliha]

The version of RPM of MONyog that you are trying to install is actually compiled on a CentOS 5.4 (x86_64) base system with C/C++ runtimes installed!

[Sayan Chaliha]

Hi,

The only dependencies that you seem to be missing are glibc and libstdc++. These are the only two libraries we don't bundle with MONyog, as they are standard C++ runtimes, and available in all Linux repositories. You see the other failed dependencies because all other libraries depend on it.

Try this:

Code:

yum install gnu-gcc libstdc++

[Sayan Chaliha]

Furthermore, the new versions of MONyog will create a core dump in the event of a crash. You'll find the core dump in

Code:

/usr/local/MONyog/bin/

(by default; when MONyog is installed using the RPM pacakge).

Should you ever come across another crash of the sort, please do report it (with the crash dump) to http://www.webyog.com/support/

[Author]

Posts