8/31/2023 0 Comments Nxserver logs![]() ![]() For example, you can read more about this here in the Enterprise Desktop guide. ![]() If you want to view details about user access, session ID etc, you can view this type of information by running ânxserver âhistoryâ. In version 7 and onward, enabling log_level to â7â will show all events useful for debugging. Session recording events is definitely something we can evaluate adding to extend and improve the current support for auditing. File transfer operations are not logged in server log. Logger::log nxnode 6244 Jan 15 11:32:02 enb-test NXSERVER-3.5. ![]() File transfer operations are logged into server log. 3.on servers config: try paste local rules after the rules for processing remote logs. 2.on servers config: comment out string & and check. Logs contain the word âAuditâ and are logged also to Rotemya Please, check, if there events from client on the servers local logs Some following tips may be helpful: 1.be sure that last string of config files is blank. Gather the server logs, from the location (s) outlined above generally, ZIPPING each directory listed in the table above works best Send the logs to IBM Support. Gather the .metadata.log file and ZIP it.# Enable or disable the creation of file transfer logs for auditing Reproduce the problem, Stop the server (s) involved, Exit Rational Application Developer. The log contains information like the file name, the direction of the transfer, the size in bytes, start and end dates, the result and the transfer rate, information which can be easily parsed by custom scripts. This feature allows system administrators to audit all activities about transferring files from client to server and vice-versa. Hi, logging of file transfer activity is available in version 8 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |