OmniSSHAgent: Named pipe stops working after a while the system is on
It seems that named pipe stops working after a while the system is on:
PS C:\Users\Maicol> ssh-add -l
Error connecting to agent: No such file or directory
PS C:\Users\Maicol> Get-ChildItem \\.\pipe\|findstr open
------ 01/01/1601 01:00 1 openssh-ssh-agent
WSL:
~ ❯ ssh-add -l 19:43:23
error fetching identities: communication with agent failed
However, Git bash works:
$ ssh-add -l
3072 SHA256:xInBcA48YT6jmmOEWQrXtC+xw+c6V2V2cVgAWT6K9hg id_rsa (RSA)
256 SHA256:ZgvmgA5CNIpEbTZWepclAdXC9fVBFsB1kvmM14Egjm8 id_ed25519 (ED25519)
I’ve currently tested the named pipe mode and the 1password proxy mode and the two modes are affected. Do you have any clue? Thanks
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 31 (28 by maintainers)
It was working on Friday (May 27) but broke between then and today (May 31).
I tried:
None of those worked
Rebooted my laptop, and it’s back to working again 🤷
I think I’m seeing the same issue:
What’s strange is it runs outside of socat:
I’ve been using this every day since I added my comments, and it’s been stable ever since then. I guess something changed, but I don’t know what.
No, I’m not using Cygwin and the others.
I’m only using WSL2 and rarely Powershell
I’ve debugged a bit and it seems Omni overwrites the pipe used by Microsoft OpenSSH:
I’ve checked in env variables and there was a manually added SSH_AUTH_SOCK variable that was causing this issue.
I’ll keep you updated if I have the previous issues
@masahide windows ssh-add never worked for me (in the PC I’m currrently using. On another PC works):
I’m not sure whether restarting 1Password fixes the original test (I will try that when I get it), but it fixes this one: https://github.com/masahide/OmniSSHAgent/issues/20#issuecomment-1152414315
Yes, I only restart 1Password. Other things and services are untouched
Useful detail (maybe): restarting 1password when this happens fixes the issue
New issue today, but I don’t know if it’s related:
Log:
Thanks. From the information you gave us, it looks like the omni-socat.exe is fine and the socat process is causing the problem.
It may be a problem with the combination of socat and WSL2. https://github.com/microsoft/WSL/issues/7560
I’ll look into it some more, but if there’s nothing I can do about it. I think I can solve this problem by creating something like
socatmyself. Please give me some time.@masahide new case:
Rebooted and works… next time!
@masahide got this again and nothing has been logged
I don’t know redownloading helped, I’ll let you know in some days if I get the error again.
Chmodded. Now I get:
Let me try to chmod it
First console:
Second console:
There isn’t a specific time when this occurs
Yes, the error of the OP
This after updating to 0.3.1:
After update the result is: