[Mahesh]

Hi,

We have released 3.06 Final you can see the changelogs here,

http://www.webyog.com/blog/2009/04/17/mysq…g-306-released/

You can install windows trial build in a different machine, If it has already expired.

Sorry for this inconvenience.

[Mahesh]

Hi,

We have fixed this issue in v 3.06.

You can see the change logs from here,

http://www.webyog.com/blog/2009/04/17/mysq…g-306-released/

[Mahesh]

BTW: We have fixed an issue related to linux 32 bit builds ( MONyog was not populating data for Monitors/Advisors), that has been fixed in version 3.06.

You can see the change logs here,

http://www.webyog.com/blog/2009/04/17/mysq…g-306-released/

[Mahesh]

We have fixed this issue in v 3.06 .

You can see the changelogs from here,

http://www.webyog.com/blog/2009/04/17/mysq…g-306-released/

[Mahesh]

I sent you a PM ,

Please create a support ticket from here ,

http://www.webyog.com/support/ttx.cgi

[Mahesh]

Hi,

We observed log file given by you, i can see that Query time always 0(zero).

It is recommended not to keep long_query_time=0 .

Please make changes in your my.ini/my.cnf and change this to long_query_time=1 (OR more).

BTW: We have fixed this issue if long_query_time=0 , then MONyog was not displaying queries, it has been fixed in development tree.

Soon we are releasing v 3.06 with this fix too.

[Mahesh]

I have uploaded the debug TAR package here,

To Download,

http://www.webyog.com/downloads/betas/not_…0.x86_64.tar.gz

If it is still crashing for you, then please send us the “core dump” which helps us in analyzing the problem.

Please follow the steps given below for generating the “core dump”. This will help us to know what is causing the problem.

These are the steps that you need to follow:

1) Execute ulimit -c unlimited in terminal.

2) Now unzip the TAR package in the same terminal, tar -xzf MONyog-trial-3.0.6-0.x86_64.tar.gz

3) This package is debug binary, After unzipping, you will see “MONyog” directory, inside that there is a “bin” directory, after navigating inside the bin directory, execute this to start MONyog,

./MONyog start

MONyog in debug mode is started now.

4) If MONyog crashes then dump file will be created in present working directory by default, with the name “core.(process id of MONyog)”. (If you are not able to find the “core.(process id of MONyog)” file after the crash then it will be created in the path mentioned in the file /proc/sys/kernel/core_pattern).

[Mahesh]

Please mail the source and target .SQL dump ( zip attachments) to “[email protected]” OR else you can create a support ticket from here,

http://webyog.com/support/ttx.cgi

Thanks,

Mahesh

[Mahesh]

Hi Bruce,

We have tried in Red Hat Enterprise Linux ES release 3 (Taroon ) and followed procedure to reproduce the issue, but with no success.

We will try to reproduce it , and update you with details.

[Mahesh]

Hi Bruce,

We are not able to reproduce issue yet, as a workaround please try this,

1) Uninstall MONyog from your machine( rpm -e MONyog-trial) and then, remove MONyog directory from /usr/local/MONyog , rm -rf usr/local/MONyog.

2) Do a fresh installation of MONyog trial, is it working for you now?

Also tell us the output of these command from a linux shell,

1) cat /etc/issue and

2) uname -a

[Mahesh]

Hi,

I can Understand that you have two tables Movie and Genre both are having Foreign Key relationship on a genreid key.

You want to see Movie — Genre column as dropdown so, that it will show fields of Genre table's columns.

But it is not feasible to show Table data like this.

Table — View Data will show only data of the same table.

[Mahesh]

Hi,

We have fixed these issues in 8.04 Beta 2 version.

You can see the changelogs here, http://www.webyog.com/blog/2009/03/17/sqly…-been-released/

To Download,

http://www.webyog.com/en/downloads.php

Please try 8.04 beta 2 and If you still have issues please let us know .

BTW: We are planning to release 8.04 Final version soon, probably on Monday.

[Mahesh]

We checked this in both 32 bit Redhat and 64 bit CentOS, this is not reproducible at our end.

So, We need information listed below,

1) Please try using other browser ?

2) Try restarting MONyog service ?

2) Can you zip and attach a MONyog.log file.?

4) Which Linux version you are using 32/64 bit? Please paste the output of command “cat /etc/issue” ?

Thanks,

Mahesh

[Mahesh]

BTW: Which OS you are using ?

We got it reproduced only in Vista that too with Specific DB's .

[Mahesh]

Issue Confirmed

We will fix this with high priority.

Thanks For reporting.

[Author]

Posts