I have deployed MySQL on OpenShift (kubernetes) with GlusterFS as persistent storage and i am getting following error after every 2 seconds in MySQL Container logs

2020-01-17T18:00:04.787586Z 1541 [Note] Got an error reading communication packets
2020-01-17T18:00:06.787610Z 1543 [Note] Got an error reading communication packets
2020-01-17T18:00:08.787548Z 1544 [Note] Got an error reading communication packets
2020-01-17T18:00:10.787586Z 1546 [Note] Got an error reading communication packets
2020-01-17T18:00:12.787575Z 1547 [Note] Got an error reading communication packets

I tried by changing below variables but no success

  • set @@global.max_connections = 400;
  • max_allowed_packet=256M
  • innodb_log_buffer_size = 32M
  • innodb_log_file_size = 2047M
  • SET GLOBAL thread_cache_size=50;

i tried to set SET GLOBAL log_warnings=3; for details logging but nothing is showing

$ mysql --version
mysql  Ver 14.14 Distrib 5.7.28, for Linux (x86_64) using  EditLine wrapper

Internet is full of tips about how to solve this error message, but the usual solutions are tweaking the various timeout and max_allowed_packet settings. However, changing these settings made no difference to me, the error kept happening infact now i shut all application and only MySql is running but still error is repeating. Although my services are not hampering but i have implemented Centralized logging and this log is flooding it.

I also run mysqltuner but its suggestion are for query cache only and tunning it has no effect


So if there is not client why MySQL is showing this message as no reading or writing happening??

Extra Details:

  • Please post your complete MySQL my.cnf content for analysis. Thank You for data already posted. Commented Jan 21, 2020 at 13:53
  • Alas the stats are for 5 minutes -- need 24 hours. Also need to know how much RAM you have.
    – Rick James
    Commented Jan 25, 2020 at 19:08

1 Answer 1


After spending lot of time I am able to resolve my issue and reason is that in Openshitf/kubernetes we have section to verify readiness of mysql like

      port: 3306
    initialDelaySeconds: 20
    periodSeconds: 2
    timeoutSeconds: 1

So it was pinging every two seconds on 3306 port, i changed it to below and its resolved the issue,

          - sh
          - -c
          - "mysqladmin ping -u root -p${MYSQL_ROOT_PASSWORD}"
        initialDelaySeconds: 5
        periodSeconds: 2
        timeoutSeconds: 1
  • 1
    Excellent on resolving the readinessProbe. You may want to be a few more seconds tolerant on initial Delay Seconds. If you will post your MySQL my.cnf, I will suggest how you can resolve this earlier observation of yours. "i tried to set SET GLOBAL log_warnings=3; for details logging but nothing is showing" Commented Jan 21, 2020 at 14:58
  • @WilsonHauck Thanks for asking about conf and really appreciated i have added conf link above. gist.github.com/imranrazakhan/5ec96905048758eb49cf7ac6140bdfff Commented Jan 22, 2020 at 15:18
  • After reviewing the recent post of 6 cat conf files, would it be possible to schedule date/time a 5 minute Skype chat to more quickly come to a conclusion on which of these 6 files contribute to the startup of your instance? My Skype ID is [email protected] - NOT Skype for Business. Thanks Commented Jan 22, 2020 at 20:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.