View Full Version : Device operation failed
Whenever I try to connect to a station to make it managed, I get the following error messages:
2009-11-05 11:13:03 Device operation failed: null
2009-11-05 11:12:25 Provisioning scheduled.
2009-11-02 11:16:03 New device UB: [xxxxxxxxx] discovered
This happens on quite a few of my units. I also can't upgrade the firmware remotely on these units. Most of these units are v3.4. I have confirmed that I can upgrade these via the web interface one at a time. Also, the status indicator is grey'd out. Any help would be appreciated.
Thanks
Jay
UBNT-Thomas
11-09-2009, 01:38 PM
This looks like a problem related to the particular network interface setup or the JDK version that I found at another customers environment recently.
Can you please pull the update (not the full installer) from
http://www.ubnt.com/forum/showpost.php?p=51414&postcount=1
and let me know whether it solves the issue?
No it did not. Still getting the same messages,
UBNT-Thomas
11-10-2009, 07:41 PM
Please check your private messages and provide the info requested.
bryonj
11-20-2009, 01:31 PM
I am having the same problem... Kind of... All my "M" devices respond fine. But when AirControl tries to configure the legacy devices it fails... I think I see why. It is defaulting to port 80 to try to talk to those devices and all my network uses a different port number for the web access... How do I change this so AirControl will work???
Thanks!
Bryon
UBNT-Thomas
11-20-2009, 02:39 PM
The problem is different. It's because AirControl attempts to enable SSH through the web interface when it is not enabled. Manually enable SSH and make sure firmware is at least 3.4 and AirControl won't try to access the web interface.
bryonj
11-20-2009, 08:35 PM
I have manually enabled SSH and all firmware is 3.4 but still no joy.... AM I missing something??? The majority of these are NS's and NS Loco's... I also have a couple of Powerstations as well... Still they will not allow me to "Manage" them and be visible in AirControl....
Also everything is Layer 3 accessible....
Bryon
bryonj
11-20-2009, 08:49 PM
This NS has ver 3.5 firmware in it and here is the log from its failure:
info[22:46:20,200]: 204.xx.xx.xx-Provisioning scheduled.
info[22:46:21,227]: 204.xx.xx.xx-Device operation failed: Failed to access http://204.xx.xx.xx for legacy web provisioning.
Interesting....
Bryon
UBNT-Thomas
11-21-2009, 02:08 PM
Whoops, due to another recent change the web UI was accessed even when SSH is already enabled. I just fixed this bug and the change is now part of the windows installer and update. Please give it a try.
bryonj
11-21-2009, 09:22 PM
FIXED IT! So far so good.... All 3.4 and 3.5 NS's are being managed by AirControl now...
Thanks Thomas!
Bryon
