|
|
|
|
Re: MQTT error on Beaglebone with debian [message #1586325 is a reply to message #1586265] |
Mon, 26 January 2015 20:02 |
Dan Cristian Messages: 17 Registered: January 2015 |
Junior Member |
|
|
I do not have ethtool installed, looks like it is not installed in this latest debian image I downloaded from beaglebone site.
I have just installed ethtool and good news, the error dissapeared and it looks like kura succesfully started. log attached.
However I still cannot open the admin interface, again the browser times out and I see no activity in the log while trying to open the admin page from a different computer.
Any new ideeas?
Netstat shows that there is a listener on port 8888.
dcristian@beaglebone:~$ netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:3350 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6010 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:6012 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.115:22 192.168.0.104:29658 ESTABLISHED
tcp 0 256 192.168.0.115:22 192.168.0.104:29657 ESTABLISHED
tcp 0 0 192.168.0.115:22 192.168.0.104:29659 ESTABLISHED
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::8888 :::* LISTEN
tcp6 0 0 :::3000 :::* LISTEN
tcp6 0 0 ::1:6010 :::* LISTEN
tcp6 0 0 ::1:6011 :::* LISTEN
tcp6 0 0 ::1:6012 :::* LISTEN
tcp6 0 0 :::5002 :::* LISTEN
tcp6 0 0 :::1450 :::* LISTEN
tcp6 0 0 :::8080 :::* LISTEN
udp 0 0 0.0.0.0:67 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:41564 0.0.0.0:*
udp 0 0 0.0.0.0:40080 0.0.0.0:*
udp6 0 0 :::42231 :::*
udp6 0 0 :::36243 :::*
udp6 0 0 :::48596 :::*
Iptables looks fine, probably not a firewall issue as I did no changes to firewall rules.
dcristian@beaglebone:~$ sudo iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- localhost anywhere tcp dpt:rfe
ACCEPT tcp -- anywhere anywhere tcp dpt:1450
ACCEPT tcp -- anywhere anywhere tcp dpt:1450
ACCEPT tcp -- 10.234.0.0/16 anywhere tcp dpt:http
ACCEPT tcp -- anywhere anywhere tcp dpt:http
ACCEPT tcp -- anywhere anywhere tcp dpt:http
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT icmp -- anywhere anywhere icmp echo-request state NEW,RELATED,ESTABLISHED
Chain FORWARD (policy DROP)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT icmp -- anywhere anywhere icmp echo-reply state RELATED,ESTABLISHED
-
Attachment: kura.log
(Size: 99.56KB, Downloaded 116 times)
|
|
|
Re: MQTT error on Beaglebone with debian [message #1586332 is a reply to message #1586325] |
Mon, 26 January 2015 20:06 |
Dan Cristian Messages: 17 Registered: January 2015 |
Junior Member |
|
|
Forgot to add ethtool output:
dcristian@beaglebone:~$ sudo ethtool eth0
Settings for eth0:
Current message level: 0x00000000 (0)
Link detected: yes
Looking at netstat output above I suspect that the cause if kura does not listen on the tcp interface, it only listen to tcp v6 one. I have tried to connect with telnet from a different computer directly to port 8888 and connection times out.
Not sure how I can enable kura to listen on 8888 on all network interfaces, any ideea?
[Updated on: Mon, 26 January 2015 20:28] Report message to a moderator
|
|
|
Re: MQTT error on Beaglebone with debian [message #1586476 is a reply to message #1586332] |
Mon, 26 January 2015 22:04 |
Dan Cristian Messages: 17 Registered: January 2015 |
Junior Member |
|
|
I finally managed to get it work.
I first disabled IPV6 support on beagle to force kura to listen on IPV4 interface. I added these lines in /etc/sysctl.conf and restarted the system:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv6.conf.eth0.disable_ipv6 = 1
Then I changed kura config.ini line to org.osgi.service.http.port=80 as per the default setup and restarted kura.
Make sure you disable the default http server on port 80 using:
systemctl disable bonescript.service
systemctl disable bonescript.socket
systemctl disable bonescript-autorun.service
It looks like debian on beagle by default (maybe due to kura settings) does not accept tcp connections to upper ports.
With the above tweaks I can now open the admin interface. If you want to change kura port use the kura admin interface to open a new port in the firewall and then change the port in kura config.ini. This way I managed to have kura running on port 8888.
Thanks all for your help.
[Updated on: Mon, 26 January 2015 22:12] Report message to a moderator
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04274 seconds