Just to add. I have a similar setup(centos) and running cas server version
5.3.0
I always package war file and deploy to tomcat webapps directory and start
tomcat manually. And my cas.properties file looks like
logging.config: file:/etc/cas/config/log4j2.xml
cas.authn.accept.users=
Emmanuel,
The last log line is deploying 'webapps/cas'. I deploy the war file,
'webapps/cas.war'. This should not make a difference but maybe.
Are you creating a war file? Is it in webapps directory? Or are you creating a
link from webapps/cas to some other directory where there is an exploded
Thanks Ray. I am running one server and I deployed CAS to Tomcat.
I have changed the Tomcat port to 8447 and restarted.
Here are some outputs:
*systemctl status -l tomcat*
tomcat.service - Apache Tomcat Web Application Container
Loaded: loaded (/etc/systemd/system/tomcat.service; enabled;
Emmanuel,
Are you running two servers; CAS and tomcat? Or did you deploy CAS to tomcat?
You could edit tomcat's server.xml and change port 8443 to something else.
Ray
On Wed, 2019-01-02 at 18:02 +0100, Emmanuel Chukwu wrote:
Hi Ramakrishna,
Thanks for you recommendation. I configured CAS to
Hi Ramakrishna,
Thanks for you recommendation. I configured CAS to run on the standard
https port (443) and Tomcat to run on port 8443.
I have tried option (1) and this is the process running on port 8443.
tcp6 0 0 :::8443 :::*
LISTEN 6869/jsvc.exec
Each time I
Possible solutions.
1. Kill the process running on 8443 and start cas.
or
2. Change the port of cas in properties file and try restarting.
or
3. Build, Package cas.war file and manually deploy in tomcat and restart.
Also check if log folder has appropriated permission to create / write log
Happy New Year. Welcome to 2019 everyone. I am wishing all a happy and
successful year ahead.
Please I still need help with this issue.
On Fri, Dec 28, 2018 at 8:25 PM Emmanuel Chukwu
wrote:
> Dear all,
> I just finished installing and configuring CAS 5.3 on CentOS 7 using
> David's notes
>
