Out Error Packets

Sign in Pricing Blog Support Search GitHub got packets out of order mysql This repository Watch 424 Star 7,866 Fork 1,268 mysql nodejs mysqljs/mysql Code Issues 92 Pull requests 18 Projects 0 Wiki Pulse Graphs New issue Error: Packets out of order. Got: 1 Expected: 2 #1363 Open adrianseeley opened this Issue Mar 2, 2016 · 23 comments Projects None yet Labels needs investigation Milestone No milestone Assignees dougwilson 6 participants adrianseeley commented Mar 2, 2016 I'm trying to do multi-row inserts using: sql.query('INSERT INTO fx (t, s, o, h, l, c) VALUES ?', [values], function (err) { I get: Error: Packets out of order. Got: 1 Expected: 2 at Parser.write (C:\Users\Admin\Desktop\fx\node_modules\mysql\lib\protocol\Parser.js:39:19) at Protocol.write (C:\Users\Admin\Desktop\fx\node_modules\mysql\lib\protocol\Protocol.js:39:16) at Socket. (C:\Users\Admin\Desktop\fx\node_modules\mysql\lib\Connection.js:96:28) at Socket.emit (events.js:107:17) at readableAddChunk (_stream_readable.js:163:16) at Socket.Readable.push (_stream_readable.js:126:10) at TCP.onread (net.js:538:20) -------------------- at Pool.query (C:\Users\Admin\Desktop\fx\node_modules\mysql\lib\Pool.js:191:23) at non_recurse_l (C:\Users\Admin\Desktop\fx\fx_to_db.js:50:6) at recurse_d (C:\Users\Admin\Desktop\fx\fx_to_db.js:67:9) at Object. (C:\Users\Admin\Desktop\fx\fx_to_db.js:70:8) at Module._compile (module.js:460:26) at Object.Module._extensions..js (module.js:478:10) at Module.load (module.js:355:32) at Function.Module._load (module.js:310:12) at Function.Module.runMain (module.js:501:10) at startup (node.js:129:16) As my stack trace, I did some playing around, and inserting 1000 or so rows works perfectly fine in a single query, but trying to insert 100k or even 1m starts throwing packets out of order errors. Package version from NPM: 2.10.2 MySql version: MySQL Workbench Community (GPL) for Windows version 6.3.6 CE build 511 (64 bit) dougwilson added the needs inv

Sign in Pricing Blog Support Search GitHub This repository Watch 424 Star 7,866 Fork 1,268 mysqljs/mysql Code Issues 92 Pull requests 18 Projects 0 Wiki Pulse Graphs New issue Error: Packets out of order. Got: 0 Expected: 2 #844 Closed pornel opened this Issue Jun 6, 2014 · 7 comments Projects None yet Labels needs investigation Milestone No milestone Assignees dougwilson 4 participants pornel commented Jun 6, 2014 Once in a while I'm seeing this error thrown: at Parser._trackAndVerifyPacketNumber (node_modules/mysql/lib/protocol/Parser.js:322:15) at Parser.write (node_modules/mysql/lib/protocol/Parser.js:40:12) at Protocol.write (node_modules/mysql/lib/protocol/Protocol.js:37:16) at Socket. (node_modules/mysql/lib/Connection.js:75:28) at Socket.EventEmitter.emit (events.js:107:17) at readableAddChunk (_stream_readable.js:159:16) at Socket.Readable.push (_stream_readable.js:126:10) at TCP.onread (net.js:514:20) https://github.com/mysqljs/mysql/issues/1363 I'm running MySQL 5.5.18 and node v0.11.12. I'm using connection pools. Oddly, the error is thrown long after my app finishes querying data and responds to the request. Is that a problem I should be worried about? Incompatibility or maybe just a network error? Is it possible to catch that error and handle it gracefully? (other than via a domain) dougwilson added the needs investigation label Jun 6, 2014 dougwilson https://github.com/mysqljs/mysql/issues/844 commented Jun 6, 2014 Is that a problem I should be worried about? Incompatibility or maybe just a network error? It usually indicates a compatibility issue with the server and the packets it is exchanging with the client. It would be awesome if you were able to distill the error down to a specific sequence or calls. You always included the MySQL version number, which is a good start :) Is it possible to catch that error and handle it gracefully? (other than via a domain) Somehow these throws get into the code base. It should not be doing that, so I'll release a patch that makes it catch-able. 👍 1 dougwilson self-assigned this Jun 6, 2014 pornel commented Jun 6, 2014 Do you have a packet logging facility in the library? If I could enable some extra logging and give you the log that'd be great. On a high level I don't do anything interesting with the library (only simple CRUD) and the error doesn't seem to be triggered by any particular query. dougwilson commented Jun 6, 2014 Do you have a packet logging facility in the library? If I could enable some extra logging and give you the log that'd be great. Oh, sorry. S

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of http://unix.stackexchange.com/questions/116686/packet-loss-with-rx-error-packets this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/12027-53.html _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's out error how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Packet loss with RX error packets up vote 2 down vote favorite I am seeing packet loss from all my blade servers within the HP Blade C7000 enclosure. # ping 192.168.2.140 PING 192.168.2.140 (192.168.2.140) 56(84) bytes of data. 64 bytes from 192.168.2.140: icmp_seq=1 out error packets ttl=64 time=0.210 ms 64 bytes from 192.168.2.140: icmp_seq=2 ttl=64 time=0.185 ms 64 bytes from 192.168.2.140: icmp_seq=4 ttl=64 time=0.206 ms 64 bytes from 192.168.2.140: icmp_seq=6 ttl=64 time=0.164 ms 64 bytes from 192.168.2.140: icmp_seq=7 ttl=64 time=0.210 ms 64 bytes from 192.168.2.140: icmp_seq=8 ttl=64 time=0.213 ms 64 bytes from 192.168.2.140: icmp_seq=9 ttl=64 time=0.213 ms --- 192.168.2.140 ping statistics --- 9 packets transmitted, 7 received, 22% packet loss, time 8000ms rtt min/avg/max/mdev = 0.164/0.200/0.213/0.018 ms # ping 192.168.2.165 PING 192.168.2.165 (192.168.2.165) 56(84) bytes of data. 64 bytes from 192.168.2.165: icmp_seq=1 ttl=64 time=0.990 ms 64 bytes from 192.168.2.165: icmp_seq=3 ttl=64 time=0.204 ms 64 bytes from 192.168.2.165: icmp_seq=4 ttl=64 time=0.165 ms 64 bytes from 192.168.2.165: icmp_seq=5 ttl=64 time=0.168 ms --- 192.168.2.165 ping statistics --- 6 packets transmitted, 4 received, 33% packet loss, time 5001ms rtt min/avg/max/mdev = 0.165/0.381/0.990/0.352 ms $ /sbin/ifconfig eth0 Link encap:Ethernet HWaddr E4:11:5B:D0:36:B0 inet addr:192.168.2.163 Bcast:192.168.2.255 Mask:255.255.255.192 inet6 addr: fe80::e611:5bff:fed0:36b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:44022 errors:29632 dropped:0 overruns:0 frame:10025 TX packets:42694 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4345443 (4.1 MiB) TX bytes:4549025 (4.3 MiB) $ netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-

Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Troubleshooting Switch Port and Interface Problems Download Print Available Languages Download Options PDF (108.2 KB) View with Adobe Reader on a variety of devices Updated:Apr 03, 2009 Document ID:12027 Contents Introduction Prerequisites Requirements Components Used Conventions Physical Layer Troubleshooting Using the LEDs to Troubleshoot Check the Cable and Both Sides of the Connection Ethernet Copper and Fiber Cables Gigabit Ethernet Troubleshooting Connected vs Notconnected Most Common Port and Interface Troubleshooting Commands for CatOS and Cisco IOS Understanding Specific Port and Interface Counter Output for CatOS and Cisco IOS Show Port for CatOS and Show Interfaces for Cisco IOS Show Mac for CatOS and Show Interfaces Counters for Cisco IOS Show Counters for CatOS and Show Counters Interface for Cisco IOS Show Controller Ethernet-Controller for Cisco IOS Show Top for CatOS Common System Error Messages Error Messages on WS-X6348 Modules %PAGP-5-PORTTO / FROMSTP and %ETHC-5-PORTTO / FROMSTP %SPANTREE-3-PORTDEL_FAILNOTFOUND %SYS-4-PORT_GBICBADEEPROM: / %SYS-4-PORT_GBICNOTSUPP %AMDP2_FE-3-UNDERFLO %INTR_MGR-DFC1-3-INTR: Queueing Engine (Blackwater) [1]: FIC Fabric-A Received Unexpected Control Code Command Rejected: [Interface] not a Switching Port Common Port and Interface Problems Port or Interface Status is Disable or Shutdown Port or Interface Status is errDisable Port or Interface Status is Inactive Uplink Port or Interface Status is Inactive Deferred Counter on the Catalyst Switch Interface Starts Incrementing Intermittent Failure to set timer [value] from vlan [vlan no] Trunking Mode Mismatch Jumbos, Giants, and Baby Giants Cannot Ping End Device Using Set Port Host or Switchport Host to Fix Startup Delays Speed/Duplex, Autonegotiation, or NIC Issues Spanning Tree Loops UDLD: One-Way Link Deferred Frames (Out-Lost or Out-Discard) Software Problems Hardware Problems Input Errors on a Layer 3 Interface Connected to a Layer 2 Switchport Rapidly Incrementing Rx-No-Pkt-Buff Counter and Input Errors Understand Unknown Protocol Drops Trunking between a Switch and a Router Connectivity Issues due to Oversubscription Subinterfaces in SPA Modules Troubleshooting rxTotalDrops Troubleshoot Output Drops Last Input Never from the Output of Show interface Command Related Information Introduction This document is intended to help determine why a port or interface experiences pro