Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
ssh-agent stopped working
Hi,
After last nigthly update ssh-agent stopped working with error:
sign_and_send_pubkey: signing failed for ED25519 "SSH key ed25519 private" from agent: agent refused operation
Here's a log...
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.
