[Stack Guard Vulnerability in Red Hat Enterprise Linux 7]
Yesterday I came across incident where the agent did not start as the “emctl” command got failed with a new error message. This happened after recent Infrastructure Maintenance Activity where OS patching was scheduled by our Infrastructure team on all servers. The host on which this issue occur had OS Version RHEL 7 “Red Hat Enterprise Linux Server release 7.3 (Maipo)”.
So all emctl commands whether it was “emctl start agent”, “agent stop agent” even “emctl help” failed. The error returned was “agent_220.127.116.11.0/perl/bin/perl: Argument list too long”. Check the screenshot below explains the entire scenario.
ERROR Message:- “agent_18.104.22.168.0/perl/bin/perl: Argument list too long”
Cause:- Why are applications failing to start with error message “Argument list too long” after applying the fix for Stack Guard Vulnerability in Red Hat Enterprise Linux 7 ?
Solution:- Change the commonenv file found in agent_22.214.171.124.0/bin to hash out this line
After making this change the issue got fixed and emctl command was running successfully without any issue.
Yesterday itself I came across this error when I was creating a new database for “Always On Monitoring” for my OEM13c production environment.
The error message was simple enough to understand that there was some syntax problem in my “tnsnames.ora” file which caused this Error message to pop-up before DBCA can start its cloning process.
As mentioned in the error message the database name “ENGTST”, and it says that an unexpected char or LITERAL before or at ENGTST. So it became easy for me to troubleshoot. I search for the entry in tnsnames.ora file and found that there was an extra space in the very beginning. After removing that extra space, I re-ran the process and it did not fail again at the same step.
Very small issue yet, I came across it for the first time to thought to share it with everyone.
Other possibility for error “TNS-04404” can also be
- Running the Network Configuration Assistant (NETCA) on the database server, to modify the Local Service Name settings that are stored within the TNSNAMES.ORA configuration file.
Usually if you receive this error, the particular TNS entry that is problematic will be always indicated in the error message. Example in my scenario the “ENGTST” was the problematic entry.
To solve this error, make the necessary changes in the “tnsnames.ora” file and you should be good to go.