CAS management
128 views
Skip to first unread message
alain ubfc
Jul 22, 2019, 6:04:48 AM7/22/19
to CAS Community
Hello,
I’ve been stuck on cas-management for several weeks now.
I followed the Dacurry documentation https://dacurry-tns.github.io/deploying-apereo-cas/building_svcmgmt_overview.html but nothing works.
Here is my configuration of my cas-management.properties file
# Adresse du Serveur CAS
cas.server.name=https://cas.osnetworking.com:8443
cas.server.prefix=https://cas.osnetworking.com:8443/cas
#cas.server.prefix=${cas.server.name}/cas
logging.config=file:/etc/cas/config/log4j2-management.xml
##################################################################
# Update this URL to point at server running this management app #
##################################################################
#cas.mgmt.serverName: ${cas.server.name}
mgmt.serverName=https://casmanagement.osnetworking.com:8443
server.context-path=/cas-management
#server.port=8443
spring.thymeleaf.mode = HTML
mgmt.adminRoles[0]=ROLE_ADMIN
mgmt.userRoles[0]=ROLE_USER
mgmt.userPropertiesFile=file:/etc/cas/config/users.json
######################################
# Gestion des Logs de cas-management #
######################################
logging.config=file:/etc/cas/config/log4j2-management.xml
################################
# Gestion des services en JSON #
################################
cas.serviceRegistry.json.location=file:/etc/cas/services
cas.serviceRegistry.initFromJson = true
############################################################
# Liste des attributs sélectionables depuis le CAS-Manager #
############################################################
cas.authn.attributeRepository.stub.attributes.UDC_IDENTIFIER: UDC_IDENTIFIER
cas.authn.attributeRepository.stub.attributes.cn: cn
cas.authn.attributeRepository.stub.attributes.displayName: displayName
cas.authn.attributeRepository.stub.attributes.givenName: givenName
cas.authn.attributeRepository.stub.attributes.mail: mail
cas.authn.attributeRepository.stub.attributes.sn: sn
cas.authn.attributeRepository.stub.attributes.uid: uid
Here is my json file.
/*
* Wildcard service définition that applies to any https or imaps url.
* Do not use this definition in a production environment.
*/
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^https://casmanagment.osnetworking.com/cas-management/.*",
"name" : "CAS Services Management",
"id" : 1563530823,
"description" : "CAS services management webapp",
"evaluationOrder" : 5500
"allowedAttributes":["cn","sAMAccountName","mail"]
}Is my file correct ?
Thank you
Best regard
alain ubfc
Jul 23, 2019, 4:30:13 AM7/23/19
to CAS Community
| Hello, |
Sorry i had erased the message of Mailvaganam Hari by making a bad handling :
Is port 8443 appearing in the URL redirect? If it is – won’t match with the ACL in the JSON file.
alain ubfc
Jul 24, 2019, 2:14:22 AM7/24/19
to CAS Community
Hello,
In fact I noticed that the/var/log/case-management file has nothing in it.
Yet I set the rights for the file cas-management.log with the chown -R tomcat:tomcat/var/log/cas-management command.
[2019-07-22 08:57:43] [info] 2019-07-22 08:57:43,429 main ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@6ea59bb2] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@506344b1[pattern=/var/log/cas-management/cas-%d{yyyy-MM-dd-HH}-%i.log, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy, SizeBasedTriggeringPolicy(size=10485760), TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)]), strategy=DefaultRolloverStrategy(min=1, max=5, useMax=true), advertiseURI=null, layout=%highlight{%d %p [%c] - <%m>%n}, filePermissions=null, fileOwner=null]] java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@6ea59bb2] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@506344b1[pattern=/var/log/cas-management/cas-%d{yyyy-MM-dd-HH}-%i.log, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy, SizeBasedTriggeringPolicy(size=10485760), TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)]), strategy=DefaultRolloverStrategy(min=1, max=5, useMax=true), advertiseURI=null, layout=%highlight{%d %p [%c] - <%m>%n}, filePermissions=null, fileOwner=null]]
[2019-07-22 08:57:43] [info] 2019-07-22 08:57:43,442 main ERROR Null object returned for RollingFile in Appenders.
[2019-07-22 08:57:45] [info] 2019-07-22 08:57:45,023 main ERROR RollingFileManager (/var/log/cas-management/cas-management.log) java.io.FileNotFoundException: /var/log/cas-management/cas-management.log (Read-only file system) java.io.FileNotFoundException: /var/log/cas-management/cas-management.log (Read-only file system)
Do you have any idea?
Thank you
Best regard
David Curry
Jul 24, 2019, 7:30:30 AM7/24/19
to cas-...@apereo.org
[2019-07-22 08:57:45] [info] 2019-07-22 08:57:45,023 main ERROR RollingFileManager (/var/log/cas-management/cas-management.log) java.io.FileNotFoundException: /var/log/cas-management/cas-management.log (Read-only file system)
Is your file system mounted read-only? Is the directory writable by the tomcat user (or whatever user is running the tomcat process)? RollingFileAppenders need write permission to the directory the log files are in, not just the log files themselves.
--
DAVID A. CURRY, CISSP
DIRECTOR • INFORMATION SECURITY & PRIVACY
THE NEW SCHOOL • INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david...@newschool.edu
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/774ca497-366e-4a20-ac7b-81a933eb55ad%40apereo.org.
alain ubfc
Jul 24, 2019, 8:49:45 AM7/24/19
to CAS Community
Hello David,
Thank you for your answer.
The directory /var/log/cas-management has the following rights :
drwxr-x--- 2 tomcat adm 4096 juil. 22 09:23 cas-management
And for the filecas-management.log
-rw-r----- 1 tomcat tomcat 0 juil. 19 14:39 cas-management.log
That's what i did. And i doesn't work.
That's what i did. And i doesn't work.
How to do this ?
Best regard
Best regard
[2019-07-22 08:57:45] [info] 2019-07-22 08:57:45,023 main ERROR RollingFileManager (/var/log/cas-management/cas-management.log) java.io.FileNotFoundException: /var/log/cas-management/cas-management.log (Read-only file system)Is your file system mounted read-only? Is the directory writable by the tomcat user (or whatever user is running the tomcat process)? RollingFileAppenders need write permission to the directory the log files are in, not just the log files themselves.--
DAVID A. CURRY, CISSP
DIRECTOR • INFORMATION SECURITY & PRIVACY
THE NEW SCHOOL • INFORMATION TECHNOLOGY71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david...@newschool.edu
On Wed, Jul 24, 2019 at 2:14 AM alain ubfc <alai...@gmail.com> wrote:
Hello,In fact I noticed that the/var/log/case-management file has nothing in it.Yet I set the rights for the file cas-management.log with the chown -R tomcat:tomcat/var/log/cas-management command.
David Curry
Jul 24, 2019, 8:55:37 AM7/24/19
to cas-...@apereo.org
Are you positive that the tomcat process is actually running as the tomcat user?
The error message says read-only file system. Are you sure the file system is mounted read-write? Can you create files in it?
Have you turned on debug-level logging to get a more granular idea of what's going on?
Are all the file and directory names spelled correctly everywhere?
Is the regular cas log file (not the management server) in /var/log/cas? Is it being successfully written to?
Beyond "check everything" I'm not sure what advice to give you; it could be a dozen different things.
--
DAVID A. CURRY, CISSP
DIRECTOR • INFORMATION SECURITY & PRIVACY
THE NEW SCHOOL • INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david...@newschool.edu
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/5e999c26-0b23-4cc9-a521-cbdfa36fa1a1%40apereo.org.
alain ubfc
Jul 24, 2019, 9:13:02 AM7/24/19
to CAS Community
David,
I have the log of tomcat /var/log/tomcat/catalina.ou. And it works.
Here is my file /etc/fstab
Here is my file /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/casermgnt--vg-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=af1e7cbd-4161-4099-9000-a7ebbb14c336 /boot ext2 defaults 0 2
/dev/mapper/casermgnt--vg-home /home ext4 defaults 0 2
/dev/mapper/casermgnt--vg-tmp /tmp ext4 defaults 0 2
/dev/mapper/casermgnt--vg-var /var ext4 defaults 0 2
/dev/mapper/casermgnt--vg-swap_1 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
I don't see it.
Le mercredi 24 juillet 2019 13:30:30 UTC+2, David Curry a écrit :
[2019-07-22 08:57:45] [info] 2019-07-22 08:57:45,023 main ERROR RollingFileManager (/var/log/cas-management/cas-management.log) java.io.FileNotFoundException: /var/log/cas-management/cas-management.log (Read-only file system)Is your file system mounted read-only? Is the directory writable by the tomcat user (or whatever user is running the tomcat process)? RollingFileAppenders need write permission to the directory the log files are in, not just the log files themselves.--
DAVID A. CURRY, CISSP
DIRECTOR • INFORMATION SECURITY & PRIVACY
THE NEW SCHOOL • INFORMATION TECHNOLOGY71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david...@newschool.edu
On Wed, Jul 24, 2019 at 2:14 AM alain ubfc <alai...@gmail.com> wrote:
Hello,In fact I noticed that the/var/log/case-management file has nothing in it.Yet I set the rights for the file cas-management.log with the chown -R tomcat:tomcat/var/log/cas-management command.
David Curry
Jul 24, 2019, 9:24:24 AM7/24/19
to cas-...@apereo.org
Check that the process is actually running as tomcat. Turn on debug logging and see what's happening. Compare the owners and modes of the working logs (cas) to the non-working ones (cas-management).
There's a permission that's wrong, or it's running as the wrong user, or there's a typo in a path name, or something. It's really just a matter of meticulously checking everything. Don't assume anything, check everything.
--
DAVID A. CURRY, CISSP
DIRECTOR • INFORMATION SECURITY & PRIVACY
THE NEW SCHOOL • INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david...@newschool.edu
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/cd674a0f-844e-4397-a374-fbbe0b7d1219%40apereo.org.
Matthew Uribe
Jul 24, 2019, 9:32:44 AM7/24/19
to CAS Community
Alain,
Your fstab file shows that /var should be mounting correctly, but a file system can become read-only for any number of reasons. If it is in fact read only, then any user, even root, would not be able to write to it. You could try the following command from the directory /var/log/cas-management : touch testfile
If it creates testfile, then the file system is not read only. If it is read only, you may need to un/remount /var, or simply reboot. If the file system encountered some kind of error, a reboot should hopefully correct it.
That's a good start, just to reduce the problem down to either something wrong at the OS level, or otherwise, something wrong in the configuration of your application. If the file system is not read only, then, as David said, check everything detail by detail. Also to one of David's points, start up Tomcat and look at ps or top to see which uid the is running the Tomcat process. If it's not tomcat or root (please don't run tomcat as root!), then it won't be able to write to /var/log/cas-management
Matt
alain ubfc
Jul 24, 2019, 10:53:07 AM7/24/19
to CAS Community
Matthew,
I relanched tomcat each time as root.
We can see that the /var is in rw.
I relanched tomcat each time as root.
So i addes the user toto in the casermgnt group.
I cheched the mounting of the partitions :
casermgnt@casermgnt:~$ cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=1005320k,nr_inodes=251330,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=204244k,mode=755 0 0
/dev/mapper/casermgnt--vg-root / ext4 rw,relatime,errors=remount-ro 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup2 /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=10494 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
/dev/sda1 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 0
/dev/mapper/casermgnt--vg-home /home ext4 rw,relatime 0 0
/dev/mapper/casermgnt--vg-tmp /tmp ext4 rw,relatime 0 0
/dev/mapper/casermgnt--vg-var /var ext4 rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=204240k,mode=700,uid=1000,gid=1000 0 0
We can see that the /var is in rw.
Is that why the server doesn't start ?
Or it has nothing to do with.
Thank you
Matthew Uribe
Jul 24, 2019, 12:51:27 PM7/24/19
to CAS Community
Thank you for confirming that your /var mount point is rw. Also, since you are running tomcat as root (definitely not recommended for PROD), permissions should not be an issue. It sounds like you need to make sure your configurations are all uniform. Specifically, that your /etc/cas/config/log4j2-management.xml file exists, and contains the correct path to /var/log/cas-management
Also, I noticed that your cas-management.properties file contains this line twice (I don't know if that causes problems or not):
logging.config=file:/etc/cas/config/log4j2-management.xml
alain ubfc
Jul 25, 2019, 3:04:24 AM7/25/19
to CAS Community
Hello Matthew,
I just looked in /etc/cas/config ans i have the file you asked me to check.
I removed the excess line line in /etc/cas/config/management.properties
For the user casermgnt i saw that he has no right to launch tomcat when i make the following command :
systemctl restart tomcat9.service
I have do a sudo to throw it.
Do you have any idea ?
Thank you
alain ubfc
Jul 25, 2019, 5:12:28 AM7/25/19
to CAS Community
Hello David,
My Server does not start.
I looked at your documentation on your site.
I have this as a mistake.
main ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@22624097] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@25503263[pattern=/var/log/cas-management/cas-%d{yyyy-MM-dd-HH}-%i.log, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy, SizeBasedTriggeringPolicy(size=10485760), TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)]), strategy=DefaultRolloverStrategy(min=1, max=5, useMax=true), advertiseURI=null, layout=%highlight{%d %p [%c] - <%m>%n}, filePermissions=null, fileOwner=null]] java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@22624097] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@25503263[pattern=/var/log/cas-management/cas-%d{yyyy-MM-dd-HH}-%i.log, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy, SizeBasedTriggeringPolicy(size=10485760), TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)]), strategy=DefaultRolloverStrategy(min=1, max=5, useMax=true), advertiseURI=null, layout=%highlight{%d %p [%c] - <%m>%n}, filePermissions=null, fileOwner=null]]
main ERROR Unable to invoke factory method in class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.RollingFileAppender java.lang.IllegalStateException: No factory method found for class org.apache.logging.log4j.core.appender.RollingFileAppender
main ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@22624097] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@37b55625[pattern=/var/log/cas-management/cas-%d{yyyy-MM-dd-HH}-%i.log, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy, SizeBasedTriggeringPolicy(size=10485760), TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)]), strategy=DefaultRolloverStrategy(min=1, max=5, useMax=true), advertiseURI=null, layout=%highlight{%d %p [%c] - <%m>%n}, filePermissions=null, fileOwner=null]] java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@22624097] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@37b55625[pattern=/var/log/cas-management/cas-%d{yyyy-MM-dd-HH}-%i.log, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[OnStartupTriggeringPolicy, SizeBasedTriggeringPolicy(size=10485760), TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=false)]), strategy=DefaultRolloverStrategy(min=1, max=5, useMax=true), advertiseURI=null, layout=%highlight{%d %p [%c] - <%m>%n}, filePermissions=null, fileOwner=null]]
main ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.RollingFileAppender for element RollingFile: java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@22624097] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@79d66388[pattern=/var/log/cas-management/cas-management-%d{yyyy-MM-dd-HH}-%i.log.gz, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=true)]), strategy=DefaultRolloverStrategy(min=1, max=7, useMax=true), advertiseURI=null, layout=%d %p [%c] - %m%n, filePermissions=null, fileOwner=null]] java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@22624097] unable to create manager for [/var/log/cas-management/cas-management.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@79d66388[pattern=/var/log/cas-management/cas-management-%d{yyyy-MM-dd-HH}-%i.log.gz, append=true, bufferedIO=true, bufferSize=8192, policy=CompositeTriggeringPolicy(policies=[TimeBasedTriggeringPolicy(nextRolloverMillis=0, interval=1, modulate=true)]), strategy=DefaultRolloverStrategy(min=1, max=7, useMax=true), advertiseURI=null, layout=%d %p [%c] - %m%n, filePermissions=null, fileOwner=null]]
ERROR [org.apereo.cas.CasEmbeddedContainerUtils] - <class org.apereo.cas.CasEmbeddedContainerUtils cannot access a member of class org.apereo.cas.mgmt.CasManagementEmbeddedContainerUtils$1 with modifiers "">
Error creating bean with name 'cachingAttributeRepository' defined in class path resource [org/apereo/cas/config/CasPersonDirectoryConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.services.persondir.IPersonAttributeDao]: Factory method 'cachingAttributeRepository' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'aggregatingAttributeRepository' defined in class path resource [org/apereo/cas/config/CasPersonDirectoryConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.services.persondir.IPersonAttributeDao]: Factory method 'aggregatingAttributeRepository' threw exception; nested exception is java.lang.IllegalStateException: No Scope registered for scope name 'refresh'
[info] Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.services.persondir.IPersonAttributeDao]: Factory method 'cachingAttributeRepository' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'aggregatingAttributeRepository' defined in class path resource [org/apereo/cas/config/CasPersonDirectoryConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.services.persondir.IPersonAttributeDao]: Factory method 'aggregatingAttributeRepository' threw exception; nested exception is java.lang.IllegalStateException: No Scope registered for scope name 'refresh'
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'aggregatingAttributeRepository' defined in class path resource [org/apereo/cas/config/CasPersonDirectoryConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apereo.services.persondir.IPersonAttributeDao]: Factory method 'aggregatingAttributeRepository' threw exception; nested exception is java.lang.IllegalStateException: No Scope registered for scope name 'refresh'
[crit] Erreur lors du déploiement de l'archive [/var/lib/tomcat9/webapps/cas-management.war] de l'application web
[2019-07-25 10:52:51] [crit] java.lang.IllegalStateException: Erreur lors du démarrage du conteneur fils
I've been going in circles for several weeks now
Same Linux Debian operating system 10
Do you have any idea?
Thank you
Best regard
To unsubscribe from this group and stop receiving emails from it, send an email to cas-...@apereo.org.
alain ubfc
Jul 25, 2019, 5:16:03 AM7/25/19
to CAS Community
Hello David
I've been going in circles for several weeks now
My case server works well it is on another vm.
Same Linux Debian operating system 10
Thank you
Best regard
Le lundi 22 juillet 2019 12:04:48 UTC+2, alain ubfc a écrit :
David Curry
Jul 25, 2019, 7:59:56 AM7/25/19
to cas-...@apereo.org
Nothing is going to work correctly until you get the permissions fixed. That means the uid/gid running the Tomcat process, the ownership on the files and directories, and the permissions on the files and directories all have to be compatible.
We've suggested more than once that you turn on debug logging to see what's going on. Have you done that yet? What were the results?
We've also suggested that you go through every single thing, one by one, and *verify* (don't assume, *verify*) that it's correct. Have you done that yet? If you have a working server running CAS, then you should be able to compare things between the two of them and make sure the non-working server is set up exactly like the working server.
There are any number of things that could cause the error you're seeing if they're not done correctly. It's impossible to know which one of them is the problem without checking all of them. That's why we keep telling you to check everything.
--
DAVID A. CURRY, CISSP
DIRECTOR • INFORMATION SECURITY & PRIVACY
THE NEW SCHOOL • INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 646 909-4728 • david...@newschool.edu
On Thu, Jul 25, 2019 at 5:12 AM alain ubfc <alai...@gmail.com> wrote:
Hello David,
Reply all
Reply to author
Forward
0 new messages