NICMx / FORT-validator

RPKI cache validator
MIT License
50 stars 24 forks source link

[1.5.0] Mode standalone sometimes generates no output #49

Closed dorpauli closed 3 years ago

dorpauli commented 3 years ago

Hello,

currently i run some tests with fort 1.5.0 and observe some unusual behaviour. On a Raspberry Pi 4 with 4 GB (raspberry pi os lite 64bit) i did every half an hour the validation run with fort --mode standalone --log.level debug --validation-log.enabled=true --validation-log.level warning --local-repository /home/pi/.rpki-cache --output.roa /home/pi/csv/$date.csv --tal /home/pi/tals. Most of the time it runs smoothly through the validation within 6 to 10 minutes. But sometimes (about 10 time within 2 days) there is an empty csv file and more often it generates the output 1-2 hours after the validation started. The Log shows different behaviour. Sometimes there are validation entries and sometimes not. Also a timeout occurs, when the output is empty.

I thought maybe it' related to the SBC and so i did a one day test on a powerful server (Ubuntu 20.04). In this one day, there were only 2 empty files and no delay on the output generation. So it's kind of related to the raspberry, but i think the 2 empty files are still problematic.

Now i upload some log outputs of the different cases(date always means the start time CET). Raspberry pi 4 empty output: 2021-04-02_16-00.log 2021-04-02_17-30.log 2021-04-03_00-00.log 2021-04-03_04-00.log 2021-04-04_05-30.log

Raspberry pi 4 validate over hours but full output: 2021-04-02_12-30.log 2021-04-02_13-30.log 2021-04-02_19-30.log 2021-04-03_09-30.log

Ubuntu Server no output: 2021-04-07_00-00.log 2021-04-07_07-30.log