Monyog Data Maintenance Issue

[BenMc]

I have been trying to do some maintenance on the data for a server that has been giving us a lot of trouble. My issue is that the sniffer data size is in excess of 18G. When I try to run data maintenance routine on the server it just runs for hours and never seems to finish.

The size of the data is now impacting the performance of MONyog in general, so I am looking for some way to clean the data [vacuum] without impacting the other monitoring that MONyog is doing. Is there a some way of executing this on the command line? Should I just delete the data and start over?

MONyog is running on a linux machine.

[Sayan Chaliha]

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.

[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]

'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.

[Sayan Chaliha]

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.

[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?

[Sayan Chaliha]

Hi Ben,

When you delete a registered server, all the data for that server should be completely removed. I'd suggest that you open a support ticket here so that support engineers will be better able to help you (note that all information that you share in the forums is public while every bit of communication in the support system is kept private).

In the meantime here's a workaround:

— Make a note of the server ID (the 4-digit number)

— Stop MONyog

— In the data folder of MONyog you'll find a folder with the ID as the name — delete it

— Restart MONyog and you shouldn't see that connection again

Before you do delete the data, take a backup. It would definitely help in debugging the issue.

[Author]

Posts