aalqinneh Posted February 21, 2019 Share Posted February 21, 2019 Followed the instructions to deploy the JasperReports IO product on AWS via the template after the successful completion I am unable to access the instance on port 8080. I did successfully SSH into the instance and also pinged 8.8.8.8. My security groups are all configured correctly allowing 0.0.0.0/0 (SSH, TCP, HTTP/S). My theory is that the jenkins portion of the code in the AMI is failing and it's not deploying the webservice. Can someone please help look into the template for me asap - I'm looking at utilizing JRIO for a big project.Thanks! Link to comment Share on other sites More sharing options...
aalqinneh Posted February 22, 2019 Author Share Posted February 22, 2019 confirmed that there is an issue with the template. the bucket being created is empty, no report templates/sample data or anything else in it. Might be someting to do with the AMI referenced in the template... can't really use this product now. I know that there is no support for this product but it would be fantastic just to get a response acknowledging that an issue does exist.Thanks Link to comment Share on other sites More sharing options...
nkeleber Posted February 22, 2019 Share Posted February 22, 2019 @aalqinneh,We are aware of the issue and are working to resolve it and push the changes to AWS. It's due to a very recent java update on AWS. In the meanwhile, try restarting jrio service. It should bring it back up.- Natalia Link to comment Share on other sites More sharing options...
aalqinneh Posted February 22, 2019 Author Share Posted February 22, 2019 @nkeleber thank you very much for your response! Do you mean restart the EC2 instance? Additionally, is there any individual I can speak with directly? We're positioning this solution for a client and would love a discussion with the product team. Link to comment Share on other sites More sharing options...
nkeleber Posted February 22, 2019 Share Posted February 22, 2019 @aalqinneh. Yes, restarting ec2 instance would help. I have sent an email with contact information.Have a great day!- Natalia Link to comment Share on other sites More sharing options...
aalqinneh Posted February 22, 2019 Author Share Posted February 22, 2019 Thank you for the feedback @nkeleber it seems like the issue is resolved. Appreciate your prompt response. Link to comment Share on other sites More sharing options...
aalqinneh Posted February 22, 2019 Author Share Posted February 22, 2019 Known issue which is resolved by restarting the jrio instance. (Jasper is looking into deploying a new template) Link to comment Share on other sites More sharing options...
nkeleber Posted February 23, 2019 Share Posted February 23, 2019 No problem at all. Glad to hear that issue is resolved. cheers,Natalia Link to comment Share on other sites More sharing options...
ysavochenko Posted February 25, 2019 Share Posted February 25, 2019 One small correction here - restarting JRIO ec2 is not required, it will also work if you restart JRIO service:sudo service jrio stopsudo service jrio start Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now