Welcome to the Linux Foundation Forum!

crio.service failed (Step 5 of Exercise 3.2)

parkershamblin
parkershamblin Posts: 7
in LFD259 Class Forum

Hi, I'm getting the following output after running the sudo systemctl restart crio command.

sudo systemctl restart crio
Job for crio.service failed because a fatal signal was delivered to the control process.
See "systemctl status crio.service" and "journalctl -xe" for details.

I've made sure to copy the steps in part 4. Here is my registries.conf file.

Best Answer

  • nosal.peter
    nosal.peter Posts: 1
    edited March 2022 Answer ✓

    I was facing the same issue.

    After rebooting the server (sudo reboot) and connecting to it again, sudo systemctl status crio gives active status.

    There's a note in the Lab "Sometimes a reboot works to bring crio to typical operation.", but I didn't pay much attention to it and it should be better explained.

Answers

  • parkershamblin
    parkershamblin Posts: 7
    edited March 2022

    And this is the ouput I get after running the command "systemctl status crio.service"

    :~$ systemctl status crio.service
    ● crio.service - Container Runtime Interface for OCI (CRI-O)
    Loaded: loaded (/lib/systemd/system/crio.service; enabled; vendor preset: enabled)
    Active: failed (Result: core-dump) since Wed 2022-03-16 06:18:08 UTC; 1s ago
    Docs: https://github.com/cri-o/cri-o
    Process: 225062 ExecStart=/usr/bin/crio $CRIO_CONFIG_OPTIONS $CRIO_RUNTIME_OPTIONS $CRIO_STORAGE_OPTIONS $CRIO_NETWORK_OPTIONS $CRIO_METRICS_OPTIONS (code=dumped, signal=ABRT)
    Main PID: 225062 (code=dumped, signal=ABRT)

    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: crio.service: Main process exited, code=dumped, status=6/ABRT
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: crio.service: Failed with result 'core-dump'.
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: crio.service: Scheduled restart job, restart counter is at 5.
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: Stopped Container Runtime Interface for OCI (CRI-O).
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: crio.service: Start request repeated too quickly.
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: crio.service: Failed with result 'core-dump'.
    Mar 16 06:18:08 ip-172-31-28-98 systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).

  • parkershamblin
    parkershamblin Posts: 7

    @nosal.peter said:
    I was facing the same issue.

    After rebooting the server (sudo reboot) and connecting to it again, sudo systemctl status crio gives active status.

    There's a note in the Lab "Sometimes a reboot works to bring crio to typical operation.", but I didn't pay much attention to it and it should be better explained.

    Thanks @nosal.peter this got it working.

  • jacq0807
    jacq0807 Posts: 2

    Got the same issue and indeed rebooting the actual cp node solved the problem. Thank you.

Categories

Upcoming Training