Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • Mike Coulten
    Member

    Hi, I am debugging similar errors on my mySQL 5.5 on RedHat linux servers

    130807 22:44:32 [Warning] Aborted connection 8026 to db: 'ENERGYALERT' user: 'FLCF' host: '192.168.100.12' (Got an error reading communication packets)

    We get these errors intermittently and often we get a group of connections all aborting i.e. all of our Matlab (JDBC) connections but all other connections are unaffected. We can simulate these disconnects by rebooting the server the client is on but logs show no reboots or users online at the time of the disconnects being investigated.

    I dont think its MoNyog related but reading this ticket we will be turning off MoNyog monitoring on one db to test if it is

    in reply to: Clearing The History From Monyog #33140
    Mike Coulten
    Member

    Ah ha, fixed it. Set data retention to 5 minutes and its all cleared automatically

    in reply to: Dashboard System Availability Intermittent #33135
    Mike Coulten
    Member

    Fair point, sorry to be grumpy 🙂 and thanks for the help

    in reply to: Dashboard System Availability Intermittent #33133
    Mike Coulten
    Member
    'Shalmali' wrote:

    ClientAliveInterval should be more than server's data collection. Could you please try this and lets us know.

    Thanks, I found ClientAliveInterval in the sshd-config on the servers I was connecting to and set it to 900 (seconds). Would have been helpful if you had told me where to find this as I first went searching in MONyog's settings! It seems to be working.

    Interestingly the server that was working OK – no intermittency – had the ClientAliveInterval line commented out in the sshd-config file. Presumably this disables all closing of SSH sessions as the data collection interval for this server was the same as for the ones that were intermittent

    I like MONyog but I am finding the documentation poor which seems odd to me since MONyog is sold as a “DBA in a box” i.e. its helpful for people who don't know mySQL DBA very well. The MONyog documentation seems to be written by an expert user for an expert user. To be fair, its the way I write my app documentation, but that's why I get someone else to do it ! Is there any other documentation other than the browser interface help system? What about third party stuff? Any books on MONyog?

Viewing 4 posts - 1 through 4 (of 4 total)