ERROR error rsp for use db, error:Database not exist, dbFName:log
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 25.1k
- Forks
- 5k
- Avg merge
- 4d 59m
- Merged PRs (30d)
- 7
Description
Bug Description
使用TDinsight进行监控,页面能正常打开;
但是taosKeeper启动后,日志一直报数据库不存在,实际上log库已存在;
Environment (please complete the following information):
TDengine Version 3.0.4.1
ERROR LOG
06/25 10:36:15.326269 00009765 UTL ERROR SML smlBuildCol error col not same count
06/25 10:36:15.326927 00009765 QRY ERROR error rsp for use db, error:Database not exist, dbFName:log
06/25 10:36:30.325906 00009765 QRY ERROR error rsp for use db, error:Database not exist, dbFName:log
06/25 10:36:45.327102 00009770 QRY ERROR error rsp for use db, error:Database not exist, dbFName:log
Additional Context
taos> show databases;
name |
information_schema |
performance_schema |
log |
test |
pdtb |
pdt |
Query OK, 6 row(s) in set (0.001995s)
taos> use log;
Database changed.
taos> show stables;
stable_name |
logs |
taosadapter_restful_http_re... |
log_dir |
keeper_monitor |
dnodes_info |
data_dir |
taosadapter_system_mem_percent |
log_summary |
m_info |
vnodes_role |
cluster_info |
taosadapter_restful_http_re... |
temp_dir |
grants_info |
taosadapter_system_cpu_percent |
vgroups_info |
d_info |
taosadapter_restful_http_re... |
taosadapter_restful_http_re... |
Query OK, 19 row(s) in set (0.002146s)
taos> select * from cluster_info limit 3;
ts | first_ep | first_ep_dnode_id | version | master_uptime | monitor_interval | dbs_total | tbs_total | stbs_total | dnodes_total | dnodes_alive | mnodes_total | mnodes_alive | vgroups_total | vgroups_alive | vnodes_total | vnodes_alive | connections_total | topics_total | streams_total | protocol | cluster_id |
2023-06-20 10:09:36.856 | cdh3:6030 | 2 | 3.0.4.1 | 31.97222 | 30 | 4 | 10835 | 22 | 3 | 3 | 3 | 3 | 22 | 22 | 26 | 26 | 47 | 0 | 0 | 1 | 167695581068298336 |
2023-06-20 10:10:06.872 | cdh3:6030 | 2 | 3.0.4.1 | 31.97222 | 30 | 4 | 10882 | 22 | 3 | 3 | 3 | 3 | 22 | 22 | 26 | 26 | 47 | 0 | 0 | 1 | 167695581068298336 |
2023-06-20 10:10:36.889 | cdh3:6030 | 2 | 3.0.4.1 | 31.97222 | 30 | 4 | 10882 | 22 | 3 | 3 | 3 | 3 | 22 | 22 | 26 | 26 | 47 | 0 | 0 | 1 | 167695581068298336 |
Query OK, 3 row(s) in set (0.005818s)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by reproducing the taosKeeper use-log failure on TDengine 3.0.4.1 and compare it with the successful taos shell commands shown. Done means identifying the cause of the false missing-database error and adding a regression check for this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100