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

[McIDAS #WPD-667222]: Fwd: McIDAS 2017 install

Hi Greg,

re:
> Thanks for the RESOLV.SRV file and the instructions.

No worries.

re:
> I've set up ADDE
> for our datasets, modifying the group name to EOLGOESR from RTGOESR so both
> could be accessed without interference.

The "standard" way of setting up redundant ADDE servers is to keep the
dataset definitions the same and have the end-user change their DATALOC
to point at the server that they want to access.  This prevents them
from having to remember server-specific dataset names for the same
products.

re:
> I'm able to confirm that everything
> works on typhoon,

Can I assume that the fully qualified name for the machine in question
is typhoon.eol.ucar.edu?  If yes, the firewall on typhoon is not allowing
me to access the ADDE server from home, so I can poke around on it (from
home, at least).

re:
> meaning I can view the ADDE files locally with mcidas. I
> tried doing a DATALOC ADD on our processing server down here at FL but I
> don't seem to be able to access the files remotely. Dataloc seems to work

DATALOC manipulates the local client routing table after doing a name/ip
lookup; it does not actually access the remote machine, so there is no surprise
that it works.

re:
> but when I try a DSINFO IMAGE EOLGOESR I get an error:
> 
> xtuser@lightning6:~$ dsinfo.k IMAGE EOLGOESR
> pipe read: Connection reset by peer
> No Datasets found of Type: IMAGE in Group: EOLGOESR
> DSINFO -- done

The 'pipe read' error is telling us that something is interrupting
the transaction before it is complete.  This is very similar to, if
not the same as, what COMET is experiencing.  This is very troubling
and mysterious given that our ADDE installation on ingest.unidata.ucar.edu
is not exhibiting problems for ADDE transactions outside of COMET's.

re:
> /var/log/messages on typhoon contains:
> Mar 23 13:33:56 typhoon xinetd[1647]: START: mcidas pid=12393
> from=::ffff:128.117.82.27
> Mar 23 13:33:56 typhoon xinetd[12393]: execv( /home/mcidas/bin/mcservsh )
> failed: Permission denied (errno = 13)
> Mar 23 13:33:56 typhoon xinetd[1647]: EXIT: mcidas status=0 pid=12393
> duration=0(sec)

OK, thanks for the sleuthing.

re:
> We've double checked the directory permissions and the group memberships
> and everything looks right. Any ideas?

Questions:

 - what is/are the read/write permissions on the script ~mcidas/bin/mcservsh?

 - what are the read/write permissions on ~mcidas and ~mcidas/.mcenv?

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: WPD-667222
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.