[FOLIO-567] folio demo site down Created: 21/Apr/17  Updated: 12/Nov/18  Resolved: 25/Apr/17

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P1
Reporter: Wolfram Schneider Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 3 hours, 30 minutes
Original estimate: Not Specified

Sprint:

 Description   

Hi guys, it seems that our demo site http://folio-uidemo.aws.indexdata.com/ is down

ping folio-uidemo.aws.indexdata.com
PING ec2-54-164-117-118.compute-1.amazonaws.com (54.164.117.118): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1



 Comments   
Comment by John Malconian [ 21/Apr/17 ]

Updated the back end configuration and rebuilt Jenkins FOLIO_UI_Demo_1. Site back up.

Comment by Wolfram Schneider [ 25/Apr/17 ]

Our demo site is down again. I see that the jenkins job FOLIO_UI_Demo_2 failed at 1:30 UTC this morning, https://jenkins-aws.indexdata.com/job/FOLIO_UI_Demo_2/lastBuild/console

Comment by Wolfram Schneider [ 25/Apr/17 ]

I restarted both jenkins jobs FOLIO_UI_Demo_1/FOLIO_UI_Demo_2 - both are failing.

Comment by Wolfram Schneider [ 25/Apr/17 ]

Is there an option to roll back a failed build? I wish I could build a working folio-uidemo this morning myself (Niels had a presentation in Helsinki).

Comment by Mike Taylor [ 25/Apr/17 ]

Do we understand why the site is down?

I thought that, now it's based on released artifacts rather than build-tips, this wasn't supposed to happen.

Comment by John Malconian [ 25/Apr/17 ]

Last night's demo site build failed. Looks like the problem was a race condition during the module registration phase where module registration would start before Okapi itself was fully started. So, in this case, this was a deployment issue. Issue has been resolved.

In general, if you see that either FOLIO_UI_Demo_1 or FOLIO_UI_Demo_2 has failed. Do NOT run the other job. Please don't run either job manually unless the demo is not up at all (as was the case in this instance).

Generated at Thu Feb 08 23:06:44 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.