[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #CNE-889859]: Setting up ADDE server

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #CNE-889859]: Setting up ADDE server
  • Date: Thu, 07 Jun 2007 09:25:42 -0600
Hi Mike,

The output you sent shows that access to the ER dataset works fine from
the 'mcidas' account where the data is local (LOCAL-DATA).  I guess
I misinterpreted your original email to mean that you could not access
the data at all.  I now understand that you are unable to get access
to the dataset through the remote ADDE interface (please correct me if
I am wrong).

Given that you have correctly setup the ~mcidas/.mcenv file, the
next question is if you configured the remote ADDE interface.  You do
this as 'root' as follows:

<login as 'root'>
cd /usr/local/mcidas
sh ./mcinet2006.sh install mcadde

This will setup the needed file in /etc/xinetd.d (named mcidas) with
the information needed to access datasets setup in the 'mcidas'
account.

The next step in the process is making sure that xinetd is running; is
it?  If no, you need to configure your system (I am assuming you are
running a Linux system) to run xinetd on boot:

<as 'root'>
chkconfig --levels 2345 xinetd

Now start xinetd:

/etc/init.d/xinetd start

If xinetd had not been running previously, this sequence would have started
it and you should be able to access the datasets through the remote ADDE
server on your machine _IF_ your firewall is setup to allow access to
your machine using port 112.  Is your machine's firewall setup to allow
access through port 112?

Finally, is access to your machine open outside of ERAU?  If it is, please
send me the fully qualified name of the machine so I can run some tests
from Unidata.  If your machine is not setup outside of ERAU, I could 
troubleshoot
for you (assuming that the above didn't work) if you give me logins as 'mcidas'
and possibly 'root'.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: CNE-889859
Department: Support McIDAS
Priority: Normal
Status: Closed