What is Nostr?
Stefano Marinelli /
npub1ef5…gcpc
2024-06-24 07:58:23

Stefano Marinelli on Nostr: Experts in OmniOS, SmartOS, IllumOS, and Solaris, I have a question: I have an OmniOS ...

Experts in OmniOS, SmartOS, IllumOS, and Solaris, I have a question: I have an OmniOS VPS with several zones, obviously in their ZFS datasets. I'm simulating an emergency restore on another equivalent VPS, just as I do with all my backups. I created a live snapshot of my zone (without halting and detaching) and I'm copying it to the other VPS with a command similar to:
zfs send -vcR rpool/zones/nginx@toMove01 | ssh root@myIP "zfs receive -F rpool/zones/nginx"
The copy completes successfully. At that point, on the destination VPS, I run:
zonecfg -z nginx -f nginx.cfg

The content of nginx.cfg is:
create -b
set zonepath=/zones/nginx
set brand=pkgsrc
set autoboot=true
set limitpriv=default
set ip-type=exclusive
add net
set allowed-address="192.168.123.254/24"
set physical="nginx0"
set mac-addr="2:8:20:9:d7:f2"
set global-nic="internal0"
set defrouter="192.168.123.1"
end
add attr
set name="resolvers"
set type="string"
set value="1.1.1.1,9.9.9.9"
end

The zone is created and is in a configured state. When I run zoneadm -z nginx attach, no output is given, so everything seems okay, but in fact, the zone remains "configured" and a start returns:
[2024-06-24 09:50:41.92728] [29919] [warn] WARNING: cannot 'boot' nginx. nginx is configured and not installed.
Running the install command will create different datasets.

Can you give me some advice? Thank you very much!

#OmniOS #SmartOS #IllumOS #Solaris #ZFS #SysAdmin #TechSupport #IT
Author Public Key
npub1ef53dd26zz26wlxa70xrl238fywamsrfp24nxxysesczwv425r0q6tgcpc