[BenMc]

'Sayan wrote:

Hey Ben,

Glad that its working for you. Btw, which version of MONyog are you using? Usually not being able to shut MONyog down could mean something's terribly wrong.

Well – in day two I have found that there is something terribly wrong.

First: we are running version 4.02 [just upgraded].

Here are some select log files:

[4.01] [2010-10-04 19:14:57] src/ysqlite.cpp(438) ErrCode:7 ErrMsg:[DB: /usr/local/MONyog/bin/..//data/0007/sniffer.data] out of memory

[4.01] [2010-10-04 19:14:58] src/ysqlite.cpp(438) ErrCode:7 ErrMsg:[DB: /usr/local/MONyog/bin/..//data/0007/sniffer.data] out of memory

[4.01] [2010-10-04 19:15:31] src/ymysql.cpp(395) ErrCode:2006 ErrMsg:MySQL server has gone away

[4.01] [2010-10-04 19:16:09] src/ymysql.cpp(395) ErrCode:2006 ErrMsg:MySQL server has gone away

[4.01] [2010-10-04 19:16:25] sniffer.cpp(616) ErrCode:-1 ErrMsg:DeleteFromSnapshot: Unable to execute SQLite query DELETE FROM [query_snapshot] WHERE (1286234136 – 259200) >= uptime

[4.01] [2010-10-04 19:16:25] sniffer.cpp(498) ErrCode:-1 ErrMsg:CleanSnifferDatabase: DeleteAllData failed

[4.01] [2010-10-04 19:17:48] sniffer.cpp(616) ErrCode:-1 ErrMsg:DeleteFromSnapshot: Unable to execute SQLite query DELETE FROM [query_snapshot] WHERE (1286233924 – 259200) >= uptime

[4.01] [2010-10-04 19:17:48] sniffer.cpp(498) ErrCode:-1 ErrMsg:CleanSnifferDatabase: DeleteAllData failed

[4.01] [2010-10-04 19:20:40] src/ymysql.cpp(395) ErrCode:2006 ErrMsg:MySQL server has gone away

[4.01] [2010-10-04 19:21:21] src/ymysql.cpp(395) ErrCode:2006 ErrMsg:MySQL server has gone away

[4.01] [2010-10-04 19:23:03] sniffer.cpp(486) ErrCode:-1 ErrMsg:CleanSnifferDatabase: Unable to execute SQLite query SELECT COUNT(*) from [query_snapshot]

[4.02 ] [2010-10-05 09:00:06] configlist.cpp(3161) ErrCode:-1 ErrMsg:[DB: /usr/local/MONyog/bin/..//data/0009/sniffer.data] duplicate column name: host

[4.02 ] [2010-10-05 09:00:06] configlist.cpp(3161) ErrCode:-1 ErrMsg:[DB: /usr/local/MONyog/bin/..//data/0009/sniffer.data] there is already another table or index with this name: query_master_bak

[4.02 ] [2010-10-05 09:05:52] src/ymysql.cpp(395) ErrCode:2006 ErrMsg:MySQL server has gone away

[4.02 ] [2010-10-05 09:05:52] src/ymysql.cpp(395) ErrCode:2006 ErrMsg:MySQL server has gone away

Now, what is interesting is that server 0009 is a duplicate of server 0018. I was deleted and then added back again later. However, it appears that the original configuration was not removed from the system. It's sniffer.data file is now in excess of 28GB.

I restarted MONyog and now the system has a load average of over 20 and climbing – I am at a loss here.

How can I manually remove this server without damaging MONyog?

[BenMc]

'BenMc' wrote:

Well, now my issues have escalated. MONyog is now dominating the system resources. I am trying to stop it gracefully, but after 5 minutes it will not stop. I may have to kill it.

Once I have it shut down I will follow the directions above.

Thank you.

Your directions worked very well – data file down below a gigabyte.

Thank you.

[BenMc]

'Sayan wrote:

Hi Ben,

There is a high possibility that sniffer.data could have gotten corrupted somehow. Otherwise VACUUM should've worked just fine. You could try the following:

1. Disable Sniffer for that particular server.

2. Open sniffer.data using the SQLite3 command line (your Linux box should have it pre-installed):

Code:

sqlite3

3. Next, do an integrity check:

Code:

PRAGMA integrity_check;

4. If the integrity check passes, try running vacuum:

Code:

VACUUM;

Let me know how it goes.

Well, now my issues have escalated. MONyog is now dominating the system resources. I am trying to stop it gracefully, but after 5 minutes it will not stop. I may have to kill it.

Once I have it shut down I will follow the directions above.

Thank you.

[BenMc]

'Sayan wrote on '06:

Hi BenMc,

That's really weird.. No user has ever reported anything to that effect before. Anyway, I'm going to need a few details to get a clear view of your problem:

1) What is the OS of the system running MONyog?

2) What is the OS of the system running MySQL?

3) Which version of MONyog are you using?

Additionally, the MONyog error log (MONyog.log) can be found in:

— Windows XP: C:Documents and SettingsAll UsersApplication DataWebyogMONyog

— Linux: /usr/local/MONyog/

(if installation was done using the default settings).

Some updates….

1) Red Hat Enterprise Linux ES release 4 (Nahant Update 3) [32 bit]

2) Red Hat Enterprise Linux Server release 5.1 (Tikanga)[64 bit]

3) MONyog version 3.65 [installed with RPM]

I restarted the MONyog service, which took 3 attempts before shutting down so I could restart. After restarting the system it became VERY responsive and I was able to get the configurations I wanted.

However – after working in the system for a while [30 min?] I am getting slowness again. Graphs are not loading in the system properly [can take up to 3 refreshes to get all graphs].

I am now seeing errors in the log file, but all seem to be related to my own mistakes in the configuration [failed ssh connections, etc] and various other 'human' error alerts.

[Author]

Posts