forums › forums › Monyog › Using Monyog › Processlist – Memory Constraint
- This topic is empty.
-
AuthorPosts
-
-
January 11, 2011 at 5:50 am #12223mitchnMember
When accessing the processlist of Monyog (v4.1.2) it complains of the following:
[4.12] [2011-01-11 16:42:39] [Server: Master_DB0] srcysqlite.cpp(463) ErrCode:19 ErrMsg:[DB: :memory:] constraint failed
[4.12] [2011-01-11 16:42:39] [Server: Master_DB0] processlistmgr.cpp(394) ErrCode:-1 ErrMsg:GetProcessListInfoFromMySQL: Unable to populate SQLite table for 'Master_DB0' — [DB: :memory:] constraint failed
[4.12] [2011-01-11 16:42:39] [Server: Master_DB0] processlistmgr.cpp(174) ErrCode:-1 ErrMsg:[DB: :memory:] constraint failed
[4.12] [2011-01-11 16:42:40] [Server: DB5_Slave] srcysqlite.cpp(463) ErrCode:19 ErrMsg:[DB: :memory:] constraint failed
[4.12] [2011-01-11 16:42:40] [Server: DB5_Slave] processlistmgr.cpp(394) ErrCode:-1 ErrMsg:GetProcessListInfoFromMySQL: Unable to populate SQLite table for 'DB5_Slave' — [DB: :memory:] constraint failed
[4.12] [2011-01-11 16:42:40] [Server: DB5_Slave] processlistmgr.cpp(174) ErrCode:-1 ErrMsg:[DB: :memory:] constraint failed
The two servers are identical in hardware, and work on the older 3.75 version of Monyog without issue. All other tabs work, except the processlist. Any ideas on why? Other servers work fine, just these two, which are 128GB IBM 4-socket machines.
-
January 11, 2011 at 6:52 am #31799MaheshMember
We have tried migration from v3.75 to v4.12 but could not able to reproduce this scenario.
Can you please tell us certain information mentioned below:
1) Attach a MONyog.log file
2) Attach a screenshot showing processlist page of problematic server?
Also what does other MySQL client returns on execution of:
SHOW FULL PROCESSLIST;
Also please paste the result of this query here itself.
3) MySQL server version?
-
January 11, 2011 at 9:19 am #31800peterlaursenParticipant
1) Also see http://dev.mysql.com/doc/refman/5.1/en/show-processlist.html
(note that only with recent servers PROCESS priivilege will suffice for seeing all threads – older servers require SUPER privilege).
But in neither case MONyog should log such errors of course. It should insert what it can retrieve.
2) and tell the returns of the statement: “SHOW GRANTS for 'user'@'host'”
(where 'user'@'host' is the MONyog user on this host
3) If this MySQL server was upgraded from an earlier version, are you sure that 'mysql_upgrade' was executed after the upgrade?
Try execute “SHOW CREATE TABLE mysql.user” and paste the result here.
-
January 11, 2011 at 11:14 am #31801mitchnMember'Mahesh' wrote:
We have tried migration from v3.75 to v4.12 but could not able to reproduce this scenario.
Can you please tell us certain information mentioned below:
1) Attach a MONyog.log file
2) Attach a screenshot showing processlist page of problematic server?
Also what does other MySQL client returns on execution of:
SHOW FULL PROCESSLIST;
Also please paste the result of this query here itself.
3) MySQL server version?
1) Attached.
2) Also attached. 'SHOW FULL PROCESSLIST' works fine within SQLyog and all other MySQL clients.
3) MySQL Version is 5.0.51a_Community. Any Monyog version below 4.0 works fine.
To answer the other 3 questions:
1) The user privilege (in this case it is the Root user) is fine, as it can query 'SHOW FULL PROCESSLIST' without issue in query browsers.
2) It's root user, with no modifications made so it is the super_user.
3) Server has been active in production since a clean install back in February 2008, so it's been running a while (no upgrade has been performed as yet).
-
January 11, 2011 at 12:27 pm #31802sandhya.rMember
Can you please
1) Attach the output of the query “SHOW FULL PROCESSLIST”.
2) Make a duplicate connection of the problematic server and try whether it is reproducible with that server or not.
-
January 11, 2011 at 9:55 pm #31803mitchnMember'sandhya.r' wrote:
Can you please
1) Attach the output of the query “SHOW FULL PROCESSLIST”.
2) Make a duplicate connection of the problematic server and try whether it is reproducible with that server or not.
1) Attached.
2) Creation of a new connection for the same server does not address the issue. I have 2 replica servers, and the issue remains for both these two servers. The other servers that are monitored don't have this issue.
-
January 11, 2011 at 11:15 pm #31804peterlaursenParticipant
OK .. thanks. We will check the log tomorrow.
-
January 12, 2011 at 6:03 am #31805sandhya.rMember
Issue Confirmed.
The problem was with “Id” column. It is fixed now.
We will provide you a special build to verify this bug fix. Please tell which MONyog build you are using(Windows/Linux32/LInux64)?
-
January 12, 2011 at 7:07 am #31806mitchnMember'sandhya.r' wrote:
Issue Confirmed.
The problem was with “Id” column. It is fixed now.
We will provide you a special build to verify this bug fix. Please tell which MONyog build you are using(Windows/Linux32/LInux64)?
The version installed is the latest windows stable version: Stable 4.1.2-0.
Thanks,
Mitch
-
January 12, 2011 at 1:14 pm #31807
-
January 13, 2011 at 4:34 am #31808mitchnMember
It has been installed and Processlist works again for those servers. Thank you for your assistance!
Regards,
Mitch
-
-
AuthorPosts
- You must be logged in to reply to this topic.