[daip] AIPS error at log in

[Eric Greisen]

On 5/12/21 9:40 PM, shen lu via Daip wrote:
> Dear,
> 
> I was trying to infall AIPS, but after I infall it via perl. It has been successfully installed. However, when I log in, there are few errors. I copy the message below. Could you help me on the installation?
> 
> Best,
> Lu
> 
> START_AIPS: Your initial AIPS printer is the
> START_AIPS:  - system name , AIPS type
> 
> START_AIPS: User data area assignments:
> DADEVS.PL: This program is untested under Perl version 5.018
>   (Using global default file /Users/shenlu/workspace/aips/DA00/DADEVS.LIST for DADEVS.PL)
>    Disk 1 (1) is /Users/shenlu/workspace/aips/DATA/SHENS-IMAC-PRO_1
> 
> Tape assignments:
>    Tape 1 is REMOTE
>    Tape 2 is REMOTE
> 
> START_AIPS: I am GUESSING you are at a workstation called shens-imac-pro
> START_AIPS: Starting TV servers on shens-imac-pro asynchronously
> START_AIPS:  - with Internet Sockets...
> START_AIPS: Starting TPMON daemons on SHENS-IMAC-PRO asynchronously...
> Starting up 31DEC21 AIPS with normal priority
> ERROR  3 ON UNIT TTDEV01         , GETTING HOST/SERVICE BY NAME
> ZMSGOP: ZTTOPN RETURNS ERROR =   1 FOR LUN =   6
> ZDCHIN: COULD NOT READ PARAMETER FILE
> ZDCHIN: (USING MINIMUM SYSTEM CONFIGURATION)
> Begin the one true AIPS number 1 (release of 31DEC21) at priority =   0
> AIPS 1: ZOPEN: FILE DA00:SPD000000;          NOT FOUND
> ZDCHIN: COULD NOT READ PARAMETER FILE
> ZDCHIN: (USING MINIMUM SYSTEM CONFIGURATION)
> AIPS 1: ZDCHIN: NO NETSP ENTRY FOR DA01
> AIPS 1: You are assigned TV device/server   1
> AIPS 1: You are assigned graphics device/server   1
> AIPS 1: Enter user ID number
> ?DADEVS.PL: This program is untested under Perl version 5.018
> XASERVERS: TVSERV is already running on host shens-imac-pro, user shenlu
> XASERVERS: Start XAS on shens-imac-pro, DISPLAY /private/tmp/com.apple.launchd.EuTIUO2Oui/org.macosforge.xquartz:0
> XAS: ** TrueColor FOUND!!!
> XAS: ***  Using shared memory option for speed ***
> XAS: Using screen width 2550 height 1318,
>      max grey level 8191 in 16 grey-scale memories
> Shared memory id failure: Cannot allocate memory
> XASERVERS: TEKSRV is already running on host shens-imac-pro, display /private/tmp/com.apple.launchd.EuTIUO2Oui/org.macosforge.xquartz:0, user shenlu
> XASERVERS: MSGSRV is already running on host shens-imac-pro, display /private/tmp/com.apple.launchd.EuTIUO2Oui/org.macosforge.xquartz:0, user shenlu
> 
> AIPS 1: Enter user ID number
> ?1
> AIPS 1: ZOPEN: FILE DA00:PWD000000;          NOT FOUND
> 
> _______________________________________________
> Daip mailing list
> Daip at listmgr.nrao.edu
> https://listmgr.nrao.edu/mailman/listinfo/daip
> 

It seems that some things went wrong near the end of the installation. 
Most likely you did not do the step - in a separate window - to
execute fix_aips_macos.sh under a bash shell.  That is necessary or AIPS 
programs cannot run.  It seems as if you ran that eventually because
AIPS was able to execute.  You need to

source $AIPS_ROOT/LOGIN.SH
RUN FILAIP
8 2

RUN POPSGN
0 POPSDAT TST
<cr>

<cr> = press Enter key

Then probably the SP, PW and many other files will be present.

Then there is the problem of the XAS TV display and shared memory.  The 
text below comes from the AIPS Manager FAQ.

  On the latest "leopard", "snow leopard", "lion", "mountain lion", and 
"yosemite" (X 10.5-10.10) systems, /etc/rc is gone and creating it will 
have no effect. You need to create an /etc/sysctl.conf file and put the 
values in it,

             kern.sysv.shmmax=10485760
             kern.sysv.shmmin=1
             kern.sysv.shmmni=32
             kern.sysv.shmseg=8
             kern.sysv.shmall=4096


You should use the values you had when you were running tiger. Those 
could be in /Previous\ System/etc/rc, assuming you have "Previous 
System". So three different OS upgrades and three different ways to 
adjust the default shared memory. Note: You will need to reboot the 
system for the change in shared memory to take place. You can check if 
the shared memory changes happened by typing "sysctl kern.sysv" in a 
terminal or xterm window. Look for the kern.sysv.shm* values. If the 
values have not changed, make sure you haven't inadvertently left in 
"sysctl -w" in the /etc/sysctl.conf file or mis-typed one of the values. 
If the /etc/sysctl.conf file is not properly formatted, or shmmax is not 
an integer multiple of shmall, the shared memory will not be adjusted 
after the reboot.


Eric Greisen