It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Any pointers appreciated. I am using a php script that works fine when both JIRA and nagios share host.
But when i switch to another host and direct the nagios alert to my jira-- i have problerms , see below.
thx,james
tomcat access_log on zsms-t01 (jira host)
When we run script from same machine jira is running on - no problems
158.85.84.247 713x1432x1 jamest [03/Dec/2015:11:53:40 -0600] "POST /login.jsp?os_username=jamest&os_password=1234&os_cookie=true HTTP/1.1" 200 35037 279 "-" "-" "1qea4mt"
158.85.84.247 713x1433x1 jamest [03/Dec/2015:11:53:40 -0600] "POST /secure/CreateIssue.jspa?pid=10201&issuetype=10003 HTTP/1.1" 200 42166 88 "-" "-" "1qea4mt"
158.85.84.247 713x1434x1 jamest [03/Dec/2015:11:53:40 -0600] "POST /secure/CreateIssueDetails.jspa?atl_token=BQYK-4I1M-ORR5-VI0C|b36b990538bf6e73cdf743f303cb1d5ea4468951|lin&pid=10201&issuetype=10003&summary=NAGIOS%3A+TUNNEL+on+zsms+is+CRITICAL&description=%7Bcolor%3A%233b0b0b%7D%2ANagios+Problem+Alert%2A%7Bcolor%7D%0A%0AThe+following+information+was+provided+by+Nagios%3A%0A%2A+Date+%26+Time%3A+12-03-2015+11%3A53%3A40%0A%2A+Status+Information%3A+CRITICAL%3A+zsms-t01.mizaas.com+Tunnel+DOWN%0A%2A+Current+Host+State%3A+UP%0A%2A+Current+Service+State%3A+CRITICAL%0A%2A+Host+Address%3A+127.0.0.1%2C158.85.84.247%0A&priority=2&assignee=jamest HTTP/1.1" 302 - 119 "-" "-" "1qea4mt"
158.85.84.247 713x1435x1 jamest [03/Dec/2015:11:53:40 -0600] "GET /browse/NTJ-133 HTTP/1.1" 200 71293 144 "-" "-" "1qea4mt"
BUT when we run script from a different machine ( zsmsyow) than jira is running on - The login fails.
tomcat access_log on zsms-t01 (jira host)
206.191.38.52 - - [03/Dec/2015:12:02:08 -0600] "POST /login.jsp?os_username=jamest&os_password=12345&os_cookie=true HTTP/1.1" 500 - 0 "-" "-" "-"
206.191.38.52 - - [03/Dec/2015:12:02:08 -0600] "POST /secure/CreateIssue.jspa?pid=10201&issuetype=10003 HTTP/1.1" 500 - 0 "-" "-" "-"
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.