Reply
Regular Member
nelson6069
Posts: 442
Registered: ‎10-15-2012
Posts: 442
Kudos: 12
Registered: 10-15-2012

Unifi AP LR cannot connect, but can ping it.

UNIFI AP LR -1 (172.16.2.25) <- The one which cannot be connected.
UNIFI AP LR -2 (172.16.2.24)
Unifi AP LR cannot connect, i connect to AP 2 and ping to 172.16.2.25(AP 1).
What is the problem?

Here is my log file from my controller:

***** SERVER RESTARTED *****


Mon Jun 03 02:32:03 [initandlisten] MongoDB starting : pid=1364 port=27117 dbpath=C:\Users\Win 7\Ubiquiti UniFi\data\db 64-bit host=Win7-PC
Mon Jun 03 02:32:03 [initandlisten] db version v2.0.1, pdfile version 4.5
Mon Jun 03 02:32:03 [initandlisten] git version: 3a5cf0e2134a830d38d2d1aae7e88cac31bdd684
Mon Jun 03 02:32:03 [initandlisten] build info: windows (6, 1, 7601, 2, 'Service Pack 1') BOOST_LIB_VERSION=1_42
Mon Jun 03 02:32:03 [initandlisten] options: { bind_ip: "127.0.0.1", dbpath: "C:\Users\Win 7\Ubiquiti UniFi\data\db", logappend: true, logpath: "logs/mongod.log", nohttpinterface: true, port: 27117 }
Mon Jun 03 02:32:03 [initandlisten] journal dir=C:/Users/Win 7/Ubiquiti UniFi/data/db/journal
Mon Jun 03 02:32:03 [initandlisten] recover : no journal files present, no recovery needed
Mon Jun 03 02:32:03 [initandlisten] waiting for connections on port 27117
Mon Jun 03 02:32:03 [initandlisten] connection accepted from 127.0.0.1:57997 #1
Mon Jun 03 02:32:22 [initandlisten] connection accepted from 127.0.0.1:58106 #2
Mon Jun 03 02:32:22 [initandlisten] connection accepted from 127.0.0.1:58107 #3
Mon Jun 03 02:32:22 [initandlisten] connection accepted from 127.0.0.1:58108 #4
Mon Jun 03 02:32:22 [initandlisten] connection accepted from 127.0.0.1:58110 #5
Mon Jun 03 02:33:03 [clientcursormon] mem (MB) res:46 virt:277 mapped:80
Mon Jun 03 02:33:21 [initandlisten] connection accepted from 127.0.0.1:58136 #6
Mon Jun 03 02:38:03 [clientcursormon] mem (MB) res:50 virt:279 mapped:80
Mon Jun 03 02:43:03 [clientcursormon] mem (MB) res:51 virt:279 mapped:80
Mon Jun 03 02:48:03 [clientcursormon] mem (MB) res:51 virt:279 mapped:80
Mon Jun 03 02:53:03 [clientcursormon] mem (MB) res:52 virt:279 mapped:80
Mon Jun 03 02:58:03 [clientcursormon] mem (MB) res:52 virt:279 mapped:80
Mon Jun 03 02:59:43 [initandlisten] connection accepted from 127.0.0.1:58465 #7
Mon Jun 03 02:59:43 [conn7] terminating, shutdown command received
Mon Jun 03 02:59:43 dbexit: shutdown called
Mon Jun 03 02:59:43 [conn7] shutdown: going to close listening sockets...
Mon Jun 03 02:59:43 [conn7] closing listening socket: 392
Mon Jun 03 02:59:43 [conn7] shutdown: going to flush diaglog...
Mon Jun 03 02:59:43 [conn7] shutdown: going to close sockets...
Mon Jun 03 02:59:43 [conn7] shutdown: waiting for fs preallocator...
Mon Jun 03 02:59:43 [conn7] shutdown: lock for final commit...
Mon Jun 03 02:59:43 [conn7] shutdown: final commit...
Mon Jun 03 02:59:43 [conn7] shutdown: closing all files...
Mon Jun 03 02:59:43 [conn7] closeAllFiles() finished
Mon Jun 03 02:59:43 [conn7] journalCleanup...
Mon Jun 03 02:59:43 [conn7] removeJournalFiles
Mon Jun 03 02:59:43 [conn7] shutdown: removing fs lock...
Mon Jun 03 02:59:43 dbexit: really exiting now


***** SERVER RESTARTED *****


Tue Jun 04 02:11:27 [initandlisten] MongoDB starting : pid=3564 port=27117 dbpath=C:\Users\Win 7\Ubiquiti UniFi\data\db 64-bit host=Win7-PC
Tue Jun 04 02:11:27 [initandlisten] db version v2.0.1, pdfile version 4.5
Tue Jun 04 02:11:27 [initandlisten] git version: 3a5cf0e2134a830d38d2d1aae7e88cac31bdd684
Tue Jun 04 02:11:27 [initandlisten] build info: windows (6, 1, 7601, 2, 'Service Pack 1') BOOST_LIB_VERSION=1_42
Tue Jun 04 02:11:27 [initandlisten] options: { bind_ip: "127.0.0.1", dbpath: "C:\Users\Win 7\Ubiquiti UniFi\data\db", logappend: true, logpath: "logs/mongod.log", nohttpinterface: true, port: 27117 }
Tue Jun 04 02:11:27 [initandlisten] journal dir=C:/Users/Win 7/Ubiquiti UniFi/data/db/journal
Tue Jun 04 02:11:27 [initandlisten] recover : no journal files present, no recovery needed
Tue Jun 04 02:11:27 [initandlisten] waiting for connections on port 27117
Tue Jun 04 02:11:27 [initandlisten] connection accepted from 127.0.0.1:53011 #1
Tue Jun 04 02:11:56 [initandlisten] connection accepted from 127.0.0.1:53108 #2
Tue Jun 04 02:11:56 [initandlisten] connection accepted from 127.0.0.1:53109 #3
Tue Jun 04 02:11:56 [initandlisten] connection accepted from 127.0.0.1:53110 #4
Tue Jun 04 02:11:56 [initandlisten] connection accepted from 127.0.0.1:53111 #5
Tue Jun 04 02:12:27 [clientcursormon] mem (MB) res:44 virt:277 mapped:80
Tue Jun 04 02:14:27 [clientcursormon] mem (MB) res:49 virt:274 mapped:80
Tue Jun 04 02:19:27 [clientcursormon] mem (MB) res:52 virt:278 mapped:80


***** SERVER RESTARTED *****


Tue Jun 04 02:25:40 [initandlisten] MongoDB starting : pid=4000 port=27117 dbpath=C:\Users\Win 7\Ubiquiti UniFi\data\db 64-bit host=Win7-PC
Tue Jun 04 02:25:40 [initandlisten] db version v2.0.1, pdfile version 4.5
Tue Jun 04 02:25:40 [initandlisten] git version: 3a5cf0e2134a830d38d2d1aae7e88cac31bdd684
Tue Jun 04 02:25:40 [initandlisten] build info: windows (6, 1, 7601, 2, 'Service Pack 1') BOOST_LIB_VERSION=1_42
Tue Jun 04 02:25:40 [initandlisten] options: { bind_ip: "127.0.0.1", dbpath: "C:\Users\Win 7\Ubiquiti UniFi\data\db", logappend: true, logpath: "logs/mongod.log", nohttpinterface: true, port: 27117 }
Tue Jun 04 02:25:40 [initandlisten] journal dir=C:/Users/Win 7/Ubiquiti UniFi/data/db/journal
Tue Jun 04 02:25:40 [initandlisten] recover begin
Tue Jun 04 02:25:40 [initandlisten] recover lsn: 537745
Tue Jun 04 02:25:40 [initandlisten] recover C:/Users/Win 7/Ubiquiti UniFi/data/db/journal/j._0
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:0 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:59845 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:119805 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:179755 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:239675 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:299495 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:359285 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:418495 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover skipping application of section seq:478235 < lsn:537745
Tue Jun 04 02:25:40 [initandlisten] recover cleaning up
Tue Jun 04 02:25:40 [initandlisten] removeJournalFiles
Tue Jun 04 02:25:40 [initandlisten] recover done
Tue Jun 04 02:25:40 [initandlisten] preallocating a journal file C:/Users/Win 7/Ubiquiti UniFi/data/db/journal/prealloc.0
        618659840/1073741824    57%
        775946240/1073741824    72%
        870318080/1073741824    81%
        954204160/1073741824    88%
        1069547520/1073741824    99%
Tue Jun 04 02:26:06 [initandlisten] waiting for connections on port 27117
Tue Jun 04 02:26:06 [initandlisten] connection accepted from 127.0.0.1:49440 #1
Tue Jun 04 02:26:10 [conn1] query ace.device ntoreturn:3000 nscanned:30 reslen:20 109ms
Tue Jun 04 02:26:11 [conn1] remove ace.stat query: { type: "current" } 530ms
Tue Jun 04 02:26:36 [initandlisten] connection accepted from 127.0.0.1:49535 #2
Tue Jun 04 02:26:36 [initandlisten] connection accepted from 127.0.0.1:49536 #3
Tue Jun 04 02:26:36 [initandlisten] connection accepted from 127.0.0.1:49537 #4
Tue Jun 04 02:26:36 [initandlisten] connection accepted from 127.0.0.1:49538 #5
Tue Jun 04 02:26:36 [initandlisten] connection accepted from 127.0.0.1:49539 #6
Tue Jun 04 02:26:37 [conn6] remove ace.event query: { key: { $in: [ "EVT_WG_Roam", "EVT_WG_Connected", "EVT_WG_Disconnected", "EVT_WU_Roam", "EVT_WU_Connected", "EVT_WU_Disconnected" ] }, datetime: { $lt: new Date(1369679196875) } } 1070ms
Tue Jun 04 02:26:41 [conn1] query ace.map.chunks ntoreturn:1 nscanned:1 nreturned:1 reslen:149602 190ms
Tue Jun 04 02:27:06 [clientcursormon] mem (MB) res:45 virt:278 mapped:80
Tue Jun 04 02:32:06 [clientcursormon] mem (MB) res:48 virt:279 mapped:80
Tue Jun 04 02:36:17 [initandlisten] connection accepted from 127.0.0.1:49859 #7
Tue Jun 04 02:36:17 [conn7] terminating, shutdown command received
Tue Jun 04 02:36:17 dbexit: shutdown called
Tue Jun 04 02:36:17 [conn7] shutdown: going to close listening sockets...
Tue Jun 04 02:36:17 [conn7] closing listening socket: 396
Tue Jun 04 02:36:17 [conn7] shutdown: going to flush diaglog...
Tue Jun 04 02:36:17 [conn7] shutdown: going to close sockets...
Tue Jun 04 02:36:17 [conn7] shutdown: waiting for fs preallocator...
Tue Jun 04 02:36:17 [conn7] shutdown: lock for final commit...
Tue Jun 04 02:36:17 [conn7] shutdown: final commit...
Tue Jun 04 02:36:17 [conn7] shutdown: closing all files...
Tue Jun 04 02:36:17 [conn7] closeAllFiles() finished
Tue Jun 04 02:36:17 [conn7] journalCleanup...
Tue Jun 04 02:36:17 [conn7] removeJournalFiles
Tue Jun 04 02:36:17 [conn7] shutdown: removing fs lock...
Tue Jun 04 02:36:17 dbexit: really exiting now


***** SERVER RESTARTED *****


Tue Jun 04 21:23:45 [initandlisten] MongoDB starting : pid=4712 port=27117 dbpath=C:\Users\Win 7\Ubiquiti UniFi\data\db 64-bit host=Win7-PC
Tue Jun 04 21:23:45 [initandlisten] db version v2.0.1, pdfile version 4.5
Tue Jun 04 21:23:45 [initandlisten] git version: 3a5cf0e2134a830d38d2d1aae7e88cac31bdd684
Tue Jun 04 21:23:45 [initandlisten] build info: windows (6, 1, 7601, 2, 'Service Pack 1') BOOST_LIB_VERSION=1_42
Tue Jun 04 21:23:45 [initandlisten] options: { bind_ip: "127.0.0.1", dbpath: "C:\Users\Win 7\Ubiquiti UniFi\data\db", logappend: true, logpath: "logs/mongod.log", nohttpinterface: true, port: 27117 }
Tue Jun 04 21:23:45 [initandlisten] journal dir=C:/Users/Win 7/Ubiquiti UniFi/data/db/journal
Tue Jun 04 21:23:45 [initandlisten] recover : no journal files present, no recovery needed
Tue Jun 04 21:23:45 [initandlisten] waiting for connections on port 27117
Tue Jun 04 21:23:46 [initandlisten] connection accepted from 127.0.0.1:49394 #1
Tue Jun 04 21:23:47 [conn1] query ace.device ntoreturn:3000 nscanned:30 reslen:20 156ms
Tue Jun 04 21:23:47 [conn1] remove ace.stat query: { type: "current" } 234ms
Tue Jun 04 21:23:47 [initandlisten] connection accepted from 127.0.0.1:49396 #2
Tue Jun 04 21:23:51 [initandlisten] connection accepted from 127.0.0.1:49413 #3
Tue Jun 04 21:23:57 [initandlisten] connection accepted from 127.0.0.1:49431 #4
Tue Jun 04 21:23:58 [initandlisten] connection accepted from 127.0.0.1:49433 #5
Tue Jun 04 21:23:59 [initandlisten] connection accepted from 127.0.0.1:49442 #6
Tue Jun 04 21:24:00 [initandlisten] connection accepted from 127.0.0.1:49443 #7
Tue Jun 04 21:24:01 [initandlisten] connection accepted from 127.0.0.1:49448 #8
Tue Jun 04 21:24:01 [initandlisten] connection accepted from 127.0.0.1:49451 #9
Tue Jun 04 21:24:07 [initandlisten] connection accepted from 127.0.0.1:49464 #10
Tue Jun 04 21:24:16 [conn2] remove ace.event query: { key: { $in: [ "EVT_WG_Roam", "EVT_WG_Connected", "EVT_WG_Disconnected", "EVT_WU_Roam", "EVT_WU_Connected", "EVT_WU_Disconnected" ] }, datetime: { $lt: new Date(1369747456133) } } 124ms
Tue Jun 04 21:24:45 [clientcursormon] mem (MB) res:46 virt:282 mapped:80
Tue Jun 04 21:25:19 [conn3] update ace.stat.hourly.ap.dc:9f:db:e8:62:63 query: { time: 1370350800000, datetime: new Date(1370350800000) } update: { $inc: { user-ng-time_delta: 1370352319, user-time_delta: 1370352319, ng-time_delta: 1370352319, time_delta: 1370352319, bytes: 0 } } fastmodinsert:1 124ms
Tue Jun 04 21:25:19 [conn3] update ace.stat.hourly.ap.dc:9f:db:e8:62:63 query: { time: 1370350800000, datetime: new Date(1370350800000) } update: { $addToSet: { sta_macs: "74:2f:68:02:b4:8c", user_macs: "74:2f:68:02:b4:8c" } } moved:1 156ms
Tue Jun 04 21:26:46 [clientcursormon] mem (MB) res:51 virt:279 mapped:80
Tue Jun 04 21:31:46 [clientcursormon] mem (MB) res:53 virt:283 mapped:80
Tue Jun 04 21:36:47 [clientcursormon] mem (MB) res:54 virt:283 mapped:80
Tue Jun 04 21:41:47 [clientcursormon] mem (MB) res:54 virt:283 mapped:80



 

Regular Member
nelson6069
Posts: 442
Registered: ‎10-15-2012
Posts: 442
Kudos: 12
Registered: 10-15-2012

Re: Unifi AP LR cannot connect, but can ping it.

Here is my TOUGHSwitch log file.

 


Aug 28 16:17:18 system: Start
Aug 28 16:17:18 syslogd started: BusyBox v1.11.2
Aug 28 16:17:19 dropbear[868]: Not backgrounding
Aug 29 22:51:43 init: reloading /etc/inittab
Aug 29 22:51:43 system: Stop
Aug 29 22:51:44 dropbear[868]: premature exit: Terminated by signal
Aug 29 22:51:44 init: process '/sbin/ntpclient -n -s -c 0 -l -h pool.ntp.org' (pid 865) exited. Scheduling for restart.
Aug 29 22:51:44 init: process '/bin/telnetd -F -p 23' (pid 867) exited. Scheduling for restart.
Aug 29 22:51:44 init: process '/bin/dropbear -F -d /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 868)
Aug 29 22:51:45 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 866) exited. Scheduling for restart.
Aug 29 22:51:46 syslogd exiting
Aug 29 22:51:48 system: Start
Aug 29 22:51:48 syslogd started: BusyBox v1.11.2
Aug 29 22:51:48 pwdog[1086]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 0 5`
Aug 29 22:51:49 dropbear[1085]: Not backgrounding
Aug 29 22:52:24 init: reloading /etc/inittab
Aug 29 22:52:24 system: Stop
Aug 29 22:52:24 dropbear[1085]: premature exit: Terminated by signal
Aug 29 22:52:25 init: process '/sbin/ntpclient -n -s -c 0 -l -h pool.ntp.org' (pid 1082) exited. Scheduling for restart.
Aug 29 22:52:25 init: process '/bin/telnetd -F -p 23' (pid 1084) exited. Scheduling for restart.
Aug 29 22:52:25 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 0 5" 172.16.2.16' (pid 1086) exited. Scheduling for restart.
Aug 29 22:52:26 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1083) exited. Scheduling for restart.
Aug 29 22:52:26 init: process '/bin/dropbear -F -d /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1085
Aug 29 22:52:27 syslogd exiting
Aug 29 22:52:31 system: Start
Aug 29 22:52:31 syslogd started: BusyBox v1.11.2
Aug 29 22:52:32 pwdog[1303]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 1 5`
Aug 29 22:52:32 pwdog[1302]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 0 5`
Aug 29 22:52:32 dropbear[1301]: Not backgrounding
Aug 29 22:53:11 init: reloading /etc/inittab
Aug 29 22:53:11 system: Stop
Aug 29 22:53:12 dropbear[1301]: premature exit: Terminated by signal
Aug 29 22:53:12 init: process '/sbin/ntpclient -n -s -c 0 -l -h pool.ntp.org' (pid 1298) exited. Scheduling for restart.
Aug 29 22:53:12 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1299) exited. Scheduling for restart.
Aug 29 22:53:12 init: process '/bin/telnetd -F -p 23' (pid 1300) exited. Scheduling for restart.
Aug 29 22:53:12 init: process '/bin/dropbear -F -d /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1301
Aug 29 22:53:12 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 0 5" 172.16.2.16' (pid 1302) exited. Scheduling for restart.
Aug 29 22:53:12 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 1 5" 172.16.2.17' (pid 1303) exited. Scheduling for restart.
Aug 29 22:53:13 syslogd exiting
Aug 29 22:53:16 system: Start
Aug 29 22:53:16 syslogd started: BusyBox v1.11.2
Aug 29 22:53:16 pwdog[1520]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 1 5`
Aug 29 22:53:16 pwdog[1521]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 2 5`
Aug 29 22:53:16 pwdog[1519]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 0 5`
Aug 29 22:53:18 dropbear[1518]: Not backgrounding
Aug 29 22:54:10 init: reloading /etc/inittab
Aug 29 22:54:10 system: Stop
Aug 29 22:54:11 init: process '/sbin/ntpclient -n -s -c 0 -l -h pool.ntp.org' (pid 1515) exited. Scheduling for restart.
Aug 29 22:54:11 init: process '/bin/telnetd -F -p 23' (pid 1517) exited. Scheduling for restart.
Aug 29 22:54:11 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 0 5" 172.16.2.16' (pid 1519) exited. Scheduling for restart.
Aug 29 22:54:11 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 1 5" 172.16.2.17' (pid 1520) exited. Scheduling for restart.
Aug 29 22:54:11 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 2 5" 172.16.2.18' (pid 1521) exited. Scheduling for restart.
Aug 29 22:54:11 dropbear[1518]: premature exit: Terminated by signal
Aug 29 22:54:12 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1516) exited. Scheduling for restart.
Aug 29 22:54:12 init: process '/bin/dropbear -F -d /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1518
Aug 29 22:54:12 syslogd exiting
Aug 29 22:54:16 system: Start
Aug 29 22:54:16 syslogd started: BusyBox v1.11.2
Aug 29 22:54:16 pwdog[1738]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 1 5`
Aug 29 22:54:16 pwdog[1740]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 3 5`
Aug 29 22:54:16 pwdog[1737]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 0 5`
Aug 29 22:54:16 pwdog[1739]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 2 5`
Aug 29 22:54:19 dropbear[1736]: Not backgrounding
Aug 29 22:54:49 init: reloading /etc/inittab
Aug 29 22:54:49 system: Stop
Aug 29 22:54:50 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 0 5" 172.16.2.16' (pid 1737) exited. Scheduling for restart.
Aug 29 22:54:50 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 1 5" 172.16.2.17' (pid 1738) exited. Scheduling for restart.
Aug 29 22:54:50 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 2 5" 172.16.2.18' (pid 1739) exited. Scheduling for restart.
Aug 29 22:54:50 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 3 5" 172.16.2.19' (pid 1740) exited. Scheduling for restart.
Aug 29 22:54:50 dropbear[1736]: premature exit: Terminated by signal
Aug 29 22:54:51 init: process '/sbin/ntpclient -n -s -c 0 -l -h pool.ntp.org' (pid 1733) exited. Scheduling for restart.
Aug 29 22:54:51 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1734) exited. Scheduling for restart.
Aug 29 22:54:51 init: process '/bin/telnetd -F -p 23' (pid 1735) exited. Scheduling for restart.
Aug 29 22:54:51 init: process '/bin/dropbear -F -d /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1736
Aug 29 22:54:52 syslogd exiting
Aug 29 22:54:56 system: Start
Aug 29 22:54:56 syslogd started: BusyBox v1.11.2
Aug 29 22:54:57 pwdog[1956]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 0 5`
Aug 29 22:54:57 pwdog[1958]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 2 5`
Aug 29 22:54:57 pwdog[1960]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 4 5`
Aug 29 22:54:57 pwdog[1959]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 3 5`
Aug 29 22:54:57 pwdog[1957]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 1 5`
Aug 29 22:54:57 dropbear[1955]: Not backgrounding
Aug 29 22:55:57 pwdog[1956]: PING Watchdog is checking 172.16.2.16 (172.16.2.16).
Aug 29 22:55:57 pwdog[1958]: PING Watchdog is checking 172.16.2.18 (172.16.2.18).
Aug 29 22:55:57 pwdog[1959]: PING Watchdog is checking 172.16.2.19 (172.16.2.19).
Aug 29 22:55:57 pwdog[1960]: PING Watchdog is checking 172.16.2.20 (172.16.2.20).
Aug 29 22:55:57 pwdog[1957]: PING Watchdog is checking 172.16.2.17 (172.16.2.17).
Aug 29 22:56:57 pwdog[1956]: Missed 1 ping replies in a row.
Aug 30 16:16:32 init: reloading /etc/inittab
Aug 30 16:16:32 system: Stop
Aug 30 16:16:33 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 0 5" 172.16.2.16' (pid 1956) exited. Scheduling for restart.
Aug 30 16:16:33 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 1 5" 172.16.2.17' (pid 1957) exited. Scheduling for restart.
Aug 30 16:16:33 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 2 5" 172.16.2.18' (pid 1958) exited. Scheduling for restart.
Aug 30 16:16:33 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 3 5" 172.16.2.19' (pid 1959) exited. Scheduling for restart.
Aug 30 16:16:33 init: process '/bin/pwdog -d 60 -p 60 -c 5 -e "sh /bin/poectrl 4 5" 172.16.2.20' (pid 1960) exited. Scheduling for restart.
Aug 30 16:16:33 dropbear[1955]: premature exit: Terminated by signal
Aug 30 16:16:34 init: process '/sbin/ntpclient -n -s -c 0 -l -h pool.ntp.org' (pid 1952) exited. Scheduling for restart.
Aug 30 16:16:34 init: process '/bin/lighttpd -D -f /etc/lighttpd.conf' (pid 1953) exited. Scheduling for restart.
Aug 30 16:16:34 init: process '/bin/telnetd -F -p 23' (pid 1954) exited. Scheduling for restart.
Aug 30 16:16:34 init: process '/bin/dropbear -F -d /etc/persistent/dropbear_dss_host_key -r /etc/persistent/dropbear_rsa_host_key -p 22 ' (pid 1955
Aug 30 16:16:35 syslogd exiting
Aug 30 16:16:38 system: Start
Aug 30 16:16:39 syslogd started: BusyBox v1.11.2
Aug 30 16:16:39 pwdog[2187]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 4 5`
Aug 30 16:16:39 pwdog[2184]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 1 5`
Aug 30 16:16:39 pwdog[2186]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 3 5`
Aug 30 16:16:39 pwdog[2185]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 2 5`
Aug 30 16:16:40 pwdog[2188]: pwdog: do_now=0, initial_sleep=60, timeout=60, retry_count=5, low_mem=0 exec=`sh /bin/poectrl 0 5`
Aug 30 16:16:40 dropbear[2183]: Not backgrounding

Ubiquiti Employee
UBNT-MikeD
Posts: 2,049
Registered: ‎01-28-2013
Posts: 2049
Kudos: 497
Solutions: 212
Contributions: 17
Registered: 01-28-2013

Re: Unifi AP LR cannot connect, but can ping it.

so you cannot connect to it in the controller? or you can't connect to it wirelessly? is it broadcasting a ssid?

 

i understand you can ping it...which is a good start...have you tried ssh to see if you can connect to it that way?

UBNT_Alternate_Logo.png

Regular Member
nelson6069
Posts: 442
Registered: ‎10-15-2012
Posts: 442
Kudos: 12
Registered: 10-15-2012

Re: Unifi AP LR cannot connect, but can ping it.

i cannot connect to the UNIFI AP.

how to try using ssh?

Ubiquiti Employee
UBNT-MikeD
Posts: 2,049
Registered: ‎01-28-2013
Posts: 2049
Kudos: 497
Solutions: 212
Contributions: 17
Registered: 01-28-2013

Re: Unifi AP LR cannot connect, but can ping it.

so that means you can't wirelessly connect to it? but it is broadcasting a signal that you can see in the wifi connection area on your device/computer? does it show up in the controller?

 

here is a generic guide for SSH use. obviously enter the approprate user/pass and IP information. the default is ubnt/ubnt, but seeing as it's provisioned the user/pass will match that of the controller

 

You can SSH into your device using PuTTY for Windows or Console on MAC OS X.

For Windows:

  1. Download PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html, use it under your own risk!)
  2. Enter Hostname IP address (by default is 192.168.1.20), leave port as default and make sure you've selected protocol SSH
  3. Press "Enter" button
  4. Accept the certificate, then enter your username and password (by default credentials are ubnt in both cases) and press Enter key
  5. If it works properly you will see BZ2.x and a $ symbol, there you can enter the commands you want to use.

For MAC OS:

  1. Open Terminal (Console) under Program and Utilities
  2. Enter command "ssh -l (USERNAME) (IP ADDRESS)", by default username is ubnt and IP address 192.1681.2.0, so enter "ssh -l ubnt 192.168.1.20"
  3. Type Yes to accept the certificate, and press Enter key.
  4. Enter your device's password, by default it's "ubnt".

UBNT_Alternate_Logo.png

New Member
Robotech
Posts: 32
Registered: ‎09-02-2012
Posts: 32
Kudos: 3
Registered: 09-02-2012

Re: Unifi AP LR cannot connect, but can ping it.

[ Edited ]
I KNOW this has been here a long time but....
So,now that you know how to ssh in the Unifi AP -it would be nice to have the info here on how to reset the radio to defaults and uploading formware.
Remember if you can ping it - you should be able to ssh to it - but if you can not ping it - you may be out of luck -

I found that as a trimmed down linux ssh shell - typing "help" gives you some info on avail commands -
So here are some referances I found:

factory default:  Type:    syswrapper.sh restore-default
To upload newer firmware for AP-LR : Type:
 syswrapper.sh upgrade http://ip-of-controller:8080/dl/firmware/BZ2/version-of-ap-see-ref-table-below/firmware.bin

Then check out the table below and change the http part that you type in to match your version of controller - I am pretty sure that you have to use the firmware OF the ontoller - (input here if any)

Controller Version AP Upgrade URL UAP, UAP-LR, UAP-Outdoor, UAP-Outdoor5, PicoM2HP

3.2.1http://ip-of-controller:8080/dl/firmware/BZ2/3.2.1.2601/firmware.bin
2.4.6http://ip-of-controller:8080/dl/firmware/BZ2/2.4.6.2178/firmware.bin
2.4.5http://ip-of-controller:8080/dl/firmware/BZ2/2.4.5.2077/firmware.bin
2.4.4http://ip-of-controller:8080/dl/firmware/BZ2/2.4.4.2061/firmware.bin
2.4.3http://ip-of-controller:8080/dl/firmware/BZ2/2.4.3.2043/firmware.bin
2.3.9http://ip-of-controller:8080/dl/firmware/BZ2/2.3.9.1693/firmware.bin
2.3.8http://ip-of-controller:8080/dl/firmware/BZ2/2.3.8.1597/firmware.bin
2.2.5http://ip-of-controller:8080/dl/firmware/BZ2/2.2.5.1080/firmware.bin
2.2.4http://ip-of-controller:8080/dl/firmware/BZ2/2.2.4.1072/firmware.bin
2.2.3http://ip-of-controller:8080/dl/firmware/BZ2/2.2.3.1055/firmware.bin
2.2.2http://ip-of-controller:8080/dl/firmware/BZ2/2.2.2.1049/firmware.bin
2.2.1http://ip-of-controller:8080/dl/firmware/BZ2/2.2.1.1045/firmware.bin
2.2.0http://ip-of-controller:8080/dl/firmware/BZ2/2.2.0.996/firmware.bin
2.1.0http://ip-of-controller:8080/dl/firmware/BZ2/2.1.0.942/firmware.bin
If none of this works you could try the tftp copy option - 
http://community.ubnt.com/t5/UniFi-Controller-Installation/UniFi-Layer-3-methods-for-UAP-adoption-an...

Basicly you put the unit into tftp recive mode by pressing the reset button and holding it in as you turn the power on to the radio. The light will alternate between green and orange - that is tftp mode.
Once you get a tftp client program (your on your own to fiqure that out) -you can type from a command line :
tftp
binary
connect 192.168.1.20
put firmware.bin

The radio should give you an output of progress:
 put firmware.bin
Sent 5217643 bytes in 2.7 seconds
tftp> quit

Let it reboot and see if you can ping / ssh to it -

Good Luck!

Reply