Bug 1113094

Created attachment 912081 [details]
Engine setup log

Looks like a missing dependency in EL6 at spec file level.

(In reply to Sandro Bonazzola from comment #2)
> Looks like a missing dependency in EL6 at spec file level.

I've to correct myself, js-ant is provided by jasper. Maybe 5.5.0a dropped it?

 jasperreports-server-5.5.0a-1.el6.noarch : JasperReports Server
 Matched from:
 Filename    : /usr/share/jasperreports-server/buildomatic/js-ant

 jasperreports-server-5.5.0-7.el6.noarch : JasperReports Server
 Matched from:
 Filename    : /usr/share/jasperreports-server/buildomatic/js-ant

Looks like nothing changed about js-ant in jasper.

Petr, which version of jasper are you using?
Can you check rpm -ql jasperreports-server |grep js-ant ?

[root@change-fqdn ~]# rpm -qa | grep jasper
jasperreports-server-5.5.0-7.el6.noarch
jasper-libs-1.900.1-15.el6_1.1.x86_64

[root@change-fqdn ~]# rpm -ql jasperreports-server | grep js-ant
/usr/share/jasperreports-server/buildomatic/js-ant
/usr/share/jasperreports-server/buildomatic/js-ant.bat

Error might have occurred due to unresolvable hostname, and in any case was a failure of jasper (js-ant in particular). Relevant lines from the attached log:


     [java] org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'executionOwnerVoter': Injection of resource dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securityContextProvider': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securityContextProviderTarget' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Cannot resolve reference to bean 'userAuthorityService' while setting bean property 'userDetailsService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userAuthorityService' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Cannot resolve reference to bean 'profileAttributeService' while setting bean property 'profileAttributeService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'profileAttributeService': FactoryBean threw exception on object creation; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'profileAttributeServiceTarget' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Cannot resolve reference to bean 'unsecureRepositoryService' while setting bean property 'repositoryService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepositoryService' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Cannot resolve reference to bean 'hibernateRepositoryListeners' while setting bean property 'repositoryListeners'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hibernateRepositoryListeners' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext.xml]: Cannot resolve reference to bean 'schedulingReportDeleteListener' while setting constructor argument with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'schedulingReportDeleteListener' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportSchedulingService' while setting bean property 'schedulingService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportSchedulingService' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'reportScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'reportScheduler' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'quartzScheduler' while setting bean property 'scheduler'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'quartzScheduler' defined in file [/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-report-scheduling.xml]: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Cannot run without an instance id.


     [java]     at org.quartz.simpl.SimpleInstanceIdGenerator.generateInstanceId(SimpleInstanceIdGenerator.java:34)

     [java] Caused by: java.net.UnknownHostException: change-fqdn.rhev.lab.eng.brq.redhat.com: Name or service not known


Please try to reproduce after we'll fix other problems in setup. Currently setting needinfo on myself until we do that.

Is the hostname resolvable?


Yaniv

Yes it is resolvable.

(In reply to Petr Matyáš from comment #8)
> Yes it is resolvable.

This doesn't make sense, the hostname that is pulled from that machine is:
change-fqdn.rhev.lab.eng.brq.redhat.com
which is not resolvable (I can't ping and it is clearly a placeholder name). This is the root cause. Please make sure that your hostname is correct and resolable and try to recreate and close this bug if you can't which is most likely the case.

Yes it was back then, but I changed it to pm-rh35.rhev.lab.eng.brq.redhat.com (this one is resolvable) and I can't remember if I tried Alpha2 release afterwards, but Beta doesn't work now, that I tried. I can downgrade to Alpha2 and test it again.

(In reply to Petr Matyáš from comment #10)
> Yes it was back then, but I changed it to
> pm-rh35.rhev.lab.eng.brq.redhat.com (this one is resolvable) and I can't
> remember if I tried Alpha2 release afterwards, but Beta doesn't work now,
> that I tried. I can downgrade to Alpha2 and test it again.

Please provide log for the real failure, since this one does not list the cause as I understand.

I just finished downgrading to alpha2 release and it installs correctly, so it must have been because of the hostname I didn't change. The bug might be renamed to "No warning after js-ant fails to install" or something like that.

(In reply to Petr Matyáš from comment #12)
> I just finished downgrading to alpha2 release and it installs correctly, so
> it must have been because of the hostname I didn't change. The bug might be
> renamed to "No warning after js-ant fails to install" or something like that.

warning about?


Yaniv

To set the hostname if it isn't set and resolvable, but I guess most of the people have that set correctly, so you can probably close this bug.

*** This bug has been marked as a duplicate of bug 1226910 ***