Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

installing JEC connector

Jose Carlo Escober
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 27, 2025

I am trying to do JSM with NagiosXi Integration

Resouces:
https://operations-help.atlassian.net/wiki/spaces/OPSHELP/pages/4259967/Integrate+with+Nagios+XI

Whenever I tried to install Jira Edge connector using Debian dpkg -i jsm-nagiosxi-<your_version>.deb

The JiraEdgeConnector bin executable file is not installed

I cloned from 
https://github.com/atlassian/jsm-integration-scripts/tree/master/nagios-xi

$/opt/jsm/jsm-integration-scripts/release/jec-builder# ls

jec-deb  jec-deb-extracted  jec-deb.deb  jec-rpm  jec-win32  jec-win64  temp-dir  version.json

$/opt/jsm/jsm-integration-scripts/release/jec-builder# dpkg -i jec-deb.deb

(Reading database ... 161265 files and directories currently installed.)

Preparing to unpack jec-deb.deb ...

Unpacking jsm-nagiosxi (2024R1.2.2) over (2024R1.2.2) ...

Setting up jsm-nagiosxi (2024R1.2.2) ...

chmod: cannot access '/usr/local/bin/JiraEdgeConnector': No such file or directory




----------------------------------------------------------------------------------
I also tried installing JEC following https://operations-help.atlassian.net/wiki/spaces/OPSHELP/pages/13893679/Install+Jira+Edge+Connector

I used this package

https://github.com/atlassian/jsm-integration-scripts/releases

I get the same result as before: /usr/local/bin/JiraEdgeConnector: No such file or directory

$/opt/jsm/JEC# ls

jsm-opsview_1.0.1_all.deb

$/opt/jsm/JEC# dpkg -i jsm-opsview_1.0.1_all.deb

(Reading database ... 161265 files and directories currently installed.)

Preparing to unpack jsm-opsview_1.0.1_all.deb ...

Unpacking jsm-opsview (1.0.1) over (1.0.1) ...

Setting up jsm-opsview (1.0.1) ...

WARNING : opsview user does not exist. Please don't forget to add your opsview user to JSM group!

$/opt/jsm/JEC# sudo systemctl status jec

× jec.service - Jira Edge Connector (JEC)

     Loaded: loaded (/etc/systemd/system/jec.service; enabled; vendor preset: enabled)

     Active: failed (Result: exit-code) since Thu 2025-06-26 19:09:11 UTC; 23h ago

   Main PID: 2204259 (code=exited, status=203/EXEC)

        CPU: 1ms

 

Jun 26 19:09:11  systemd[1]: Started Jira Edge Connector (JEC).

Jun 26 19:09:11  systemd[2204259]: jec.service: Failed to locate executable /usr/local/bin/JiraEdgeConnector: No such file or directory

Jun 26 19:09:11 systemd[2204259]: jec.service: Failed at step EXEC spawning /usr/local/bin/JiraEdgeConnector: No such file or directory

Jun 26 19:09:11  systemd[1]: jec.service: Main process exited, code=exited, status=203/EXEC

Jun 26 19:09:11 systemd[1]: jec.service: Failed with result 'exit-code'.



2 answers

0 votes
Vladislav Mayzlin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2025



0 votes
Kai Krause
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 28, 2025

Hi and welcome,

 

Why the file is missing

The.debpackages that come out of jsm-integration-scripts
(jsm-nagiosxi,jsm-opsview, etc.) contain only the Integration – the systemd unit, config templates, and post-install scripts.
I think they do not ship the proprietary Jira Edge Connector binary itself.

So you have frist install the jiraEdgeConnector and then the Integration.

Sonmething like:

curl -L -o /usr/local/b in/JiraEdgeConnector https://downloads.atlassian.com/software/jiraedgeconnector/2024R1.2.2/linux/x86_64/JiraEdgeConnector

Then set the correct permissions using:
chmod 755 /usr/local/b in/JiraEdgeConnector

After that, run:
sudo systemctl daemon-reload
sudo systemctl enable --now jec

Now you have the Jec and can install the intregration for nagios

BR
Kai

Jose Carlo Escober
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2025

the curl returned an html page with 403 error. I assume the link is incorrect

<html>

<head><title>403 Forbidden</title></head>

<body>

<h1>403 Forbidden</h1>

<ul>

<li>Code: AccessDenied</li>

<li>Message: Access Denied</li>

<li>RequestId: V92QRWS81MDGTMAX</li>

<li>HostId: wAWVY7Zs+k9D+HiaKhO5rU4WbBVAaNhzWHLckL+Z//jxKYkXtFPOWnVPHDtCApUtZpWm5c5gBlY=</li>

</ul>

<hr/>

</body>

</html>

where else can I download the Jira Edge Connector?

Vladislav Mayzlin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2025

hey kai,

im from the same team as carlo. I got the JEC connector installed and properly configured i believe. I added the jec api key to jec.config.json

When i start the jec service. it seems like it turns on, all the worker nodes spawn but it timesout. i see these errors.

Jul 02 16:51:58  jec[3240218]:INFO[2025-07-02T16:51:58.521144838Z] JEC-metrics serves in http://localhost:7070/metrics.

Jul 02 16:51:58  jec[3240218]: ERROR[2025-07-02T16:51:58.52187608Z] JEC-metrics error: listen tcp :7070: bind: address already in use

jec.service: start operation timed out. Terminating.
Jul 02 16:56:58  systemd[1]: jec.service: Failed with result 'timeout'.


where is the jec-metrics server config located? i think i need to change the port on it. also any insight into this timeout?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events