Ripro Server Troubleshooting
Scinet Communication

• Error message when copying files or pages from Ripro - creates page on Whisper but does not copy files
• Message "bad directory name" on Whisper and "unable to show requested list" on PS/2
• Message "device cannot be mounted" appears on the Whisper
• Message "no communication with remote station" when accessing Ripro from Whisper or PS/2
• SciNet Server does not start after moving the LANC board to another slot on the Ripro

Error message when copying files or pages from Ripro - creates page on Whisper but does not copy files

Recommended Solution
File and page names on Ripro are case sensitive

Message "bad directory name" on Whisper and "unable to show requested list" on PS/2

Recommended Solution
Make sure "jobs" directory on Ripro has not been changed or deleted (e.g. jobs%0)

Message "device cannot be mounted" appears on the Whisper

Recommended Solution

1. Check "SciNet Exports" on exported data volume (Scismit).
2. Check permissions and owner of "jobs" and all father directories, should be "rw" for group "macusers" or "scitex".
3. Check that the Device Logical Name (in SciSmit) is in format "dx" and not "Dx".
4. Check if subnet exist or incorrect (should be LAN).
5. Run "Reorganize disks" in SciSmit(see Fixed Disks).

Message "no communication with remote station" when accessing Ripro from Whisper or PS/2

Recommended Solution

1. Reboot Whisper or PS/2.
2. Check SciNet Communications in SciSmit. Type "psp" at UNIX prompt ("ps aux |grep progs").
3. Check that the processes "lj_srv" and "rfa_servtask" appear in the list.
4. Type "scinet_ping" at Unix prompt and enter name and subnet of Whisper or PS/2 station.
5. Check that the server has a unique SciNet name and that the board and connections are O.K.
6. If any changes are made stop and start SciNet servers (SciSmit).
7. Logout and then login as user "scitex".
8. Reboot the server.

SciNet Server does not start after moving the LANC board to another slot on the Ripro

Recommended Solution

Reconfigure the LANC driver:

1. Login as "root".
2. Type "lsdev -C | grep lanc". The system will return "lancx defined 00-02 System Object" where lancx is the LANC/MCA device (e.g. lanc0) and "00-02" is the slot in which the board was previously inserted.
3. Type "rmdev -l lancx -d" (e.g. rmdev -l lanc0 -d).
4. Type "cfgmgr".
5. Type "lsdev -C | grep lanc" and verify that the device is "available".

6. Logout and then login as user "scitex".