The modules were created by others and shipped to us as outboard modules. After tracking down the sources and recompiling them as loadable modules they work fine now.
The problem may be related to the FQDN setting of our system as suggested by Randal, but I am not sure. Thanks. Fuan Tsai EES-6, MS D462 Los Alamos National Laboratory Los Alamos, NM 87545 On Mon, 3 Jun 2002, David Thompson wrote: > I don't know what the problem could be. I don't believe any of the > module loading code was touched. Why are you using outboard modules > instead of loadable modules? You may try working in script mode to > see if you can get a better error message with regards to the module > error. > > David > > >Hi dx developers, > > > >Looks like my last mail did not go through, so I am sending it again. > > > >After upgrading to 4.2.0 using the i386.rpm from opendx.org, my .nets are > >no longer able to connect to outboard modules. The error messages read > >like this: > > > >ERROR: <module_name>: Bad parameter: connection to host > >localhost.localdomain failed. > > > >These modules and nets worked happily in 4.1.3. Any suggestion to make > >them work again in 4.2? The system in question is an AMD Athlon box > >running RedHat 7.2. > > > >Thanks in advance. > > > >Fuan Tsai > >EES-6, MS D462 > >Los Alamos National Laboratory > >Los Alamos, NM 87545 > > > -- > ............................................................................. > David L. Thompson Visualization and Imagery Solutions, Inc. > mailto:[EMAIL PROTECTED] 5515 Skyway Drive, Missoula, MT 59804 > Phone : (406)257-8530 >
