Skip to main content

Unix Agent Release Notes

Version 24.0.0

2024 September

UNIX-395: Removed options for enabling and configuring SFTP transfers.

UNIX-398: lsamport.service file now contain correct LF line endings instead of CRLF.

UNIX-416: Updated agent by reenabling legacy providers for SMAFT transfers.

UNIX-418: systemd service now installs correctly even if /etc/init.d directory exists.

UNIX-420: TLS version settings now respect system-wide OpenSSL config.

UNIX-453: Internal logging ports LSAM_PORT+5 and LSAM_PORT+6 now use local UNIX sockets instead of TCP sockets to mitigate inadvertent DoS from TLS security scans.

UNIX-426: Added support for Debian12.

Version 22.0.0

2023 June

UNIX-392: Fixed an issue in UNIX agent where LSAM shuts down after "Data has not arrived in 600 seconds".

Version 21.2

2021 August

UNIX-331: Fixed an issue in UNIX agent where file transfers to a Windows machine failed if the Windows machine was configured with an IPv6 address.

UNIX-360: Fixed an issue in UNIX agent where if the /tmp folder does not exist, then it creates one under the current installation folder.

UNIX-361: Fixed an erroneous message in the UNIX agent log on core dump.

UNIX-375: Fixed an issue in UNIX agent where a Symitar Print job did not run successfully due to incorrect handling of environment variable addresses.

UNIX-382: Allows running of maintain_ofiles at a user configured time, when no jobs are running so it does not fail due to conflicts.

UNIX-388: Fixed an issue in UNIX agent where the buffer size for environment variables was increased to 2K from 1K to accommodate larger variables.

Version 21.0

2021 April

UNIX-386: Fixed an issue in UNIX agent where sometimes jobs failed with STDERR: LOGNAME this variable is read only.

UNIX-387: Fixed an issue in the UNIX agent where a user profile environment variable like SHELL was getting overwritten by another value by the agent.

Version 20.0

2020 December

UNIX-378: Fixed an issue in SMAFT wild card transfer where the specified destination file field is supposed to be a directory name, but instead it exists in the system as a regular file.

UNIX-377: Fixed an issue in which "lsam refresh" command improperly auto-configures path_to_su setting to "no" on non-Symitar platforms. The work-around is to use "lsam config" to set path_to_su to "yes" and then issue a "lsam restart" command.

UNIX-376: Fixed an issue where install_lsam script doesn't create the correct port number when LSAM_instance label option is specified.

UNIX-372: Fixed an issue where the Control File filename length is limited to 63 characters.

UNIX-349: Fixed an issue where the Installation procedure in the UNIX documentation did not specify that the install_agent script needed to be copied from the installation media/ftp site to the /tmp folder in order to update the UNIX LSAM.

Version 19.1.25

2020 May

✅ Fixed an issue where SMAFT jobs transferring from UNIX to Windows, with the job starting at the destination (Windows), could result in excessive delay and intermittent timeouts.

✅ Fixed an issue where path_to_su would not be able to execute successfully. If unable to su properly, it will now default to the older user impersonation model.

Version 19.1.16

2020 May

✳️ Added TLS support to SMAFT (SMA File Transfer) feature. Added a new parameter, SMAFT_TLS_socket to lsam.conf to designate that this port number is used for TLS SMAFT. Note also that parameters lsam_pem_file and lsam_private_key_file in lsam.conf need to be defined for TLS SMAFT to work.

✳️ Enabled starting and stopping the LSAM service using systemctl on Linux servers.

✳️ Changed the path_to_su default from "No" to "Yes" for executing jobs as this is the recommended default for new installations.

✅ Fixed an issue where filenames that have "$" embedded in them resulted in the filename being truncated after the "$" character. This problem only happened on su-submitted SMAFT jobs.

✅ Fixed an issue where the install_agent script that was used to install UNIX did not restart the agent after a system reboot. This was due to Debian and Ubuntu using different directories in Redhat for auto-restarting with systemd on reboot.

✅ Fixed an issue where multiple white spaces were trimmed in a start_image that contained an encrypted property value.

✅ Fixed an issue where "Received unauthorized message - discarded" messages may have caused communication to the sma_lsam process to crash, resulting in the agent being stopped/terminated. The safest course is to not print the contents of the discarded message.

✅ Redesigned the sma_log process to resolve an issue where the LSAM crashes intermittently on later Redhat releases.

✅ Fixed an issue where jobs fail when UNIX LSAM starts the "main_ofiles" program. Changed main_ofiles to run once daily any time between 3 AM to 4 AM when the system is likely to be idled.

Version 19.0.0

2019 July

✳️ Enhanced File Arrival jobs to now allow a total of 255 characters in the filename only (not including the path name) and 1023 characters in the path name. The previous limit for File Arrival jobs allowed for 128 characters.

✅ Fixed an issue where File Arrival jobs would return successfully when encountering a signal 11 error (or any other abnormal signal). It will now return exit code 4 and log the message "Internal system error: Abnormal signal caught".

✅ Fixed an issue where encrypted arguments in embedded script jobs were not decrypted and encrypted environment variables were not decrypted.

✅ Fixed an issue where the bound_NIC_adapter_ip setting in the lsam.conf file was not working.

✅ Fixed an issue where the UNIX LSAM would escape UNC paths of Windows filenames for SMAFT file transfer jobs that start on the UNIX side and have path_to_su enabled.

✅ Updated install_agent script to support LSAM instance label name.

✅ Fixed an issue where jobs fail when UNIX LSAM starts the "main_ofiles" program. Changed main_ofiles to run once daily any time between 3 AM to 4 AM when the system is likely to be idled.

Version 18.3.0

2018 November

✳️ Updated UNIX Job Action: File Arrival performance to utilize less CPU usage.

✳️ The days_of_output_to_keep parameter description has been updated to clarify that setting the value to 0 will disable clean-up of STDOUT and STDERR files.

✅ Fixed an issue with recognizing the profile PATH environment variable when path_to_su was enabled.

✅ Fixed an issue where TLS communication between SAM and the Job Output Retrieval Service (JORS) was not working for the following platforms: HP-UX, SOLARIS, UBUNTU, DEBIAN, and SUSE.

✅ Fixed an issue where the KILL command issued from the Enterprise Manager failed to completely terminate the "non-root" user su-submitted job. This issue only affected Redhat releases RHEL6 and higher.

Version 18.2.0

2018 September

✅ Fixed an issue with File Transfer jobs where files containing a wildcard going to a single file failed with an exit code 14099 "compression not supported" error.

✅ Fixed an issue in the Job Output Retriever where logfiles and errfiles were not written to the correct path.

Version 18.1.0

2018 June

✳️ Added the ability to define Environment Variables to UNIX Job Action: Embedded Script.

✳️ Added the ability to parse job output for UNIX jobs to determine an exit code.

✳️ Added the ability to define Environment Variables to UNIX Job Action: Run Program.

✳️ Added the following job meta-data to STDOUT files:

  • JOB_ID
  • SCHEDULE_DATE
  • SCHEDULE_NAME
  • SCHEDULE_FREQ
  • START_IMAGE
  • UNIX_LSAM_ROOT_DIR
  • JOB_START_TIME

✳️ Removed the max_burst parameter from the LSAM configuration file.

✅ Fixed an issue where FAD processed files that were already created.

✅ Fixed an issue with the UNIX LSAM where file transfers with wild cards and spaces in the file name did not work.

✅ Fixed an issue where SMA File Transfer successfully transferred a file into the parent folder (/) when the specified destination folder (e.g., /TMP) did not exist. The transfer will now fail with a sample message "Destination directory /TMP doesn't exist or accessible by user" when this condition is detected.

✅ Fixed an issue where sometimes the UNIX destination file permission was not set correctly when the UNIX LSAM would initiate an SMA File Transfer job from Windows to UNIX.

✅ Fixed an issue where a non-descriptive exit code 16 was given when performing a file transfer without specifying the destination file name. Now, file transfers can be transferred with no destination file name specified.

Version 17.1.0

2017 December

✳️ Added support to use the newer Linux systemd service to enable auto-start of LSAM on system reboot.

✳️ The Prerun, Start Image, and Arguments fields in UNIX Job Details now allow up to 2000 characters.

✳️ Updated the UNIX SMA File Transfer (SMAFT) exit codes. These codes can be found in the agent documentation for UNIX.

✳️ Updated the UNIX LSAM to allow writing files larger than 2 gigabytes for SMA File Transfer on AIX platform.

✳️ Updated the UNIX LSAM to return the actual start command of a job back to OpCon, which can be referenced on the OpCon side using the property [[JI.$START COMMAND]].

✳️ Added support for Advanced Failure Criteria to UNIX Job Action: File Arrival.

✳️ Updated the UNIX LSAM to return new exit codes for UNIX Job Action: File Arrival.

✳️ Updated the UNIX LSAM to support encrypted tokens. To use encryption token capability, tarfiles that have "SSL" support must be used since encryption relies on the SSL encryption libraries. Users do not have to enable or turn on the UNIX agent's TLS communication with OpCon to take advantage of this feature, they only need to use SSL-labeled tarfiles.

✅ Fixed an issue where the Time Sent field was displayed incorrectly in the Enterprise Manager Advanced Machine Properties.

✅ Fixed an issue where if the Start and End Time were set to zero in a File Arrival job, then the job failed even if the file was present.

✅ Fixed an issue with the UNIX LSAM where the detection of duplicate job start requests for the same job from OpCon could trigger data corruption and the crash of SMANetCom.

✅ Fixed an issue where UNIX Job Action: File Arrival would not detect a file if the path used a symbolic link.