-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
[supervisor][mutilasic] parseDatabaseConfig error and sonic-db-cli fails to set CONFIG_DB_INITIALIZED #13740
Comments
@qiluo-msft, can you take a look at this issue? |
Here is the code from https://github.com/sonic-net/sonic-buildimage/blob/master/files/build_templates/docker_image_ctl.j2#L236
In above code, '$SONIC_DB_CLI CONFIG_DB SET "CONFIG_DB_INITIALIZED" "1"' will failed with following error: Which means the database config file generated incorrectly. @mlok-nokia, do you mean this issue still exist after PR #13207? |
No. I have not seen it with the PR#13207. I thought PR#13207 may also fix this issue also |
When config file incorrect, both c++ version and python version will crash with exception: admin@vlab-08:~$ sonic-db-cli -n asic0 PING admin@vlab-08: I think here is an issue: the c++ version crash will generate core dump, and python version crash will not, will improve c++ version to not generate core dump. However, this issue caused by incorrect database config file, will be fixed by PR #13207 |
Description
On supervisor card with multiasic, sonic-db-cli fails to set the "CONFIG_DB_INITIALIZED" after configuration is loaded on an asic instance database. This causes all show commands hung. The issue could be related to the issue #12047. But this fails on the parseDatabaseConfig while the previous issue fails on the database_config.json not found.
Steps to reproduce the issue:
This is an intermittent issue. The test case reboots the system three times. The issue occurs on the third time. The following log is shown
Describe the results you received:
All show commands hung and the following log are shown in syslog.
Describe the results you expected:
Show command should work and load config should be ok.
Output of
show version
:Issues are seen on the latest code.
Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: