Difference between revisions of "Atlassian"
From Briki
(→Atlassian process fails to start on boot) |
|||
| Line 6: | Line 6: | ||
** export SHELL=/bin/sh | ** export SHELL=/bin/sh | ||
** Use "su -m user -c cmd" (rather than "su -l user -c cmd") to run the command as the chosen user | ** Use "su -m user -c cmd" (rather than "su -l user -c cmd") to run the command as the chosen user | ||
| + | |||
| + | Alternatively, it may be possible simply to change "su -l" / "su -m" to "sudo -u" | ||
=== Stash crashes immediately on startup === | === Stash crashes immediately on startup === | ||
Revision as of 20:22, 24 November 2016
Contents
Repeated requests to re-authenticate administrator password on JIRA
- https://confluence.atlassian.com/display/JIRAKB/User+is+Constantly+Logged+out+of+JIRA (see sessionCookieName option)
Atlassian process fails to start on boot
- On boot, ubuntu starts processes using "service xxx start" (rather than "/etc/init.d/service start"). This difference means there is no SHELL defined, and users with their shell set to /bin/false cannot run processes using "su". In that case, change the start-xxx.sh and stop-xxx.sh scripts in the application bin directory to:
- export SHELL=/bin/sh
- Use "su -m user -c cmd" (rather than "su -l user -c cmd") to run the command as the chosen user
Alternatively, it may be possible simply to change "su -l" / "su -m" to "sudo -u"
Stash crashes immediately on startup
- If shell for stash user (eg. atlstash) is set to /bin/false, ensure sudo (not "su") is used to switch user in start-stash.sh and stop-stash.sh
