FAQ: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Fix: remove --- horizontal lines (7 removed)) |
||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== | {{Status | ||
|status=Draft | |||
|owner=Knowledge Agent | |||
|last_update=2026-07-16 | |||
|review=Pending | |||
}} | |||
{{TOC}} | |||
== | == Overview == | ||
FAQ에 대한 기술 문서입니다. | |||
=== Summary === | |||
* | * 무엇인가? - FAQ | ||
* | * 왜 필요한가? - HPC 및 서버 환경에서 필수 개념 | ||
* | * 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시 | ||
== Purpose == | |||
이 문서가 존재하는 이유 | |||
* | * Goal: FAQ에 대한 기술 정보 제공 | ||
* | * Scope: FAQ의 개념, 사용법, 설정 | ||
* Non-goals: 다른 주제로의 확장 | |||
== Key Concepts == | |||
{| class="wikitable" | |||
! Concept | |||
! Description | |||
! Related | |||
|- | |||
| FAQ | |||
| HPC/서버 환경에서 중요한 기술 개념 | |||
| [[Linux]], [[Server]] | |||
|} | |||
== Detailed Explanation == | |||
If your system reboot randomly without [[kernel]] logs, the most possible reason would be power supply stability issue although the PSU might looks working well. | |||
Beyond PSU, we can trace the reason of system reboot to software issue or hardware issue with kernel.panic parameters, | |||
If kernel.panic system parameter is <code>0,</code> it is turned off automatic reboot on panic, any other value is the number of seconds it wait before reboot. | |||
With <code>sysctl -w kernel.panic=0</code> you would turn it off, if it is not already off. | |||
If this is set to <code>0</code> and your server still reboots itself, it would really think this is a hardware issue. If this stops the automatic rebooting, then we know the reboot is caused by a watchdog timer or other software issue | |||
* Reason - warning or information from the snapshotter<ref>https://dev.to/napicella/what-is-a-containerd-snapshotters-3eo2</ref> - image storage - that we have a lot of choices | |||
* Impact : the warning log doesn't impact the whole system operating | |||
* Solve to | |||
1.Disable the snapshotter plugins which you don't need by updating config file for your system and restart containerd, like | |||
<# /etc/containerd/config.toml | |||
disabled_plugins = ["cri", "btrfs"] | |||
2. To use ZFS, you need to mount ZFS dataset on /var/lib/containerd/io.containerd.snapshotter.v1.zfs | |||
3. To use btrfs, you need to mount btrfs to /var/lib/containerd/io.containerd.snapshotter.v1.btrfs | |||
4. For aufs, you need to modprobe it as explained in the error log | |||
* Reason - no nvidia-container-toolkit or currupt exist package | |||
* Solve to install/reinstall nvidia-container-toolkit then restart [[docker]] daemon | |||
<syntaxhighlight lang="bash"> | |||
$distribution=$(. /etc/os-release;echo $ID$VERSION_ID) \ | |||
&& curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add - \ | |||
&& curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list | |||
== Best Practices == | |||
* 최신 버전 사용 권장 | |||
* 공식 문서 참고 | |||
* 테스트 환경에서 먼저 검증 | |||
== References == | |||
* [https://wiki.hpcmate.com FAQ] | |||
== Related Pages == | |||
* [[Linux]] | |||
* [[Server]] | |||
* [[Hardware]] | |||
* [[Network]] | |||
[[Category:Server]] | |||
== Knowledge Graph == | |||
Related | |||
→ [[Linux]] | |||
→ [[Server]] | |||
→ [[Troubleshooting]] | |||
→ [[Terms]] | |||
[[Category:Reference]] | |||
Latest revision as of 11:28, 17 July 2026
Overview
FAQ에 대한 기술 문서입니다.
Summary
- 무엇인가? - FAQ
- 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
- 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
Purpose
이 문서가 존재하는 이유
- Goal: FAQ에 대한 기술 정보 제공
- Scope: FAQ의 개념, 사용법, 설정
- Non-goals: 다른 주제로의 확장
Key Concepts
| Concept | Description | Related |
|---|---|---|
| FAQ | HPC/서버 환경에서 중요한 기술 개념 | Linux, Server |
Detailed Explanation
If your system reboot randomly without kernel logs, the most possible reason would be power supply stability issue although the PSU might looks working well.
Beyond PSU, we can trace the reason of system reboot to software issue or hardware issue with kernel.panic parameters,
If kernel.panic system parameter is 0, it is turned off automatic reboot on panic, any other value is the number of seconds it wait before reboot.
With sysctl -w kernel.panic=0 you would turn it off, if it is not already off.
If this is set to 0 and your server still reboots itself, it would really think this is a hardware issue. If this stops the automatic rebooting, then we know the reboot is caused by a watchdog timer or other software issue
- Reason - warning or information from the snapshotter[1] - image storage - that we have a lot of choices
- Impact : the warning log doesn't impact the whole system operating
- Solve to
1.Disable the snapshotter plugins which you don't need by updating config file for your system and restart containerd, like
<# /etc/containerd/config.toml disabled_plugins = ["cri", "btrfs"]
2. To use ZFS, you need to mount ZFS dataset on /var/lib/containerd/io.containerd.snapshotter.v1.zfs 3. To use btrfs, you need to mount btrfs to /var/lib/containerd/io.containerd.snapshotter.v1.btrfs 4. For aufs, you need to modprobe it as explained in the error log
- Reason - no nvidia-container-toolkit or currupt exist package
- Solve to install/reinstall nvidia-container-toolkit then restart docker daemon
<syntaxhighlight lang="bash"> $distribution=$(. /etc/os-release;echo $ID$VERSION_ID) \
&& curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add - \ && curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list
Best Practices
- 최신 버전 사용 권장
- 공식 문서 참고
- 테스트 환경에서 먼저 검증
References
Related Pages
Knowledge Graph
Related
→ Linux → Server → Troubleshooting → Terms