Hi all,
I encounter a strange message in universe.log of global control :
<< 2009-06-18 11:41:36 0003116/JobMonitorApp /connect_inet_com /135888915 - connection on host <my_node> port 11015 [SOCIETE_DQM_X] err 10061 , -Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée.
DQM is not enabled on my nodes, but why is this trying to connect ?
Maybe, it's a problem on my global control config, but I don't know what to change.
If someone has an idea, this would be great.
Thanks.
Laurent
Solved : Error message in universe.log "Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée"
Started by Laurent Gaillard, Jun 18 2009 11:04 AM
6 replies to this topic
#1
Posted 18 June 2009 - 11:04 AM
#2
Posted 19 June 2009 - 10:58 AM
Hello Laurent,
I came across this message before. It was linked to some Task update. Is it also the case for you?
In this case, a fix is on its way which should be available in July.
If this is not the case, can you double-check if the DQM service is created on any of the boxes (Dollar Universe Application Server and Consoles) ? If created, is it started?
If you cannot find any DQM service on the servers, and the issue is not linked to Task updates, I would recommend you open a case at Dollar Access Tech Support and provide them with a uxtrace with options sc of both the DU Application Server and the console.
Michel
I came across this message before. It was linked to some Task update. Is it also the case for you?
In this case, a fix is on its way which should be available in July.
If this is not the case, can you double-check if the DQM service is created on any of the boxes (Dollar Universe Application Server and Consoles) ? If created, is it started?
If you cannot find any DQM service on the servers, and the issue is not linked to Task updates, I would recommend you open a case at Dollar Access Tech Support and provide them with a uxtrace with options sc of both the DU Application Server and the console.
Michel
#3
Posted 19 June 2009 - 01:26 PM
Hi Michel,
it seems that I have this problem when doing a launch, modifying a task and for "JobMonitorAPP":
And no DQM services are started.
I will wait for the patch. If you can keep me in touch about the release, this will be great.
Thanks.
Laurent
it seems that I have this problem when doing a launch, modifying a task and for "JobMonitorAPP":
<< 2009-06-18 17:20:07 0002812/JobMonitorApp /connect_inet_com /135888915 - connection on host <machine> port 11015 [SOCIETE_DQM_X] err 10061 , -Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée. << 2009-06-18 17:23:50 0005500/LaunchApp /connect_inet_com /135888915 - connection on host <machine> port 11015 [SOCIETE_DQM_X] err 10061 , -Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée. << 2009-06-19 14:19:23 0003776/TaskApp /connect_inet_com /135888915 - connection on host <machine> port 11015 [SOCIETE_DQM_X] err 10061 , -Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée.
And no DQM services are started.
I will wait for the patch. If you can keep me in touch about the release, this will be great.
Thanks.
Laurent
#4
Posted 19 June 2009 - 01:41 PM
OK, looks like the best thing to do.
I'll keep you posted when the patch is released.
Michel
I'll keep you posted when the patch is released.
Michel
#5
Posted 01 July 2009 - 05:32 PM
Hello,
patch FX24734 for V533 has been released yesterday - still in Controled Availability (so be careful and install the patch on test environments first) - and fixes the issue.
Michel
patch FX24734 for V533 has been released yesterday - still in Controled Availability (so be careful and install the patch on test environments first) - and fixes the issue.
Michel
#6
Posted 22 July 2009 - 09:49 AM
Hi Michel,
thanks for your answer.
To be sure. I have this issue on client side. My servers are not in 5.3.3 (AIX / Linux in 5.1.3 and Windows in 5.2.3).
Will this solve the issue to install this patch only on client side ?
Regards.
thanks for your answer.
To be sure. I have this issue on client side. My servers are not in 5.3.3 (AIX / Linux in 5.1.3 and Windows in 5.2.3).
Will this solve the issue to install this patch only on client side ?
Regards.
#7
Posted 24 July 2009 - 04:35 PM
Hello Laurent,
apparently the patch should be installed on both sides...
One of the customers we sent the patch to has a similar configuration - with some 533 on the servers though. Apparently the issue still occurs but less frequently.
I guess it would be worth to give it a try.
Michel
apparently the patch should be installed on both sides...
One of the customers we sent the patch to has a similar configuration - with some 533 on the servers though. Apparently the issue still occurs but less frequently.
I guess it would be worth to give it a try.
Michel
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












