search

trustification / trustify

Apache License 2.0
8 stars 15 forks source link

SIGSEGV on demo system #379

Closed ctron closed 2 weeks ago

ctron commented 1 month ago

After running for a bit, the trustify container is crashed with an exit code of 139, which should be SIGSEGV:

Jun 05 16:01:26 trustify podman[170427]: container "3af9906a614e9ed3ae1aa51fe46b160f54b11a855daba92d04dc497d5b0cfa34" exited with status code 139

The log shows this before restarting:

2024-06-05T16:09:08.974715Z  INFO run: trustify_module_importer::server: Starting run: cve    
2024-06-05T16:09:08.975052Z DEBUG run_sync: trustify_module_importer::server::common::walker::git: Starting run for: https://github.com/CVEProject/cvelistV5    
2024-06-05T16:09:08.975066Z  INFO run_sync: trustify_module_importer::server::common::walker::git: Cloning https://github.com/CVEProject/cvelistV5 into /wd/cve/https%3A%2F%2Fgithub.com%2FCVEProject%2FcvelistV5    
2024-06-05T16:09:08.984135Z  INFO run_sync: trustify_module_importer::server::common::walker::git: Already exists, opening ...    
2024-06-05T16:09:08.984386Z DEBUG run_sync:fetching updates: trustify_module_importer::server::common::walker::git: Fetching updates    
<RESTART>
2024-06-05T16:09:12.331348Z TRACE hyper_util::client::legacy::pool: checkout waiting for idle connection: ("https", trustify-sso.dentrassi.de)

That puts it into the area of libgit2, which is all C stuff.

ctron commented 1 month ago

400 might have solved this. Need to check after the next release.

ctron commented 2 weeks ago

Looks good on the demo system.