Crawler crashes on query to GraphDB

[ddeboer]

2023-11-20 19:33:18.015	
  erroredSysCall: undefined
2023-11-20 19:33:18.015	
  code: 'ECONNRESET',
2023-11-20 19:33:18.015	
  errno: 'ECONNRESET',
2023-11-20 19:33:18.014	
  type: 'system',
2023-11-20 19:33:18.014	
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
2023-11-20 19:33:18.014	
    at endReadableNT (node:internal/streams/readable:1408:12)
2023-11-20 19:33:18.014	
    at Socket.emit (node:events:526:35)
2023-11-20 19:33:18.014	
    at Socket.socketOnEnd (node:_http_client:519:9)
2023-11-20 19:33:18.014	
    at ClientRequest.emit (node:events:514:28)
2023-11-20 19:33:18.014	
    at ClientRequest.<anonymous> (file:///app/node_modules/node-fetch/src/index.js:108:11)
2023-11-20 19:33:18.014	
FetchError: request to http://graphdb/repositories/registry/statements?subj=%3Chttps%3A%2F%2Farchief.nl%2Fid%2Fdatacatalog%2Ftoegang%3E&context=%3Chttps%3A%2F%2Fdemo.netwerkdigitaalerfgoed.nl%2Fregistry%2Fregistrations%3E failed, reason: socket hang up
2023-11-20 19:33:18.014	

2023-11-20 19:33:18.014	
			       ^
2023-11-20 19:33:18.014	
			reject(new FetchError(`request to ${request.url} failed, reason: ${error.message}`, 'system', error));
2023-11-20 19:33:18.014	
file:///app/n

Socket hang up means GraphDB did not respond in time. GraphDB reports nothing at this point in time.

Executing the request manually works, but that’s not during the pressure that a crawl may be putting on GraphDB:

DELETE http://triplestore.netwerkdigitaalerfgoed.nl/repositories/registry/statements?subj=<https://archief.nl/id/datacatalog/toegang>&context=<https://demo.netwerkdigitaalerfgoed.nl/registry/registrations>

HTTP/1.1 204 
Date: Mon, 20 Nov 2023 18:58:36 GMT
Connection: keep-alive
Vary: Accept-Encoding
Cache-Control: no-store
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Content-Language: en-US
Strict-Transport-Security: max-age=15724800; includeSubDomains

<Response body is empty>

Response code: 204; Time: 360ms (360 ms); Content length: 0 bytes (0 B)