Controller 3.1.4 on Debian 9 Failing to start

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Controller 3.1.4 on Debian 9 Failing to start

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Controller 3.1.4 on Debian 9 Failing to start
Controller 3.1.4 on Debian 9 Failing to start
2019-05-16 18:40:27

Just did a clean install of Debian 9.8, downloaded the 3.1.4 version in zip form, ensured all pre requisites, then installed. Controller is failing to start.

 

How can I debug the issue?

 

All I see in systemctl status is:

 

May 16 14:11:29 eapcontroller systemd[1]: Starting LSB: Omada Controller...

May 16 14:16:29 eapcontroller systemd[1]: tpeap.service: Start operation timed out. Terminating.

May 16 14:16:29 eapcontroller systemd[1]: Failed to start LSB: Omada Controller.

May 16 14:16:29 eapcontroller systemd[1]: tpeap.service: Unit entered failed state.

May 16 14:16:29 eapcontroller systemd[1]: tpeap.service: Failed with result 'timeout'.

  0      
  0      
#1
Options
3 Reply
Re:Re:Controller 3.1.4 on Debian 9 Failing to start
2019-05-17 14:00:22

You are spot on with the mongodb issue.

 

2019-05-17 09:57:11 [main] [WARN]-[SourceFile:124] - Fail to start mongo DB server

2019-05-17 09:57:11 [main] [WARN]-[SourceFile:78] - com.tp_link.eap.start.a.a: Fail to start mongo DB server

com.tp_link.eap.start.a.a: Fail to start mongo DB server

at com.tp_link.eap.start.c.c.a(SourceFile:125) ~[eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.c.a.e(SourceFile:75) [eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.a.g(SourceFile:310) [eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.a.z(SourceFile:389) [eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.a.a(SourceFile:86) [eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.a.h(SourceFile:336) [eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.EapLinuxMain.b(SourceFile:79) [eap-start-3.1.4.jar:?]

at com.tp_link.eap.start.EapLinuxMain.start(SourceFile:36) [eap-start-3.1.4.jar:?]

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_162]

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_162]

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_162]

at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_162]

at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) [commons-daemon-1.0.15.jar:1.0.15]

2019-05-17 09:57:14 [main] [INFO]-[SourceFile:168] - mongod is not running

 

 

I have tried it with installing mongodb from apt-get and without it installed. Same error message.

 

When installed via apt-geet, doing a "systemctl status mongodb" it shows as running.

 

Thoughts?

  0  
  0  
#4
Options
Re:Re:Controller 3.1.4 on Debian 9 Failing to start
2019-05-17 14:49:44

Think I might have the issue figured out. The /opt directory is under / in the my LVM and I am seeing this in the mongod.log:

 

Fri May 17 10:46:07 [initandlisten] ERROR: Insufficient free space for journal files

Fri May 17 10:46:07 [initandlisten] Please make at least 3379MB available in /opt/tplink/EAPController/data/db/journal or use --smallfiles

 

 

Looking at root space:

 

/dev/mapper/eapcontroller--vg-root  3.1G  1.7G  1.3G  58% /

 

 

Think I need to expand root a little...

 

Thanks for the replies, BTW..

  0  
  0  
#6
Options
Re:Re:Controller 3.1.4 on Debian 9 Failing to start
2019-05-17 15:39:03

Thanks for your time.... 

 

I am all up and running after fixing the space issue that mongodb was complaining about.

  0  
  0  
#7
Options