|
Re: iwat0284e iwat4039e linux unable to connect to integrated agent controller [message #138999 is a reply to message #138964] |
Tue, 09 December 2008 14:02 |
Paul Slauenwhite Messages: 975 Registered: July 2009 |
Senior Member |
|
|
Hi Graeme,
What version of TPTP are you using? Did you install TPTP from the
update site? If so, you may be blocked by
https://bugs.eclipse.org/bugs/show_bug.cgi?id=214788, however this defect
was resolved in TPTP 4.5.0. Otherwise, please open a TPTP defect with the
steps to reproduce this issue.
Paul
"Graeme Vetterlein" <graeme.eclipse@vetterlein.com> wrote in message
news:91f296dab8b29d537e6e0feae51e0dbe$1@www.eclipse.org...
> Following the guides in:
>
> http://www.eclipse.org/tptp/test/documents/userguides/auto-g ui-viewlet/auto-gui-viewlet_viewlet_swf.html
>
> I hit a 2nd problem at the point where you launch as "test".
> It produced messages to the effect that it could not connect to agent
> controller
>
> This additionally created:
>
> Unable to load transport layer: socketTL libsocketTL.so
>
> IN the log file (found at
> ../dropins/eclipse/plugins/org.eclipse.tptp.platform.ac.linu x_ia32_4.4.1.v200808290100/agent_controller/config/servicelo g.log
>
> It was not clear to me WHAT should happen here but I now believe that an
> agent (ACServer) should be started on demand an listen on (at least) port
> 10002. This was not happening . The process was launched but did not
> listen.
>
>
>
> Turns out there are a whole bunch of links missing from
> ../dropins/eclipse/plugins/org.eclipse.tptp.platform.ac.linu x_ia32_4.4.1.v200808290100/agent_controller/lib/
>
> In essence things like libsocketTL.so.4.5.0 need to be symlinked to
> libsocketTL.so.4.5 libsocketTL.so.4 and libsocketTL.so ... similar for
> other .so files found here.
>
> Some of these are visiable if you do ldd ...ACServer, but not all (I
> assume it dynamically loads these in code). Anyhow I manually created the
> links (well ldconfig(1) + some manual)
>
>
> This finally allowed the integrated agent to start. Once it had stared an
> lsof -p <pid> shows:
> ACServer 10726 vetterlein 5r FIFO 8,1 9657153
> /tmp/IBMRAC/acmaster
> ACServer 10726 vetterlein 6u IPv4 909565 TCP *:10006
> (LISTEN)
> ACServer 10726 vetterlein 7u IPv4 909566 TCP *:10002
> (LISTEN)
> ACServer 10726 vetterlein 9u IPv4 909571 TCP *:10005
> (LISTEN)
> ACServer 10726 vetterlein 10w FIFO 8,1 9657151
> /tmp/IBMRAC/84c6d926-9a20-4fb9-9e33-5c6f7e176d71
> ACServer 10726 vetterlein 14w FIFO 8,1 9657155
> /tmp/IBMRAC/a80a2b8a-3993-41df-a7cb-1412bfd06dd8
> ACServer 10726 vetterlein 15w FIFO 8,1 9657149
> /tmp/IBMRAC/548123d3-e638-4cd3-afce-954b38fe6589
> ACServer 10726 vetterlein 16w FIFO 8,1 9657150
> /tmp/IBMRAC/fa2a8792-470d-4b4f-9408-9c8c647d0593
>
> So it's now listening on 10002
> Now if I do window->preferences->agent controller->hosts->test connection
> all works and I get a good connection
>
> ..now just need to figure out the next error: WAT4039E The Test Execution
> Harness reported the following problems: Failed to retrieve the context
> that should be used to run the test cases in
>
|
|
|
Re: iwat0284e iwat4039e linux unable to connect to integrated agent controller [message #139008 is a reply to message #138999] |
Tue, 09 December 2008 14:16 |
Paul Slauenwhite Messages: 975 Registered: July 2009 |
Senior Member |
|
|
Hi Graeme,
Did you unzip the TPTP driver on Windows before transferring to the
Liniux machine? If so, this will cause the links to disappear.
Our Release Engineering Team have confirmed that the links were correct
in the following TPTP 4.5.2 build:
TPTP-4.5.2-200812080100
Paul
"Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
news:ghltq4$q28$1@build.eclipse.org...
> Hi Graeme,
> What version of TPTP are you using? Did you install TPTP from the
> update site? If so, you may be blocked by
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=214788, however this defect
> was resolved in TPTP 4.5.0. Otherwise, please open a TPTP defect with the
> steps to reproduce this issue.
>
> Paul
> "Graeme Vetterlein" <graeme.eclipse@vetterlein.com> wrote in message
> news:91f296dab8b29d537e6e0feae51e0dbe$1@www.eclipse.org...
>> Following the guides in:
>>
>> http://www.eclipse.org/tptp/test/documents/userguides/auto-g ui-viewlet/auto-gui-viewlet_viewlet_swf.html
>>
>> I hit a 2nd problem at the point where you launch as "test".
>> It produced messages to the effect that it could not connect to agent
>> controller
>>
>> This additionally created:
>>
>> Unable to load transport layer: socketTL libsocketTL.so
>>
>> IN the log file (found at
>> ../dropins/eclipse/plugins/org.eclipse.tptp.platform.ac.linu x_ia32_4.4.1.v200808290100/agent_controller/config/servicelo g.log
>>
>> It was not clear to me WHAT should happen here but I now believe that an
>> agent (ACServer) should be started on demand an listen on (at least) port
>> 10002. This was not happening . The process was launched but did not
>> listen.
>>
>>
>>
>> Turns out there are a whole bunch of links missing from
>> ../dropins/eclipse/plugins/org.eclipse.tptp.platform.ac.linu x_ia32_4.4.1.v200808290100/agent_controller/lib/
>>
>> In essence things like libsocketTL.so.4.5.0 need to be symlinked to
>> libsocketTL.so.4.5 libsocketTL.so.4 and libsocketTL.so ... similar for
>> other .so files found here.
>>
>> Some of these are visiable if you do ldd ...ACServer, but not all (I
>> assume it dynamically loads these in code). Anyhow I manually created the
>> links (well ldconfig(1) + some manual)
>>
>>
>> This finally allowed the integrated agent to start. Once it had stared an
>> lsof -p <pid> shows:
>> ACServer 10726 vetterlein 5r FIFO 8,1 9657153
>> /tmp/IBMRAC/acmaster
>> ACServer 10726 vetterlein 6u IPv4 909565 TCP *:10006
>> (LISTEN)
>> ACServer 10726 vetterlein 7u IPv4 909566 TCP *:10002
>> (LISTEN)
>> ACServer 10726 vetterlein 9u IPv4 909571 TCP *:10005
>> (LISTEN)
>> ACServer 10726 vetterlein 10w FIFO 8,1 9657151
>> /tmp/IBMRAC/84c6d926-9a20-4fb9-9e33-5c6f7e176d71
>> ACServer 10726 vetterlein 14w FIFO 8,1 9657155
>> /tmp/IBMRAC/a80a2b8a-3993-41df-a7cb-1412bfd06dd8
>> ACServer 10726 vetterlein 15w FIFO 8,1 9657149
>> /tmp/IBMRAC/548123d3-e638-4cd3-afce-954b38fe6589
>> ACServer 10726 vetterlein 16w FIFO 8,1 9657150
>> /tmp/IBMRAC/fa2a8792-470d-4b4f-9408-9c8c647d0593
>>
>> So it's now listening on 10002
>> Now if I do window->preferences->agent controller->hosts->test connection
>> all works and I get a good connection
>>
>> ..now just need to figure out the next error: WAT4039E The Test Execution
>> Harness reported the following problems: Failed to retrieve the context
>> that should be used to run the test cases in
>>
>
>
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03888 seconds