Application server: CAUAJM_W_00002 Listener could not be started on port [9000]. Address already in use.
Article ID: 213262
Updated On:
Products
Issue/Introduction
We are busy installing Autosys Workload Automation R12.0 on our RHEL7 Linux servers, but we are facing some problems with the application server.
We have started with a default /opt/CA/SharedComponents/Csam/SockAdapter/cfg directory, which means no APPF-GLOBAL nor PORTRANGE-GLOBAL files are available in this directory.
Using this configuration, the application server starts correctly, but we get some warning messages:
CAUAJM_W_20206 Port 9000 has not been configured through the CA Secure Sockets Adapter.
CAUAJM_W_20206 Port 49179 has not been configured through the CA Secure Sockets Adapter.
So far so good, but we also have a client installed on a Solaris machine which should connect to this application server on Linux. Every CLI command issued on the Solaris machine fails because it cannot communicate with the R12.0 application server on Linux:
CAUAJM_E_10029 Communication attempt with the CA WAAE Application Server has failed! [slvncnwlmd02.lin.oper.local:9000]
CAUAJM_E_10221 Exhausted list of available Application Server(s). Failing request.
CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s).
We know that port 9000 is muxed to port 7163 on the Solaris machine, so we decided to configure port 9000 on the R12 Linux machine using these commands:
$CSAM_SOCKADAPTER/bin/csampmux stop
$CSAM_SOCKADAPTER/bin/csamconfigedit port=9000 EnableSSL=False EnablePmux=True pmuxServerPort=7163
$CSAM_SOCKADAPTER/bin/csamconfigedit portrange=49152-50176 EnableSSL=False EnablePmux=True pmuxServerPort=7163
$CSAM_SOCKADAPTER/bin/csampmux start
netstat -an | grep 9000
netstat -an | grep 7163
tcp6 0 0 :::7163 :::* LISTEN
unisrvcntr restart waae_server.DEV
But in then the application fails:
CAUAJM_W_00002 Listener could not be started on port [9000]. Proceeding... [listen(): 98: Address already in use]
CAUAJM_E_10125 AutoSys Application Server failed to establish a listener at host [slvnenwlmd06.lin.oper.local:9000]. Exiting.
CAUAJM_I_30004 AutoSys Application Server shutdown complete.
CAUAJM_I_30000 AutoSys Application Server exiting.
autoflags -a
0028 LINUX ORA 12.0 01.00 a10a1510 slvncnwlmd02.lin.oper.local slvncnwlmd02.lin.oper.local
Environment
Release : 12.0
Component : WORKLOAD CONTROL CENTER
Cause
./csam_broker is created with wrong permissions 775 in $CSAM_SOCKAPTER directory
Resolution
This is the output of the command "cat /boot/config* | grep _ACL":
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_FS_POSIX_ACL=y
CONFIG_GENERIC_ACL=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_CEPH_FS_POSIX_ACL=y
CONFIG_CIFS_ACL=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_FS_POSIX_ACL=y
CONFIG_GENERIC_ACL=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_CEPH_FS_POSIX_ACL=y
CONFIG_CIFS_ACL=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_BTRFS_FS_POSIX_ACL=y
CONFIG_FS_POSIX_ACL=y
CONFIG_GENERIC_ACL=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_CEPH_FS_POSIX_ACL=y
CONFIG_CIFS_ACL=y
Issue is with the ACL’s on /opt/CA/SharedComponents/Csam/SockAdapter.
The application server is running with userid autosys / group autosys, but this group did not have write access to the SockAdapter directory.
Add this entry to the ACL: “group:autosys:rwx”. This way the application server could be successfully started.
Socket file “.csam_broker” is still created with permission bits 775, but the application server now has write access thanks to the ACL settings.
.
Feedback
