In our server, aitf had been working fine until yesterday, precisely at starting time s20191320000320. Now it fails every time.
Procesando s20191320000320
Configuring tasks...
Configuring tasks... done 2.5 seconds
Processing chunks... 0% (0/6)
ERROR: Failed: Process column 0, row 0.
+/home/lanotadm/cspp-geo-aitf-1.0.9beta/libexec/aitf-framework exited with
+signal 11 after 36.6 seconds. Command line:
+/home/lanotadm/cspp-geo-aitf-1.0.9beta/libexec/aitf-framework pcf/root.cfg
Processing chunks... 17% (1/6)
ERROR: Failed: Process column 0, row 4.
...
Processing chunks... 0% (0/6)
Processing chunks... 100% (6/6) FAILED 57.5 seconds
ERROR: Processing chunks: 6 tasks failed.
CRITICAL ERROR: Processing failed
I tried it in a less loaded server and it fails the same.
I am attaching the logs.
I will appreciate any help.
Best regards,
Alejandro Sierra, LANOT, UNAM
AITF failing after julian day 131
AITF failing after julian day 131
- Attachments
-
- sysinfo.log.gz
- (3.94 KiB) Downloaded 1146 times
-
- aitf.log.gz
- (1.42 KiB) Downloaded 1140 times
Re: AITF failing after julian day 131
Hello Alejandro,
I know we have already discussed this issue via email, but I wanted to post it to the forum for reference for others.
The original issue was due to outdated ancillary from an upstream provider. We do monitor the ancillary data and contact the data providers when we notice outages, but unfortunately it is out of our control when providers have problems.
Regarding the warnings, they can be misleading as it's just reporting that the AVHRR SST files for today are not yet available. I would suggest ignoring these warnings unless they are referring to AVHRR files that are 4+ days old, as that would indicate a major issue. We have made changes to prevent misleading warnings like this from occurring in the next release, as well as give a warning indicator only when there are issues that would impact processing.
If you (or anyone else reading this post) have additional questions, please feel free to respond to this post or email CSPP Geo Help support at csppgeo.issues@ssec.wisc.edu
Thanks,
~Jess
I know we have already discussed this issue via email, but I wanted to post it to the forum for reference for others.
The original issue was due to outdated ancillary from an upstream provider. We do monitor the ancillary data and contact the data providers when we notice outages, but unfortunately it is out of our control when providers have problems.
Regarding the warnings, they can be misleading as it's just reporting that the AVHRR SST files for today are not yet available. I would suggest ignoring these warnings unless they are referring to AVHRR files that are 4+ days old, as that would indicate a major issue. We have made changes to prevent misleading warnings like this from occurring in the next release, as well as give a warning indicator only when there are issues that would impact processing.
If you (or anyone else reading this post) have additional questions, please feel free to respond to this post or email CSPP Geo Help support at csppgeo.issues@ssec.wisc.edu
Thanks,
~Jess