[OmniOS-discuss] Boot Environment not active after reboot
Hi, I upgraded to r151024, but after the upgraded the new boot environment is not active. When I run beadmin activate, I get "Activation Successful", but after the reboot, it is not active. When I run reboot -f -e then it does activate and boot, but when I reboot normally, it is no longer active, even though it is marked R in beadm list. Any advice would be greatly appreciated. thanks in advance! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Keepalived in an LX branded zone
One of the possible alternatives would be to install zones with
system/network/routing/vrrp, but then I still have the challenge that
haproxy is not in https://pkg.omniosce.org/r151022/core/
Kind regards/met vriendelijke groet,
Serge Fonville
http://www.sergefonville.nl
2017-12-03 19:05 GMT+01:00 Serge Fonville :
> Hi,
>
> I am currently trying to setup keepalived in an LX branded zone.
>
> Since I get a lot of errors that might be related to the fact it is an LX
> branded zone, I was wondering if someone would be so kind to shed their
> light on it.
>
> Especially since I never setup keepalived before, I am unsure if these
> errors are caused by the fact it is an LX branded zone, of just
> misconfiguration of keepalived.
>
> # Inside the zone
> keepalived.conf
>
>> global_defs {router_id haproxy01
>> vrrp_version 3
>> }
>>
>> vrrp_script check_haproxy {
>> script "/etc/keepalived/check_haproxy.sh"
>> interval 0.05
>> fall 2
>> rise 2
>> }
>>
>> vrrp_instance haproxy_instance {
>> state MASTER
>> interface haproxy01vnic0
>> virtual_router_id 25
>> priority 150
>> advert_int 0.05
>> virtual_ipaddress {
>> 192.168.1.25/2 label haproxy01vnic0:0
>> }
>> track_script {
>> check_haproxy
>> }
>> }
>>
>>
> keepalived -f /etc/keepalived/keepalived.conf -l -n
>
>> Starting Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2
>> Unable to resolve default script username 'keepalived_script' - ignoring
>> Opening file '/etc/keepalived/keepalived.conf'.
>> Starting Healthcheck child process, pid=13481
>> Initializing ipvs
>> Starting VRRP child process, pid=13482
>> Registering Kernel netlink reflector
>> Registering Kernel netlink command channel
>> Error while registering gratuitous ARP shared channel
>> Opening file '/etc/keepalived/keepalived.conf'.
>> IPVS: Can't initialize ipvs: No such file or directory
>> Keepalived_vrrp exited due to segmentation fault (SIGSEGV).
>> Please report a bug at https://github.com/acassen/keepalived/issues
>> and include this log from when keepalived started, what happened
>> immediately before the crash, and your configuration file.
>>
>
> /etc/keepalived/check_haproxy.sh
>
>> #!/bin/bash
>> kill -0 $(cat /run/haproxy.pid) && echo 'OK' && exit 0 || echo 'NOK' && exit
>> 1
>>
>>
> # Inside the global zone
> cat /etc/zones/haproxy01.xml
>
>>
>>
>> > "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
>> > autoboot="true" brand="lx" ip-type="exclusive" debugid="20">
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
> uname -v
> omnios-r151022-f9693432c2
>
> Any feedback or input is greatly appreciated!
>
> Kind regards/met vriendelijke groet,
>
> Serge Fonville
>
> http://www.sergefonville.nl
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Keepalived in an LX branded zone
Hi,
I am currently trying to setup keepalived in an LX branded zone.
Since I get a lot of errors that might be related to the fact it is an LX
branded zone, I was wondering if someone would be so kind to shed their
light on it.
Especially since I never setup keepalived before, I am unsure if these
errors are caused by the fact it is an LX branded zone, of just
misconfiguration of keepalived.
# Inside the zone
keepalived.conf
> global_defs {router_id haproxy01
> vrrp_version 3
> }
>
> vrrp_script check_haproxy {
> script "/etc/keepalived/check_haproxy.sh"
> interval 0.05
> fall 2
> rise 2
> }
>
> vrrp_instance haproxy_instance {
> state MASTER
> interface haproxy01vnic0
> virtual_router_id 25
> priority 150
> advert_int 0.05
> virtual_ipaddress {
> 192.168.1.25/2 label haproxy01vnic0:0
> }
> track_script {
> check_haproxy
> }
> }
>
>
keepalived -f /etc/keepalived/keepalived.conf -l -n
> Starting Keepalived v1.3.5 (03/19,2017), git commit v1.3.5-6-g6fa32f2
> Unable to resolve default script username 'keepalived_script' - ignoring
> Opening file '/etc/keepalived/keepalived.conf'.
> Starting Healthcheck child process, pid=13481
> Initializing ipvs
> Starting VRRP child process, pid=13482
> Registering Kernel netlink reflector
> Registering Kernel netlink command channel
> Error while registering gratuitous ARP shared channel
> Opening file '/etc/keepalived/keepalived.conf'.
> IPVS: Can't initialize ipvs: No such file or directory
> Keepalived_vrrp exited due to segmentation fault (SIGSEGV).
> Please report a bug at https://github.com/acassen/keepalived/issues
> and include this log from when keepalived started, what happened
> immediately before the crash, and your configuration file.
>
/etc/keepalived/check_haproxy.sh
> #!/bin/bash
> kill -0 $(cat /run/haproxy.pid) && echo 'OK' && exit 0 || echo 'NOK' && exit 1
>
>
# Inside the global zone
cat /etc/zones/haproxy01.xml
>
>
> "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
> brand="lx" ip-type="exclusive" debugid="20">
>
>
>
>
>
>
>
>
>
>
>
>
>
uname -v
omnios-r151022-f9693432c2
Any feedback or input is greatly appreciated!
Kind regards/met vriendelijke groet,
Serge Fonville
http://www.sergefonville.nl
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
There are 4 packages that are installed from a different publisher: FMRI: pkg://ms.omniti.com/omniti/library/apr@1.5.2-0.151014: 20170607T153003Z FMRI: pkg://ms.omniti.com/omniti/library/apr-util@1.5.4-0. 151014:20170607T153107Z FMRI: pkg://ms.omniti.com/omniti/library/uuid@1.41.14-0.151016: 20160504T142422Z FMRI: pkg://ms.omniti.com/omniti/server/nginx@1.11.13-0.151014: 20170412T171318Z If I replace these, does that fix anything? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 14:23 GMT+01:00 Serge Fonville : > I tried the suggestion of adding the publisher to the zone, and attaching > it again, but unfortunately to no avail. > I got the following error: > [Tue Nov 21 14:20:44 CET 2017] Log File: /var/tmp/web01.attach_log.j6aOsf > [Tue Nov 21 14:20:48 CET 2017]Attach Path: > /export/zones/web01/root > [Tue Nov 21 14:20:48 CET 2017] Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-19 > > [Tue Nov 21 14:20:48 CET 2017] existing > [Tue Nov 21 14:20:48 CET 2017] Installing: Using > pre-existing data in zonepath > [Tue Nov 21 14:20:48 CET 2017] Sanity Check: Passed. Looks like an > OpenSolaris system. > [Tue Nov 21 14:20:53 CET 2017] Cache: Using > /var/pkg/publisher. > [Tue Nov 21 14:20:53 CET 2017] Updating non-global zone: Output follows > > pkg install: No matching version of consolidation/osnet/osnet-incorporation > can be installed: > No matching version of incorporation/jeos/omnios-userland can be > installed: > [Tue Nov 21 14:20:58 CET 2017] ERROR: Could not update attaching zone > [Tue Nov 21 14:20:59 CET 2017] Result: Attach Failed. > > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 13:36 GMT+01:00 Serge Fonville : > >> New error: >> No matching version of consolidation/osnet/osnet-incorporation can be >> installed: >> This one seems to be close to the solution >> >> How do I progress from here? >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 12:57 GMT+01:00 Serge Fonville : >> >>> Currently I am no longer able to mount the dataset. >>> When I execute the following command, I get the followign error: >>> >>>> zoneadm -z web01 attach >>>> >>> Output: >>> ERROR: Failed to locate any dataset mounted at >>> /export/zones/web01/root. Attach requires a mounted dataset. >>> Result: Attach Failed. >>> Log: >>> [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaG >>> SG >>> [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset >>> mounted at /export/zones/web01/root. Attach requires a mounted dataset. >>> [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. >>> >>> Perhaps I broke something else in the process :-( >>> >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 7:54 GMT+01:00 Serge Fonville : >>> >>>> After having updated the canmount property to noauto of the filesystem, >>>> the system now boots again. >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-21 7:08 GMT+01:00 Serge Fonville : >>>> >>>>> After having rebooted the server, I am now no longer able to logon to >>>>> the server, the console shows messages it cannot mount the filesystem. >>>>> because its directory is not empty, since the zone is in >>>>> configured/detached state, how do I tell the system not to try to mount >>>>> it? >>>>> >>>>> Kind regards/met vriendelijke groet, >>>>> >>>>> Serge Fonville >>>>> >>>>> http://www.sergefonville.nl >>>>> >>>>> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >>>>> >>>>>> Also, since I had to remove it when I upgraded, I was under the >>>>>> impression it was gone everywhere, since pkg publisher does not show it >>>>>> on >>>>>> any other zone (including the GZ). >>>>>> >>>>>> Kind regards/met vriend
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
I tried the suggestion of adding the publisher to the zone, and attaching it again, but unfortunately to no avail. I got the following error: [Tue Nov 21 14:20:44 CET 2017] Log File: /var/tmp/web01.attach_log.j6aOsf [Tue Nov 21 14:20:48 CET 2017]Attach Path: /export/zones/web01/root [Tue Nov 21 14:20:48 CET 2017] Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-19 [Tue Nov 21 14:20:48 CET 2017] existing [Tue Nov 21 14:20:48 CET 2017] Installing: Using pre-existing data in zonepath [Tue Nov 21 14:20:48 CET 2017] Sanity Check: Passed. Looks like an OpenSolaris system. [Tue Nov 21 14:20:53 CET 2017] Cache: Using /var/pkg/publisher. [Tue Nov 21 14:20:53 CET 2017] Updating non-global zone: Output follows pkg install: No matching version of consolidation/osnet/osnet-incorporation can be installed: No matching version of incorporation/jeos/omnios-userland can be installed: [Tue Nov 21 14:20:58 CET 2017] ERROR: Could not update attaching zone [Tue Nov 21 14:20:59 CET 2017] Result: Attach Failed. Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 13:36 GMT+01:00 Serge Fonville : > New error: > No matching version of consolidation/osnet/osnet-incorporation can be > installed: > This one seems to be close to the solution > > How do I progress from here? > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 12:57 GMT+01:00 Serge Fonville : > >> Currently I am no longer able to mount the dataset. >> When I execute the following command, I get the followign error: >> >>> zoneadm -z web01 attach >>> >> Output: >> ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. >> Attach requires a mounted dataset. >> Result: Attach Failed. >> Log: >> [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG >> [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset >> mounted at /export/zones/web01/root. Attach requires a mounted dataset. >> [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. >> >> Perhaps I broke something else in the process :-( >> >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 7:54 GMT+01:00 Serge Fonville : >> >>> After having updated the canmount property to noauto of the filesystem, >>> the system now boots again. >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 7:08 GMT+01:00 Serge Fonville : >>> >>>> After having rebooted the server, I am now no longer able to logon to >>>> the server, the console shows messages it cannot mount the filesystem. >>>> because its directory is not empty, since the zone is in >>>> configured/detached state, how do I tell the system not to try to mount it? >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >>>> >>>>> Also, since I had to remove it when I upgraded, I was under the >>>>> impression it was gone everywhere, since pkg publisher does not show it on >>>>> any other zone (including the GZ). >>>>> >>>>> Kind regards/met vriendelijke groet, >>>>> >>>>> Serge Fonville >>>>> >>>>> http://www.sergefonville.nl >>>>> >>>>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>>>> >>>>>> So how do I see it in the GZ, because pkg publisher does not output >>>>>> it when I execute it on the GZ? >>>>>> >>>>>> Kind regards/met vriendelijke groet, >>>>>> >>>>>> Serge Fonville >>>>>> >>>>>> http://www.sergefonville.nl >>>>>> >>>>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>>>> >>>>>>> > Child image publisher configuration must be a superset of the >>>>>>> parent >>>>>>> image publisher configuration. >>>>>>> >>>>>>> your NGZ is lacking the ms.omniti.com publisher which you have set >>>>>>> for >
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
New error: No matching version of consolidation/osnet/osnet-incorporation can be installed: This one seems to be close to the solution How do I progress from here? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 12:57 GMT+01:00 Serge Fonville : > Currently I am no longer able to mount the dataset. > When I execute the following command, I get the followign error: > >> zoneadm -z web01 attach >> > Output: > ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. > Attach requires a mounted dataset. > Result: Attach Failed. > Log: > [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG > [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset mounted > at /export/zones/web01/root. Attach requires a mounted dataset. > [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. > > Perhaps I broke something else in the process :-( > > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 7:54 GMT+01:00 Serge Fonville : > >> After having updated the canmount property to noauto of the filesystem, >> the system now boots again. >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 7:08 GMT+01:00 Serge Fonville : >> >>> After having rebooted the server, I am now no longer able to logon to >>> the server, the console shows messages it cannot mount the filesystem. >>> because its directory is not empty, since the zone is in >>> configured/detached state, how do I tell the system not to try to mount it? >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >>> >>>> Also, since I had to remove it when I upgraded, I was under the >>>> impression it was gone everywhere, since pkg publisher does not show it on >>>> any other zone (including the GZ). >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>>> >>>>> So how do I see it in the GZ, because pkg publisher does not output it >>>>> when I execute it on the GZ? >>>>> >>>>> Kind regards/met vriendelijke groet, >>>>> >>>>> Serge Fonville >>>>> >>>>> http://www.sergefonville.nl >>>>> >>>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>>> >>>>>> > Child image publisher configuration must be a superset of the parent >>>>>> image publisher configuration. >>>>>> >>>>>> your NGZ is lacking the ms.omniti.com publisher which you have set >>>>>> for >>>>>> the GZ. >>>>>> >>>>>> after doing a: >>>>>> # pkg -R /export/zones/web01/root set-publisher -g >>>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>>>> >>>>>> attaching the zone should work. >>>>>> >>>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>>>> > Hi, >>>>>> > >>>>>> > When I tried to attach a zone I got the following errors: >>>>>> > >>>>>> > zoneadm -z web01 attach >>>>>> > >>>>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>>>> >Attach Path: /export/zones/web01/root >>>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>>> > >>>>>> > Installing: Using pre-existing data in zonepath >>>>>> > Cache: Using /var/pkg/publisher. >>>>>> > Updating non-global zone: Output follows >>>>>> > >>>>>> > Evaluation: Packages in zone web01 are out of sync >>>>>> with >>>>>> > the global zone. To proceed, retry with the -u flag. >>>>>> > Result: Attach Failed. >>>>>> > With the log file containing: >>>>>> > [Mon Nov 20 18:02:
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
Currently I am no longer able to mount the dataset. When I execute the following command, I get the followign error: > zoneadm -z web01 attach > Output: ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. Attach requires a mounted dataset. Result: Attach Failed. Log: [Tue Nov 21 12:54:41 CET 2017] Log File: /var/tmp/web01.attach_log.8DaGSG [Tue Nov 21 12:54:42 CET 2017] ERROR: Failed to locate any dataset mounted at /export/zones/web01/root. Attach requires a mounted dataset. [Tue Nov 21 12:54:42 CET 2017] Result: Attach Failed. Perhaps I broke something else in the process :-( Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 7:54 GMT+01:00 Serge Fonville : > After having updated the canmount property to noauto of the filesystem, > the system now boots again. > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 7:08 GMT+01:00 Serge Fonville : > >> After having rebooted the server, I am now no longer able to logon to the >> server, the console shows messages it cannot mount the filesystem. because >> its directory is not empty, since the zone is in configured/detached state, >> how do I tell the system not to try to mount it? >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 6:11 GMT+01:00 Serge Fonville : >> >>> Also, since I had to remove it when I upgraded, I was under the >>> impression it was gone everywhere, since pkg publisher does not show it on >>> any other zone (including the GZ). >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >>> >>>> So how do I see it in the GZ, because pkg publisher does not output it >>>> when I execute it on the GZ? >>>> >>>> Kind regards/met vriendelijke groet, >>>> >>>> Serge Fonville >>>> >>>> http://www.sergefonville.nl >>>> >>>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>>> >>>>> > Child image publisher configuration must be a superset of the parent >>>>> image publisher configuration. >>>>> >>>>> your NGZ is lacking the ms.omniti.com publisher which you have set for >>>>> the GZ. >>>>> >>>>> after doing a: >>>>> # pkg -R /export/zones/web01/root set-publisher -g >>>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>>> >>>>> attaching the zone should work. >>>>> >>>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>>> > Hi, >>>>> > >>>>> > When I tried to attach a zone I got the following errors: >>>>> > >>>>> > zoneadm -z web01 attach >>>>> > >>>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>>> >Attach Path: /export/zones/web01/root >>>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>>> > >>>>> > Installing: Using pre-existing data in zonepath >>>>> > Cache: Using /var/pkg/publisher. >>>>> > Updating non-global zone: Output follows >>>>> > >>>>> > Evaluation: Packages in zone web01 are out of sync >>>>> with >>>>> > the global zone. To proceed, retry with the -u flag. >>>>> > Result: Attach Failed. >>>>> > With the log file containing: >>>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>>> /var/tmp/web01.attach_log.olaaFy >>>>> > [Mon Nov 20 18:02:32 CET 2017]Attach Path: >>>>> > /export/zones/web01/root >>>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>>> > >>>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>>> > pre-existing data in zonepath >>>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >>>>> > OpenSolaris system. >>>>>
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
After having updated the canmount property to noauto of the filesystem, the system now boots again. Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 7:08 GMT+01:00 Serge Fonville : > After having rebooted the server, I am now no longer able to logon to the > server, the console shows messages it cannot mount the filesystem. because > its directory is not empty, since the zone is in configured/detached state, > how do I tell the system not to try to mount it? > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 6:11 GMT+01:00 Serge Fonville : > >> Also, since I had to remove it when I upgraded, I was under the >> impression it was gone everywhere, since pkg publisher does not show it on >> any other zone (including the GZ). >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-21 6:10 GMT+01:00 Serge Fonville : >> >>> So how do I see it in the GZ, because pkg publisher does not output it >>> when I execute it on the GZ? >>> >>> Kind regards/met vriendelijke groet, >>> >>> Serge Fonville >>> >>> http://www.sergefonville.nl >>> >>> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >>> >>>> > Child image publisher configuration must be a superset of the parent >>>> image publisher configuration. >>>> >>>> your NGZ is lacking the ms.omniti.com publisher which you have set for >>>> the GZ. >>>> >>>> after doing a: >>>> # pkg -R /export/zones/web01/root set-publisher -g >>>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>>> >>>> attaching the zone should work. >>>> >>>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>>> > Hi, >>>> > >>>> > When I tried to attach a zone I got the following errors: >>>> > >>>> > zoneadm -z web01 attach >>>> > >>>> > Log File: /var/tmp/web01.attach_log.olaaFy >>>> >Attach Path: /export/zones/web01/root >>>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>>> > >>>> > Installing: Using pre-existing data in zonepath >>>> > Cache: Using /var/pkg/publisher. >>>> > Updating non-global zone: Output follows >>>> > >>>> > Evaluation: Packages in zone web01 are out of sync >>>> with >>>> > the global zone. To proceed, retry with the -u flag. >>>> > Result: Attach Failed. >>>> > With the log file containing: >>>> > [Mon Nov 20 18:02:28 CET 2017] Log File: >>>> /var/tmp/web01.attach_log.olaaFy >>>> > [Mon Nov 20 18:02:32 CET 2017]Attach Path: >>>> > /export/zones/web01/root >>>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>>> > rpool/export/zones/web01/ROOT/zbe-9 >>>> > >>>> > [Mon Nov 20 18:02:32 CET 2017] existing >>>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>>> > pre-existing data in zonepath >>>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >>>> > OpenSolaris system. >>>> > pkg: Search performance is degraded. >>>> > Run 'pkg rebuild-index' to improve search speed. >>>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>>> > /var/pkg/publisher. >>>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>>> follows >>>> > >>>> > >>>> > pkg install: Invalid child image publisher configuration. Child image >>>> > publisher >>>> > configuration must be a superset of the parent image publisher >>>> > configuration. >>>> > Please update the child publisher configuration to match the parent. >>>> If the >>>> > child image is a zone this can be done automatically by detaching and >>>> > attaching the zone. >>>> > >>>> > The parent image has the following enabled publishers: >>>> > PUBLISHER 0: omnios >>>> > PUBLISHER 1: ms.omniti.com <http://ms.omniti.com> >>>> > >>
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
After having rebooted the server, I am now no longer able to logon to the server, the console shows messages it cannot mount the filesystem. because its directory is not empty, since the zone is in configured/detached state, how do I tell the system not to try to mount it? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 6:11 GMT+01:00 Serge Fonville : > Also, since I had to remove it when I upgraded, I was under the impression > it was gone everywhere, since pkg publisher does not show it on any other > zone (including the GZ). > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-21 6:10 GMT+01:00 Serge Fonville : > >> So how do I see it in the GZ, because pkg publisher does not output it >> when I execute it on the GZ? >> >> Kind regards/met vriendelijke groet, >> >> Serge Fonville >> >> http://www.sergefonville.nl >> >> 2017-11-20 19:02 GMT+01:00 Dominik Hassler : >> >>> > Child image publisher configuration must be a superset of the parent >>> image publisher configuration. >>> >>> your NGZ is lacking the ms.omniti.com publisher which you have set for >>> the GZ. >>> >>> after doing a: >>> # pkg -R /export/zones/web01/root set-publisher -g >>> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >>> >>> attaching the zone should work. >>> >>> On 11/20/2017 06:26 PM, Serge Fonville wrote: >>> > Hi, >>> > >>> > When I tried to attach a zone I got the following errors: >>> > >>> > zoneadm -z web01 attach >>> > >>> > Log File: /var/tmp/web01.attach_log.olaaFy >>> >Attach Path: /export/zones/web01/root >>> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >>> > >>> > Installing: Using pre-existing data in zonepath >>> > Cache: Using /var/pkg/publisher. >>> > Updating non-global zone: Output follows >>> > >>> > Evaluation: Packages in zone web01 are out of sync with >>> > the global zone. To proceed, retry with the -u flag. >>> > Result: Attach Failed. >>> > With the log file containing: >>> > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaa >>> Fy >>> > [Mon Nov 20 18:02:32 CET 2017]Attach Path: >>> > /export/zones/web01/root >>> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >>> > rpool/export/zones/web01/ROOT/zbe-9 >>> > >>> > [Mon Nov 20 18:02:32 CET 2017] existing >>> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >>> > pre-existing data in zonepath >>> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >>> > OpenSolaris system. >>> > pkg: Search performance is degraded. >>> > Run 'pkg rebuild-index' to improve search speed. >>> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >>> > /var/pkg/publisher. >>> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >>> follows >>> > >>> > >>> > pkg install: Invalid child image publisher configuration. Child image >>> > publisher >>> > configuration must be a superset of the parent image publisher >>> > configuration. >>> > Please update the child publisher configuration to match the parent. >>> If the >>> > child image is a zone this can be done automatically by detaching and >>> > attaching the zone. >>> > >>> > The parent image has the following enabled publishers: >>> > PUBLISHER 0: omnios >>> > PUBLISHER 1: ms.omniti.com <http://ms.omniti.com> >>> > >>> > The child image has the following enabled publishers: >>> > PUBLISHER 0: omnios >>> > [Mon Nov 20 18:02:42 CET 2017] >>> > Evaluation: Packages in zone web01 are out of sync with >>> > the global zone. To proceed, retry with the -u flag. >>> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >>> Failed. >>> > >>> > So I try to run it with -u >>> > >>> > zoneadm -z web01 attach -u >>> > >>> > Log File: /var/tmp/web01.attach_log.TNaqaR >>> >
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
Also, since I had to remove it when I upgraded, I was under the impression it was gone everywhere, since pkg publisher does not show it on any other zone (including the GZ). Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-21 6:10 GMT+01:00 Serge Fonville : > So how do I see it in the GZ, because pkg publisher does not output it > when I execute it on the GZ? > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > > 2017-11-20 19:02 GMT+01:00 Dominik Hassler : > >> > Child image publisher configuration must be a superset of the parent >> image publisher configuration. >> >> your NGZ is lacking the ms.omniti.com publisher which you have set for >> the GZ. >> >> after doing a: >> # pkg -R /export/zones/web01/root set-publisher -g >> http://pkg.omniti.com/omniti-ms/ ms.omniti.com >> >> attaching the zone should work. >> >> On 11/20/2017 06:26 PM, Serge Fonville wrote: >> > Hi, >> > >> > When I tried to attach a zone I got the following errors: >> > >> > zoneadm -z web01 attach >> > >> > Log File: /var/tmp/web01.attach_log.olaaFy >> >Attach Path: /export/zones/web01/root >> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >> > >> > Installing: Using pre-existing data in zonepath >> > Cache: Using /var/pkg/publisher. >> > Updating non-global zone: Output follows >> > >> > Evaluation: Packages in zone web01 are out of sync with >> > the global zone. To proceed, retry with the -u flag. >> > Result: Attach Failed. >> > With the log file containing: >> > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaa >> Fy >> > [Mon Nov 20 18:02:32 CET 2017]Attach Path: >> > /export/zones/web01/root >> > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: >> > rpool/export/zones/web01/ROOT/zbe-9 >> > >> > [Mon Nov 20 18:02:32 CET 2017] existing >> > [Mon Nov 20 18:02:32 CET 2017] Installing: Using >> > pre-existing data in zonepath >> > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an >> > OpenSolaris system. >> > pkg: Search performance is degraded. >> > Run 'pkg rebuild-index' to improve search speed. >> > [Mon Nov 20 18:02:39 CET 2017] Cache: Using >> > /var/pkg/publisher. >> > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output >> follows >> > >> > >> > pkg install: Invalid child image publisher configuration. Child image >> > publisher >> > configuration must be a superset of the parent image publisher >> > configuration. >> > Please update the child publisher configuration to match the parent. >> If the >> > child image is a zone this can be done automatically by detaching and >> > attaching the zone. >> > >> > The parent image has the following enabled publishers: >> > PUBLISHER 0: omnios >> > PUBLISHER 1: ms.omniti.com <http://ms.omniti.com> >> > >> > The child image has the following enabled publishers: >> > PUBLISHER 0: omnios >> > [Mon Nov 20 18:02:42 CET 2017] >> > Evaluation: Packages in zone web01 are out of sync with >> > the global zone. To proceed, retry with the -u flag. >> > [Mon Nov 20 18:02:44 CET 2017] Result: Attach >> Failed. >> > >> > So I try to run it with -u >> > >> > zoneadm -z web01 attach -u >> > >> > Log File: /var/tmp/web01.attach_log.TNaqaR >> >Attach Path: /export/zones/web01/root >> > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 >> > >> > Installing: Using pre-existing data in zonepath >> > Cache: Using /var/pkg/publisher. >> > Updating non-global zone: Output follows >> > ERROR: Could not update attaching zone >> > Result: Attach Failed. >> > >> > With the log file containing: >> > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaq >> aR >> > [Mon Nov 20 18:20:27 CET 2017]Attach Path: >> > /export/zones/web01/root >> > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: >> >
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
So how do I see it in the GZ, because pkg publisher does not output it when I execute it on the GZ? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-20 19:02 GMT+01:00 Dominik Hassler : > > Child image publisher configuration must be a superset of the parent > image publisher configuration. > > your NGZ is lacking the ms.omniti.com publisher which you have set for > the GZ. > > after doing a: > # pkg -R /export/zones/web01/root set-publisher -g > http://pkg.omniti.com/omniti-ms/ ms.omniti.com > > attaching the zone should work. > > On 11/20/2017 06:26 PM, Serge Fonville wrote: > > Hi, > > > > When I tried to attach a zone I got the following errors: > > > > zoneadm -z web01 attach > > > > Log File: /var/tmp/web01.attach_log.olaaFy > >Attach Path: /export/zones/web01/root > > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > > > Installing: Using pre-existing data in zonepath > > Cache: Using /var/pkg/publisher. > > Updating non-global zone: Output follows > > > > Evaluation: Packages in zone web01 are out of sync with > > the global zone. To proceed, retry with the -u flag. > > Result: Attach Failed. > > With the log file containing: > > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log. > olaaFy > > [Mon Nov 20 18:02:32 CET 2017]Attach Path: > > /export/zones/web01/root > > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: > > rpool/export/zones/web01/ROOT/zbe-9 > > > > [Mon Nov 20 18:02:32 CET 2017] existing > > [Mon Nov 20 18:02:32 CET 2017] Installing: Using > > pre-existing data in zonepath > > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an > > OpenSolaris system. > > pkg: Search performance is degraded. > > Run 'pkg rebuild-index' to improve search speed. > > [Mon Nov 20 18:02:39 CET 2017] Cache: Using > > /var/pkg/publisher. > > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output follows > > > > > > pkg install: Invalid child image publisher configuration. Child image > > publisher > > configuration must be a superset of the parent image publisher > > configuration. > > Please update the child publisher configuration to match the parent. If > the > > child image is a zone this can be done automatically by detaching and > > attaching the zone. > > > > The parent image has the following enabled publishers: > > PUBLISHER 0: omnios > > PUBLISHER 1: ms.omniti.com <http://ms.omniti.com> > > > > The child image has the following enabled publishers: > > PUBLISHER 0: omnios > > [Mon Nov 20 18:02:42 CET 2017] > > Evaluation: Packages in zone web01 are out of sync with > > the global zone. To proceed, retry with the -u flag. > > [Mon Nov 20 18:02:44 CET 2017] Result: Attach Failed. > > > > So I try to run it with -u > > > > zoneadm -z web01 attach -u > > > > Log File: /var/tmp/web01.attach_log.TNaqaR > >Attach Path: /export/zones/web01/root > > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > > > Installing: Using pre-existing data in zonepath > > Cache: Using /var/pkg/publisher. > > Updating non-global zone: Output follows > > ERROR: Could not update attaching zone > > Result: Attach Failed. > > > > With the log file containing: > > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log. > TNaqaR > > [Mon Nov 20 18:20:27 CET 2017]Attach Path: > > /export/zones/web01/root > > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: > > rpool/export/zones/web01/ROOT/zbe-9 > > > > [Mon Nov 20 18:20:27 CET 2017] existing > > [Mon Nov 20 18:20:27 CET 2017] Installing: Using > > pre-existing data in zonepath > > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an > > OpenSolaris system. > > [Mon Nov 20 18:20:31 CET 2017] Cache: Using > > /var/pkg/publisher. > > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output follows > > > > > > pkg install: Invalid child image publisher configuration. Child image > > publisher > > configuration must be a superset of the parent image publisher > > configuration. >
Re: [OmniOS-discuss] ERROR: Could not update attaching zone
So, that means you know how to solve it :D!! Awesome, your input is greatly appreciated!!! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-11-20 18:39 GMT+01:00 Linda Kateley : > I had that recently... just made sure I patched both sides identically > before moving > > On 11/20/17 11:26 AM, Serge Fonville wrote: > > Hi, > > When I tried to attach a zone I got the following errors: > >> zoneadm -z web01 attach >> > Log File: /var/tmp/web01.attach_log.olaaFy >Attach Path: /export/zones/web01/root > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > Installing: Using pre-existing data in zonepath > Cache: Using /var/pkg/publisher. > Updating non-global zone: Output follows > > Evaluation: Packages in zone web01 are out of sync with > the global zone. To proceed, retry with the -u flag. > Result: Attach Failed. > With the log file containing: > [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaaFy > [Mon Nov 20 18:02:32 CET 2017]Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:02:32 CET 2017] existing > [Mon Nov 20 18:02:32 CET 2017] Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an > OpenSolaris system. > pkg: Search performance is degraded. > Run 'pkg rebuild-index' to improve search speed. > [Mon Nov 20 18:02:39 CET 2017] Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration. Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent. If > the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > PUBLISHER 0: omnios > PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > PUBLISHER 0: omnios > [Mon Nov 20 18:02:42 CET 2017] > Evaluation: Packages in zone web01 are out of sync with > the global zone. To proceed, retry with the -u flag. > [Mon Nov 20 18:02:44 CET 2017] Result: Attach Failed. > > So I try to run it with -u > >> zoneadm -z web01 attach -u >> > Log File: /var/tmp/web01.attach_log.TNaqaR >Attach Path: /export/zones/web01/root > Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 > > Installing: Using pre-existing data in zonepath > Cache: Using /var/pkg/publisher. > Updating non-global zone: Output follows > ERROR: Could not update attaching zone > Result: Attach Failed. > > With the log file containing: > [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaqaR > [Mon Nov 20 18:20:27 CET 2017]Attach Path: > /export/zones/web01/root > [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: > rpool/export/zones/web01/ROOT/zbe-9 > > [Mon Nov 20 18:20:27 CET 2017] existing > [Mon Nov 20 18:20:27 CET 2017] Installing: Using > pre-existing data in zonepath > [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an > OpenSolaris system. > [Mon Nov 20 18:20:31 CET 2017] Cache: Using > /var/pkg/publisher. > [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output follows > > > pkg install: Invalid child image publisher configuration. Child image > publisher > configuration must be a superset of the parent image publisher > configuration. > Please update the child publisher configuration to match the parent. If > the > child image is a zone this can be done automatically by detaching and > attaching the zone. > > The parent image has the following enabled publishers: > PUBLISHER 0: omnios > PUBLISHER 1: ms.omniti.com > > The child image has the following enabled publishers: > PUBLISHER 0: omnios > [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone > [Mon Nov 20 18:20:36 CET 2017] Result: Attach Failed. > > On global zone: > >> pkg publisher >> > PUBLISHER TYPE STATUS P LOCATION > omnios origin online F https:/
[OmniOS-discuss] ERROR: Could not update attaching zone
Hi, When I tried to attach a zone I got the following errors: > zoneadm -z web01 attach > Log File: /var/tmp/web01.attach_log.olaaFy Attach Path: /export/zones/web01/root Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 Installing: Using pre-existing data in zonepath Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows Evaluation: Packages in zone web01 are out of sync with the global zone. To proceed, retry with the -u flag. Result: Attach Failed. With the log file containing: [Mon Nov 20 18:02:28 CET 2017] Log File: /var/tmp/web01.attach_log.olaaFy [Mon Nov 20 18:02:32 CET 2017]Attach Path: /export/zones/web01/root [Mon Nov 20 18:02:32 CET 2017] Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 [Mon Nov 20 18:02:32 CET 2017] existing [Mon Nov 20 18:02:32 CET 2017] Installing: Using pre-existing data in zonepath [Mon Nov 20 18:02:32 CET 2017] Sanity Check: Passed. Looks like an OpenSolaris system. pkg: Search performance is degraded. Run 'pkg rebuild-index' to improve search speed. [Mon Nov 20 18:02:39 CET 2017] Cache: Using /var/pkg/publisher. [Mon Nov 20 18:02:39 CET 2017] Updating non-global zone: Output follows pkg install: Invalid child image publisher configuration. Child image publisher configuration must be a superset of the parent image publisher configuration. Please update the child publisher configuration to match the parent. If the child image is a zone this can be done automatically by detaching and attaching the zone. The parent image has the following enabled publishers: PUBLISHER 0: omnios PUBLISHER 1: ms.omniti.com The child image has the following enabled publishers: PUBLISHER 0: omnios [Mon Nov 20 18:02:42 CET 2017] Evaluation: Packages in zone web01 are out of sync with the global zone. To proceed, retry with the -u flag. [Mon Nov 20 18:02:44 CET 2017] Result: Attach Failed. So I try to run it with -u > zoneadm -z web01 attach -u > Log File: /var/tmp/web01.attach_log.TNaqaR Attach Path: /export/zones/web01/root Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 Installing: Using pre-existing data in zonepath Cache: Using /var/pkg/publisher. Updating non-global zone: Output follows ERROR: Could not update attaching zone Result: Attach Failed. With the log file containing: [Mon Nov 20 18:20:23 CET 2017] Log File: /var/tmp/web01.attach_log.TNaqaR [Mon Nov 20 18:20:27 CET 2017]Attach Path: /export/zones/web01/root [Mon Nov 20 18:20:27 CET 2017] Attach ZFS Dataset: rpool/export/zones/web01/ROOT/zbe-9 [Mon Nov 20 18:20:27 CET 2017] existing [Mon Nov 20 18:20:27 CET 2017] Installing: Using pre-existing data in zonepath [Mon Nov 20 18:20:27 CET 2017] Sanity Check: Passed. Looks like an OpenSolaris system. [Mon Nov 20 18:20:31 CET 2017] Cache: Using /var/pkg/publisher. [Mon Nov 20 18:20:31 CET 2017] Updating non-global zone: Output follows pkg install: Invalid child image publisher configuration. Child image publisher configuration must be a superset of the parent image publisher configuration. Please update the child publisher configuration to match the parent. If the child image is a zone this can be done automatically by detaching and attaching the zone. The parent image has the following enabled publishers: PUBLISHER 0: omnios PUBLISHER 1: ms.omniti.com The child image has the following enabled publishers: PUBLISHER 0: omnios [Mon Nov 20 18:20:35 CET 2017] ERROR: Could not update attaching zone [Mon Nov 20 18:20:36 CET 2017] Result: Attach Failed. On global zone: > pkg publisher > PUBLISHER TYPE STATUS P LOCATION omnios origin online F https://pkg.omniosce.org/r151022/core/ Any help in resolving this greatly appreciated!! Thanks in advance!! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] VNICs disappear after reboot
Hi, I have been a happy user of OmniOS for some time now, but one thing has been bothering me. Sometimes when I reboot the server, all VNICs seem to disappear . Usually when I reboot the server a couple of times, they are back. Do I need to do something for them to appear automatically after boot? When I run dladm show-vnic they are not there, but when I try to add them, I get the error the VNIC already exists. Any help is greatly appreciated. Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Global zone has a newer version: pkg://omnios/package/pkg@0.5.11, 5.11-0.151022:20170510T220631Z
Hi, The issue is fixed. I detached all zones and then attached all zones with -u. after running pkg update again, it finally updated all the zones. Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-07-12 23:05 GMT+02:00 Serge Fonville : > Hi, > > While trying to update omnios to the new version, I receive the error I > cannot upgrade since "Global zone has a newer version: > pkg://omnios/package/pkg" > > How do I fix this,. so I can update omnios to the newest version? > > Thanks a lot in advance! > > Kind regards/met vriendelijke groet, > > Serge Fonville > > http://www.sergefonville.nl > ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Global zone has a newer version: pkg://omnios/package/pkg@0.5.11, 5.11-0.151022:20170510T220631Z
Hi, While trying to update omnios to the new version, I receive the error I cannot upgrade since "Global zone has a newer version: pkg://omnios/package/pkg" How do I fix this,. so I can update omnios to the newest version? Thanks a lot in advance! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Install postfix on OmniOS
I successfully installed postfix :D!!! Thank you very much for the effort and support!!! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-02-14 23:50 GMT+01:00 Dan McDonald : > >> On Feb 14, 2017, at 1:39 PM, Dan McDonald wrote: >> When and if someone who maintains omniti-ms gets some cycles, that someone >> can rebuild the postfix package so that the dependency in question gets >> altered. >> >> As mentioned here and elsewhere before: omniti-ms is unsupported, and is >> basically just an internal repo with world-readability. Be patient, and >> when someone has cycles, someone will get to it. Someone has read this note >> I'm sure, so it's not just shouting into the void. > > Someone was nice and had some cycles: > > pkg://ms.omniti.com/omniti/network/smtp/postfix@2.10.10-0.151014:20170214T224634Z > pkg://ms.omniti.com/omniti/network/smtp/postfix@2.11.9-0.151014:20170214T224831Z > > Try now, > Dan > ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Install postfix on OmniOS
Hi Dan, Thanks for your explanation, what would be the best course of action to get this resolved? Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl 2017-02-14 18:44 GMT+01:00 Dan McDonald : > >> On Feb 14, 2017, at 12:19 PM, Serge Fonville >> wrote: >> >> Hello, >> >> Whey trying to install postfix on OmniOS 151018 I get an error stating >> that "This version is excluded by installed incorporation". >> >> On IRC I was informed that this is due to the type of dependency the >> postfix package has on entire. >> >> Thank you very much for any help in advance! > > To query such dependencies, use pkg(1): > > bloody(~)[0]% pkg contents -rm postfix | grep entire > depend fmri=pkg:/entire@11-0.151014 type=incorporate > bloody(~)[0]% > > That one will present problems. An updated package won't, e.g.: > > bloody(~)[0]% pkg contents -rm python-34 | grep entire > depend fmri=pkg:/entire@11-0.151014 type=optional > bloody(~)[0]% > > > Dan > ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Install postfix on OmniOS
Hello, Whey trying to install postfix on OmniOS 151018 I get an error stating that "This version is excluded by installed incorporation". On IRC I was informed that this is due to the type of dependency the postfix package has on entire. Thank you very much for any help in advance! Kind regards/met vriendelijke groet, Serge Fonville http://www.sergefonville.nl ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
