taosdata
ERROR 0x17da3 error happens, code:-2147473920 - syntax error near,QID:0x1
Bug Description We are reproducing a known restart failure issue and found that taosd always outputs error logs. Although it is uncertain whether these logs are directly related to our problem, we still need to pay attention to them
Environment (please complete the following information):
- OS: [e.g. ubuntu.Docker arm64]
- Memory 2G, CPU 4C, current Disk Space 6G
- TDengine Version [e.g. 3.3.5.2]
Additional Context
we use schemaless insert data
history_shadow_test_product_v2,realm_device_id=123_device_0 P2=9.125961f32,P4=-15.589568f32,P5=12.123546f32,P6=-20.393284f32,P7=30.948837f32,P9=-35.057632f32,P10=28.355639f32,P1=-29.271955f32,P3=-12.592279f32,P8=-28.927814f32 1740707524397
We have confirmed that this statement is not a significant issue.
taos Docker is aways format error log
02/28 02:00:54.927916 00000292 C TSC connecting to server, numOfEps:2 inUse:0 user:root db:(null) key:root:dcc5bed04851fec854c035b2e40263b6:(null):0
02/28 02:00:54.927965 00000292 C TSC ep:0, edge-shadow-database:6030
02/28 02:00:54.927974 00000292 C TSC ep:1, edge-shadow-database:6030
02/28 02:00:54.929061 00000292 C TSC WARN failed to remove request from hash, code:Invalid parameters
02/28 02:00:54.931676 00000049 C TSC ERROR 0x17da3 error happens, code:-2147473920 - syntax error near,QID:0x1
02/28 02:01:56.774598 00000049 C TSC connecting to server, numOfEps:2 inUse:0 user:root db:(null) key:root:dcc5bed04851fec854c035b2e40263b6:(null):0
02/28 02:01:56.774618 00000049 C TSC ep:0, edge-shadow-database:6030
02/28 02:01:56.774626 00000049 C TSC ep:1, edge-shadow-database:6030
02/28 02:01:56.775695 00000049 C TSC WARN failed to remove request from hash, code:Invalid parameters
02/28 02:01:56.778414 00000292 C TSC ERROR 0x17da5 error happens, code:-2147473920 - syntax error near,QID:0x1
what is the " known restart failure issue " , any other issue related to this?
In our actual production environment, we encountered a situation where taosd failed to start after a physical machine reboot. We would like to see if this issue can be reproduced. I believe any anomalies should be reported to assist you in troubleshooting the issue.
we encountered a situation where taosd failed to start after a physical machine reboot.
I want to see the detail about description above
for example the whole startup log ( taosdlog)
The error logs mentioned above are not problematic, right? I am still in the process of reproducing the restart issue. Unfortunately, the on-site logs have been lost.
nice finger but we do need that startup log
once you reproduced that , just send the log to us .
There are 600,000 records in the database. After I restarted the db power supply during the stress test, the data could not be written to the db normally. The taos_adapter was maintaining a relatively high load. Taosd was not restarted either, and the db service components did not generate new logs. I don't know how to analyze this problem. But the performance shows that the db service is abnormal.
load from top
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 36 root 20 0 3693832 105568 24056 S 230.2 5.2 152:42.92 taosadapter 35 root 20 0 2861612 136072 16216 S 32.9 6.8 21:18.71 taosd
view data from taos
` taos> use iot_test; Database changed.
taos> select count() from history_shadow_test_product_v2; count() |
6423536 |
Query OK, 1 row(s) in set (0.672022s)
taos> select count() from history_shadow_test_product_v2; count() |
6423536 |
Query OK, 1 row(s) in set (0.858403s) `
log from taosd ` 3/04 12:48:48.981468 00000072 C MND vgId:1, trans:28502, start to send rsp, stage:finished failedTimes:0 code:0x0 03/04 12:48:48.981629 00000072 C MND vgId:1, trans:28502, start to lock rpc array 03/04 12:48:48.981683 00000072 C MND vgId:1, trans:28502, release transaction 03/04 12:48:48.981701 00000072 C MND vgId:1, deleteFp:0x557995c578, type:trans 03/04 12:48:48.981714 00000072 C MND trans:28502, perform delete action, row:0x7f1c112f9c stage:finished callfunc:1, stopFunc:0 03/04 12:48:54.012462 00000126 C VND vgId:62, propose vnode commit 03/04 12:48:54.013812 00000126 C VND vgId:62, commit at version 4991997 03/04 12:48:54.017679 00000126 C VND vgId:62, vnode info is saved, fname:/var/lib/taos/vnode/vnode62/vnode_tmp.json replica:1 selfIndex:0 changeVersion:1 03/04 12:48:54.018687 00000126 C VND vgId:62, vnode async commit done, commitId:721 term:14 applied:4991997 03/04 12:48:54.018712 00000225 C VND vgId:62, start to commit, commitId:721 version:4991997 term: 14 03/04 12:48:54.159320 00000225 C WAL vgId:62, save meta file: /var/lib/taos/vnode/vnode62/wal/meta-ver.tmp, firstVer:4985074, lastVer:4991997 03/04 12:48:54.159950 00000225 C WAL vgId:62, remove old meta file: /var/lib/taos/vnode/vnode62/wal/meta-ver2172 03/04 12:48:54.165823 00000225 C WAL vgId:62, save meta file: /var/lib/taos/vnode/vnode62/wal/meta-ver.tmp, firstVer:4985074, lastVer:4991997 03/04 12:48:54.166290 00000225 C WAL vgId:62, remove old meta file: /var/lib/taos/vnode/vnode62/wal/meta-ver2173 03/04 12:48:54.166871 00000225 C TSD vgId:62 begin vnode-commit task on file set:30227
new log file
==================================================
new log file
==================================================
new log file
==================================================
new log file
==================================================
new log file
================================================== `