Root Service Trees not initializing after being enabled

notai

Hello guys,

I'm having some issues regarding setting some service trees to start automatically after the boot tree.
I have a tree 'net' which contains the services required to establish a network connection, I have enabled the tree and in 66-intree it shows that it should start after boot (the first tree to initialize on system on). If I manually start the tree with '66-all -z -t net up' all of the services go up successfully and function like they should.

Is there any fix to this? Having checked a previous topic [topic]798[/topic] from a few years ago I ran

cat /var/lib/66/system/state

and found that it only returned the trees that exist which appears to be correct (base suffers the same issues as net, works if I manually start the tree but will not automatically go up)

boot
net
base

nfg

Hi nota,

When you do as root:

# 66-intree -g

does net show up as "Current"? If not, try to designate it as such:

# 66-tree -c net

Then reboot and see if startd automatically.

If that works, but base doesn't follow after it automatically (and assuming it too is already enabled), try:

# 66-tree -S net base

Hope something above helps. Best, nfg

notai

Hey nfg,

Trying your suggestions

66-intree -g

did not show net as 'current' initially, but after designating and rebooting net still did not boot up on start.

After rebooting and logging in as root checking the service trees with

66-intree

shows the Enabled property is still set to yes (the net tree was set to current this time around) on both net and base but has still had their Initialized property set to No, with their services still not activating automatically however manual activation after waiting for a minute to see if automatic initialization was just delayed still worked.

nfg

Hi again notai,

Sorry that didn't fix anything. I tried to re-create your issue with a minimal install of Obarun in a VM, but I actually couldn't get an enabled tree not to automatically start at reboot. So I'm wondering if you could give a bit more info about your installation - hardware/virtual, minimal/desktop environment (and which DE, if the latter).

Also, when you installed it, did it not automatically create a root tree for you after the boot tree?

notai

It's more than likely I borked something when installing Obarun as I used and adapted the 'install from Arch' tutorial such and other wiki pages such as 66 Intro and Boot to install Obarun from my vanilla Arch ISO. (I have wondered if the documentation is severely outdated vs the installation medium but went this route anyways)

The system is very minimal so far running only Linux on hardware (no virtual machines, no dual booting) and as of yet doesn't have a graphical environment (using a laptop to communicate on this forum). As fas as my boot tree: Yes, because of how I chose to install it I had to manually create the boot tree but once I detached the ISO the boot tree was operating just fine.

eric

the first thing to do is to read the output of

# 66-intree -o name,enabled

the boot tree should not be enabled but all trees that you want to start at boot time need to be enabled.

So, enable a tree

# 66-tree -E <treename>

Take care of the order of the tree

# 66-intree -o name,enabled,start

reorganize it if you need

# 66-tree -S <tree_to_start_before_treename> <treename>

tricks, if you need to mark a tree as the first tree to start do

# 66-tree -S <same_treename> <same_treename>

notai

Thanks Eric!

I happened to have the boot tree enabled and set to initialize first before my other trees. After disabling it and rebooting the other service trees started initializing automatically. Problem solved!

Also thank you nfg for your help yesterday.

eric

Enabling the boot tree is a common mistake. The new version of 66 take of that and prevent it.