turtlebot / turtlebot4

Turtlebot4 common packages.
Apache License 2.0
105 stars 47 forks source link

Errors were encountered while processing: ros-humble-turtlebot4-setup #483

Open PrakritTyagi opened 1 month ago

PrakritTyagi commented 1 month ago

Robot Model

Turtlebot 4 Lite

ROS distro

Humble

Networking Configuration

I do not Know

OS

Ubuntu 22.0

Built from source or installed?

Installed

Package version

ubuntu@ubuntu:~$ dpkg -s ros-$ROS_DISTRO-turtlebot4-setup
Package: ros-humble-turtlebot4-setup
Status: install ok half-configured
Priority: optional
Section: misc
Installed-Size: 158
Maintainer: rkreinin <rkreinin@clearpathrobotics.com>
Architecture: arm64
Version: 1.0.4-1jammy.20240909.222719
Config-Version: 1.0.4-1jammy.20240729.103100
Depends: chrony, curl, libcurl4-openssl-dev, network-manager, ros-humble-rmw-cyclonedds-cpp, ros-humble-rmw-fastrtps-cpp, ros-humble-robot-upstart, ros-humble-simple-term-menu-vendor, ros-humble-ros-workspace
Conffiles:
 /etc/netplan/40-ethernets.yaml 6951b8a2f7fb3a647df50f19ed2b2762
 /etc/netplan/50-wifis.yaml e8658f314d8ccb4b2a1b5c4e4177dfa1
 /etc/systemd/system/webserver.service 2523ae6ccd96188391cb0cb7ea23c39b
 /etc/turtlebot4/aliases.bash e61a911906f05218fa606b6c5dfe2692
 /etc/turtlebot4/chrony.conf b7543efe4007b9480e0703dfccfce355
 /etc/turtlebot4/cyclonedds_rpi.xml 0ec64bd77cca8e8f6940486d2b02ae99
 /etc/turtlebot4/discovery.conf cbc9b4a66fec3957b98f258787587bd8
 /etc/turtlebot4/discovery.sh 8e476f2f051ffcd3f6062a9cefdb6d3e
 /etc/turtlebot4/fastdds_discovery_create3.xml 1abbfb9fd0db423dc7fdda2c083fdfbc
 /etc/turtlebot4/fastdds_rpi.xml 962330bbabde220a0eebee74d6f5b1ac
 /etc/turtlebot4/setup.bash d7b290c54b8eda578fb45dd021cad7d6
 /etc/turtlebot4/system a3b4be75d5acaf62cee13e9778ed9267
 /etc/udev/rules.d/50-turtlebot4.rules a9cb48367140746f5dc8bc0e37fd0c38
 /etc/udev/rules.d/80-movidius.rules 2f8a6174b951839e879fec25e7cdf624
 /etc/udev/rules.d/99-gpio.rules 9c389cf82c14c517d06232c2dac2599d
Description: Turtlebot4 setup scripts

Type of issue

Other

Expected behaviour

I expected that updating the TurtleBot 4 should finish without any errors.

Actual behaviour

While updating the TurtleBot 4, ros-humble-turtlebot4-setup is not properly configured.

Error messages

Installing new spi-rtc.dtbo.
Taking backup of spi2-1cs.dtbo.
Installing new spi2-1cs.dtbo.
Taking backup of cap1106.dtbo.
Installing new cap1106.dtbo.
Taking backup of w5500.dtbo.
Installing new w5500.dtbo.
Taking backup of minipitft13.dtbo.
Installing new minipitft13.dtbo.
Taking backup of README.
Installing new README.
Errors were encountered while processing:
 ros-humble-turtlebot4-setup
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

To Reproduce

  1. Flashed the sd-card using wget https://raw.githubusercontent.com/turtlebot/turtlebot4_setup/humble/scripts/sd_flash.sh bash sd_flash.sh ~/Downloads/turtlebot4_lite_humble_1.0.4.img
  2. SSH into the Raspberry Pi using ssh ubuntu@10.42.0.1
  3. Connected the Raspberry Pi to my network by following the instructions after turtlebot4-setup
  4. Found the new IP address and SSH into it.
  5. Updating the TurtleBot 4 sudo apt update && sudo apt upgrade

Other notes

Note:

PrakritTyagi commented 1 month ago

I am thinking of creating the chrony.conf file and copying the contents of the file from turtlebot4_setup package.

Update:

I just did what i said above and here is the terminal output.

ubuntu@ubuntu:~$ sudo apt update && sudo apt upgrade
Hit:1 http://packages.ros.org/ros2/ubuntu jammy InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [128 kB]
Hit:4 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [129 kB]
Fetched 257 kB in 2s (115 kB/s)   
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  linux-headers-5.15.0-1059-raspi linux-image-5.15.0-1059-raspi linux-modules-5.15.0-1059-raspi linux-raspi-headers-5.15.0-1059
Use 'sudo apt autoremove' to remove them.
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  libde265-dev libheif1 libjs-jquery-ui libpathplan4 libopenexr-dev graphviz
  libgvpr2 libgvc6 libopenexr25 libcgraph6 libswscale-dev libcdt5 libavcodec58
  libavutil56 libswscale5 libheif-dev libavutil-dev liblab-gamut1
  libswresample3 libavformat58 libpmix-dev libavformat-dev libavcodec-dev
  libde265-0 libpmix2 libswresample-dev
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages have been kept back:
  libnetplan0 netplan.io
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up ros-humble-turtlebot4-setup (1.0.4-1jammy.20240909.222719) ...
Scanning processes...                                                                                                                       
Scanning candidates...                                                                                                                      
Scanning processor microcode...                                                                                                             
Scanning linux images...                                                                                                                    

Failed to check for processor microcode upgrades.

Restarting services...
Service restarts being deferred:
 systemctl restart NetworkManager.service
 /etc/needrestart/restart.d/dbus.service
 systemctl restart networkd-dispatcher.service
 systemctl restart packagekit.service
 systemctl restart polkit.service
 systemctl restart ssh.service
 systemctl restart systemd-journald.service
 systemctl restart systemd-logind.service
 /etc/needrestart/restart.d/systemd-manager
 systemctl restart systemd-networkd.service
 systemctl restart systemd-resolved.service
 systemctl restart systemd-udevd.service
 systemctl restart turtlebot4.service
 systemctl restart unattended-upgrades.service
 systemctl restart user@1000.service
 systemctl restart webserver.service
 systemctl restart wpa_supplicant.service

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

There was a prompt for kernal pending kernel upgrade Screenshot from 2024-10-13 21-30-41

Next there was a prompt for restarting services which I canceled.

Can some tell me is my setup complete or did I mess up somewhere?

smatarCPR commented 1 month ago

Hello @PrakritTyagi Thank you for reaching out on the Turtlebot 4 Github page. A bit of background on this matter, there is a known bug with regards to obtaining the chrony.conf file, but we have pushed a bug fix for this, but copying the file template and creating it from scratch is a viable option. From our end it the file appears fine and the terminal output seems reasonable. Are you encountering any operational issues with the Turtlebot?

In terms of the kernel, where is this update coming from? Have you connected a monitor to the Raspberry Pi?

Looking forward to hearing from you soon. Best Regards, Saif

PrakritTyagi commented 1 month ago

HI @smatarCPR Thanks for replying. I was waiting for the reply, and I have not tried out operating the Turtlebot with turtlebot4_lite_humble_1.0.4.img, ill let you know.

In terms of kernel I get the kernel update msg through ssh. I didnt connect the monitor to the Raspi. Can you tell me what the expected kernel version is for both lite and standard turtlebots running ros2 humble after running sudo apt update && sudo apt upgrade??

ill do everything again and if i encounter any operational issue ill let you know. Best Regards.

smatarCPR commented 4 weeks ago

Hello @PrakritTyagi , Apologies for the late reply on this. We don't not have a specified kernel version, you are free to use the most up to date version of the kernel available to you. The kernel screen you are seeing is simply a notification that a newer version of the kernel is available for use and you should restart the Pi so that the kernel can be used.

Are you able to get past this kernel screen?

Looking forward to hearing from you soon. Best Regards, Saif