[midPoint] Installation of midpoint 3.5 on CentOS 7 failed

Tue Apr 11 13:27:08 CEST 2017

Hi Ivan!

Great! It works!!!

Thank you very much. 

It seems the distribution midpoint package contains at least one file 
differing to file contained in war. 

Radim 

Od:     Ivan Noris <ivan.noris at evolveum.com>
Komu:   midpoint at lists.evolveum.com
Datum:  11.04.2017 12:49
Předmět:        Re: [midPoint] Installation of midpoint 3.5 on CentOS 7 
failed
Odeslal:        "midPoint" <midpoint-bounces at lists.evolveum.com>

Hi Radim,
that's strange.
Let's see what I would do - and you can compare this to your situation:
1. download midpoint.war file or dist archive and extract midpoint.war 
from there
2. copy midpoint.war to tomcat/webapps. Do not start Tomcat yet.
3. create empty /var/opt/midpoint directory writable by tomcat user
4. configure tomcat to run with -Dmidpoint.home=/var/opt/midpoint
5. start tomcat
This must work. Please note that I have just used midpoint.war file and 
nothing else from the binary distribution. Midpoint will create 
config.xml, default embedded H2 database in /var/opt/midpoint and several 
other empty directories.
Regards,
Ivan

On 04/10/2017 06:00 PM, Radim Jaeger wrote:
Hi Ivan! 

Well. I completely reinstalled midpoint 3.5 into a clear place. 
I found in the /var/opt/midpoint/schema   the subdirectory xml with some 
content. 

Subsequently, I changed the owner of subtree /var/opt/midpoint to 
tomcat:tomcat., deleted the subdirectory /midpoint and the file "old" file 
midpoint.war from the tomcat webapps directory, copied the "fresh" file 
midpoint.war to tomcat webapps directory and started the tomcat service. 

The same error occurs :-( 

Radim 

Od:        Ivan Noris <ivan.noris at evolveum.com> 
Komu:        midpoint at lists.evolveum.com 
Datum:        10.04.2017 17:36 
Předmět:        Re: [midPoint] Installation of midpoint 3.5 on CentOS 7 
failed 
Odeslal:        "midPoint" <midpoint-bounces at lists.evolveum.com> 

Hi Radim, 
my guess is that your /var/opt/midpoint/schema directory contains the 
midpoint schemas (did you extract the zip/tar.gz into /var/opt/midpoint?) 
The "schema" subdirectory is only for schema additions (custom attributes 
etc.), not for the standard ones. Can you check that please? 
/var/opt/midpoint should be completely empty at the start with 
just-downloaded midpoint, possibly with config.xml if you have real 
database. 
Please let me know, 
Ivan 

On 04/10/2017 05:29 PM, Radim Jaeger wrote: 
Hi everybody! 

I'm new in the Midpoint IDM. My company wants to test its reliability for 
a public IT services provided by governmental bodies. 

I tried to install Midpoint v3.5 on the plain CentOS 7 following 
instruction found on your website. 

Kernel version:                3.10.0-514.10.2.el7.x86_64 
Java Home:                /usr/java/jdk1.8.0_121/jre 
Java vendor:                Oracle 
Tomcat:                8.5.13.0 
CATALINA_HOME:        /opt/tomcat 
MIDPOINT_HOME:        /var/opt/midpoint 

When I copied the midpoint.war to the Tomcat webapps directory and started 
Tomcat service, it particullary fails. Tomcat started all applications 
except midpoint :-(   

In the catalina.out I found errors   

06-Apr-2017 15:38:22.210 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application 
archive /opt/tomcat/webapps/midpoint.war 
06-Apr-2017 15:38:28.034 INFO [localhost-startStop-1] 
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned 
for TLDs yet contained no TLDs. Enable debug logging for this logger for a 
complete list of JARs that were scanned but no TLDs were found in them. 
Skipping unneeded JARs during scanning can improve startup time and JSP 
compilation time. 
midpoint.home = /var/opt/midpoint/ 
Loading midPoint configuration from file /var/opt/midpoint/config.xml 
06-Apr-2017 15:38:32.457 SEVERE [localhost-startStop-1] 
org.apache.catalina.core.StandardContext.startInternal One or more 
listeners failed to start. Full details will be found in the appropriate 
container log file 
06-Apr-2017 15:38:32.458 SEVERE [localhost-startStop-1] 
org.apache.catalina.core.StandardContext.startInternal Context [/midpoint] 
startup failed due to previous errors 
06-Apr-2017 15:38:32.472 INFO [localhost-startStop-1] 
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web 
application archive /opt/tomcat/webapps/midpoint.war has finished in 
10,261 ms 

In the idm.log I found logs indicating the midpoint started but failed : 

2017-04-06 15:38:32,324 [] [localhost-startStop-1] ERROR 
(com.evolveum.midpoint.prism.schema.XmlEntityResolverImpl): Unable to 
resolve entity with publicID: null, systemID: 
http://midpoint.evolveum.com/xml/ns/public/common/common-core-3.xsd 
2017-04-06 15:38:32,324 [] [localhost-startStop-1] ERROR 
(com.evolveum.midpoint.prism.schema.XmlEntityResolverImpl): Unable to 
resolve entity with publicID: null, systemID: 
http://midpoint.evolveum.com/xml/ns/public/common/common-core-3.xsd 
2017-04-06 15:38:32,442 [] [localhost-startStop-1] ERROR 
(com.evolveum.midpoint.prism.schema.SchemaHandler): Error occured during 
schema parsing: [Fatal] on line 1 at 
http://midpoint.evolveum.com/xml/ns/public/common/common-core-3.xsd, null 
White spaces are required between publicId and systemId. 
2017-04-06 15:38:32,443 [] [localhost-startStop-1] WARN 
(org.springframework.web.context.support.XmlWebApplicationContext): 
Exception encountered during context initialization - cancelling refresh 
attempt: org.springframework.beans.factory.BeanCreationException: Error 
creating bean with name 'repositoryFactory': Injection of autowired 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Could not 
autowire field: private com.evolveum.midpoint.prism.PrismContext 
com.evolveum.midpoint.init.RepositoryFactory.prismContext; nested 
exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'prismContext' defined in class path 
resource [ctx-configuration.xml]: Bean instantiation via factory method 
failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to 
instantiate [com.evolveum.midpoint.prism.PrismContext]: Factory method 
'createInitializedPrismContext' threw exception; nested exception is 
com.evolveum.midpoint.util.exception.SchemaException: XML error during XSD 
schema parsing: White spaces are required between publicId and 
systemId.(embedded exception null) in system resource 
xml/ns/public/common/audit-3.xsd 
2017-04-06 15:38:32,457 [] [localhost-startStop-1] ERROR 
(org.springframework.web.context.ContextLoader): Context initialization 
failed 

The midpoint startup correctly created keystore 
/var/opt/midpoint/keystore.jceks , but did not create H2 database files 
:-( 

Please, help me! What am I doing wrong? 

Serviceconfig and logs are attached. 

Thank you in advance 

Radim Jaeger 

_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint

-- 
Ivan Noris
Senior Identity Engineer
evolveum.com
_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint

_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint

-- 
Ivan Noris
Senior Identity Engineer
evolveum.com
_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170411/0bc81026/attachment.htm>