Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invariant pattern "LiabilitiesMatchOffers" did not match any invariants #2264

Closed
FakeC0de opened this issue Sep 3, 2019 · 1 comment · Fixed by #2265
Closed

Invariant pattern "LiabilitiesMatchOffers" did not match any invariants #2264

FakeC0de opened this issue Sep 3, 2019 · 1 comment · Fixed by #2265
Assignees

Comments

@FakeC0de
Copy link

FakeC0de commented Sep 3, 2019

As what is said in the example .cfg file, I just used an expression like INVARIANT_CHECKS = ["LiabilitiesMatchOffers"], but when I trying to run stellar-core with this .cfg file, it exited with error info says there is no parament like "LiabilitiesMatchOffers":

2019-09-03T21:08:52.082 GCI6S [default FATAL] Got an exception: Invariant pattern 'LiabilitiesMatchOffers' did not match any invariants. Registered invariants are: AccountSubEntriesCountIsValid, BucketListIsConsistentWithDatabase, ConservationOfLumens, LedgerEntryIsValid, MinimumAccountBalance [ApplicationUtils.cpp:69]
2019-09-03T21:08:52.082 GCI6S [default FATAL] Please report this bug along with this log file if this was not expected [ApplicationUtils.cpp:70]

Someone told me that "IIRC" is the old name for the invariant, but this example file was updated 21 days ago? Is there anything in the example file that maybe need to be fixed?
My stellar-core's version is v11.4.0-2-g859fae62

@FakeC0de
Copy link
Author

FakeC0de commented Sep 6, 2019

Sorry to adding one more question, but I am trying to create an offer on the core, but when I try to check it on the stellar-core's database, I noticed that the selling_liabilities column and buying_liabilities column are all <null>, so I checked the Github's example, then here with this question. But after I followed the @jonjove 's request's changes and recompiled & reinstalled the stellar-core, the problem is still there. Is there any possible clue about this problem?
My configuration file for running core (one node, standalone mode) is like this:

HTTP_PORT=11626
PUBLIC_HTTP_PORT=true
RUN_STANDALONE=true

NETWORK_PASSPHRASE="Test OneNode Network ; Aug 2019"

INVARIANT_CHECKS = [".*"]

KNOWN_CURSORS=["HORIZON"]

NODE_SEED="SB4GP*****3XH6Z self"
NODE_IS_VALIDATOR=true

# Postgres DB URL
DATABASE="postgresql://dbname=stellar_node_db host=localhost user=user password=password"

COMMANDS=["ll?level=trace"]

FAILURE_SAFETY=0
UNSAFE_QUORUM=true

[QUORUM_SET]
THRESHOLD_PERCENT=100

VALIDATORS=["$self"]

[HISTORY.vs]
get="cp /tmp/stellar-core/history/vs/{0} {1}"
put="cp {0} /tmp/stellar-core/history/vs/{1}"
mkdir="mkdir -p /tmp/stellar-core/history/vs/{0}"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants