Mysql Error 20016
Reporter: Ben Im Email Updates: Status: Can't repeat Impact on me: None Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious) Version:mysql-cluster-gpl-7.3.0-linux2.6-x86_64 OS:Linux (3.2.0-29-generic #46-Ubuntu) Assigned to: Bogdan Kecman View Add Comment Files Developer Edit Submission View Progress Log Contributions [8 Nov 2012 18:06] Ben Im Description: mysql-cluster-gpl-7.3.0-linux2.6-x86_64.tar.gz 3.2.0-29-generic #46-Ubuntu Got the following error: 07.11.2012 10:02:57 ERROR [JDBCExceptionReporter] Got temporary error 20016 'Query aborted due to node failure' from NDBCLUSTER All ndb data nodes are up, connected, and communicating with each other according to ndbinfo > VIEW > nodes & transporters. Setup consists of 2 clusters 2 ndb data and sql nodes per cluster ndb data and sql nodes are on a same host 2 ndb mgmt nodes for the clusters, 10.10.104.48 & 50 Cluster Configuration --------------------- [ndbd(NDB)] 4 node(s) id=3 @10.10.104.121 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 0, Master) id=4 @10.10.104.42 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 0) id=5 @10.10.104.43 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 1) id=6 @10.10.104.122 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 1) [ndb_mgmd(MGM)] 2 node(s) id=1 @10.10.104.48 (mysql-5.5.25 ndb-7.3.0) id=2 @10.10.104.50 (mysql-5.5.25 ndb-7.3.0) [mysqld(API)] 4 node(s) id=20 @10.10.104.121 (mysql-5.5.25 ndb-7.3.0) id=21 @10.10.104.42 (mysql-5.5.25 ndb-7.3.0) id=22 @10.10.104.43 (mysql-5.5.25 ndb-7.3.0) id=23 @10.10.104.122 (mysql-5.5.25 ndb-7.3.0) Thanks, Ben How to repeat: 1. Clusters were functioning fine. 2. stopped mysql.server service on 10.10.104.42. 3. And then "4 stop" to stop ndb data from ndb_mgm. 4. Then I was not able to connect this node, 4. I had to shutdown all ndb data nodes and then restart ndb data nodes and mysql.server on all nodes. 5. Repeated #2, #3, #4 for testing. Maybe 2 or 3 times. 6. show command and ndbinfo indicate that all nodes are connected and functioning. Then I got the above error, 20016. Error log attached. [8 Nov 2012 18:15] Ben Im Error log is 960K large. Is there a way to generate error log smaller than 500K? Below generates 960K log: root@NDB-Mgmt:/usr/local/mysql/bin# ./ndb_error_reporter ../config.ini username --fs Copying data from node 3 vidder@10.10.104.121's password: ndb_3_error.log 100% 4560 4.5KB/s 00:00 scp: /var/lib/mysql-cluster/ndb_3_fs: Permission denied ndb_3_out.log 100% 192KB 192.4KB/s 00:00 ndb_3.pid 100% 4 0.0KB/
Reporter: Ben Im Email Updates: Status: Can't repeat Impact on me: None Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S2 (Serious) Version:mysql-cluster-gpl-7.3.0-linux2.6-x86_64 OS:Linux (3.2.0-29-generic #46-Ubuntu) Assigned to: Bogdan Kecman View Add Comment Files Developer Edit Submission View Progress Log Contributions [8 Nov 2012 18:06] Ben Im Description: mysql-cluster-gpl-7.3.0-linux2.6-x86_64.tar.gz 3.2.0-29-generic #46-Ubuntu Got the following error: 07.11.2012 10:02:57 ERROR [JDBCExceptionReporter] Got temporary error 20016 'Query aborted due to node failure' from NDBCLUSTER All ndb data nodes are up, connected, and communicating with https://bugs.mysql.com/bug.php?id=67523 each other according to ndbinfo > VIEW > nodes & transporters. Setup consists of 2 clusters 2 ndb data and sql nodes per cluster ndb data and sql nodes are on a same host 2 ndb mgmt nodes for the clusters, 10.10.104.48 & 50 Cluster Configuration --------------------- [ndbd(NDB)] 4 node(s) id=3 @10.10.104.121 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 0, Master) id=4 https://bugs.mysql.com/bug.php?id=67523&files=1 @10.10.104.42 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 0) id=5 @10.10.104.43 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 1) id=6 @10.10.104.122 (mysql-5.5.25 ndb-7.3.0, Nodegroup: 1) [ndb_mgmd(MGM)] 2 node(s) id=1 @10.10.104.48 (mysql-5.5.25 ndb-7.3.0) id=2 @10.10.104.50 (mysql-5.5.25 ndb-7.3.0) [mysqld(API)] 4 node(s) id=20 @10.10.104.121 (mysql-5.5.25 ndb-7.3.0) id=21 @10.10.104.42 (mysql-5.5.25 ndb-7.3.0) id=22 @10.10.104.43 (mysql-5.5.25 ndb-7.3.0) id=23 @10.10.104.122 (mysql-5.5.25 ndb-7.3.0) Thanks, Ben How to repeat: 1. Clusters were functioning fine. 2. stopped mysql.server service on 10.10.104.42. 3. And then "4 stop" to stop ndb data from ndb_mgm. 4. Then I was not able to connect this node, 4. I had to shutdown all ndb data nodes and then restart ndb data nodes and mysql.server on all nodes. 5. Repeated #2, #3, #4 for testing. Maybe 2 or 3 times. 6. show command and ndbinfo indicate that all nodes are connected and functioning. Then I got the above error, 20016. Error log attached. [8 Nov 2012 18:15] Ben Im Error log is 960K large. Is there a way to generate error log smaller than 500K? Below generates 960K log: root@NDB-Mgmt:/usr/local/mysql/bin# ./ndb_error_reporter ../config.ini username --fs Copying dat
Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic Program SAS http://support.sas.com/kb/20/016.html OnDemand For Academics USERS GROUPS Advanced Search support.sas.com Knowledge Base Support Training & Books Store Support Communities Knowledge Base Products & Solutions System Requirements Install Center Third-Party Software Reference Documentation Papers Samples & SAS Notes Browse by Topic Search Samples Search Usage Notes Search Installation Notes Search Problem Notes Focus Areas Usage Note 20016: "MySQL server has mysql error gone away" When loading a large SAS Solutions Data Mart or SAS Strategic Performance Management database to the MySQL server, you might encounter an error message in the command prompt window: "MySQL server has gone away" The error is often a result of the packet buffer overflowing. To circumvent the problem, try increasing the size of the max_allowed_packet and mysql error 20016 restarting the server. The max_allowed_packet size is often set to 2MB; increase it to 4MB. This parameter is set in the <my.ini> file, in the MySQL root directory on the data-tier machine. Operating System and Release InformationProduct FamilyProductSystemProduct ReleaseSAS ReleaseReportedFixed*ReportedFixed*SAS SystemSAS Financial ManagementMicrosoft Windows Server 2003 Standard Edition4.3Microsoft® Windows® for 64-Bit Itanium-based Systems4.2Microsoft Windows XP Professional2.0Microsoft Windows NT Workstation2.0Microsoft Windows XP 64-bit Edition2.0Microsoft Windows Server 2003 Enterprise Edition2.0Microsoft Windows Server 2003 Datacenter Edition2.0Microsoft Windows 2000 Server2.0Microsoft Windows 2000 Professional2.0Microsoft Windows 2000 Datacenter Server2.0Microsoft Windows 2000 Advanced Server2.0AIX4.364-bit Enabled AIX4.3SAS SystemSAS Strategic Performance ManagementMicrosoft Windows Server 2003 Standard Edition4.3Microsoft® Windows® for 64-Bit Itanium-based Systems4.1Microsoft Windows XP Professional2.0Microsoft Windows NT Workstation2.1Microsoft Windows XP 64-bit Edition2.0Microsoft Windows Server 2003 Enterprise Edition2.0Microsoft Windows Server 2003 Datacenter Edition2.0Microsoft Windows 2000 Server2.0Microsoft Windows 2000 Professional2.0Microsoft Windows 2000 Datacenter Server2.0Microsoft Windows 2000 Advanced Server2.064-bit Enabled AIX4.3AIX4.3* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed. Type:Usage NotePriority:Date Modified:2010-06-16 16:28:50Date Created:2007-04-19 14:42:50 This content is pres