I get this error (see below) repeated in the linstor error-reports list output every 2 hours or so. This has been this way since I’ve been using my 2 node ProxmoxVE w/rpi tie-breaker cluster. I’ve just been ignoring it, since everything appears to be working fine. I don’t see any issue other than a periodic error-report.
My guess is that this is coming from the proxmox side, and linbit doesn’t handle this API call. I’m not too familiar with the guts of the code here, but when trying to find anything on “QuerySpaceTracking” on the web I came up empty. I’m wondering if anyone else is seeing this, particularly those running this kind of setup with proxmox on 2 nodes, and 1 node Raspberry PI as the tie-breaker. @proxmeup I think you have a similar setup.
I just noticed, this only gets reported with Node: pve-rpi1, which is the RPi node. I wonder if that helps narrow it down. The RPi is a tiebreaker for all my storage-pools, except one which is where I have the linstor-db replicated. The content is small enough, and I wanted the data on all three nodes, for the highest level of HA, and speed is not a concern for me on this pool.
As I’m typing more ideas pop into my head, I wonder if the QuerySpaceTracking is being sent to all three nodes, but the rpi node can’t handle it because it is the only one not running proxmox, or using the binaries from the proxmox/linbit repos. Just a guess, I need to confirm all this.
Any pointers would be appreciated.
root@pve4:~# linstor error-reports show 67AB5B3F-BDD94-000251
ERROR REPORT 67AB5B3F-BDD94-000251
============================================================
Application: LINBIT® LINSTOR
Module: Satellite
Version: 1.30.2
Build ID: 9b7fae3f07c1017b5de4f476d2c57491728aefbe
Build time: 2024-12-18T15:44:05+00:00
Error time: 2025-03-04 09:36:44
Node: pve-rpi1
Thread: MainWorkerPool-3
Access context information
Identity: PUBLIC
Role: PUBLIC
Domain: PUBLIC
Peer: 10.12.13.24:42972
============================================================
Reported error:
===============
Category: LinStorException
Class name: LinStorException
Class canonical name: com.linbit.linstor.LinStorException
Generated at: Method 'callApi', Source file 'CommonMessageProcessor.java', Line #445
Error message: Non-existent API 'QuerySpaceTracking' called by the client
Error context:
The request was received on connector service 'NetComService' of type 'NetComService'
ErrorContext:
Description: The API call 'QuerySpaceTracking' cannot be executed.
Cause: The specified API does not exist
Correction: - Correct the client application to call a supported API
- Load the API module required by the client application into the server
Details: The API call name specified by the client was:
QuerySpaceTracking
Call backtrace:
Method Native Class:Line number
callApi N com.linbit.linstor.proto.CommonMessageProcessor:445
handleDataMessage N com.linbit.linstor.proto.CommonMessageProcessor:293
doProcessInOrderMessage N com.linbit.linstor.proto.CommonMessageProcessor:245
lambda$doProcessMessage$4 N com.linbit.linstor.proto.CommonMessageProcessor:230
subscribe N reactor.core.publisher.FluxDefer:46
subscribe N reactor.core.publisher.Flux:8773
onNext N reactor.core.publisher.FluxFlatMap$FlatMapMain:427
drainAsync N reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber:453
drain N reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber:724
onNext N reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber:256
drainFused N reactor.core.publisher.SinkManyUnicast:319
drain N reactor.core.publisher.SinkManyUnicast:362
tryEmitNext N reactor.core.publisher.SinkManyUnicast:237
tryEmitNext N reactor.core.publisher.SinkManySerialized:100
processInOrder N com.linbit.linstor.netcom.TcpConnectorPeer:418
doProcessMessage N com.linbit.linstor.proto.CommonMessageProcessor:228
lambda$processMessage$2 N com.linbit.linstor.proto.CommonMessageProcessor:165
onNext N reactor.core.publisher.FluxPeek$PeekSubscriber:185
runAsync N reactor.core.publisher.FluxPublishOn$PublishOnSubscriber:440
run N reactor.core.publisher.FluxPublishOn$PublishOnSubscriber:527
call N reactor.core.scheduler.WorkerTask:84
call N reactor.core.scheduler.WorkerTask:37
run N java.util.concurrent.FutureTask:317
run N java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask:304
runWorker N java.util.concurrent.ThreadPoolExecutor:1144
run N java.util.concurrent.ThreadPoolExecutor$Worker:642
run N java.lang.Thread:1583
END OF ERROR REPORT.