Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
New Member
Posts: 19
Registered: ‎11-10-2015
Kudos: 9
Solutions: 2
Accepted Solution

AWS Unifi Controller Stopped - [exec] error, rc=100

So I've had my AWS controller on 5.2.9 since it was released.  Didn't have any problems upgrading, but now it appears that I've lost HTTP access to the controller.  Displays "site cannot be reached".  I can SSH in fine.  I've tried stopping/starting the service and have also tried a MongoDB repair, but that hasn't worked.

 

Server Log shows a ton of:

 

[2016-11-28 18:15:21,810] <db-server> ERROR system - [exec] error, rc=100
[2016-11-28 18:15:21,810] <db-server> INFO db - DbServer stopped
[2016-11-28 18:15:25,840] <db-server> ERROR system - [exec] error, rc=100
[2016-11-28 18:15:25,840] <db-server> INFO db - DbServer stopped
[2016-11-28 18:15:29,870] <db-server> ERROR system - [exec] error, rc=100
[2016-11-28 18:15:29,870] <db-server> INFO db - DbServer stopped
[2016-11-28 18:15:33,912] <db-server> ERROR system - [exec] error, rc=100
[2016-11-28 18:15:33,912] <db-server> INFO db - DbServer stopped
[2016-11-28 18:15:37,942] <db-server> ERROR system - [exec] error, rc=100
[2016-11-28 18:15:37,942] <db-server> INFO db - DbServer stopped

 

Everything I've searched for seems to point back to storage space issues.  I have it on an 8GB volume which shows 2.4GB available.  Is that not enough?  I also tried the prune function, but couldn't get it to work either.  Says:

 

Error: couldn't connect to server 127.0.0.1:27117 at src/mongo/shell/mongo.js:147

 

Tried to view mongo logs via "nano mongod.log", but it hangs for a few seconds thens shows a "Killed" message and doesn't display any data.

 

I have a backup from a few months back, but have done quite a bit of work since then and would rather not start over if possible.  Any help or guidance is greatly appreciated.  I'm a linux novice, but can follow instructions.

 

Thanks!


Accepted Solutions
New Member
Posts: 19
Registered: ‎11-10-2015
Kudos: 9
Solutions: 2

Re: AWS Unifi Controller Stopped - [exec] error, rc=100

It ended up coming down to storage space.  Not sure why it needs more than 3GBs to operate, but I increased the available storage and bam, started working.

 

I used this Youtube video as a guide.  Pretty straight forward and didn't need to do some of the steps at the end.

 

https://www.youtube.com/watch?v=LqgE1igqJG0

 

As soon as the snapshot restored to the larger drive, it instantly started working.  New backup saved.

 

Cheers.

View solution in original post


All Replies
New Member
Posts: 19
Registered: ‎11-10-2015
Kudos: 9
Solutions: 2

Re: AWS Unifi Controller Stopped - [exec] error, rc=100

Maybe I wasn't sure how to display the mongo log, but it's littered with:

 

Mon Nov 21 14:59:52.548 [initandlisten] ERROR: Insufficient free space for journal files
Mon Nov 21 14:59:56.579 [initandlisten] ERROR: Insufficient free space for journal files

 

But I have 2.4GB available.  Either way, can anyone guide me through a way to fix/extend the storage space on AWS to fix this problem?

New Member
Posts: 19
Registered: ‎11-10-2015
Kudos: 9
Solutions: 2

Re: AWS Unifi Controller Stopped - [exec] error, rc=100

It ended up coming down to storage space.  Not sure why it needs more than 3GBs to operate, but I increased the available storage and bam, started working.

 

I used this Youtube video as a guide.  Pretty straight forward and didn't need to do some of the steps at the end.

 

https://www.youtube.com/watch?v=LqgE1igqJG0

 

As soon as the snapshot restored to the larger drive, it instantly started working.  New backup saved.

 

Cheers.

New Member
Posts: 19
Registered: ‎12-22-2014

Re: AWS Unifi Controller Stopped - [exec] error, rc=14

[ Edited ]

 

I got a variation of the DB server err. in unifi.log

[2017-02-11 18:54:30,004] <launcher> INFO system - ======================================================================
[2017-02-11 18:54:30,005] <launcher> INFO system - UniFi 5.4.11 (build atag_5.4.11_9184 - release) is started
[2017-02-11 18:54:30,005] <launcher> INFO system - ======================================================================
[2017-02-11 18:54:30,015] <launcher> INFO system - BASE dir:/usr/lib/unifi
[2017-02-11 18:54:30,020] <launcher> INFO system - Current System IP: 172.31.46.139
[2017-02-11 18:54:30,028] <launcher> INFO system - Hostname: ip-172-31-46-139
[2017-02-11 18:54:30,030] <launcher> INFO system - Valid keystore is missing. Generating one ...
[2017-02-11 18:54:30,031] <launcher> INFO system - Generating Certificate[UniFi]... please wait...
[2017-02-11 18:54:31,676] <launcher> INFO system - Certificate[UniFi] generated!
[2017-02-11 18:54:31,747] <launcher> INFO db - waiting for db connection...
[2017-02-11 18:54:32,248] <launcher> INFO db - Connecting to mongodb://127.0.0.1:27117
[2017-02-11 18:54:32,968] <db-server> ERROR system - [exec] error, rc=14
[2017-02-11 18:54:32,968] <db-server> INFO db - DbServer stopped

 

as far as i can tell mongo is starting just fine

 

Sat Feb 11 19:46:02.124 [initandlisten] MongoDB starting : pid=8489 port=27017 dbpath=/var/lib/mongodb 64-bit host=ip-172-31-46-139
Sat Feb 11 19:46:02.125 [initandlisten] db version v2.4.9
Sat Feb 11 19:46:02.125 [initandlisten] git version: nogitversion
Sat Feb 11 19:46:02.125 [initandlisten] build info: Linux orlo 3.2.0-58-generic #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013 x86_64 BOOST_LIB_VERSION=1_54
Sat Feb 11 19:46:02.125 [initandlisten] allocator: tcmalloc
Sat Feb 11 19:46:02.125 [initandlisten] options: { bind_ip: "127.0.0.1", config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", journal: "true", logappend: "true", logpath: "/var/log/mongodb/mongodb.log" }
Sat Feb 11 19:46:02.126 [initandlisten] journal dir=/var/lib/mongodb/journal
Sat Feb 11 19:46:02.126 [initandlisten] recover : no journal files present, no recovery needed
Sat Feb 11 19:46:02.132 [initandlisten] waiting for connections on port 27017
Sat Feb 11 19:46:02.133 [websvr] admin web console waiting for connections on port 28017

 

plenty of spacce on the instance 

df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda1       30G  4.5G   24G  16% /

it looks to me that there is a missmatch of the ports, mongo is starting on 27017, and unifi is trying to connect on 27117!

 

Installer bug ?

Highlighted
New Member
Posts: 1
Registered: ‎05-16-2017

Re: AWS Unifi Controller Stopped - [exec] error, rc=14

I Just moved the folder from C:\Users\<YOUR USER>\Ubiquiti UniFi to C:\Program Files\ and now it worked
Reply