Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue related to installing OEC on Local Servers


Hi Guys,

I was trying to install OEC on my local servers (CentOS 6.10).  I ran the following command (suggested by Installation page):

sudo rpm -i opsgenie-oec-1.1.1.rhel6.x86_64.rpm

and got the below error:

Starting Opsgenie Edge Connector (OEC)INFO[2021-02-10T13:54:24.650075803-05:00] OEC version is 1.1.2
INFO[2021-02-10T13:54:24.650302874-05:00] OEC commit version is ce55d5202eb29611616e32a6921c89e464d2de76
INFO[2021-02-10T13:54:24.650658946-05:00] Visibility timeout cannot be lesser than 15 seconds or greater than 12 hours, default value[30 s.] is set.
INFO[2021-02-10T13:54:24.650797902-05:00] OEC-metrics serves in http://localhost:7070/metrics .
ERROR[2021-02-10T13:54:24.651091827-05:00] OEC-metrics error: listen tcp :7070: bind: address already in use
INFO[2021-02-10T13:54:24.651341524-05:00] Queue processor is starting.
ERROR[2021-02-10T13:54:24.851069741-05:00] Queue processor could not get initial token and will terminate.
FATAL[2021-02-10T13:54:24.851132448-05:00] Token could not be received from Opsgenie, status: 422 Unprocessable Entity, message: {"message":"Key format is not valid!","took":0.0,"requestId":"41dfdd23-c220-4e59-b82e-c18395d91c91"}
warning: %post(opsgenie-oec-rhel6-1.1.1-1.x86_64) scriptlet failed, exit status 1

 The Port 7070 is used by internal applications and that cannot be changed.

Please suggest what could be the solution.

Thanks in advance

4 answers

1 accepted

0 votes
Answer accepted

The Answer to the above query is to edit the OEC Service file:

ExecStart=/usr/local/bin/OpsgenieEdgeConnector --metric-port 7071 (Any port which you want to use)

Any updates here? In my case port 7070 is not in use. Do I need to open it in the EC2 security groups?

Darryl Lee
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 03, 2021

Hi Ben,

This is Darryl, Opsgenie Support, I am here to help. :)

If your port 7070 is not in use, the OEC service should be running without any problem.

The other thing required is your OEC can reach out to AWS SQS to poll the tasks, the domain name is varied depends on your Opsgenie hosted region.

Also ensure you have followed the instructions on these two docs to configure your config.json and run it.

Hope this helps.

Kind regards,
Darryl Lee
Opsgenie Support

I do have the same problem, waiting for atlassian for a solution here.


if you do

netstat -tulpn | grep -i "7070"


It will show you a process of Edge Connector already running but the process of starting it up, cranks down.

I'd be glad to hear an answer for this cause you can't alter the port that app is running on linux as i know.


################## EDIT ###################

I found that Processes from /usr/local/bin/OpsgenieEdgeConnector were already running and keeping the port up (if you kill 7070 is not enough to restart oec)


You have to kill previous failed processes to be able to start it again


If you do


watch -n 1 journalctl -xe


You will see that EVEN if OEC process is killed, worker is alive and working, i think this is a bug.


If port 7070 is already used, you can alter the port the OEC will use in the oecService.json.  At least, that is where that setting is in the Windows install.  I am not sure for the Linux one.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events