-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Orchagent crashes on start #46
Comments
It can easily reproduced by running the following command In recent version we see it a lot. Some containers are not started. Each time it is a different container. This has been found even without the new PR of single ONIE image. |
Attached logs in zip |
the logs show the syncd is doing a hard reinit, this happens when the database is not clear. The database is clear when swss start, but I do not see swss service has started. Do you have swss.service in /etc/systemd/system/? can you add syncd.service to be run after swss.service and try to reboot the box to see if the issue is addressed or not. |
Updated After in syncd.service:
After restart swss is not running:
This usually can be fixed with: |
Issue is no longer reproducible after flush DB commands were moved from syncd.service to swss.service in the following commit: |
HLD: show/clear ip/ipv6 arp/neighbors
Sonic-buildimage revision - c199614b69be65edfecc504f6fd3042dbc3d195c
Orchagent aborted with no error messages
Backtrace:
The text was updated successfully, but these errors were encountered: