Error starting up #257
Comments
|
I'll check it out. Current master everything? |
|
yes just double checked to make sure :) |
|
I'm struggling to get a working environment to reproduce. Using the latest beta on a pi3b+ rosmaster fails to start: This is also backed up by mavros not appearing to be on the python path... |
can't find boost libraries.. |
|
I know |
|
I have deeper issues: mav@maverick-raspberry:~$ ~/software/maverick/bin/rosmaster.sh apdev
... logging to /srv/maverick/var/log/ros/apdev/0c1e2b0c-e068-11ea-a898-b827eb2b499a/roslaunch-maverick-raspberry-5485.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
RLException: Unable to contact my own server at [http://maverick-raspberry:45231/].
This usually means that the network is not configured properly.
A common cause is that the machine cannot ping itself. Please check
for errors by running:
ping maverick-raspberry
For more tips, please see
http://wiki.ros.org/ROS/NetworkSetup
The traceback for the exception was written to the log file
mav@maverick-raspberry:~$ ping maverick-raspberry
PING maverick-raspberry.local (192.168.0.12) 56(84) bytes of data.
From 192.168.0.11 (192.168.0.11) icmp_seq=1 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=2 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=3 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=4 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=5 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=6 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=7 Destination Host Unreachable
From 192.168.0.11 (192.168.0.11) icmp_seq=8 Destination Host Unreachable
^C
--- maverick-raspberry.local ping statistics ---
9 packets transmitted, 0 received, +8 errors, 100% packet loss, time 17ms
pipe 4
mav@maverick-raspberry:~$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:7e:1c:cf txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2062583 bytes 922520567 (879.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2062583 bytes 922520567 (879.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.11 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2001:8003:1848:8f01:ba27:ebff:fe2b:499a prefixlen 64 scopeid 0x0<global>
inet6 fe80::ba27:ebff:fe2b:499a prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:2b:49:9a txqueuelen 1000 (Ethernet)
RX packets 26321 bytes 31012955 (29.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 16379 bytes 3776891 (3.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
mav@maverick-raspberry:~$ Appears to be a hostname issue? |
Looks like your dhcp lease has renewed with a different IP. Either change the entry in /etc/hosts with the new IP or run |
|
okay, yep. /etc/hosts was pointing to the wrong ip. Running a configure now. |
|
okay. I'm now seeing the same boost issue as you. |
|
|
|
|
okay, new problem
|
|
winning yet? no... |
🥳 |
|
summary: The ldconfig might be needed also... e.g. |
|
Very odd, shoudln't ever have to install these by hand. Must be missing a rosdep somewhere, not seen this before. |
|
Ah balls I know what the problem is - I took a shortcut creating the maverick-raspberry image by copying maverick-raspberrylite ~/software to cut down on the build time. This bypasses the various system installs that are done inside the various protected build flag compiles which aren't then done after the build flags are installed. I'll fix and produce a new image. The raspberrylite image should be fine :) |
|
I flashed the lite image and that appears to be working. |
|
I've fixed/updated the full raspberry image! |
|
Running How can this be fixed? Followed this thread but could not find a viable solution. Ran |
|
Hi, yep this is still an issue that I have not yet worked on. You can modify the configuration file for maverick-api to avoid loading the mavros plugin for the time being. |
|
I'll make this change in maverick tonight: That line needs |
|
Hi, thanks that solves this problem. However, I'm getting another issue: I think my configuration is wrong somewhere. Could you please help me with this? PS: In the previous issue, I tried setting INVALID = -1 in /srv/maverick/software/python/lib/python3.7/site-packages/graphql/error/init.py |
|
They modified the graphql core library, specifically around the custom type handling. The original root error you ran into is some code designed to handle the parameter value type which can be either a float or an int. Anyway, it looks like there is another issue possibly with the port default port selection. I'll take a look after work today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@SamuelDudley - maybe something to do with a recent graphql update?
The text was updated successfully, but these errors were encountered: