Ok, the problem was solved. The administrator of our UI had change the
firewall rules :-) and I was not allowed to access to wms port 7443...
Cheers
Alvaro
> Yes I did and our DNS seems to resolve back from UI
>
> dig -x 84.21.169.16
>
> ; <<>> DiG 9.2.4 <<>> -x 84.21.169.16
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61016
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
>
> ;; QUESTION SECTION:
> ;16.169.21.84.in-addr.arpa. IN PTR
>
> ;; ANSWER SECTION:
> 16.169.21.84.in-addr.arpa. 172800 IN PTR wms01.egee.cesga.es.
>
> ;; AUTHORITY SECTION:
> 169.21.84.in-addr.arpa. 172800 IN NS ns1.cesga.es.
> 169.21.84.in-addr.arpa. 172800 IN NS ns2.cesga.es.
>
> ;; ADDITIONAL SECTION:
> ns1.cesga.es. 300 IN A 193.144.33.38
> ns2.cesga.es. 300 IN A 193.144.33.39
>
> ;; Query time: 1 msec
> ;; SERVER: 193.144.33.38#53(193.144.33.38)
> ;; WHEN: Tue Jul 17 13:49:19 2007
> ;; MSG SIZE rcvd: 166
>
> Cheers
> Alvaro
>> Hello,
>>
>> Can you check your DNS entries and the /etc/hosts file?
>> 84.21.169.16 <http://84.21.169.16> does not resolve back to
>> wms01.egee.cesga.es <http://wms01.egee.cesga.es>
>>
>> dig -x 84.21.169.16 <http://84.21.169.16>
>> ; <<>> DiG 9.2.4 <<>> -x 84.21.169.16 <http://84.21.169.16>
>> ;; global options: printcmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57900
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;16.169.21.84.in-addr.arpa. IN PTR
>>
>> ;; AUTHORITY SECTION:
>> 84.in-addr.arpa. 7102 IN SOA ns-pri.ripe.net
>> <http://ns-pri.ripe.net>. ops.ripe.net <http://ops.ripe.net>.
>> 2007071748 3600 7200 1209600 7200
>>
>> ;; Query time: 7 msec
>> ;; SERVER: 194.42.16.11#53( 194.42.16.11 <http://194.42.16.11>)
>> ;; WHEN: Tue Jul 17 13:55:47 2007
>> ;; MSG SIZE rcvd: 98
>>
>>
>> regards,
>> Yiannis
>>
>> On 7/17/07, *Alvaro Simon Garcia* < [log in to unmask]
>> <mailto:[log in to unmask]>> wrote:
>>
>> Dear all
>>
>> After last production update our wms server is falling submitting
>> jobs,
>> we got this error running glite-wms-job-submit
>>
>>
>> Connecting to the service
>> https://wms01.egee.cesga.es:7443/glite_wms_wmproxy_server
>>
>> Connection failed: Connection timed out
>> connect failed in tcp_connect()
>> Error code: SOAP-ENV:Client
>>
>> Error - Operation failed
>> Unable to find any endpoint where to connect
>>
>>
>>
>> It seems that GLITE_LOCATION is not defined (Bug 19102
>> https://savannah.cern.ch/bugs/?19102) but after change
>> /opt/glite/etc/init.d/* scripts to set GLITE_LOCATION to /opt/glite
>> instead of /home/glbuild/GLITE_3_0_0/stage the problem still
>> remains.
>>
>> Any idea?
>>
>> Cheers and thanks
>> Alvaro
>>
>>
>
>
|