From bdbd394fede27def1728f7bc2e099cd50c5953b1 Mon Sep 17 00:00:00 2001 From: yengliong Date: Thu, 1 Aug 2024 10:18:23 +0800 Subject: [PATCH] Update doc for dispatcher database troubleshooting (#534) Signed-off-by: yengliong --- docs/In-Band Manageability Developer Guide.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/docs/In-Band Manageability Developer Guide.md b/docs/In-Band Manageability Developer Guide.md index 975c96669..965855c6f 100644 --- a/docs/In-Band Manageability Developer Guide.md +++ b/docs/In-Band Manageability Developer Guide.md @@ -836,3 +836,24 @@ Example of inbm-update-log.log: } ``` + + +### Dispatcher-Agent Failed to Get Element from Database +There will be an issue if the dispatcher agent is accessing the database with the old database structure. +The error log would look like: + +```text +dispatcher.dispatcher_exception.DispatcherException: Error in getting the all single schedules from database: no such column: ssj.task_id +``` + +The workaround is to remove the old database and restart the dispatcher agent. + +Step 1: +```shell +sudo rm /var/intel-manageability/scheduler.db +``` + +Step 2: +```shell +sudo systemctl restart inbm-dispatcher +``` \ No newline at end of file