[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#801173: ssh-agents kill each other

2015-10-07 09:30:12 Harald Dunkel:
> Package: openssh-client
> Version: 1:6.6p1-4~bpo70+1
> I start 2 vnc sessions at boot time using cron, e.g.
> 	% crontab -l
> 	@reboot ssh-agent vncserver :42
> 	@reboot sleep 3; ssh-agent vncserver :43
> UID != 0
> Problem: The first ssh-agent gets killed. Suspect is the
> second agent. The first vnc session has no connection to
> an ssh-agent. Besides that, both are fine. SSH_AGENT_PID
> and SSH_AUTH_SOCK are defined in both sessions, but of
> course they do not match.
> If I login on the console, then libpam-ssh gives me yet
> another new ssh-agent, and the 2nd vncserver agent is
> pushing up the daisies, too.

Please do an strace on the ssh-agent to find out why it dies:

@reboot strace -ttTffo st ssh-agent vncserver :42
@reboot sleep 3; strace -ttTffo st ssh-agent vncserver :43

Keep the sessions short or the output files get really large; perhaps you can 
just wait until the process dies and then kill all of the remaining processes.


Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: