Andrej, sorry, normally the person who supplies the additional
information sets the status back to 'new' or 'confirmed' as needed. We
don't say that nearly often enough. sorry.
** Changed in: openssh (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because
Ooops ... sorry ... thanks for the update!
On 12 May 2015 at 08:44, Seth Arnold 1446...@bugs.launchpad.net wrote:
Andrej, sorry, normally the person who supplies the additional
information sets the status back to 'new' or 'confirmed' as needed. We
don't say that nearly often enough. sorry.
Can you please let me know in which way this is still incomplete?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about
knock knock
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Still incomplete?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Hi Robie,
The pid I posted didn't exist on the system anymore when you asked.
I took a snapshot of current pids, ran the scp from remote again, this
time the pid in question was 31397, and that, too, appears to be transient.
After ssh-agent died that pid didn't exist anymore. Any cunning plan on
Try looking into process accounting.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1446448
Title:
ssh-agent terminates
To manage notifications about this bug go to:
Brendan Gregg has an awesome execsnoop tool that can report systemwide
execs in his perf-tools package, the whole thing is a goldmine of
amazing tools:
http://www.brendangregg.com/blog/2014-07-28/execsnoop-for-linux.html
Probably this is easier than the process accounting.
Thanks
--
You
Aight, thanks Seth for the execsnoop link, excellent stuff to have in
your tool-box. I just re-ran my test-case, and this is the new strace
output, with the correlating execsnoop snippet.
select(5, [3 4], [], NULL, NULL)= 1 (in [4])
read(4, \0\0\0\1\v, 1024) = 5
select(5, [3
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Your strace suggests that the process is being killed by a SIGTERM from
pid 21284 which is running as root. Can you reproduce again and try to
determine which process your SIGTERM is coming from?
--- SIGTERM
10 matches
Mail list logo
