1. created vpc service
2. created efs service
3. created postgres service
4. created the jira-tmp.tungsten.io.tungsten.io subdomain (mistake made, should have been jira-tmp.tungsten.io)
5. create the jira instance
6. reverted the table update back to jira
Vanessa Valderrama
added a comment - 1. created vpc service
2. created efs service
3. created postgres service
4. created the jira-tmp.tungsten.io.tungsten.io subdomain (mistake made, should have been jira-tmp.tungsten.io)
5. create the jira instance
6. reverted the table update back to jira
The instance is created: e428b8f2-687d-4cf4-b190-e0c52bb7e8ff
Getting a 502 when I go to https://jira-tmp.tungsten.io/
Vanessa Valderrama
added a comment - The instance is created: e428b8f2-687d-4cf4-b190-e0c52bb7e8ff
Getting a 502 when I go to https://jira-tmp.tungsten.io/
Invalid Xlog option '-Xlog:gc*:file=/opt/atlassian/jira/logs/atlassian-jira-gc%t.log:tags,time,uptime,level:filecount=5,filesize=20M', see error log for details.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Vanessa Valderrama
added a comment - Invalid Xlog option '-Xlog:gc*:file=/opt/atlassian/jira/logs/atlassian-jira-gc %t.log:tags,time,uptime,level:filecount=5,filesize=20M', see error log for details.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
pending documentation