Administering the Genero Application Server / Log files |
The GAS logs may include some sensitive or personal user data that is gathered during the normal course of running applications.
"Start process" Directory: /opt/fourjs/fglgws/demo, Command line: "/opt/fourjs/fglgws/bin/fglrun" demo.42m
All VM content written to the standard output (stdout and stderr) is redirected to the session log files (vm-<session-id>.log).
If you are using the fastcgi dispatcher, all the FastCGI protocol parameters can be logged, including IP addresses, and authentication information (REMOTE_USER, etc).
The GAS may log all environment at start up, including all system environment variables, system limits, etc. In the proxy log, some information on where the DVM will connect is also logged. For example, ... "FGLSERVER" 127.0.0.1:49913:
Clients send additional environment information to the logs at start up. For example, the GDC sends device MAC address, user name, host name, etc.
The monitor page, though not directly related to the log files, provides access to dispatcher and proxies / VM log files. It also provides a list of active sessions, with detailed information on the user agent, IP addresses, command lines used to start applications, authenticated user (CGI REMOTE_USER), environment variables, and access to configuration of available applications and services.
What are you using the data for?
Gas log files are essential for debugging and support response, and for that purpose are used for collecting status information on the VMs and the proxies.
Where is the data being stored?
The data is stored on the server running the GAS. Consider who has access to the log files, and ensure access is restricted to administrators and users who need to work with the GAS log files.
Do you still need the data?
Consider how long you need to keep logs. Review your log file management system and remove log files after a predefined period. See Manage the Genero Application Server log files.