Skip to content
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

crash with unhandled entity type 7 #76

Closed
BenCastricum opened this issue Nov 30, 2022 · 6 comments
Closed

crash with unhandled entity type 7 #76

BenCastricum opened this issue Nov 30, 2022 · 6 comments

Comments

@BenCastricum
Copy link

Starting 29th of Nov at 13:00 CET our dockerized rpki-client no longer produces any files.

Docker logging:

2022-11-30T08:30:50.064813443Z rpki-client: rpki-rps.arin.net/repository/8a848ade7fb71aa9017fdd9c5dd324c7/0/EB1DD8AA3E2B6864E06379C751DBFFFCC6418350.mft: no valid mft available
2022-11-30T08:30:50.100377723Z rpki-client: rpki-rps.arin.net/repository/8a848ade7fb71aa901800003287f4402/0/2BF7605B8927C87448B3B294A8B61D8E983248E0.mft: no valid mft available
2022-11-30T08:30:50.287559589Z rpki-client: rpki-rps.arin.net/repository/8a848adf7fb722e9017ffead9f534ac5/0/BFA2750976CA07F56A68976B0F01EB862F17C3B3.mft: no valid mft available
2022-11-30T08:31:05.479810276Z rpki-client: unhandled entity type 7
2022-11-30T08:31:05.566212488Z rpki-client: poll[0]: bad fd
2022-11-30T08:31:05.566249456Z rpki-client: write[0]: Broken pipe
2022-11-30T08:31:05.566256810Z rpki-client: parser process exited abnormally
2022-11-30T08:31:05.571419260Z rpki-client: not all files processed, giving up
2022-11-30T08:31:05.966877368Z rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.4]

We are still using rpki-client 7.9

sudo docker inspect --format='{{index .RepoDigests 0}}' rpki/rpki-client:7.9
rpki/rpki-client@sha256:81f6c17b508e5184185a15e33f6f9f578d454ed6e78d67fa78c9182bf5f911ce
@cjeker
Copy link
Member

cjeker commented Nov 30, 2022

This problem has been fixed in the 8.0 release.
It was caused by improper handling of .asa files. It seems a CA added a .asa file triggering this bug.

@job
Copy link
Member

job commented Nov 30, 2022

However 8.0 had this issue blocking some folks from using it rpki-client/rpki-client-openbsd@ec0949c

@cjeker
Copy link
Member

cjeker commented Nov 30, 2022

In that case a quick fix would be to downgrade to 7.8 until 8.1 is out. It does not have this problem with .asa files.

@robert-scheck
Copy link
Contributor

robert-scheck commented Nov 30, 2022

However 8.0 had this issue blocking some folks from using it rpki-client/rpki-client-openbsd@ec0949c

rpki-client/rpki-client-container@a1eed1d was added to a re-tagged 8.0 container image (including a fixed rsync) a month ago, technically nothing should prevent from using the latest container image tag anymore.

@BenCastricum
Copy link
Author

Thanks, we are running 7.8 and the latest 8.0 on our test environment at the moment. If no problems occur we will switch back to 7.8. We prefer a solid tag for a release, and 7.8 has already done some time in our production environment.

@cjeker
Copy link
Member

cjeker commented Dec 14, 2022

rpki-client 8.2 finally was released which has both the .asa file exception and the proxy port handling fixed.
So this should be solved for good now.

@cjeker cjeker closed this as completed Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants