graphprotocol / mission-control-indexer

Technical indexer documentation and infrastructure templates for the Mission Control testnet
21 stars 4 forks source link

CLI: [GraphQL] could not access status of transaction 0 #109

Closed saschagoebel closed 3 years ago

saschagoebel commented 3 years ago

When running a CLI command like

graph indexer rules set Qme2hDXrkBpuXAYEuwGPAjr6zwiMZV4FHLLBa3BHzatBWx decisionBasis never

the response is always

[GraphQL] could not access status of transaction 0

The same command worked without problems yesterday.

The indexer-agent logs don't show anything suspicious:

[2020-09-25 07:54:10.061 +0000] DEBUG (IndexerAgent/1 on 35272826f10a): POST / 200 181 - 9.136 ms
    component: "IndexerManagementServer"
[2020-09-25 07:56:33.260 +0000] DEBUG (IndexerAgent/1 on 35272826f10a): POST / 200 137 - 21.416 ms
    component: "IndexerManagementServer"
saschagoebel commented 3 years ago

Found the issue. Database Server Disk was full.