Bug 48369

GemStone/S 64 Bit

3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3, earlier versions

3.5.1

Remote process support logs may not be written to preferred location

The location in which Gem process log files are written is controlled by a number of settings, including #dir and #log directives in the GEMSTONE_NRS_ALL, the NRS for the client process, and -D setting for startnetldi on the server and, in a remote gem configuration, the client node startnetldi -D. This allows flexibility to specify paths for the client and server log files from the respective NetLDIs, or from the client process.

In earlier versions, the expansion of the %D with the startnetldi -D argument was done early and could result in invalid log file locations on the server node.

v3.5 included changes, including -D becoming a default directory, and the precedence of settings was calculated differently. While Gem logs were located correctly for most configurations, the location calculation for the logs for the shared page cache monitor and cache page server for a remote Gem was not done correctly, and for some configurations, these logs could be written to default location (the home directory).

Workaround

Configuring the location of process log files may need adjustments, in the Gem's NRS, the GEMSTONE_NRS_ALL, and/or the -D arguments to startnetldi. Contact GemTalk Techincal Support for assistance with the options for a specific version.


Last updated: 10/10/19