Jump to content

megusta

Members
 View Profile  See their activity

  • Posts

    3

  • Joined

  • Last visited

 Content Type 

Posts posted by megusta

    Cgroup failure

    in Beginners

    Posted

    Hello,

    I've some trouble to install K3s on my OrangePi Zero2, somewhere I read it could be a kernel problem (not activated). I get following message. Can someone help me?

      

    Apr 08 20:39:15 oPi2 k3s[4055]: time="2022-04-08T20:39:15+02:00" level=info msg="Run: k3s kubectl"
Apr 08 20:39:15 oPi2 k3s[4055]: time="2022-04-08T20:39:15+02:00" level=fatal msg="failed to find cpu cgroup (v2)"
Apr 08 20:39:15 oPi2 systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
Apr 08 20:39:15 oPi2 systemd[1]: k3s.service: Failed with result 'exit-code'.
Apr 08 20:39:15 oPi2 systemd[1]: Failed to start Lightweight Kubernetes.

      

     k3s.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s.service; disabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/k3s.service.d
             └─dietpi.conf
     Active: failed (Result: exit-code) since Fri 2022-04-08 20:39:15 CEST; 2s ago
       Docs: https://k3s.io
    Process: 4051 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
    Process: 4053 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=1/FAILURE)
    Process: 4054 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
    Process: 4055 ExecStart=/usr/local/bin/k3s server (code=exited, status=1/FAILURE)
   Main PID: 4055 (code=exited, status=1/FAILURE)
    # uname -a
Linux oPi2 4.9.255-sun50iw9 #1 SMP PREEMPT Tue Mar 1 23:28:34 UTC 2022 aarch64 GNU/Linux

# cat os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

     

    0

    How to install, enable and start watchdog in H3

    in Beginners

    Posted

    hey guys,

    can someone help me, maybe I forgot something. My watchdog.service doesn't work :(

      

    watchdog.service - watchdog daemon
   Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: ena
bled)
   Active: inactive (dead) since Mon 2019-10-28 23:58:27 CET; 15h ago
  Process: 2836 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchd
og $watchdog_options (code=exited, status=2)
  Process: 2833 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog
_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, status=0/SUCCE
SS)
      CPU: 24ms

Warning: Journal has been rotated since unit was started. Log output is incomplete o
r unavailable.

      

    echo 1 > /dev/watchdog

    it works, orange pi zero restarts

    my /etc/default/watchdog 

    # Start watchdog at boot time? 0 or 1
run_watchdog=1
# Start wd_keepalive after stopping watchdog? 0 or 1
run_wd_keepalive=1
# Load module before starting watchdog
watchdog_module="none"
# Specify additional watchdog options here (see manpage).

    my /etc/watchdog.conf 

    ping                    = 1.1.1.1
ping                    = 192.168.178.1
interface               = wlan0
#file                   = /var/log/messages
#change                 = 1407

# Uncomment to enable test. Setting one of these values to '0' disables it.
# These values will hopefully never reboot your machine during normal use
# (if your machine is really hung, the loadavg will go much higher than 25)
#max-load-1             = 24
#max-load-5             = 18
#max-load-15            = 12

# Note that this is the number of pages!
# To get the real size, check how large the pagesize is on your machine.
#min-memory             = 1
#allocatable-memory     = 1

#repair-binary          = /usr/sbin/repair
#repair-timeout         = 60
test-binary             = /usr/local/bin/watchdog_led.sh
test-timeout            = 60

# The retry-timeout and repair limit are used to handle errors in a more robust
# manner. Errors must persist for longer than retry-timeout to action a repair
# or reboot, and if repair-maximum attempts are made without the test passing a
# reboot is initiated anyway.
#retry-timeout          = 60
#repair-maximum         = 1

watchdog-device = /dev/watchdog

# Defaults compiled into the binary
temperature-sensor      =/sys/class/thermal/thermal_zone0/temp 
max-temperature = 90

# Defaults compiled into the binary
#admin                  = root
interval                = 20
#logtick                = 1
#log-dir                = /var/log/watchdog

# This greatly decreases the chance that watchdog won't be scheduled before
# your machine is really loaded
realtime                = yes
priority                = 1

# Check if rsyslogd is still running by enabling the following line
#pidfile                = /var/run/rsyslogd.pid
pidfile         = /var/lib/zerotier-one/zerotier-one.pid

    my  /etc/systemd/system.conf 

    RuntimeWatchdogSec=16
ShutdownWatchdogSec=10min

    my /boot/armbianEnv.txt 

    verbosity=7
logo=disabled
console=none
disp_mode=1920x1080p60
overlay_prefix=sun8i-h3
overlays=usbhost2 usbhost3
rootdev=UUID=***
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u
extraarg=thiswatchdogparameter=value
extraarg=sunxi_wdt.nowayout=1

    lsmod 

    Module                  Size  Used by
xt_nat                 16384  7
xt_tcpudp              16384  21
veth                   20480  0
xt_conntrack           16384  1
ipt_MASQUERADE         16384  8
nf_conntrack_netlink    32768  0
nfnetlink              16384  2 nf_conntrack_netlink
xt_addrtype            16384  2
iptable_filter         16384  1
iptable_nat            16384  1
nf_nat_ipv4            16384  2 ipt_MASQUERADE,iptable_nat
nf_nat                 24576  2 xt_nat,nf_nat_ipv4
nf_conntrack           77824  6 xt_nat,ipt_MASQUERADE,nf_conntrack_netlink,xt_conntrack,nf_nat_ipv4,nf_nat
nf_defrag_ipv6         16384  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
br_netfilter           20480  0
aufs                  167936  0
aes_arm_bs             20480  0
crypto_simd            16384  1 aes_arm_bs
cryptd                 20480  1 crypto_simd
ccm                    20480  9
overlay                77824  5
sun8i_codec_analog     24576  0
sun8i_adda_pr_regmap    16384  1 sun8i_codec_analog
snd_soc_simple_card    16384  0
sun4i_i2s              20480  0
snd_soc_simple_card_utils    16384  1 snd_soc_simple_card
snd_soc_core          114688  4 sun4i_i2s,sun8i_codec_analog,snd_soc_simple_card_utils,snd_soc_simple_card
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_pcm                69632  3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core
lima                   40960  0
xradio_wlan            94208  1
sun4i_gpadc_iio        16384  0
snd_timer              24576  1 snd_pcm
gpu_sched              20480  1 lima
snd                    45056  3 snd_timer,snd_soc_core,snd_pcm
ttm                    57344  1 lima
soundcore              16384  1 snd
industrialio           49152  1 sun4i_gpadc_iio
mac80211              450560  1 xradio_wlan
sun8i_ths              16384  0
cfg80211              393216  2 mac80211,xradio_wlan
cpufreq_dt             16384  0
uio_pdrv_genirq        16384  0
uio                    16384  1 uio_pdrv_genirq
thermal_sys            57344  3 cpufreq_dt,sun8i_ths,sun4i_gpadc_iio
usb_f_acm              16384  1
u_serial               20480  1 usb_f_acm
g_serial               16384  0
libcomposite           40960  2 g_serial,usb_f_acm
ip_tables              20480  2 iptable_filter,iptable_nat
x_tables               20480  7 xt_nat,ip_tables,iptable_filter,xt_tcpudp,ipt_MASQUERADE,xt_addrtype,xt_conntrack
pwrseq_simple          16384  1

     

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept