crio.service failed (Step 5 of Exercise 3.2)
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
-
I was facing the same issue.
After rebooting the server (
sudo reboot
) and connecting to it again,sudo systemctl status crio
givesactive
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.
1
Answers
-
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).0 -
@nosal.peter said:
I was facing the same issue.After rebooting the server (
sudo reboot
) and connecting to it again,sudo systemctl status crio
givesactive
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.
1 -
Got the same issue and indeed rebooting the actual cp node solved the problem. Thank you.
0
Categories
- All Categories
- 112 LFX Mentorship
- 112 LFX Mentorship: Linux Kernel
- 604 Linux Foundation IT Professional Programs
- 315 Cloud Engineer IT Professional Program
- 139 Advanced Cloud Engineer IT Professional Program
- 52 DevOps Engineer IT Professional Program
- 67 Cloud Native Developer IT Professional Program
- 3 Express Training Courses
- 3 Express Courses - Discussion Forum
- 5.3K Training Courses
- 17 LFC110 Class Forum - Discontinued
- 8 LFC131 Class Forum
- 30 LFD102 Class Forum
- 178 LFD103 Class Forum
- LFD110 Class Forum
- 24 LFD121 Class Forum
- LFD133 Class Forum
- 2 LFD137 Class Forum
- 62 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 127 LFD232 Class Forum - Discontinued
- LFD233 Class Forum
- LFD237 Class Forum
- 22 LFD254 Class Forum
- 643 LFD259 Class Forum
- 107 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 1 LFS101 Class Forum
- LFS112 Class Forum
- LFS116 Class Forum
- LFS118 Class Forum
- LFS142 Class Forum
- LFS144 Class Forum
- 2 LFS145 Class Forum
- LFS146 Class Forum
- LFS151 Class Forum
- LFS157 Class Forum
- LFS158 Class Forum
- LFS162 Class Forum
- LFS167 Class Forum
- 28 LFS200 Class Forum
- 735 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 13 LFS203 Class Forum
- 98 LFS207 Class Forum
- 299 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 36 LFS243 Class Forum
- 12 LFS244 Class Forum
- LFS245 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 141 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 2 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 109 LFS260 Class Forum
- 144 LFS261 Class Forum
- 39 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 198 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 254 LFW211 Class Forum
- 173 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 781 Hardware
- 198 Drivers
- 68 I/O Devices
- 37 Monitors
- 95 Multimedia
- 174 Networking
- 87 Printers & Scanners
- 83 Storage
- 742 Linux Distributions
- 80 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 23 openSUSE
- 143 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 347 Ubuntu
- 450 Linux System Administration
- 31 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 89 Linux Security
- 76 Network Management
- 101 System Management
- 46 Web Management
- 51 Mobile Computing
- 18 Android
- 23 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 355 Off Topic
- 109 Introductions
- 167 Small Talk
- 18 Study Material
- 504 Programming and Development
- 283 Kernel Development
- 203 Software Development
- 844 Software
- 210 Applications
- 180 Command Line
- 3 Compiling/Installing
- 107 Games
- 308 Installation
- 51 All In Program
- 51 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)