Ist für HW-Version 3 oder? Ich habe hier davon 6x V2

toms01 wrote

Hi!

For my configuration this is not a solution:

#ifconfig
enp3s0 Link encap:Ethernet Hardware Adresse xxx
inet Adresse:1.2.3.5 Bcast:1.2.3.7 Maske:255.255.255.252
inet6-Adresse: fe80::c23f:d5ff:fe6b:6a19/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1
RX-Pakete:835 Fehler:0 Verloren:178 Überläufe:0 Fenster:0
TX-Pakete:579 Fehler:0 Verloren:0 Überläufe:0 Träger:0
Kollisionen:0 Sendewarteschlangenlänge:1000
RX-Bytes:138117 (138.1 KB) TX-Bytes:128621 (128.6 KB)

enp3s0:0 Link encap:Ethernet Hardware Adresse xxx
inet Adresse:192.168.1.4 Bcast:192.168.1.255 Maske:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1

lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:65536 Metrik:1
RX-Pakete:626 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
TX-Pakete:626 Fehler:0 Verloren:0 Überläufe:0 Träger:0
Kollisionen:0 Sendewarteschlangenlänge:1
RX-Bytes:43694 (43.6 KB) TX-Bytes:43694 (43.6 KB)

-> Starting EAP Controller ........./usr/bin/tpeap: Zeile 79: 2076 Killed nohup $JAVA_TOOL -server -Xms128m -Xmx1024m -XX:MaxHeapFreeRatio=60 -XX:MinHeapFreeRatio=30 -XX:+UseSerialGC -XX:+HeapDumpOnOutOfMemoryError -Deap.home="${eapHome}" -cp ${eapHome}"/lib/com.tp-link.eap.start-0.0.1-SNAPSHOT.jar:"${eapHome}"/lib/*:"${eapHome}"/external-lib/*" com.tp_link.eap.start.EapMain start > ${eapHome}/logs/startup.log 2>&1

Did you try shutting down the interface(s) while starting up the EAPC service?

Regards
Peter


Edit1:
Shutting down the physical interface worked as expected on an Ubuntu 16.04 LTS VM.
Reconfiguring on the fly with ifconfig gave mixed results.
Forget the workaround with the alias interface - it's not for production use anyway.

I received an e-mail from the german support team asking for details on August 21st, which I replied to with details.
Let's wait for the fix ...

Regards
Peter


Edit1:
German support was unable to reproduce the problem on their side and told me that it must be something inside our network.

Well, it was indeed something in our network - the EAPC running on a Windows Server ...

To sum this up for future victims of this incredible software product:
If you already have an EAP Controller running on a Windows system, to manage your APs you have to shut that EAP Controller down before firing up your brand new EAP Controller on Linux.

[SIZE=2]The reason why changing the IP adress on the Linux EAPC did allow it to start it up was, that communication between both EAPCs was interrupted this way.
So changing it to a public IP did work, just because that IP was not part of the local subnet.
Funny thing is, that both EAPCs will stay running if you disrupt network connectivity on startup of the second - it looks like there are no further checks implemented.

Why this fabulous piece of software does not just log "There is already an EAP Controller running on your network - shutting down!"[SIZE=4] [SIZE=2]... well, I don't know why the person writing this mess thought it would be a good idea to omit useful error logging.

Long story short: this is another case of good hardware made useless by bad software[/SIZE][/SIZE].
We will definitely not deploy Auranet hardware to any of our customer's networks.
[/SIZE][SIZE=1][/SIZE]

Hi, I found another issue with EAP Control Software.

Init script says it's running but http site drop 503 error, same on port 8043. In server.log there are a lot of exceptions and netstat doesn't see http server


2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : eap.properties
2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : mongodb.properties
2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : jetty.properties
2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : netty.properties
2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : log4j.properties
2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : user.params.properties
2017-09-19 19:46:14 [main] [INFO]-[ConfigurationFactory.java:39] - success to load configuration : device.properties
2017-09-19 19:46:24 [main] [INFO]-[ContextHandler.java:2040] - Initializing Spring root WebApplicationContext
2017-09-19 19:46:26 [pool-5-thread-1] [INFO]-[DeviceContext.java:76] - Eap Controller isn't prepared to handle event


2017-09-19 19:46:48 [main] [ERROR]-[ContextLoader.java:331] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduleController': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.ScheduleServiceI com.tp_link.eap.web.schedule.ScheduleController.scheduleService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduleService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.impl.TaskManager com.tp_link.eap.monitor.task.service.impl.ScheduleService.taskManager; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.service.ApServiceI com.tp_link.eap.monitor.task.service.impl.TaskManager.apService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException:


Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.ScheduleServiceI com.tp_link.eap.web.schedule.ScheduleController.scheduleService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduleService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.impl.TaskManager com.tp_link.eap.monitor.task.service.impl.ScheduleService.taskManager; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.service.ApServiceI com.tp_link.eap.monitor.task.service.impl.TaskManager.apService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apRepository': Invocation of init method failed; nested exception is com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:508)



Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.service.ApServiceI com.tp_link.eap.monitor.task.service.impl.TaskManager.apService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apRepository': Invocation of init method failed; nested exception is com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:292)


Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apRepository': Invocation of init method failed; nested exception is com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:292)


Caused by: com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms
at com.mongodb.BaseCluster.getServer(BaseCluster.java:87)
at com.mongodb.DBTCPConnector.getServer(DBTCPConnector.java:654)
at com.mongodb.DBTCPConnector.access$300(DBTCPConnector.java:39)
at com.mongodb.DBTCPConnector$MyPort.getConnection(DBTCPConnector.java:503)
at com.mongodb.DBTCPConnector$MyPort.get(DBTCPConnector.java:451)
at com.mongodb.DBTCPConnector.getPrimaryPort(DBTCPConnector.java:409)
at com.mongodb.DBCollectionImpl.createIndex(DBCollectionImpl.java:337)
at com.mongodb.DBCollection.createIndex(DBCollection.java:564)


2017-09-19 19:46:48 [main] [ERROR]-[ContextLoader.java:331] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduleController': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.ScheduleServiceI com.tp_link.eap.web.schedule.ScheduleController.scheduleService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduleService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.impl.TaskManager com.tp_link.eap.monitor.task.service.impl.ScheduleService.taskManager; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.service.ApServiceI com.tp_link.eap.monitor.task.service.impl.TaskManager.apService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apRepository': Invocation of init method failed; nested exception is com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms


Caused by: org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.ScheduleServiceI com.tp_link.eap.web.schedule.ScheduleController.scheduleService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduleService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.task.service.impl.TaskManager com.tp_link.eap.monitor.task.service.impl.ScheduleService.taskManager; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.service.ApServiceI com.tp_link.eap.monitor.task.service.impl.TaskManager.apService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apRepository': Invocation of init method failed; nested exception is com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:508)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'taskManager': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.service.ApServiceI com.tp_link.eap.monitor.task.service.impl.TaskManager.apService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private com.tp_link.eap.monitor.monitor.repo.ApRepository com.tp_link.eap.monitor.monitor.service.impl.ApService.apRepo; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'apRepository': Invocation of init method failed; nested exception is com.mongodb.MongoTimeoutException: Timed out while waiting for a server that matches AnyServerSelector{} after 4510 ms
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:292)

2017-09-19 19:46:51 [pool-5-thread-1] [INFO]-[DeviceContext.java:76] - Eap Controller isn't prepared to handle event


root@dashboard02:/opt/tplink/EAPController/bin#

Hi, It is ubuntu 16.04 , but one important info! when I install it on pure system it works, but when i restart the host , eap software is not able to start manually/automatically. Re-install also did not help

yup R1D2

this is our fault, we find solution on problem on manual, but not read completely from start to end ;-(