Let’s find a way to onboard @chagara to help out with the JIRA issue. I’d like to take the opportunity with @pascal to add someone to the team that is interested.
2 Likes
Darious, I’ll look into it then. Can someone provide a list of the plugins and I’ll make sure if they are available in cloud/server and we can go from there.
This is the list I see on the admin page:
- Announcer for JIRA
- Application Links Link Rendering Plugin
- Atlassian Hipchat Integration Plugin
- Atlassian Hipchat Integration Plugin Core
- Atlassian Universal Plugin Manager Plugin
- Atlassian Universal Plugin Manager Self-Update Plugin
- Balsamiq Mockups
- Bitbucket Importer Plugin for JIRA
- Gliffy JIRA Plugin
- HipChat Core Plugin
- HipChat for JIRA
- JIRA Agile
- JIRA Calendar Plugin
- JIRA Charting Plugin
- JIRA iCalendar Plugin
- JIRA Importers Plugin (JIM)
- JIRA Misc Workflow Extensions
- JIRA Toolkit Plugin
- JIRA Watcher Field
- JIRA Workflow Designer Plugin
- Links Hierarchy Reports
- Redmine Importers Plugin for JIRA
- ServiceRocket JIRA Utilities
- SuggestiMate for JIRA
- SuggestiMate for JIRA
- Support Tools Plugin
- Wallboard Plugin
- Zephyr for JIRA
JIRA Calendar Plugin and JIRA Watcher Field are disabled and one of the SuggestiMate for JIRA plugins is a free trial. I think Zephyr for JIRA is expired.
@michael already got us credits.
1 Like
It’s correct, 1Gb is the maximum heap JIRA can use.
VM Input Arguments -Djava.util.logging.config.file=/opt/jira/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -XX:MaxPermSize=256m -Xms512m -Xmx1024m -Djava.awt.headless=true -Datlassian.standalone=JIRA
By the way, what happened 4 hours ago? It seems like JIRA was restarted (uptime says 4 hours, 33 minutes, 47 seconds).
@janflowers, I am not giving somebody I know nothing about access to the production systems. No respect to you @chagara of course! It’s not personal here, just a matter of security. I will however take any suggestions.
Probably ran out of memory.
1 Like
Is there a way to check the logs? They are in /opt/jira/logs
If it was an out of memory it should be there.
Give me an ssh key in pm and you can 
– please keep the private key somewhat secure 
2 Likes
I realised we may also have to host the database, so we’re looking at more like $40/mo.
Off the top of my head: branding, single sign-on, existing content, and potentially cost.
In the Atlassian products I’ve managed, I’m a big fan of limiting add-ons to only the very few that are robust and well-supported (i.e., regularly released ahead of Atlassian releases) like Balsamiq, Gliffy, and Zephyr. Avoiding other add-ons and never touching SQL under the hood help ensure upgrading is smooth.
Here’s a list of add-ons running on JIRA. I’ve removed some I know are supplied by Atlassian out of the box; some of these may fall into that category as well:
- Announcer for JIRA
- Application Links Link Rendering Plugin
- Balsamiq Mockups
- Bitbucket Importer Plugin
- Gliffy JIRA Plugin
- JIRA Charting Plugin
- JIRA iCalendar Plugin
- JIRA Importers Plugin (JIM)
- JIRA Misc Workflow Extensions
- JIRA Toolkit Plugin
- JIRA Workflow Designer Plugin
- Links Hierarchy Reports
- Redmine Importers Plugin for JIM
- ServiceRocket JIRA Utilities
- SuggestiMate for JIRA
- SuggestiMate for JIRA
- Wallboard Plugin
- Zephyr for JIRA
Not too bad.
Per this page, a Micro won’t do. They recommend a M3 or C3. For our community and size, I’d assume we’d need something like a c3.xlarge. From the pricing page, it looks like in USD a c3.xlarge instance ranges from $688.67/year ($2066 paid up front for 3 yr term) up to $1844.64/year ($0.21/hour on demand on a leap year).
2 Likes
I’m not sure we need that much (although I’m sure it would be great). The c3.xlarge has 7.5GB of RAM and at the moment we’re somewhat managing with just 1GB.
That cost seems reasonable for a product serving the entire community. Does that include us being able to hand off some of the tasks we are currently doing on the infra team to support JIRA or would those still remain with the community?
When you do any on-boarding to infrastructure, please take copious notes. We can use those notes to develop some on-boarding documentation. To facilitate scaling up the support team, I think we need to move away from an all-or-none model – i.e., we should be able to bring someone to support a specific application or service. To help with this, I’ve created a hierarchy of folders in the shared Google Drive Infrastructure folder both to organize documentation and also allow us to share contents at an appropriate level.
It looks like Atlassian recommends nothing less than 3.75 GB (at least when directing people to AWS).
1 Like
We’d still maintain that server.
That is understandable and I’m not asking for the keys to the kingdom but, help in anyway I can. I don’t expect to be handed everything either. I’ll help in anyway I can suggestions, hints research does not matter.
2 Likes
I do appreciate your help – jus can’t hand anyone access to production systems. Already had one case where some people did something to one of our staging servers, so i’m not even more vigilant with who I grant access.
no problem. I’ll help the way I can by researching what Darious asked before. Then we can go from there.
2 Likes
Definitely an out of memory:
OutOfMemory due to Large Mailbox Processing https://confluence.atlassian.com/jirakb/outofmemory-due-to-large-mailbox-processing-216433923.html?utm_medium=logScan&utm_source=STP
OutOfMemory due to Mail Loop OutOfMemory due to Mail Loop | Jira | Atlassian Documentation? utm_medium=logScan&utm_source=STP
OutOfMemory Errors Due to Third-Party JIRA Plugins https://confluence.atlassian.com/jirakb/outofmemory-errors-due-to-third-party-jira-plugins-216433918.html?utm_medium=logScan&utm_source=STP
OutOfMemory due to Remote API https://confluence.atlassian.com/jirakb/outofmemory-due-to-remote-api-216433936.html?utm_medium=logScan&utm_source=STP
OutOfMemoryError caused by a large number of Issue Security Levels https://jira.atlassian.com/browse/JRA-19622?utm_source=STP&utm_medium=logScan
1 Like
yeah there are ways to fix those. Specially the mail box part. At my job last year we had those mail loop and it took everything down.