When reconfiguring boot@system I got this bug

66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
parse: fatal: unable to run: /etc/66/service/boot@system/configure/configure

Now I can't boot into the system. Now I am trying to recover with KNOPPIX.
TTY12 is available - but I get the same error there.
How to solve the problem?

Are you sure to be up to date?
if the tty12 is available you don't need to chroot your system. You can repair from tty12 directly.
So from tty12 you can do

# mount -o remount,rw / # this remount your root partition in read write mode.
# pacman -Sy 66 oblibs 66-tools skalibs execline s6
# 66 reconfigure boot@system
# 66 reboot # only if you don't get any errors with the previous command

    eric if the tty12 is available you don't need to chroot your system. You can repair from tty12 directly.

    I get the same error there.
    And I can't log in as a user on TTY12.

    • eric replied to this.

      i'm a little confuse now because you tell me

      batjka911 I get the same error there.

      and right after

      batjka911 And I can't log in as a user on TTY12.

      how you can launch the 66 reconfigure if you are not log in??

      batjka911 I don't understand the question a bit.

      Are you sure to use the last version of the 66 packages and skalibs familly?
      Why do you use the boot@ service from /etc/66/service instead of the provided one by Obarun at /usr/share/66/service?

      As our famous satirist used to say - "One awkward move and you're a father."
      The system is now completely broken.

      66 enable boot@system
      parse: fatal: unable to parse file of service: local-authfiles

      Can it be recovered from KNOPPIX or reinstalled?

      We need more details to be able to help you.
      Did you have this troubles because you are in migration phase? Or because 66 at some point failed after a particular command?
      If you are migrating, did you followed the migration instructions?
      Can you provide us some useful information like the output of the following commands:

      # 66 version
      # 66 tree status -g
      # 66 status boot@system
      # pacman -Qs 66 
      # pacman -Qs skalibs
      You can accomplish this from tty12.

      I had a successful migration. Everything was fine. Just after yesterday's system update I got the error again this morning at work, which was sort of fixed with the new version 66-0.7.0.2 After that I tried reconfiguring boot@system and boot-user@ again. But the error I pointed out in the first post reappeared. The system did not boot.
      Authorization on TTY12 had an error with my user and the archlinux user became available. So I tried to recover with it, but failed.

      Well, after that I did something stupid. I deleted /var/lib/66/ /etc/66 ${HOME}/.66 and now I don't know how to recover. Through archchroot updated (reinstalled) all the packages mentioned.

      Now in order. (Doing everything via archchroot in last obarun live cd )

      [root@Ob66 /]# 66 version
      version: info: 0.7.1.0
      [root@Ob66 /]# 66 tree status -g
      Name        : global
      Current     : no
      Enabled     : yes
      Allowed     : root
      Groups      : admin
      Depends     : \
                    └─None
      Required by : \
                    └─None
      Contents    : \
                    └─None
      
      Name        : moduleboot
      Current     : no
      Enabled     : no
      Allowed     : root
      Groups      : admin
      Depends     : \
                    └─None
      Required by : \
                    └─None
      Contents    : \
                    └─None
      
      Name        : modulesession
      Current     : no
      Enabled     : no
      Allowed     : root
      Groups      : admin
      Depends     : \
                    └─None
      Required by : \
                    └─None
      Contents    : \
                    └─None
      [root@Ob66 /]# 66 status boot@system
      status: fatal: service: boot@system is not parsed -- try to parse it using '66 parse boot@system'
      [root@Ob66 /]# 66 parse boot@system
      parse: fatal: unable to parse file of service: local-authfiles
      [root@Ob66 /]# pacman -Qs 66
      local/66 0.7.1.0-1 (base s6-suite)
          Service manager built around s6
      local/66-tools 0.1.0.2-1 (base s6-suite)
          small tools and helpers for service scripts execution
      local/bluetoothd-66serv 0.7.0-3
          bluetoothd service for 66 service manager
      local/boot-user@-66serv 0.5.2-2
          Set of services to create a nested user scandir with console tracker and display manager support for 66 service
          manager
      local/boot@-66serv 3.7.0-3 (base s6-suite)
          Complete and portable set of services to properly boot a machine with 66 service manager
      local/connmand-66serv 0.7.0-3
          connmand service for 66 service manager
      local/console-tracker@-66serv 0.2.1-1
          General service to enable any console tracker
      local/consolekit-66serv 0.7.0-3
          consolekit service for 66 service manager
      local/cupsd-66serv 0.7.0-3
          cupsd service for 66 service manager
      local/dbus-66serv 0.7.0-3
          dbus service for 66 service manager
      local/dhcpcd-66serv 0.7.0-3
          dhcpcd service for 66 service manager
      local/dockerd-66serv 0.7.0-3
          dockerd service for 66 service manager
      local/httpd-66serv 0.7.0-3
          httpd service for 66 service manager
      local/libisofs 1.5.6-1
          Library to pack up hard disk files and directories into a ISO 9660 disk image
      local/libvirtd-66serv 0.7.0-3
          libvirtd service for 66 service manager
      local/mysqld-66serv 0.7.0-3
          mysqld service for 66 service manager
      local/openntpd-66serv 0.7.0-3
          openntpd service for 66 service manager
      local/pipewire-66serv 0.7.0-3
          pipewire service for 66 service manager
      local/qemu-guest-agent-66serv 0.2.0-1
          qemu-guest-agent service for 66 tools
      local/scandir@-66serv 0.4.2-2
          Service to create a nested user scandir for 66 service manager
      local/tty@-66serv 0.7.0-3
          tty@ service for 66 service manager
      local/wpa_supplicant-66serv 0.7.0-3
          wpa_supplicant service for 66 service manager
      local/xdg-user-dirs-66serv 0.7.0-3
          xdg service for 66 service manager
      [root@Ob66 /]# pacman -Qs skalibs
      local/skalibs 2.14.1.1-3 (base s6-suite)
          A general-purpose low-level C library

      moduleboot and modulesession? i dont think those are default tree names. by the looks of it, you need to recreate boot@system and boot-user@<username>

        negative recreate boot@system and boot-user@<username>

        sudo 66 enable boot@system                     
        tree: info: Created successfully tree: global
        tree: info: Enabled successfully tree: global
        tree: info: Permissions rules set successfully for tree: global
        tree: info: Created successfully tree: moduleboot
        tree: info: Permissions rules set successfully for tree: moduleboot
        parse: info: launch configure script of module: boot@system
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        touch: cannot touch '/activated/tty-earlier@tty12': No such file or directory
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        parse: fatal: unable to run: /etc/66/service/boot@system/configure/configure

        That's better. But there's a problem.

        sudo 66 -t boot enable boot@system       
        tree: info: Created successfully tree: global
        tree: info: Enabled successfully tree: global
        tree: info: Permissions rules set successfully for tree: global
        tree: info: Created successfully tree: boot
        tree: info: Already disabled tree: boot
        tree: info: Set successfully: boot to group: boot
        tree: info: Dependencies successfully managed for tree: boot
        tree: info: Required by successfully managed for tree: boot
        tree: info: Permissions rules set successfully for tree: boot
        parse: info: launch configure script of module: boot@system
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        touch: cannot touch '/activated/tty-earlier@tty12': No such file or directory
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        parse: fatal: unable to run: /etc/66/service/boot@system/configure/configure
        sudo 66 -t session enable boot-user@grandpa
        tree: info: Created successfully tree: session
        tree: info: Set successfully: session to group: admin
        tree: info: Dependencies successfully managed for tree: session
        tree: info: Required by successfully managed for tree: global
        tree: info: Required by successfully managed for tree: session
        tree: info: Already enabled tree: global
        tree: info: Enabled successfully tree: session
        tree: info: Permissions rules set successfully for tree: session
        parse: info: launch configure script of module: scandir@grandpa
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        sed: can't read /frontend/svscan@: No such file or directory
        66-yeller: fatal: invalid format of COLOR_ENABLED environment variable
        parse: fatal: unable to run: /etc/66/service/scandir@grandpa/configure/configure
        sudo 66 -z tree status -g                
        Name        : global
        Current     : no
        Enabled     : yes
        Allowed     : root
        Groups      : admin
        Depends     : \
                      └─None
        Required by : \
                      └─session (Enabled)
        Contents    : \
                      └─None
        
        Name        : boot
        Current     : no
        Enabled     : no
        Allowed     : root
        Groups      : boot
        Depends     : \
                      └─None
        Required by : \
                      └─None
        Contents    : \
                      └─None
        
        Name        : session
        Current     : no
        Enabled     : yes
        Allowed     : root
        Groups      : admin
        Depends     : \
                      └─global (Enabled)
        Required by : \
                      └─None
        Contents    : \
                      └─None

        Downgraded versions

        obcore/66         0.7.0.2-1
        obcore/66-tools   0.1.0.1-1
        obcore/oblibs     0.2.1.3-1
        obcore/s6         2.12.0.3-2

        and repaired everything in arch-chroot

        Ok, so , you clearly hit a bug. Just try to make a fresh installation and got same problem as you.
        I will try to fix as soon as possible

          eric I will try to fix as soon as possible

          I think it would also need to rebuild the live cd with the fixes.

          I don't understand how I could have missed this bug. Shame on me. In any case, the problem should be resolved. Just sync and update to get the latest release meaning 0.7.1.1.
          I've just done a new installation and everything seems to be fine now.

          It's never wrong to do nothing. So far, so good.
          I'm marking the problem as solved.

          batjka911 changed the title to [SOLVED] Reconfigure bug .

          Powered by Obarun