"Scheduled SON messages stop displaying a few minutes after the replay finishes. " - message from SON witness (Sophie) #223

New issue

Closed

opened 2021-12-09 02:19:24 +00:00 by hbelakon · 5 comments

hbelakon commented

2021-12-09 02:19:24 +00:00

(Migrated from gitlab.com)

https://t.me/PeerplaysDiscussions/110948

And with that list posted again we keep going in circles.
Just read the rest of the discussion in rocket chat.

It ends with me posting the following:

"Now gotten to the point where it shows the Scheduled SON messages but it exits a few minutes after the replay finishes.
These are the last lines in the log."

"This is the config.ini I'm using"

No replies from PBSA since september.
I also sent more logs and info about the segfault in a private message.
No reply to those either.

https://t.me/PeerplaysDiscussions/110948 And with that list posted again we keep going in circles. Just read the rest of the discussion in rocket chat. It ends with me posting the following: "Now gotten to the point where it shows the Scheduled SON messages but it exits a few minutes after the replay finishes. These are the last lines in the log." <Logfile> "This is the config.ini I'm using" <CONFIG> No replies from PBSA since september. I also sent more logs and info about the segfault in a private message. No reply to those either.

hbelakon commented

2021-12-09 02:19:24 +00:00

(Migrated from gitlab.com)

assigned to @prandnum

hbelakon commented

2021-12-09 13:41:26 +00:00

(Migrated from gitlab.com)

changed title from "Scheduled SON messages {-exits-} a few minutes after the replay finishes. " - message from SON witness (Sophie) to "Scheduled SON messages {+stop displaying+} a few minutes after the replay finishes. " - message from SON witness (Sophie)

changed title from **"Scheduled SON messages {-exits-} a few minutes after the replay finishes. " - message from SON witness (Sophie)** to **"Scheduled SON messages {+stop displaying+} a few minutes after the replay finishes. " - message from SON witness (Sophie)**

serkixenos commented

2021-12-09 13:57:25 +00:00

(Migrated from gitlab.com)

@hbelakon
There are four related tickets for this problem.

https://gitlab.com/PBSA/peerplays/-/issues/51
https://gitlab.com/PBSA/peerplays/-/issues/58
https://gitlab.com/PBSA/peerplays/-/issues/168
https://gitlab.com/PBSA/peerplays/-/issues/185

The fix is provided on 5th October
9b3c84c2bd

Two open tickets are related to Mainnet test. As we did not make a release yet, the fix is not available on master branch. It will be once we make a release.

@hbelakon There are four related tickets for this problem. https://gitlab.com/PBSA/peerplays/-/issues/51 https://gitlab.com/PBSA/peerplays/-/issues/58 https://gitlab.com/PBSA/peerplays/-/issues/168 https://gitlab.com/PBSA/peerplays/-/issues/185 The fix is provided on 5th October https://gitlab.com/PBSA/peerplays/-/commit/9b3c84c2bdd0f251140b08cd0a0683e1abafdd5e Two open tickets are related to Mainnet test. As we did not make a release yet, the fix is not available on master branch. It will be once we make a release.

hbelakon commented

2021-12-09 19:53:47 +00:00

(Migrated from gitlab.com)

@serkixenos thanks for clarification. I will move it to "complete" then , and close OK ?

hbelakon commented

2021-12-09 19:54:01 +00:00

(Migrated from gitlab.com)

changed the status to Resolved by closing the incident

changed the status to **Resolved** by closing the incident

hbelakon (Migrated from gitlab.com) closed this issue

2021-12-09 19:54:01 +00:00