openwsip-2

[SKapoor]

Federico,

     Installing openWISP-2 finally facing this issue while loading manager-2

 sudo ansible-playbook -i hosts playbook.yml -u admin -k --ask-sudo-pass
SSH password:
SUDO password[defaults to SSH password]:

PLAY [openwisp2] ***************************************************************

TASK [setup] *******************************************************************
fatal: [192.168.6.244]: UNREACHABLE! => {"changed": false, "msg": "Authentication failure.", "unreachable": true}
    to retry, use: --limit @/home/zbtdell02/openwisp2-ansible-playbook/playbook.retry

PLAY RECAP *********************************************************************
192.168.6.244              : ok=0    changed=0    unreachable=1    failed=0 

Need your help

Regards

[Federico Capoano]

It seems ansible cannot log in via SSH into your machine.

Can you ping 192.168.6.244? Eg:

ping 192.168.6.244

Can you log in via ssh with the user admin? Eg:

 

ssh admin@192.168.6.244

Are you sure the password is correct?

The first thing you have to get sorted is to be able to SSH into 192.168.6.244 via ansible.

Federico

[sonia kapoor]

I tried doing ssh but no luck..

In the wisp-2 readme :

Create a new file hosts on your local machine with the following contents:

[openwisp2]
openwisp2.mydomain.com

Substitute openwisp2.mydomain.com with your hostname (ip addresses are allowed as well).

This tells whatever IP I m getting for local machine I have to put in host file replacing openwisp2.myfomain.com

So , if I m not wrong ping will always work but whn I try doing ssh it is not working...

I m using ubunthu-14.04 ..Is there any limitations on the  

Ansible version to be used ?

What is going wrong ?

Regards

--
You received this message because you are subscribed to a topic in the Google Groups "OpenWISP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openwisp/siqqAoIxnK4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openwisp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Federico Capoano]

Find out how to login via ssh into your server.

Bytheway, are you using a server or are you trying this on a desktop pc?

If you are using a server, you may ask to your hosting support or a friend that knows a bit of system administration.

If you are using your own pc you can run the playbook locally, consult the ansible documentation and look on google for "running ansible playbook locally".

For any question regarding ubuntu, their support channels are very active.

[SKapoor]

Hi Federico

I did it locally on my vmware machine. I am able to bring up openWISP-2 manager.

What I did different from README is instead of

ansible-playbook -i hosts playbook.yml -u ubunthu -k --ask-sudo-pass

I used this

ansible-playbook -i hosts playbook.yml -c local -k --ask-sudo-pass
and it worked for me, curious to know why -u ubunthu didnt work for me?
Step-2 will try to bring up openwisp-2 firmware.
thanks so much federico :)
regards

[Federico Capoano]

Well, it could be you were trying the wrong user/password combination or any other information to connect via SSH was not correct.

Anyway, the important thing is that you made it.

To compile an OpenWRT image with openwisp-config, I suggest you to follow the instructions in "Compiling a custom OpenWRT/LEDE image"

You received this message because you are subscribed to the Google Groups "OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.

[sonia kapoor]

Thanks for helping out, I have already started on firmware side procedures. Will update you the progress soon.

One question I have wrt group ap firmware upgrade!! Is that supported with openwisp2?

Thanks in advance,

[Federico Capoano]

See below.

On Friday, February 3, 2017 at 4:08:37 PM UTC+1, SKapoor wrote:

Thanks for helping out, I have already started on firmware side procedures. Will update you the progress soon.

Welcome.

 

One question I have wrt group ap firmware upgrade!! Is that supported with openwisp2?

 

I haven't understood very well your question.

Do you need to upgrade the firmware on a group of routers?

If that's the case, openwisp2 doesn't have this feature yet, even though has been on our wish list for a while.

[SKapoor]

Federico,

Why I am getting these logs that AP is not able to register?

 logread -f

Fri Feb  3 15:49:34 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: attempt to call global 'post' (a nil value)

Fri Feb  3 15:49:34 2017 daemon.err uhttpd[1175]: stack traceback:

Fri Feb  3 15:49:34 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/controller/openwisp/actions.lua:12: in function 'v'

Fri Feb  3 15:49:34 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:536: in function 'createtree'

Fri Feb  3 15:49:34 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:201: in function 'dispatch'

Fri Feb  3 15:49:34 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

Fri Feb  3 15:49:39 2017 daemon.err openwisp: Failed to connect to controller during registration: curl exit code 51

Fri Feb  3 15:49:55 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: attempt to call global 'post' (a nil value)

Fri Feb  3 15:49:55 2017 daemon.err uhttpd[1175]: stack traceback:

Fri Feb  3 15:49:55 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/controller/openwisp/actions.lua:12: in function 'v'

Fri Feb  3 15:49:55 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:536: in function 'createtree'

Fri Feb  3 15:49:55 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:201: in function 'dispatch'

Fri Feb  3 15:49:55 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

Fri Feb  3 15:50:01 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: attempt to call global 'post' (a nil value)

Fri Feb  3 15:50:01 2017 daemon.err uhttpd[1175]: stack traceback:

Fri Feb  3 15:50:01 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/controller/openwisp/actions.lua:12: in function 'v'

Fri Feb  3 15:50:01 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:536: in function 'createtree'

Fri Feb  3 15:50:01 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:201: in function 'dispatch'

Fri Feb  3 15:50:01 2017 daemon.err uhttpd[1175]:       /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167>

Fri Feb  3 15:50:10 2017 daemon.info openwisp: Registering device...

Fri Feb  3 15:50:16 2017 daemon.err openwisp: Failed to connect to controller during registration: curl exit code 51

Fri Feb  3 15:50:46 2017 daemon.info openwisp: Registering device...

Fri Feb  3 15:50:51 2017 daemon.err openwisp: Failed to connect to controller during registration: curl exit code 51

Fri Feb  3 15:51:21 2017 daemon.info openwisp: Registering device...

To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenWISP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openwisp/siqqAoIxnK4/unsubscribe.

To unsubscribe from this group and all its topics, send an email to openwisp+unsubscribe@googlegroups.com.

[Federico Capoano]

Google "curl exit code 51"

To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "OpenWISP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openwisp/siqqAoIxnK4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openwisp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenWISP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.

[Federico Capoano]

The CURL docs cites:

CURLE_PEER_FAILED_VERIFICATION (51)

The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK.

Please read SSL certificates gotchas section in the ansible-openwisp2 README.

Is it clear?

General suggestions: every time you get an error on the log, look for the most significant part on google.

Federico

[sonia kapoor]

With regards to question on group firmware upgrade, your understandi is  correct.. 

is it supported in openwisp1?

Roughly when you planning for this feature support in openwisp2? 

Thanks

--

[Federico Capoano]

No is not supported in OpenWISP1 either.

I can't plan this right now, I have to focus on bringing all the features of OpenWISP1 Manager into OpenWISP2 first.

Federico

You received this message because you are subscribed to the Google Groups "OpenWISP" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.

[SKapoor]

Yes, Federico clear. Let me just do it and will update you :)

[SKapoor]

Finally up and running ..

Thanks a ton :) Federico

 logread -f

Sat Feb  4 07:45:01 2017 daemon.info openwisp: New device registered successfully as 52:2F:59:E8:1E:49, id: 14b03501-a7e7-4382-83ad-5cc4e7540ec9

Sat Feb  4 07:45:01 2017 daemon.info openwisp: Local configuration outdated

Sat Feb  4 07:45:01 2017 daemon.info openwisp: Downloading configuration from controller...

Sat Feb  4 07:45:02 2017 daemon.info openwisp: Configuration downloaded, now applying it...

Sat Feb  4 07:45:03 2017 daemon.info openwisp: The following uci configs have been renamed: dhcp.cfg02411c, dropbear.cfg024dd4, firewall.cfg1c92bd, fi.

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service dhcp has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service dropbear has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service firewall has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service network has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service openwisp has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service rpcd has been reloaded via init.d script

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service system has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service ucitrack has been reloaded via procd/ubus

Sat Feb  4 07:45:04 2017 daemon.info openwisp: Service wireless has been reloaded via procd/ubus

[   59.450000] device wlan0 left promiscuous mode

[   59.450000] br-lan: port 2(wlan0) entered disabled state

Sat Feb  4 07:45:05 2017 kern.info kernel: [   59.450000] device wlan0 left promiscuous mode

Sat Feb  4 07:45:05 2017 kern.info kernel: [   59.450000] br-lan: port 2(wlan0) entered disabled state

Sat Feb  4 07:45:06 2017 daemon.notice netifd: lan (1286): Performing a DHCP renew

Sat Feb  4 07:45:06 2017 daemon.notice netifd: lan (1286): Sending renew...

Sat Feb  4 07:45:06 2017 daemon.notice netifd: lan (1286): Lease of 192.168.1.109 obtained, lease time 259200

Sat Feb  4 07:45:06 2017 daemon.info openwisp: OpenWISP config agent received reload trigger

Sat Feb  4 07:45:06 2017 daemon.notice netifd: radio0 (1826): Configuration file: /var/run/hostapd-phy0.conf

[   60.450000] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Sat Feb  4 07:45:06 2017 kern.info kernel: [   6[   60.460000] device wlan0 entered promiscuous mode

0.450000] IPv6: [   60.460000] br-lan: port 2(wlan0) entered forwarding state

ADDRCONF(NETDEV_[   60.470000] br-lan: port 2(wlan0) entered forwarding state

UP): wlan0: link is not ready

Sat Feb  4 07:45:06 2017 kern.info kernel: [   60.460000] device wlan0 entered promiscuous mode

Sat Feb  4 07:45:06 2017 kern.info kernel: [   60.460000] br-lan: port 2(wlan0) entered forwarding state

Sat Feb  4 07:45:06 20[   60.500000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

17 kern.info kernel: [   60.470000] br-lan: port 2(wlan0) entered forwarding state

Sat Feb  4 07:45:06 2017 daemon.notice netifd: radio0 (1826): Using interface wlan0 with hwaddr 00:20:a6:f6:1d:fe and ssid "wmcRadioA"

Sat Feb  4 07:45:06 2017 kern.info kernel: [   60.500000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Sat Feb  4 07:45:06 2017 daemon.notice netifd: radio0 (1826): wlan0: interface state UNINITIALIZED->ENABLED

Sat Feb  4 07:45:06 2017 daemon.notice netifd: radio0 (1826): wlan0: AP-ENABLED 

Sat Feb  4 07:45:07 2017 daemon.notice netifd: Network device 'wlan0' link is up

Sat Feb  4 07:45:07 2017 daemon.notice netifd: lan (1286): Performing a DHCP renew

Sat Feb  4 07:45:07 2017 daemon.notice netifd: lan (1286): Sending renew...

Sat Feb  4 07:45:07 2017 daemon.notice netifd: lan (1286): Lease of 192.168.1.109 obtained, lease time 259200

[   62.470000] br-lan: port 2(wlan0) entered forwarding state

Sat Feb  4 07:45:08 2017 kern.info kernel: [   62.470000] br-lan: port 2(wlan0) entered forwarding state

Sat Feb  4 07:45:10 2017 daemon.info openwisp: Configuration test succeded

Sat Feb  4 07:45:11 2017 daemon.info openwisp: Configuration applied succesfully

Sat Feb  4 07:45:11 2017 daemon.info openwisp: OpenWISP config agent started

On Saturday, 4 February 2017 12:05:54 UTC+5:30, SKapoor wrote:

Yes, Federico clear. Let me just do it and will update you :)

On Friday, 3 February 2017 21:34:16 UTC+5:30, Federico Capoano wrote:

The CURL docs cites:

CURLE_PEER_FAILED_VERIFICATION (51)

The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK.

inally 

[Federico Capoano]

Great news. 

Federico