-
Notifications
You must be signed in to change notification settings - Fork 109
Cannot connect to krd even after restart of the daemon #126
Comments
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? |
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 |
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 |
Ok thanks for checking. Could you please send an email to support@krypt.co
where we can continue debugging?
…On Sun, Jun 18, 2017 at 2:35 PM gae123 ***@***.***> wrote:
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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#126 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABSUU-zQunSCeuqmDL-GdpB3ZPIWL1ukks5sFW30gaJpZM4N9h58>
.
|
Following up -- the issue was that the |
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
The text was updated successfully, but these errors were encountered: