0 Replies Latest reply: Jul 2, 2013 8:04 AM by Alex22207 RSS

    Default UNIX System Authentication Fails after Installation of SGD 5.0 on OEL6

    Alex22207

      SGD noob here.  Standing up a SGD environment in my home environment  to check it out and maybe pitch it to a client for the next generation of some stuff I'm supporting now.  Things were going quite well for  a while, then I suddenly hit a wall that I hope someone here can get me over.  I suspect that it's an obvious noobism that an experienced SGD administrator will recognize and resolve quickly.

       

      The background:  I successfully installed SGD 5.0, logged into my webtop as Administrator after a clean install per the installation guide.  From there I accessed my OEL6 instance on which I have installed SGD.  No problems, until a few hours later when I couldn't log in to the webtop as anything other than "Anonymous".  My login attempts appear to time out and the login page includes an "invalid credentials" error message under the credentials form.  The credentials are valid.

       

      As a part of my troubleshooting efforts, I've deleted the VM image and did a complete clean install of OEL6 and SGD.  The error persists.

       

      There are no login records in the SGD logs at /opt/tarantella/var/logs.  The output of the /opt/tarantella/webserver/tomcat/7.0.37_axis1.4/logs/catalina.out is:

       

      ID: 788

      Message context:

      Message ID: 23

      Bean action: http://sgd.sun.com/webservices/document/webtopsession

      Full action: http://sgd.sun.com/webservices/document/webtopsession/authenticate

      Started to wait: Sun Jun 23 22:26:48 EDT 2013

      Current time: Sun Jun 23 22:26:53 EDT 2013

      Sun Jun 23 22:26:58 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:26:58 EDT 2013 AxisMessageMonitor

      788, waited 10001 ms

      Sun Jun 23 22:27:03 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:03 EDT 2013 AxisMessageMonitor

      788, waited 15001 ms

      Sun Jun 23 22:27:08 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:08 EDT 2013 AxisMessageMonitor

      788, waited 20002 ms

      Sun Jun 23 22:27:13 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:13 EDT 2013 AxisMessageMonitor

      788, waited 25002 ms

      Sun Jun 23 22:27:18 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:18 EDT 2013 AxisMessageMonitor

      788, waited 30002 ms

      Sun Jun 23 22:27:23 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:23 EDT 2013 AxisMessageMonitor

      788, waited 35003 ms

      Sun Jun 23 22:27:28 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:28 EDT 2013 AxisMessageMonitor

      788, waited 40003 ms

      Sun Jun 23 22:27:33 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:33 EDT 2013 AxisMessageMonitor

      788, waited 45004 ms

      Sun Jun 23 22:27:38 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:38 EDT 2013 AxisMessageMonitor

      788, waited 50004 ms

      Sun Jun 23 22:27:43 EDT 2013 AxisMessageMonitor

      788, no response received

      Sun Jun 23 22:27:43 EDT 2013 AxisMessageMonitor

      788, waited 55004 ms

      Sun Jun 23 22:27:48 EDT 2013 AxisMessageMonitor

      788, received response

      Sun Jun 23 22:27:48 EDT 2013 AxisMessageMonitor

      788, waited 60002 ms in total

      2013-06-23 22:27:48 WARNING ID: 3, Fault code   : Client.LoginFailed

      2013-06-23 22:27:48 WARNING ID: 3, Fault string : Invalid credentials

       

       

      --------------------------------------------------

      There is a jserver error log that contains the following.  Not sure if it's relevant, but I provide it for general awareness:

       

      2013/06/23 20:15:34.438    (pid 8212)    server/common/error    #1372032934438

      Oracle Secure Global Desktop (5.0) ERROR:

       

      Attempt to process a request failed:

      java.lang.NullPointerException

          at com.sco.tta.server.server.asad.AsadEnvelopeConnect$AsadConnectContext.close(AsadEnvelopeConnect.java:842)

          at com.sco.tta.server.server.asad.AsadEnvelopeConnect.close(AsadEnvelopeConnect.java:290)

          at com.sco.tta.server.server.ReaderTask.closeConnection(ReaderTask.java:254)

          at com.sco.tta.server.server.ReaderTask.cleanupTask(ReaderTask.java:568)

          at com.sco.tta.server.server.ReaderTask.runTask(ReaderTask.java:433)

          at com.sco.tta.server.server.Task.run(Task.java:125)

          at com.sco.cid.common.WorkerPool$Worker.run(WorkerPool.java:469)

          at java.lang.Thread.run(Thread.java:662)

      .

       

      One request failed, but the server will continue to process

      other requests.

       

      Report this error to customer support.

       

      --------------------------------------------------

       

      This error message repeats several times.

       

      I would appreciate some pointers.  Which additional log files, if any, should I posts to assist with troubleshooting?  Thanks in advance.

       

      Alex

       

      Bump.  No pointers?  I followed the installation and configuration instructions exactly (or at least I think I did).  I even blew away the image and reinstalled ol6 and SGD5.  What would cause a default logon failure on a clean install?  Clearly, something is preventing my credentials from making the round trip from the web server to the authentication mechanism and back, or I would be forwarded to the webtop.