Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

Cannot connect to krd even after restart of the daemon #126

Closed
gae123 opened this issue Jun 18, 2017 · 5 comments
Closed

Cannot connect to krd even after restart of the daemon #126

gae123 opened this issue Jun 18, 2017 · 5 comments

Comments

@gae123
Copy link

gae123 commented Jun 18, 2017

Env: MacOS 10.12.5

I had everything working for a few days. Now I am getting the following. Maybe reboot will fix it but obviously i want to avoid that (in my last reboot my mac was up for 59 days!!). Any suggestions? Is there a log file somewhere?

$ kr restart
Restarted Kryptonite daemon.
$ kr me
Could not connect to Kryptonite daemon. Make sure it is running by typing "kr restart".
$ ps -efwww | grep kr
501 4303 1 0 8:41AM ?? 0:00.12 /usr/local/bin/krd
501 4306 69038 0 8:41AM ttys005 0:00.00 grep kr

@gae123
Copy link
Author

gae123 commented Jun 18, 2017

The problem has now gone away. I still do not see the notifications on my phone and the whole setup does not work but this might be unrelated. Was there any maintenance going on with your servers this morning?

@kcking
Copy link
Contributor

kcking commented Jun 18, 2017

Thank you for reporting.

Our servers were not down for maintenance as we use AWS SQS / AWS SNS which are maintained/replicated by AWS.

Please check the "system.log" tab in the "Console.app" application to see if krd is printing any error messages, this should explain why your phone is not receiving notifications.

@gae123
Copy link
Author

gae123 commented Jun 18, 2017

I see quite a few of these:

ERROR ▶ Push error: InvalidParameter: Invalid parameter: TargetArn Reason: An ARN must have at least 6 elements, not 1

ERROR ▶ Request timed out

ERROR ▶ evicting request

@kcking
Copy link
Contributor

kcking commented Jun 18, 2017 via email

@kcking
Copy link
Contributor

kcking commented Jun 18, 2017

Following up -- the issue was that the SNSEndpointARN in the persisted pairing somehow was set to "" on iOS. Since re-pairing fixed the issue, I am closing for now.

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

No branches or pull requests

2 participants