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

Invalid argument(s): Unsupported block type for private key: 17 #287

Closed
cconstab opened this issue Jan 27, 2023 · 4 comments
Closed

Invalid argument(s): Unsupported block type for private key: 17 #287

cconstab opened this issue Jan 27, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@cconstab
Copy link
Member

cconstab commented Jan 27, 2023

Describe the bug

When sending an at_talk message from @atgps01 to @atgps02 messages never arrive. When running with -v the following message appears in the log:-

'SEVERE|2023-01-27 09:09:43.059190| atTalk |Invalid argument(s): Unsupported block type for private key: 17'

This was the first time that these two atSigns communicated. This issue does NOT happen everytime in fact I have not seen it at all with other atSigns communicating.

But I also see no way to correct the error from a dev point of view.

Steps to reproduce

  1. First I run two at_talk commands to communicate between atgps01 and atgps02 then send message from atgps01
  2. Message is never received
  3. And then I run the same command but with -v and see the error message

Expected behavior

Never to have a miss managed key if that is what the issue is.

Screenshots

No response

Smartphones

code used is the nosync branch which uses the at_chops lib

https://github.com/atsign-foundation/at_talk/tree/nosync

Were you using an atApplication when the bug was found?

at_talk

Additional context

I was testing to ensure that newly created atSigns can communicate without a problem using chops and notification (this used to have other issues in that the RSA key was not in place)

@cconstab cconstab added the bug Something isn't working label Jan 27, 2023
@gkc
Copy link
Contributor

gkc commented Jan 27, 2023

@cconstab has either atSign been reset?

@cconstab
Copy link
Member Author

The error log is pretty brutal, here is a sample..

SEVERE|2023-01-27 09:51:11.602642| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.604640| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.607638| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.609641| atTalk |Invalid argument(s): Unsupported block type for private key: 17 

SEVERE|2023-01-27 09:51:11.613155| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.616157| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.619156| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.621663| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.624675| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.627676| atTalk |Invalid argument(s): Unsupported block type for private key: 17 

SEVERE|2023-01-27 09:51:11.631180| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.634187| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.638185| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.641185| atTalk |Invalid argument(s): Unsupported block type for private key: 17 

SEVERE|2023-01-27 09:51:11.645393| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.648395| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.650900| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.653906| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.656907| atTalk |Invalid argument(s): Unsupported block type for private key: 17 

SEVERE|2023-01-27 09:51:11.659906| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.662933| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.665938| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.668444| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.670958| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.673963| atTalk |Invalid argument(s): Unsupported block type for private key: 17 

SEVERE|2023-01-27 09:51:11.677008| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.680009| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.682518| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.685519| atTalk |Invalid argument(s): Unsupported block type for private key: 17

SEVERE|2023-01-27 09:51:11.688777| atTalk |Invalid argument(s): Unsupported block type for private key: 17 

@cconstab
Copy link
Member Author

So on a hunch I deleted the ~/.ai6bh/@atgps01 directory to force a resync and can now send stuff again.. If anyone needs/wants the deleted directory I have it..

@cconstab
Copy link
Member Author

Root cause found and reported here:

atsign-foundation/at_client_sdk#900

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants