Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Off Topic
    4. Proxmox
    5. nach Update -- Startprobleme

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    nach Update -- Startprobleme

    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      lessthanmore @Negalein last edited by

      @negalein Welche Meldung(en) kommen in der PVE?

      Negalein 1 Reply Last reply Reply Quote 0
      • arteck
        arteck Developer Most Active @Negalein last edited by

        @negalein das ist ok so...

        1 Reply Last reply Reply Quote 0
        • Negalein
          Negalein Global Moderator @lessthanmore last edited by

          @lessthanmore sagte in nach Update -- Startprobleme:

          Welche Meldung(en) kommen in der PVE?

          das kommt beim Startversuch des LXC

          root@proxmox:~# lxc-start 102
          lxc-start: 102: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 869 No such file or directory - Failed to receive the container state
          lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
          lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
          lxc-start: 102: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options
          
          arteck 1 Reply Last reply Reply Quote 0
          • arteck
            arteck Developer Most Active @Negalein last edited by arteck

            @negalein weiter gehts

            cat /var/lib/lxc/102/config
            

            ansonsten auch noch

            lxc-start -n 102 -l DEBUG -o /tmp/lxc-debug.log
            

            dann in /tmp/lxc-debug.log schauen da muss mehr stehen

            Negalein 1 Reply Last reply Reply Quote 0
            • Negalein
              Negalein Global Moderator @arteck last edited by

              @arteck sagte in nach Update -- Startprobleme:

              cat /var/lib/lxc/102/config

              root@proxmox:~# cat /var/lib/lxc/102/config
              lxc.cgroup.relative = 0
              lxc.cgroup.dir.monitor = lxc.monitor/102
              lxc.cgroup.dir.container = lxc/102
              lxc.cgroup.dir.container.inner = ns
              lxc.arch = amd64
              lxc.include = /usr/share/lxc/config/ubuntu.common.conf
              lxc.include = /usr/share/lxc/config/ubuntu.userns.conf
              lxc.seccomp.profile = /var/lib/lxc/102/rules.seccomp
              lxc.apparmor.profile = generated
              lxc.apparmor.raw = deny mount -> /proc/,
              lxc.apparmor.raw = deny mount -> /sys/,
              lxc.mount.auto = sys:mixed
              lxc.monitor.unshare = 1
              lxc.idmap = u 0 100000 65536
              lxc.idmap = g 0 100000 65536
              lxc.tty.max = 2
              lxc.environment = TERM=linux
              lxc.uts.name = pihole
              lxc.cgroup2.memory.max = 536870912
              lxc.cgroup2.memory.swap.max = 536870912
              lxc.rootfs.path = /var/lib/lxc/102/rootfs
              lxc.net.0.type = veth
              lxc.net.0.veth.pair = veth102i0
              lxc.net.0.hwaddr = 7A:50:48:A4:AF:DB
              lxc.net.0.name = eth0
              lxc.net.0.script.up = /usr/share/lxc/lxcnetaddbr
              lxc.cgroup2.cpuset.cpus = 3
              

              /tmp/lxc-debug.log

              
              lxc-start 102 20250626145349.836 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type u nsid 0 hostid 100000 range 65536
              lxc-start 102 20250626145349.836 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g nsid 0 hostid 100000 range 65536
              lxc-start 102 20250626145349.837 INFO     lxccontainer - ../src/lxc/lxccontainer.c:do_lxcapi_start:997 - Set process title to [lxc monitor] /var/lib/lxc 102
              lxc-start 102 20250626145349.837 DEBUG    lxccontainer - ../src/lxc/lxccontainer.c:wait_on_daemonized_start:858 - First child 2898894 exited
              lxc-start 102 20250626145349.837 INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
              lxc-start 102 20250626145349.837 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "102", config section "lxc"
              lxc-start 102 20250626145350.375 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: unsupported Ubuntu version '24.04'
              
              lxc-start 102 20250626145350.384 ERROR    conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 255
              lxc-start 102 20250626145350.384 ERROR    start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "102"
              lxc-start 102 20250626145350.384 ERROR    start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "102"
              lxc-start 102 20250626145350.384 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "102", config section "lxc"
              lxc-start 102 20250626145350.806 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp0: not mounted.
              
              lxc-start 102 20250626145350.806 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp0' failed: e>
              
              lxc-start 102 20250626145350.809 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: umount: /var/lib/lxc/.pve-staged-mounts/mp1: not mounted.
              
              lxc-start 102 20250626145350.809 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-poststop-hook 102 lxc post-stop produced output: command 'umount -- /var/lib/lxc/.pve-staged-mounts/mp1' failed: e>
              
              lxc-start 102 20250626145350.846 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "102", config section "lxc"
              lxc-start 102 20250626145351.348 ERROR    lxccontainer - ../src/lxc/lxccontainer.c:wait_on_daemonized_start:869 - No such file or directory - Failed to receive the container state
              lxc-start 102 20250626145351.348 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
              lxc-start 102 20250626145351.348 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:309 - To get more details, run the container in foreground mode
              lxc-start 102 20250626145351.348 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options
              
              arteck 1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @Negalein last edited by arteck

                @negalein

                sudo nano /usr/share/lxc/hooks/lxc-pve-prestart-hook
                
                if [ "$ID" = "ubuntu" ] && [ "$VERSION_ID" = "24.04" ]; then
                    echo "unsupported Ubuntu version '$VERSION_ID'" >&2
                    exit 255
                fi
                

                auskommentieren also so

                # if [ "$ID" = "ubuntu" ] && [ "$VERSION_ID" = "24.04" ]; then
                #     echo "unsupported Ubuntu version '$VERSION_ID'" >&2
                #     exit 255
                # fi
                

                speichern

                wenn du die zeilen nicht findest dann poste die /usr/share/lxc/hooks/lxc-pve-prestart-hook.. das muss so ähnlich drin stehen

                startet der dann

                lxc-start -n 102 -F
                

                ist bissel wild aber da greif der grätscht ein check dazwischen

                Negalein 1 Reply Last reply Reply Quote 0
                • Negalein
                  Negalein Global Moderator @arteck last edited by

                  @arteck sagte in nach Update -- Startprobleme:

                  wenn du die zeilen nicht findest dann poste die /usr/share/lxc/hooks/lxc-pve-prestart-hook.. das muss so ähnlich drin stehen

                  lxc-pve-prestart-hook

                  arteck 1 Reply Last reply Reply Quote 0
                  • arteck
                    arteck Developer Most Active @Negalein last edited by arteck

                    @negalein grosses tennis... ideen aus...

                    hast du eine Sicherung ?? dann spiel die zurück..
                    alles andere ist murks..

                    Ubuntu 24.04 ist zur Zeit das problem..

                    Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 102 lxc pre-start produced output: unsupported Ubuntu version '24.04'
                    

                    du könntest den check noch verarschen und dem eine 22 unterjubeln .. aber das ist nicht sinn der sache

                    Negalein Meister Mopper 2 Replies Last reply Reply Quote 0
                    • Negalein
                      Negalein Global Moderator @arteck last edited by

                      @arteck sagte in nach Update -- Startprobleme:

                      hast du eine Sicherung ?? dann spiel die zurück..

                      Danke, spiel das Backup ein.

                      1 Reply Last reply Reply Quote 0
                      • Meister Mopper
                        Meister Mopper @arteck last edited by

                        @Negalein

                        Ubuntu 24.04 ist zur Zeit das problem..

                        Mal wieder ein Argument für den Umstieg auf das Original => Debian.

                        Ich habe auch noch drei headless Ubuntu-Server laufen und stelle die jetzt nach und nach auf Debian um.

                        Ich warte aktuell aber noch auf das offizielle Ausrollen von Trixie, sonst müsste ich bald wieder ein release-upgrade fahren.
                        Das erspare ich mir.

                        Negalein 1 Reply Last reply Reply Quote 0
                        • Negalein
                          Negalein Global Moderator @Meister Mopper last edited by

                          @meister-mopper sagte in nach Update -- Startprobleme:

                          Mal wieder ein Argument für den Umstieg auf das Original => Debian.

                          werde ich jetzt auch nach und nach machen.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          631
                          Online

                          31.9k
                          Users

                          80.1k
                          Topics

                          1.3m
                          Posts

                          4
                          14
                          218
                          Loading More Posts
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes
                          Reply
                          • Reply as topic
                          Log in to reply
                          Community
                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                          The ioBroker Community 2014-2023
                          logo