We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
今天升级7.7.2,重启服务报了两个错误,详见日志,请帮忙看看如何处理,谢谢
Dec 5 17:01:12 ecs-nightingale n9e: #033[0m#033[31;1m[4810.160ms] #033[33m[rows:32590]#033[35m ALTER TABLE `alert_his_event` ADD `original_tags` text COMMENT 'labels key=val,,k2=v2'#033[0m Dec 5 17:01:12 ecs-nightingale n9e: 2024-12-05 17:01:12.783355 ERROR ormx/ormx.go:67 #033[31;1m/home/runner/work/nightingale/nightingale/models/migrate/migrate.go:80 #033[35;1mError 1072: Key column 'last_eval_time' doesn't exist in table Dec 5 17:01:12 ecs-nightingale n9e: #033[0m#033[33m[0.092ms] #033[34;1m[rows:0]#033[0m CREATE INDEX `idx_last_eval_time` ON `role_operation`(`last_eval_time`) Dec 5 17:01:12 ecs-nightingale n9e: 2024-12-05 17:01:12.783383 ERROR migrate/migrate.go:81 failed to migrate table: Error 1072: Key column 'last_eval_time' doesn't exist in table
7.7.2,centos7,x86
The text was updated successfully, but these errors were encountered:
你这个日志怎么感觉串行了,role_operation 这个表原本也是不应该有 last_eval_time 字段的
Sorry, something went wrong.
这就是原始日志啊,不可能串行吧?
能复现吗,奇奇怪怪的嘞,role_operation 确实没有 last_eval_time
无法复现,重新启动n9e看不到这个报错了
No branches or pull requests
Question and Steps to reproduce
今天升级7.7.2,重启服务报了两个错误,详见日志,请帮忙看看如何处理,谢谢
Relevant logs and configurations
Version
7.7.2,centos7,x86
The text was updated successfully, but these errors were encountered: