Bug 271749 - Enabling CVS debugging as described in Eclipse CVS FAQ is not producing any logging with SSH connection in console
Summary: Enabling CVS debugging as described in Eclipse CVS FAQ is not producing any l...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact: Szymon Brandys CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-09 05:51 EDT by Valdemar Lemche CLA
Modified: 2019-09-06 16:05 EDT (History)
2 users (show)

See Also:


Attachments
Description of problem connecting to CVS using SSH (6.16 KB, text/plain)
2009-04-09 05:51 EDT, Valdemar Lemche CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valdemar Lemche CLA 2009-04-09 05:51:37 EDT
Created attachment 131385 [details]
Description of problem connecting to CVS using SSH

Build ID: M20090211-1700

Steps To Reproduce:
1. Create file <eclipse root>\.options containing:
org.eclipse.team.cvs.core/debug=true
org.eclipse.team.cvs.core/cvsprotocol=true

2. Run eclipse with following switches:
-console -consolelog -clean -debug

3. Verify that eclipse is loading .options in console:
<SNIP>
Debug options:
    file:/C:/eclipse/.options loaded
</SNIP>

4. Tried browse a CVS repository through SSH (where I get a Unknown response), but all I get in console is this:
Valid-responses ok error M E Updated Template Copy-file Mod-time Set-static-directory Update-existing Clear-static-directory Set-sticky New-entry MT Notified Created Remove-entry Checked-in Merged Removed Valid-requests Clear-sticky Module-expansion
valid-requests

5. Verify eclipse actually logged into the CVS server through SSH:
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: SELinux support disabled
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: PAM: establishing credentials
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: permanently_set_uid: 1000/1000
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: Entering interactive session for SSH2.
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: server_init_dispatch_20
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: server_input_channel_open: ctype session rchan 256 win 16384 max 16384
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: input_session_request
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: channel 0: new [server-session]
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_new: session 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_open: channel 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_open: session 0: link with channel 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: server_input_channel_open: confirm session
Apr  9 11:27:57 filestore.se.lemche.net sshd[29989]: User child is on pid 29991
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: server_input_channel_req: channel 0 request exec reply 1
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_by_channel: session 0 channel 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_input_channel_req: session 0 req exec
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: Received SIGCHLD.
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_by_pid: pid 29992
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_exit_message: session 0 channel 0 pid 29992
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_exit_message: release channel 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_by_channel: session 0 channel 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_close_by_channel: channel 0 child 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: session_close: session 0 pid 0
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: channel 0: free: server-session, nchannels 1
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: Connection closed by 192.168.1.95
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: debug1: do_cleanup
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: Transferred: sent 3576, received 3240 bytes
Apr  9 11:27:57 filestore.se.lemche.net sshd[29991]: Closing connection to 192.168.1.95 port 3171
Apr  9 11:27:57 filestore.se.lemche.net sshd[29989]: debug1: PAM: cleanup
Apr  9 11:27:57 filestore.se.lemche.net sshd[29989]: debug1: PAM: deleting credentials
Apr  9 11:27:57 filestore.se.lemche.net sshd[29989]: debug1: PAM: closing session
Apr  9 11:27:57 filestore.se.lemche.net sshd[29989]: pam_unix(sshd:session): session closed for user atterdag


More information:
I'm following this CVS FAQ: http://wiki.eclipse.org/index.php/CVS_FAQ#Is_there_any_equivalent_to_CVS_CLIENT_LOG_in_Eclipse.3F

I've verified that if I use pserver, then I get the expected debugging information in console.

This bug is a spin-off from 21180.

I've attached my comment to 21180 as a reference to my entire problem.
Comment 1 Mike Wilson CLA 2009-05-05 14:28:19 EDT
Changing Version tag to something more believable.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:05:27 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.