ssh-agent stopped working

I'm seeing this too (Mac, 1Password 8.9.11, Terminal.app):

sign_and_send_pubkey: signing failed for ED25519 "SSH Key" from agent: agent refused operation

In my case the issue seems to be because I use a Touch ID laptop with an external display and the lid closed. If I open the lid, quit/lock 1Password, and unlock using Touch ID then my SSH command works. I can then close the lid and it continues to work.

The clue for this was in the logs:

ERROR 2023-01-06T09:37:30.131 tokio-runtime-worker(ThreadId(4)) [1P:op-automated-unlock/src/lib.rs:295] Failed to authorize using system biometry: FailedToUnlockWithKeys(BiometryUnavailable)
INFO 2023-01-06T09:37:30.131 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-ssh-agent/src/lib.rs:460] Session was not authorized

I have also started seeing this issue and sent a diagnostic report of my own. What's strange is that this only appears to be happening on one particular git repo for me. All of my other git repos (same host, github.com) seem to work fine. I've tried restarting 1password and my computer to no avail. I've also tried recloning the repo to no avail. I am using Alacritty, tmux, and zsh on a fresh install of macOS.

The ticket number I got back is: #DMI-82239-715

Done. The support ID number I received is [#IFU-93959-615].

Hi ravron:

That would be helpful as well. Please follow the same steps but mention your username. 🙂

Jack

Jack_P_1P I am happy to do so as well, if you like. I am still experiencing the issue as described previously.

Hi @kudzuspaver:

I'd like to ask you to create a diagnostics report from your Mac:

Sending Diagnostics Reports (Mac)

Attach the diagnostics to an email message addressed to support+forum@1password.com.

With your email please include:

• A link to this thread: https://1password.community/discussion/130082/ssh-agent-stopped-working#latest
• Your forum username: kudzuspaver

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

I am also facing this issue, it is quite disruptive and I consider disabling the ssh agent until it is fixed. Any idea when a fix can be expected? Thanks, otherwise I love the feature!

Jack_P_1P: I'm using iTerm2, 3.4.18.

Hi ravron:

Are you using Terminal.app, iTerm, or another terminal app? Let me know, as we're continuing to investigate this.

Jack

I'm running into this as well. I see it both during SSH authentication and also during git commit signing using my SSH key.


WARN 2022-12-19T13:19:55.881 tokio-runtime-worker(ThreadId(8)) [1P:ssh/op-ssh-agent/src/lib.rs:426] Unable to get client_info for pid: 58009
WARN 2022-12-19T13:20:22.788 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree


With git commit signing configured, a command like git commit --allow-empty -m 'Test commit' sporadically fails

```
$ git commit --allow-empty -m 'Test commit'
error: agent returned an error

fatal: failed to write commit object
$ git commit --allow-empty -m 'Test commit'
[test-1Password 8e11b5f05f] Test commit
$ git commit --allow-empty -m 'Test commit'
error: agent returned an error

fatal: failed to write commit object
```

Each time it fails, the 1Password_rCURRENT.log shows the pair of WARN logs I listed above. Versions:

• 1Password for Mac 8.9.11 (80911019)
• macOS 13.1 (22C65)

I recently upgraded from macOS 12 to macOS 13. Perhaps that's part of it. My suspicion is that 1Password is trying to get information about the process requesting a signature with the SSH key, and that for some reason it is occasionally unable to get that information. No obvious rhyme or reason sticks out to me:


$ for _ in {0..19}; do git commit --allow-empty -m 'Test commit' &> /dev/null && echo 'Success' || echo 'Failure'; done
Failure
Failure
Success
Failure
Success
Success
Failure
Success
Failure
Success
Failure
Success
Success
Failure
Success
Success
Failure
Success
Failure
Success


And success rate varies:


$ for _ in {0..19}; do git commit --allow-empty -m 'Test commit' &> /dev/null && echo 'Success' || echo 'Failure'; done | sort | uniq -c
5 Failure
15 Success
$ for _ in {0..19}; do git commit --allow-empty -m 'Test commit' &> /dev/null && echo 'Success' || echo 'Failure'; done | sort | uniq -c
8 Failure
12 Success


From reading the other posts on this thread, it seems there are two separate issues. One is the sporadic failure to get client_info, and the other is no GUI info available. I've only experienced the former, not the latter.