It's all about the answers!

Ask a question

Error logging into server using scm command line tool


Jason Mobarak (102) | asked Jun 09 '16, 9:04 p.m.
edited Jun 11 '16, 3:02 p.m. by David Lafreniere (4.3k7)
Seeing the follow error when attempting to login in to our ccm server:
scm login -r 'https://{redacted}/ccm' -n pw -u xyz -c
Password ({redacted} @ https://{redacted}/ccm):
Problem running 'login':
Could not log in to https://{redacted}/ccm as user xyz: CRJAZ2917E The repository on the following server cannot be reached: https://{redacted}/ccm. Verify that the server address is correct.
CRJAZ2917E The repository on the following server cannot be reached: https://{redacted}/ccm. Verify that the server address is correct.
Check the log for details about the error at "/Users/{redacted}/.jazz-scm". If you have configured custom logging check your log configuration settings for the path to the log file.

This is the trace log:

 # Time - Type - Port - Description
2016/Jun/09 17:52:10.313 - START_LISTENING - 59019 - Listening on port 59019
daemonEntryDir = /Users/<>/.jazz-scm/daemons/D8be60000
daemonUuid = <>
buildId = RTC-I20150519-1214
listeningPort = 59019
2016/Jun/09 17:52:10.369 - CONNECT - 59020 - Client connected
2016/Jun/09 17:52:10.375 - REQUEST - 59020 - GET /service/com.ibm.team.filesystem.client.rest.IFilesystemRestClient/TeamRepository?repositoryUrl=https%3A%2F%2F{redacted}%2Fccm
2016/Jun/09 17:52:10.807 - JSON_REQUEST - 59020 - Request, Progress-Key: null
repositoryUrl = https://{redacted}/ccm
2016/Jun/09 17:52:10.833 - JSON_RESPONSE - 59020 - Response (200)
{
   "_eQualifiedClassName": "http:\/\/schemas.xmlsoap.org\/soap\/envelope\/:Envelope",
   "soapenv:Body": {
       "_eQualifiedClassName": "http:\/\/schemas.xmlsoap.org\/soap\/envelope\/:Body",
       "response": {
           "_eQualifiedClassName": "http:\/\/\/com\/ibm\/team\/core\/services.ecore:Response",
           "interface": "com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient",
           "method": "getTeamRepository",
           "returnValue": {
               "_eQualifiedClassName": "http:\/\/\/com\/ibm\/team\/core\/services.ecore:NullDataArg",
               "type": "NULL"
           }
       }
   }
}
2016/Jun/09 17:52:10.837 - RESPONSE - 59020 - 200
2016/Jun/09 17:52:10.864 - REQUEST - 59020 - POST /service/com.ibm.team.filesystem.client.rest.IFilesystemRestClient/Login
2016/Jun/09 17:52:10.869 - JSON_REQUEST - 59020 - Request, Progress-Key: null
repositoryUrl = https://{redacted}/ccm
userId = {redacted}
password = {redacted}
smartCard = false
kerberos = false
proxyPort = -1
2016/Jun/09 17:52:11.114 - JSON_RESPONSE - 59020 - Response (500)
{
   "errorClass": "com.ibm.team.repository.common.TeamRepositoryException",
   "errorCode": 500,
   "errorMessage": "CRJAZ2917E The repository on the following server cannot be reached: https:\/\/{redacted}\/ccm. Verify that the server address is correct.",
   "errorTrace": [
       "com.ibm.team.repository.client.util.RepositoryUtil.getRepositoryId2(RepositoryUtil.java:137)",
       "com.ibm.team.repository.client.internal.TeamRepositoryService.connectToAndUpdateTeamRepository(TeamRepositoryService.java:401)",
       "com.ibm.team.repository.client.internal.TeamRepositoryService.getTeamRepositoryWithOverride(TeamRepositoryService.java:180)",
       "com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postLogin(FilesystemRestClient.java:548)",
       "sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)",
       "sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)",
       "sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)",
       "java.lang.reflect.Method.invoke(Method.java:498)",
       "com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:322)",
       "com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628)",
       "com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470)",
       "org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)"
   ],
   "errorTraceMarshall": [
       {
           "errorTraceClassName": "com.ibm.team.repository.client.util.RepositoryUtil",
           "errorTraceFileName": "RepositoryUtil.java",
           "errorTraceLineNumber": 137,
           "errorTraceMethodName": "getRepositoryId2"
       },
       {
           "errorTraceClassName": "com.ibm.team.repository.client.internal.TeamRepositoryService",
           "errorTraceFileName": "TeamRepositoryService.java",
           "errorTraceLineNumber": 401,
           "errorTraceMethodName": "connectToAndUpdateTeamRepository"
       },
       {
           "errorTraceClassName": "com.ibm.team.repository.client.internal.TeamRepositoryService",
           "errorTraceFileName": "TeamRepositoryService.java",
           "errorTraceLineNumber": 180,
           "errorTraceMethodName": "getTeamRepositoryWithOverride"
       },
       {
           "errorTraceClassName": "com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient",
           "errorTraceFileName": "FilesystemRestClient.java",
           "errorTraceLineNumber": 548,
           "errorTraceMethodName": "postLogin"
       },
       {
           "errorTraceClassName": "sun.reflect.NativeMethodAccessorImpl",
           "errorTraceFileName": "NativeMethodAccessorImpl.java",
           "errorTraceLineNumber": -2,
           "errorTraceMethodName": "invoke0"
       },
       {
           "errorTraceClassName": "sun.reflect.NativeMethodAccessorImpl",
           "errorTraceFileName": "NativeMethodAccessorImpl.java",
           "errorTraceLineNumber": 62,
           "errorTraceMethodName": "invoke"
       },
       {
           "errorTraceClassName": "sun.reflect.DelegatingMethodAccessorImpl",
           "errorTraceFileName": "DelegatingMethodAccessorImpl.java",
           "errorTraceLineNumber": 43,
           "errorTraceMethodName": "invoke"
       },
       {
           "errorTraceClassName": "java.lang.reflect.Method",
           "errorTraceFileName": "Method.java",
           "errorTraceLineNumber": 498,
           "errorTraceMethodName": "invoke"
       },
       {
           "errorTraceClassName": "com.ibm.team.filesystem.client.daemon.JSONHandler",
           "errorTraceFileName": "JSONHandler.java",
           "errorTraceLineNumber": 322,
           "errorTraceMethodName": "handle"
       },
       {
           "errorTraceClassName": "com.ibm.team.filesystem.client.internal.http.HttpConnection",
           "errorTraceFileName": "HttpConnection.java",
           "errorTraceLineNumber": 628,
           "errorTraceMethodName": "readNextRequest"
       },
       {
           "errorTraceClassName": "com.ibm.team.filesystem.client.internal.http.HttpConnection$1",
           "errorTraceFileName": "HttpConnection.java",
           "errorTraceLineNumber": 470,
           "errorTraceMethodName": "run"
       },
       {
           "errorTraceClassName": "org.eclipse.core.internal.jobs.Worker",
           "errorTraceFileName": "Worker.java",
           "errorTraceLineNumber": 54,
           "errorTraceMethodName": "run"
       }
   ]
}
2016/Jun/09 17:52:11.114 - RESPONSE - 59020 - 500

2 answers



permanent link
Shashikant Padur (3.9k27) | answered Jun 09 '16, 11:39 p.m.
JAZZ DEVELOPER
To verify that the server is reachable can you try connecting via the browser?

Comments
Jason Mobarak commented Jun 10 '16, 1:45 a.m.

It works fine via the browser and the eclipse client.  From the trace log it looks like it's getting an initial 200 response to the first request, but a 500 response from the second request.


Shashikant Padur commented Jun 10 '16, 5:14 a.m.
JAZZ DEVELOPER

Are you using any proxy on your machine?


Jason Mobarak commented Jun 10 '16, 7:41 p.m.

 There is a proxy on my machine, but I disabled it for this test.


Jason Mobarak commented Jun 10 '16, 7:43 p.m.

 If the proxy is enabled I get a different error, after I disabled the proxy, I got this error.


Shashikant Padur commented Jun 13 '16, 4:31 a.m. | edited Jun 13 '16, 4:31 a.m.
JAZZ DEVELOPER

If you need to use the proxy to connect to the rtc server then set the following environment variable before running scm command line:

http_proxy="http://<yourproxyhost>:<yourproxyport>" or
https_proxy="https://<yourproxyhost>:<yourproxyport>"


Jason Mobarak commented Jun 13 '16, 5:10 p.m.

  Hi Shashikant-- Like I said, I've tried with and without our proxy.  We have eclipse configured to bypass the proxy for this domain, so direct access should work from the command line.  With the proxy enabled I see 404 errors, with the proxy disabled I see the 500 error.  Any other ideas?  Thanks, -Jason

showing 5 of 6 show 1 more comments

permanent link
Jason Mobarak (102) | answered Jun 13 '16, 7:26 p.m.
This appears to be mostly user error, I modified the scm script to attempt to resolve an SSL error, and that appears to have caused most of the problems.  However I had to follow the instructions here:

https://jazz.net/forum/questions/104164/command-line-tools-fail-to-run-after-upgrade-from-3015-to-401-mkroot-problem

And set the RTC_SCRIPTS_BASE and PRGPATH environment variables.  Also, the able to run the command line tools and the eclipse client at the same time I had to set SCM_ALLOW_INSECURE.

Your answer


Register or to post your answer.