Troubleshooting Tips

No files shown when selecting a remote default directory for FTP root

While mounting an FTP filesystem, you are asked to select a remote default directory for the FTP filesystem root, but the dialog box does not show any files (as shown below).

Solution

Upgrade the version of Java on your desktop.

Problem

While viewing the output from the FTP file system, the output is cut off:

(9 May 07:35:36) Synchronizing C:\ftp_filesystems\yarda\ovms_plugins\ideserver\sources\vmsnative\usrwrtnsyssv

(9 May 07:35:36) Synchronizing C:\ftp_filesystems\yarda\ovms_plugins\ideserver\sources\mainrmisvr\bin\org\net

Solution

This is a bug in NetBeans 3.6. If you double click on the Output tab, the tab expands to fill the entire window, as shown below, and the entire line of each message appears. Double click on the output tab again to return the output tab to its previous size and position. The output from the FTP operation will no longer be cut off.

Problem

You created and connected to a remote server, but then are notified that the server has unexpectedly failed, as shown below.

Solution 1

The cause can usually be found in the user server log file on your OpenVMS system.

The login directory for the account in which the remote user server is running contains a file named IDE$USER_YKTCM6.LOG. The following user server log file shows that the logical name table is full.

$ type IDE$USER_YKTCM6.LOG
Defining TZ as US/EASTERN
Calling Java setup procedure SYS$COMMON:[SYSMGR]JAVA$142_SETUP.COM;7
%SYSTEM-F-EXLNMQUOTA, logical name table is full
USER          job terminated at 16-MAY-2005 08:16:23.43
Accounting information:
Buffered I/O count:    61      Peak working set size:       2432
Direct I/O count:      33      Peak virtual size:         171744
Page faults:           177     Mounted volumes:             0
Charged CPU time:   0 00:00:00.06      Elapsed time:        0 00:00:00.14
$

To solve this problem, increase the size of JTQuota for the user account. (To run a remote user server, the minimum JTQUOTA is 60,000.)

Solution 2

You may also see the server unexpectedly fails error when the working set size is too small. For example:

$ type IDE$USER_UDPZMD.LOG;1
$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
Defining TZ as US/EASTERN
Calling Java setup procedure SYS$COMMON:[SYSMGR]JAVA$142_SETUP.COM;7
Pointing the parent server process at the FastVM, subprocess will use Classic VM
Starting User Server using RMI port 1099
JAVA_SWITCHES = " -Xss512k -Xdynclassgc "-Dsun.rmi.dgc.server.gcInterval=30000" -V "
Could not allocate heap of size 16.0 MB.
**Out of memory, exiting.**, file JDEV:[fastvm.srcjava.sys.alpha]gcinit.c;2, line 248
USER          job terminated at 16-MAY-2005 08:37:16.88
Accounting information:
Buffered I/O count:   198      Peak working set size:       5936
Direct I/O count:      78      Peak virtual size:         217072
Page faults:          842      Mounted volumes:                0
Charged CPU time:       0 00:00:00.12      Elapsed time:       0 00:00:00.39
$

To solve this problem, increase the size of WSEXTENT for the user account to at least 200,000, and increase the PGFLQUO for the process to at least 500,000.

Problem

You mounted an FTP filesystem but see a long list of .log files displayed under your top-level directory.

Solution

In the Filesystems tab, right click on the FTP filesystem and select Properties. In the space next to Ignored Files Extensions, type log and press Enter. Then click Close. The log files will disappear from view.