Closed cedricdcc closed 3 months ago
The Mint transport error
s are thrown in identifier
and dispatcher
on completion of each request to mu-cl-resources
, which by default is configured to do HTTP connection reuse. The error comes up each time a TCP connection is closed without further consequences.
During today's meeting we found that -for some still to-be-determinded reason- the ldes-consumer-manager
didn't function properly on the Windows machine Cedric tested with. Each time the Python Docker library tries to pull the ldes consumer image the WSGI worker crashes and another one is respawned. Running the service in development mode fixes the problem for now.
No LDES feed is being harvested by the vocabserver-app.
The feeds that were tested for this were:
All of the above for the build that redpencil has but also the build-images locally from the vocabserver-app as the ghcr.io images do not complete this task succesfully.
Current investigation of the logs from the docker-stack point to a mint transport error coming from the semtech/mu-identifier image