[erlang-questions] code_server:call/2 problem?

Evans, Matthew <>
Fri Mar 18 19:16:50 CET 2011


Do you see any crashes on the remote nodes?

It does look like the remote code_server application has got a request, but it for some reason fails (corrupted data perhaps?). I'm wondering if you could attach a remote shell to one of those nodes and trace the code_server module?

-----Original Message-----
From:  [mailto:] On Behalf Of Olivier BOUDEVILLE
Sent: Friday, March 18, 2011 1:32 PM
To: 
Subject: [erlang-questions] code_server:call/2 problem?

Hi,

We are running a distributed Erlang program on a user node from which a 
number of computing nodes are spawned, via SSH for the remote hosts. To 
perform the automatic deployment, two deployment-related modules are sent 
to each of the spawned nodes, using the traditional approach (first a call 
to code:get_object_code/1 then a rpc:multicall of code:load_binary).

However, sometimes (not frequently), with the exact same settings, the 
first module cannot be deployed successfully. We have indeed:

{ResList,BadNodes} = rpc:multicall( Nodes, code, load_binary, [ 
ModuleName, ModuleFilename, ModuleBinary ], Timeout ),

that returns:
ResList = 
[{badrpc,{'EXIT',{badarg,[{code_server,call,2},{rpc,'-handle_call_call/6-fun-0-',5}]}}}]
BadNodes = []

This happens with R14B02, but most probably with previous versions as 
well.
Apparently this happens often (always?) on a node created on the user 
host.
I am pretty sure the deployed node is "fresh" (blank, vanilla).
And ignoring the badrpc will result in a undef error as soon as the first 
function of the first helper module is called, even if delaying the call 
(a race condition was suspected if ever the actual loading was 
asynchronous).

Would anyone see a cause for such a badarg non-systematic error?

Thanks in advance for any hint,
Best regards,

Olivier Boudeville.
---------------------------
Olivier Boudeville

EDF R&D : 1, avenue du Général de Gaulle, 92140 Clamart, France
Département SINETICS, groupe ASICS (I2A), bureau B-226
Office : +33 1 47 65 59 58 / Mobile : +33 6 16 83 37 22 / Fax : +33 1 47 
65 27 13



Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires et les informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination, toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse.

Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système, ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercions également d'en avertir immédiatement l'expéditeur par retour du message.

Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécurisées ou dénuées de toute erreur ou virus.
____________________________________________________

This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in this Message is confidential. Any use of information contained in this Message not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.

If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return message.

E-mail communication cannot be guaranteed to be timely secure, error or virus-free.


More information about the erlang-questions mailing list