Re: [OmniOS-discuss] initialboot

[PÁSZTOR György]

Hi,

"Al Slater"  írta 2017-07-31 22:24-kor:
> I was thinking that if there was some way to "re-enable" initial-boot,
> then I could drop a /.initialboot script, re-enable initial-boot and
> then shutdown before creating new AMI, such that when an instance based
> upon the new AMI was launched, it would run .initialboot.
> 
> The problem is, enabling initial-boot immediately runs the .initialboot
> script and then disables itself.  So, I hoped there was a way to enable
> the service such that it did not immediately enable, but was enabled so
> it would start after the next reboot.

It's much cleaner now.

I saw sg. in svcadm's man, about marking a service temporarily... which is
in effect until the next reboot.
But, a much simpler solution what I tested:
I started my script with this:

trap 'rm /tmp/x' SIGINT
trap 'rm /tmp/x' SIGTERM

while [ -f /tmp/x ]; do
  sleep 5
done

And here follows your real script.


Before you'd enable again initial-boot, just touch /tmp/x

Maybe not the best workaround, but at least it works! ;)

Cheers,
Gyu
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] initialboot

[Al Slater]

Hi,

Sorry, I clearly didn't explain well enough.

Normally, initial-boot is enabled in the iso/kayak image that is
installed.  When it is started on the first boot it runs /.initialboot
and then disables itself.

I was thinking that if there was some way to "re-enable" initial-boot,
then I could drop a /.initialboot script, re-enable initial-boot and
then shutdown before creating new AMI, such that when an instance based
upon the new AMI was launched, it would run .initialboot.

The problem is, enabling initial-boot immediately runs the .initialboot
script and then disables itself.  So, I hoped there was a way to enable
the service such that it did not immediately enable, but was enabled so
it would start after the next reboot.

Al

On 31/07/17 21:49, PÁSZTOR György wrote:
> Hi,
> 
> I hope you don't mind, but I started a new thread with this, since it seems
> a completly new topic.
> 
> "Al Slater"  írta 2017-07-31 21:05-kor:
>> One more question though, is there any way to enable an SMF service for
>> the next reboot, but not immediately.  Specifically, I want to enable
>> the initial-boot service with a .initialboot file in place, then create
>> a new AMI.
> 
> I don't completely understand. You want to enable initialboot after the
> boot was complete, and only after a certain amount of time?
> I'm not sure, what this initialboot exactly does, but it seems not a simple
> service, it's a milestone. Maybe, I would not mess with it.
> Otherwise, if I need a delay between the service and the boot, and it's
> important to remain "disabled" while it's not enabled:
> Create an @reboot cronjob. I don't remember which cron implementation is
> the default. On linux's vixie's cron the time can be @reboot.
> 
>> I wist to use .initialboot to grab the instance configuration from
>> amazon (hostname, root keys etc) and configure appropriately when the
>> new instance starts.
> 
> Again: I don't completely understand your scenario.
> You created one ami, and you want to "close it back", and clone it several
> times, so after it's first reboot, it should do the initalboot steps?
> Why do you want to wait?
> What I just found about the /.initialboot, it's a simple shell script.
> If you need to wait here, why not just put a sleep command into the
> beginning of the script?
> Or if you have to wait for some specific resource: Why don't poll it once
> per every 5 sec or so?
> 
> Cheers,
> Gyu
> 



___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

On 31/07/17 21:30, Eric Sproul wrote:
> On Mon, Jul 31, 2017 at 4:05 PM, Al Slater  wrote:
>> One more question though, is there any way to enable an SMF service for
>> the next reboot, but not immediately.  Specifically, I want to enable
>> the initial-boot service with a .initialboot file in place, then create
>> a new AMI.
>>
>> I wist to use .initialboot to grab the instance configuration from
>> amazon (hostname, root keys etc) and configure appropriately when the
>> new instance starts.
> 
> Hi Al,
> The initial-boot service isn't really suitable for this sort of thing.
> You might want to check out
> pkg://omnios/system/management/ec2-credential which specifically
> handles setting up the credentials at first boot.  That could be
> trivially extended[1] to set the system hostname and probably any
> other "standard" thing that operators want.
> 
> Eric
> 
> [1] 
> https://github.com/omniosorg/omnios-build/blob/master/build/ec2-credential/files/install-ec2-credential

Thanks for the pointer Eric.

-- 
Al Slater

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] initialboot

[PÁSZTOR György]

Hi,

I hope you don't mind, but I started a new thread with this, since it seems
a completly new topic.

"Al Slater"  írta 2017-07-31 21:05-kor:
> One more question though, is there any way to enable an SMF service for
> the next reboot, but not immediately.  Specifically, I want to enable
> the initial-boot service with a .initialboot file in place, then create
> a new AMI.

I don't completely understand. You want to enable initialboot after the
boot was complete, and only after a certain amount of time?
I'm not sure, what this initialboot exactly does, but it seems not a simple
service, it's a milestone. Maybe, I would not mess with it.
Otherwise, if I need a delay between the service and the boot, and it's
important to remain "disabled" while it's not enabled:
Create an @reboot cronjob. I don't remember which cron implementation is
the default. On linux's vixie's cron the time can be @reboot.

> I wist to use .initialboot to grab the instance configuration from
> amazon (hostname, root keys etc) and configure appropriately when the
> new instance starts.

Again: I don't completely understand your scenario.
You created one ami, and you want to "close it back", and clone it several
times, so after it's first reboot, it should do the initalboot steps?
Why do you want to wait?
What I just found about the /.initialboot, it's a simple shell script.
If you need to wait here, why not just put a sleep command into the
beginning of the script?
Or if you have to wait for some specific resource: Why don't poll it once
per every 5 sec or so?

Cheers,
Gyu
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Eric Sproul]

On Mon, Jul 31, 2017 at 4:05 PM, Al Slater  wrote:
> One more question though, is there any way to enable an SMF service for
> the next reboot, but not immediately.  Specifically, I want to enable
> the initial-boot service with a .initialboot file in place, then create
> a new AMI.
>
> I wist to use .initialboot to grab the instance configuration from
> amazon (hostname, root keys etc) and configure appropriately when the
> new instance starts.

Hi Al,
The initial-boot service isn't really suitable for this sort of thing.
You might want to check out
pkg://omnios/system/management/ec2-credential which specifically
handles setting up the credentials at first boot.  That could be
trivially extended[1] to set the system hostname and probably any
other "standard" thing that operators want.

Eric

[1] 
https://github.com/omniosorg/omnios-build/blob/master/build/ec2-credential/files/install-ec2-credential
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Postfix service: syslog reports "fatal: the Postfix mail system is already running" every second

[Andries Annema]

Thanks, Jim. That is indeed the suggested cause that I find all over the 
web, however even if I stop the postfix-service, then manually delete 
the .pid and .lock file and then restart the service, it still reports 
that it's already running.

I don't see how it could be.
Also, the very same package worked flawlessly on r151014, but now on 
r151022 it starts bugging me.




On 2017-07-30 22:00, Jim Klimov wrote:

On July 30, 2017 5:42:31 PM GMT+02:00, Andries Annema  
wrote:

In the mean time I tried upgrading the separate test-system from
r151022
"vanilla" to the CE-edition -  r151022i by now - hoping this might
somehow also solve the below postfix "already running" error. But, it
didn't.

Again I tried the solution that worked on r151014 and also a reboot,
but
without success.

This "Postfix mail system is already running"-issue is all over the
internet - not specifically on Solarish-systems, that is - but I am
clearly missing something here, as I don't seem to get the issue out of

there.

Is there anyone out there with some ideas on this, pretty please?

Thanks.

Andries


On 2017-07-14 14:45, Andries Annema wrote:

Hi all,

Have been running postfix from the "ms.omniti.com" publisher for some
years now on r151014 without issues.
Last week I updated my October 2016 r151014 system to the latest
r151014-status, as a first step in the direction of upgrading to the
latest LTS. I'm not actually there yet to upgrade to r151022; first I
want to make sure all my services and packages run flawlessly on that
version. Turns out that being careful pays off.

In this update process, postfix got updated to
2.11.9-0.151014:20170214T224831Z.
It still works, but /var/log/syslog is filled with a new line ever
second stating:

" [ID 947731 mail.crit] fatal: the Postfix mail system is already
running"

And /var/svc/log/network-smtp-postfix:default.log is repeatedly

filled

with line pairs like:
"[ Jul 14 13:48:50 Executing start method ("/opt/omni/sbin/postfix
start"). ]
[ Jul 14 13:48:51 Stopping because service exited with an error. ]
[ Jul 14 13:48:51 Executing start method ("/opt/omni/sbin/postfix
start"). ]
[ Jul 14 13:48:51 Stopping because service exited with an error. ]
[ Jul 14 13:48:51 Failing too quickly, throttling. ]"

Simply disabling and re-enabling the SMF service does not help.
What did help was this:
$ sudo svcadm disable postfix
$ sudo fuser -k /var/lib/postfix/master.lock
$ sudo rm /var/lib/postfix/master.lock
$ sudo rm /var/spool/postfix/pid/master.pid
$ sudo svcadm enable postfix

That, however, was on r151014.
On a separate, freshly installed r151022 test-system, I installed

this

same postfix 2.11.9 package and the same issue emerged.
However, the fix that worked on r151014, does not seem to work on
r151022.
Rebooting doesn't help either.

Funny thing is: it does deliver email nicely, despite this restarting
issue.

I tried downgrading to postfix 2.10.10: problem still exists.
Tried downgrading further, to 2.10.2: not possible, because the
manifest states a "incorporate" dependency on the

"entire@11-0.151014"

package. Hm, right... now I'm out of ideas.
Any clues?

Regards,
Andries


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

IIRC the root problem was that some pid-file was left in place before 
restarting, e.g. by ungraceful reboot or timed-out stop with a kill.
--
Typos courtesy of K-9 Mail on my Android


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH

[Andries Annema]

Could this be in any way related to the issue I reported recently 
(http://lists.omniti.com/pipermail/omnios-discuss/2017-July/009079.html) 
where I tried to run "pkglint" in order to prepare an IPS package and 
got a "MemoryError" with the specific statement that "This is an 
internal error in pkg(5) version ..."?


Not sure if it does, because I got this error on a freshly installed 
r151022 "vanilla" system, so no upgrade from r151014 or anything. Also, 
if I run "pkg install pkg:/package/pkg" now on that system, it responds 
with "No updates necessary for this image", so I doubt it is really 
related.
However, I couldn't help but ask, as I haven't received any response on 
the other matter yet and both are related to "pkg"...


Andries


On 2017-07-31 17:14, Davide Poletto wrote:
Hello all, just a follow up about the upgrade from OmniOS r151014 to 
OmniOSce r151022 (r151022i) via OmniOS r151022: it was flawless in my 
case...the only additional step it required before the final pkg 
update -rv documented step (so the system was still on OmniOS r151022) 
was the mandatory update of pkg(5) package:


 /usr/bin/pkg update -rv
WARNING: pkg(5) appears to be out of date, and should be updated before
running update.  Please update pkg(5) by executing 'pkg install
pkg:/package/pkg' as a privileged user and then retry the update.

root@nas01:~# pkg install pkg:/package/pkg
Packages to update:   1
   Create boot environment:  No
Create backup boot environment: Yes

DOWNLOADPKGS FILESXFER (MB)   SPEED
Completed1/1 42/42  1.2/1.2  430k/s

PHASE  ITEMS
Removing old actions 1/1
Installing new actions   1/1
Updating modified actions  43/43
Updating package state database Done
Updating package cache   1/1
Updating image stateDone
Creating fast lookup database   Done
Reading search indexDone
Updating search index1/1
Updating package cache   1/1

I'm pretty sure that, when the system still was on OmniOS r151022 (so 
when the publisher was still pkg.omniti.com/omnios/r151022/ 
), the system was also fully 
up-to-date...I remember I did a pkg update -nv to check its 
status...but no updates were necessary (so the pkg(5) update's 
requirement reported above probably is a direct consequence of the 
publisher repository change from pkg.omniti.com/omnios/r151022/ 
 to 
pkg.omniosce.org/r151022/core/  
which is the mandatory step prior of the final pkg update -rv command 
execution).


Worth to mention that additional step on the 
https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md#upgrading-from-omniti-released-r151022 
paragraph?


Davide.

On Mon, Jul 31, 2017 at 10:25 AM, Krzysztof Grzempa 
> wrote:


Hello Jens
Currenty im out of home.
I will try it out tommorow and report results...

Thanks
Chris

29.07.2017 00:28 "Jens Bauernfeind"
> napisał(a):

Hi,

what happens when you just try to update entire?
pkg update -nv entire
or
pkg install -nv entire

Best Regards,
Jens

From: OmniOS-discuss [omnios-discuss-boun...@lists.omniti.com
] on behalf of
Krzysztof Grzempa [grzem...@gmail.com ]
Sent: Friday, July 28, 2017 10:50
To: omnios-discuss@lists.omniti.com

Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch
from SunSSH  to OpenSSH

HI,
So, any other ideas ? I would like to avoid plain new
installation scenario :)

Regards,
Kris

2017-07-28 1:29 GMT+02:00 Dan McDonald >>:
Yeah that's right.  Sorry -- had to ask.

Dan

Sent from my iPhone (typos, autocorrect, and all)

On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa
>> wrote:

Hi Dan,
I had done prerequsities before i started:

root@mojvps:/root# pkg list -v ca-bundle
FMRIIFO
pkg://omnios/web/ca-bundle@5.11-0.151014:20170414T020006Z
  i--

Re: [OmniOS-discuss] Loader On Mirrored Setup

[Mini Trader]

Is this the suggested command to use because it wasn't mentioned anywhere
on the loader wiki.

On Mon, Jul 31, 2017 at 11:15 AM Peter Tribble 
wrote:

>
>
> On Sun, Jul 30, 2017 at 9:14 PM, Mini Trader 
> wrote:
>
>> Hello all,
>>
>> If moving to Loader and using a mirrored setup is there anything that
>> must be done to ensure that Loader is installed on both drives?
>>
>
> This should be automatic. Note that the bootadm install-bootloader
> command works on pools, not disks, so if you have a mirrored pool
> it will do all sides of the mirror.
>
> If you replace one of the drives then you'll have to run bootadm
> install-bootloader
> on the pool again and it will put the loader on the replacement drive for
> you.
>
> --
> -Peter Tribble
> http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Loader On Mirrored Setup

[Peter Tribble]

On Sun, Jul 30, 2017 at 9:14 PM, Mini Trader 
wrote:

> Hello all,
>
> If moving to Loader and using a mirrored setup is there anything that must
> be done to ensure that Loader is installed on both drives?
>

This should be automatic. Note that the bootadm install-bootloader
command works on pools, not disks, so if you have a mirrored pool
it will do all sides of the mirror.

If you replace one of the drives then you'll have to run bootadm
install-bootloader
on the pool again and it will put the loader on the replacement drive for
you.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH

[Davide Poletto]

Hello all, just a follow up about the upgrade from OmniOS r151014 to
OmniOSce r151022 (r151022i) via OmniOS r151022: it was flawless in my
case...the only additional step it required before the final pkg update -rv
documented step (so the system was still on OmniOS r151022) was the
mandatory update of pkg(5) package:

 /usr/bin/pkg update -rv
WARNING: pkg(5) appears to be out of date, and should be updated before
running update.  Please update pkg(5) by executing 'pkg install
pkg:/package/pkg' as a privileged user and then retry the update.

root@nas01:~# pkg install pkg:/package/pkg
Packages to update:   1
   Create boot environment:  No
Create backup boot environment: Yes

DOWNLOADPKGS FILESXFER (MB)
SPEED
Completed1/1 42/42  1.2/1.2
430k/s

PHASE  ITEMS
Removing old actions 1/1
Installing new actions   1/1
Updating modified actions  43/43
Updating package state database Done
Updating package cache   1/1
Updating image stateDone
Creating fast lookup database   Done
Reading search indexDone
Updating search index1/1
Updating package cache   1/1

I'm pretty sure that, when the system still was on OmniOS r151022 (so when
the publisher was still pkg.omniti.com/omnios/r151022/), the system was
also fully up-to-date...I remember I did a pkg update -nv to check its
status...but no updates were necessary (so the pkg(5) update's requirement
reported above probably is a direct consequence of the publisher repository
change from pkg.omniti.com/omnios/r151022/ to pkg.omniosce.org/r151022/core/
which is the mandatory step prior of the final pkg update -rv command
execution).

Worth to mention that additional step on the
https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md#upgrading-from-omniti-released-r151022
paragraph?

Davide.

On Mon, Jul 31, 2017 at 10:25 AM, Krzysztof Grzempa 
wrote:

> Hello Jens
> Currenty im out of home.
> I will try it out tommorow and report results...
>
> Thanks
> Chris
>
> 29.07.2017 00:28 "Jens Bauernfeind" 
> napisał(a):
>
>> Hi,
>>
>> what happens when you just try to update entire?
>> pkg update -nv entire
>> or
>> pkg install -nv entire
>>
>> Best Regards,
>> Jens
>> 
>> From: OmniOS-discuss [omnios-discuss-boun...@lists.omniti.com] on behalf
>> of Krzysztof Grzempa [grzem...@gmail.com]
>> Sent: Friday, July 28, 2017 10:50
>> To: omnios-discuss@lists.omniti.com
>> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from
>> SunSSH  to OpenSSH
>>
>> HI,
>> So, any other ideas ? I would like to avoid plain new installation
>> scenario :)
>>
>> Regards,
>> Kris
>>
>> 2017-07-28 1:29 GMT+02:00 Dan McDonald > @kebe.com>>:
>> Yeah that's right.  Sorry -- had to ask.
>>
>> Dan
>>
>> Sent from my iPhone (typos, autocorrect, and all)
>>
>> On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa > > wrote:
>>
>> Hi Dan,
>> I had done prerequsities before i started:
>>
>> root@mojvps:/root# pkg list -v ca-bundle
>> FMRI
>>IFO
>> pkg://omnios/web/ca-bundle@5.11-0.151014:20170414T020006Z
>> i--
>>
>> there is 'April' certificates..right ?
>>
>> Kris
>>
>> 2017-07-27 22:28 GMT+02:00 Dan McDonald > @kebe.com>>:
>> You're sure you're on the very latest 014? Could be lack of updated
>> certificates...
>>
>> Dan
>>
>> Sent from my iPhone (typos, autocorrect, and all)
>>
>> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa > > wrote:
>>
>> Guys,
>> I will grab this thread as it is somehow similiar. I want to upgrade from
>> r151014 to r151022. I went throught all steps of:
>> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
>> but when Im performing upgrade:
>>
>> # /usr/bin/pkg update --be-name r151022
>>
>> i got:
>>
>> root@mojvps:/root# /usr/bin/pkg update --be-name r151022
>> Creating Plan (Running solver): |
>> pkg update: No solution was found to satisfy constraints
>> Plan Creation: Package solver has not found a solution to update to
>> latest available versions.
>> This may indicate an overly constrained set of packages are installed.
>>
>> latest incorporations:
>>
>>   pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z
>>   pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.15102
>> 2:20170510T210757Z
>>   pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,
>> 5.11-0.151022:20170510T212740Z
>>   pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-0.
>> 151022:20170511T001737Z
>> Dependency analysis is unable to 

Re: [OmniOS-discuss] Ldap crash causing system to hang fixed in illumos...

[Dominik Hassler]

Hi Oliver,

a pkg archive containing an updated system/library is available:
https://downloads.omniosce.org/pkg/system_library_8543.p5p

Please provide feedback as soon as you could test it. Thanks.

Regards,
Dominik

On 07/31/2017 11:26 AM, Oliver Weinmann wrote:

Hi Andy,

These are great news. Thanks a lot. I'm happy to test. :)

But first I guess I have to upgrade my current omnios 151022 to latest omniosce.

Best Regards,
Oliver

-Original Message-
From: Andy Fiddaman [mailto:omn...@citrus-it.net]
Sent: Montag, 31. Juli 2017 11:19
To: Oliver Weinmann 
Cc: omnios-discuss 
Subject: Re: [OmniOS-discuss] Ldap crash causing system to hang fixed in 
illumos...


On Mon, 31 Jul 2017, Oliver Weinmann wrote:

; Hi Guys,
;
; I'm currently facing this bug under OmniOS 151022 and I just got informed 
that this has been fixed:
;
; https://www.illumos.org/issues/8543
;
; As this bug is causing a complete system hang only a reboot helps. Can this 
maybe be implemented?
;
; Best Regards,
; Oliver

Hi Oliver,

I've opened an issue for you at
https://github.com/omniosorg/illumos-omnios/issues/26
and you can track progress there.

We plan to include this fix in next Monday's release but we're building a test 
update today and somebody will be in touch directly if you want to test it 
early.

Regards,

Andy

--
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk Rock House 
Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and 
Wales | Company number 4899123

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

On 31/07/2017 11:39, Peter Tribble wrote:
> 
> 
> On Mon, Jul 31, 2017 at 11:09 AM, Al Slater  > wrote:
> 
> On 31/07/2017 11:07, Al Slater wrote:
> > On 30/07/2017 20:15, Peter Tribble wrote:
> >> > The following should get you going:
> >> >
> >> > 
> https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/
> 
> 
> >> 
>  
> >
> >
> > OK, I followed the above procedure and have produced an AMI.
> >
> > When I create an instance and try to boot it, I get the following in the
> > system log:
> 
> SunOS Release 5.11 Version omnios-r151022-f9693432c2 64-bit
> 
> Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights
> reserved.
> 
> NOTICE: Cannot read the pool label from '/xpvd/xdf@51728:a'
> NOTICE: spa_import_rootpool: error 5
> 
> Cannot mount root on /xpvd/xdf@51728:a fstype zfs
> panic[cpu0]/thread=fbc38560: vfs_mountroot: cannot mount root
> Warning - stack not written to the dump buffer
> fbc7ad70 genunix:vfs_mountroot+39b ()
> fbc7adb0 genunix:main+138 ()
> fbc7adc0 unix:_locore_start+90 ()
> 
> 
> How can I fix this?
> 
> 
> You're likely the first person down this path.
> 
> Generically, this means that the device paths embedded in the pool
> don't match those provided by the "hardware" you're booting on.
> 
> So the system thinks it should have a disk at /xpvd/xdf@51728:a
> 
> On my instance, I have:
> 
> /dev/rdsk/c2t0d0s0 -> ../../devices/xpvd/xdf@51712:a,raw
> 
> In other words, 51712 not 51728.
> 
> For this to work, you have to set up your xen instance to exactly mirror
> what EC2 provides. Somehow it's gotten mixed up. In your configuration,
> did you use xvda? I think 51728 is what you get if you use xvdb for the
> disk,
> which won't work. I had:
> 
> disk=[  'file:/home/ptribble/iso/tribblix-0m20.1.iso,hdb:cdrom,r',
> 'file:/root/ami-template.img,xvda,w' ]
> 

Thanks Peter,  I see what happened...

I started off with the instructions from
https://wiki.openindiana.org/oi/Creating+OpenIndiana+EC2+image

Then changed to following the instructions at
https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/

while neglecting to change the disks line in my xen config.

Oh well, starting again...

-- 
Al Slater



___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Peter Tribble]

On Mon, Jul 31, 2017 at 11:09 AM, Al Slater  wrote:

> On 31/07/2017 11:07, Al Slater wrote:
> > On 30/07/2017 20:15, Peter Tribble wrote:
> >> > The following should get you going:
> >> >
> >> > https://www.prakashsurya.com/post/2017-02-06-creating-a-
> custom-amazon-ec2-ami-from-iso/
> >>  custom-amazon-ec2-ami-from-iso/>
> >
> > OK, I followed the above procedure and have produced an AMI.
> >
> > When I create an instance and try to boot it, I get the following in the
> > system log:
>
> SunOS Release 5.11 Version omnios-r151022-f9693432c2 64-bit
>
> Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights
> reserved.
>
> NOTICE: Cannot read the pool label from '/xpvd/xdf@51728:a'
> NOTICE: spa_import_rootpool: error 5
>
> Cannot mount root on /xpvd/xdf@51728:a fstype zfs
> panic[cpu0]/thread=fbc38560: vfs_mountroot: cannot mount root
> Warning - stack not written to the dump buffer
> fbc7ad70 genunix:vfs_mountroot+39b ()
> fbc7adb0 genunix:main+138 ()
> fbc7adc0 unix:_locore_start+90 ()
>
>
> How can I fix this?
>

You're likely the first person down this path.

Generically, this means that the device paths embedded in the pool
don't match those provided by the "hardware" you're booting on.

So the system thinks it should have a disk at /xpvd/xdf@51728:a

On my instance, I have:

/dev/rdsk/c2t0d0s0 -> ../../devices/xpvd/xdf@51712:a,raw

In other words, 51712 not 51728.

For this to work, you have to set up your xen instance to exactly mirror
what EC2 provides. Somehow it's gotten mixed up. In your configuration,
did you use xvda? I think 51728 is what you get if you use xvdb for the
disk,
which won't work. I had:

disk=[  'file:/home/ptribble/iso/tribblix-0m20.1.iso,hdb:cdrom,r',
'file:/root/ami-template.img,xvda,w' ]

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

[Al Slater]

On 31/07/2017 11:07, Al Slater wrote:
> On 30/07/2017 20:15, Peter Tribble wrote:
>> > The following should get you going:
>> >
>> > 
>> https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/
>> 
>> 
> 
> OK, I followed the above procedure and have produced an AMI.
> 
> When I create an instance and try to boot it, I get the following in the
> system log:

SunOS Release 5.11 Version omnios-r151022-f9693432c2 64-bit

Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.

NOTICE: Cannot read the pool label from '/xpvd/xdf@51728:a'
NOTICE: spa_import_rootpool: error 5

Cannot mount root on /xpvd/xdf@51728:a fstype zfs
panic[cpu0]/thread=fbc38560: vfs_mountroot: cannot mount root
Warning - stack not written to the dump buffer
fbc7ad70 genunix:vfs_mountroot+39b ()
fbc7adb0 genunix:main+138 ()
fbc7adc0 unix:_locore_start+90 ()


How can I fix this?

-- 
Al Slater


___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Ldap crash causing system to hang fixed in illumos...

[Oliver Weinmann]

Hi Andy,

These are great news. Thanks a lot. I'm happy to test. :)

But first I guess I have to upgrade my current omnios 151022 to latest omniosce.

Best Regards,
Oliver

-Original Message-
From: Andy Fiddaman [mailto:omn...@citrus-it.net] 
Sent: Montag, 31. Juli 2017 11:19
To: Oliver Weinmann 
Cc: omnios-discuss 
Subject: Re: [OmniOS-discuss] Ldap crash causing system to hang fixed in 
illumos...


On Mon, 31 Jul 2017, Oliver Weinmann wrote:

; Hi Guys,
;
; I'm currently facing this bug under OmniOS 151022 and I just got informed 
that this has been fixed:
;
; https://www.illumos.org/issues/8543
;
; As this bug is causing a complete system hang only a reboot helps. Can this 
maybe be implemented?
;
; Best Regards,
; Oliver

Hi Oliver,

I've opened an issue for you at
https://github.com/omniosorg/illumos-omnios/issues/26
and you can track progress there.

We plan to include this fix in next Monday's release but we're building a test 
update today and somebody will be in touch directly if you want to test it 
early.

Regards,

Andy

--
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk Rock House 
Farm | Green Moor | Wortley | Sheffield | S35 7DQ Registered in England and 
Wales | Company number 4899123

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Ldap crash causing system to hang fixed in illumos...

[Andy Fiddaman]

On Mon, 31 Jul 2017, Oliver Weinmann wrote:

; Hi Guys,
;
; I'm currently facing this bug under OmniOS 151022 and I just got informed 
that this has been fixed:
;
; https://www.illumos.org/issues/8543
;
; As this bug is causing a complete system hang only a reboot helps. Can this 
maybe be implemented?
;
; Best Regards,
; Oliver

Hi Oliver,

I've opened an issue for you at
https://github.com/omniosorg/illumos-omnios/issues/26
and you can track progress there.

We plan to include this fix in next Monday's release but we're building a
test update today and somebody will be in touch directly if you want to
test it early.

Regards,

Andy

-- 
Citrus IT Limited | +44 (0)333 0124 007 | enquir...@citrus-it.co.uk
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151014: failed to switch from SunSSH to OpenSSH

[Krzysztof Grzempa]

Hello Jens
Currenty im out of home.
I will try it out tommorow and report results...

Thanks
Chris

29.07.2017 00:28 "Jens Bauernfeind" 
napisał(a):

> Hi,
>
> what happens when you just try to update entire?
> pkg update -nv entire
> or
> pkg install -nv entire
>
> Best Regards,
> Jens
> 
> From: OmniOS-discuss [omnios-discuss-boun...@lists.omniti.com] on behalf
> of Krzysztof Grzempa [grzem...@gmail.com]
> Sent: Friday, July 28, 2017 10:50
> To: omnios-discuss@lists.omniti.com
> Subject: Re: [OmniOS-discuss] OmniOS r151014: failed to switch from
> SunSSH  to OpenSSH
>
> HI,
> So, any other ideas ? I would like to avoid plain new installation
> scenario :)
>
> Regards,
> Kris
>
> 2017-07-28 1:29 GMT+02:00 Dan McDonald  @kebe.com>>:
> Yeah that's right.  Sorry -- had to ask.
>
> Dan
>
> Sent from my iPhone (typos, autocorrect, and all)
>
> On Jul 27, 2017, at 4:36 PM, Krzysztof Grzempa > wrote:
>
> Hi Dan,
> I had done prerequsities before i started:
>
> root@mojvps:/root# pkg list -v ca-bundle
> FMRI
>IFO
> pkg://omnios/web/ca-bundle@5.11-0.151014:20170414T020006Z
> i--
>
> there is 'April' certificates..right ?
>
> Kris
>
> 2017-07-27 22:28 GMT+02:00 Dan McDonald  @kebe.com>>:
> You're sure you're on the very latest 014? Could be lack of updated
> certificates...
>
> Dan
>
> Sent from my iPhone (typos, autocorrect, and all)
>
> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa > wrote:
>
> Guys,
> I will grab this thread as it is somehow similiar. I want to upgrade from
> r151014 to r151022. I went throught all steps of:
> https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
> but when Im performing upgrade:
>
> # /usr/bin/pkg update --be-name r151022
>
> i got:
>
> root@mojvps:/root# /usr/bin/pkg update --be-name r151022
> Creating Plan (Running solver): |
> pkg update: No solution was found to satisfy constraints
> Plan Creation: Package solver has not found a solution to update to latest
> available versions.
> This may indicate an overly constrained set of packages are installed.
>
> latest incorporations:
>
>   pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z
>   pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.
> 151022:20170510T210757Z
>   pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.
> 11,5.11-0.151022:20170510T212740Z
>   pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-
> 0.151022:20170511T001737Z
> Dependency analysis is unable to determine exact cause.
> Try specifying expected results to obtain more detailed error messages.
>
>
> I set publisher correctly IHMO:
>
> root@mojvps:/root# pkg publisher
> PUBLISHER   TYPE STATUS P LOCATION
> omnios  origin   online F
> https://pkg.omniti.com/omnios/r151022/
>
>
> Any ideas ?
>
> I want to upgrade to CE after that.
>
> Thanks in advance
> Kris
>
> 2017-07-24 17:01 GMT+02:00 Davide Poletto  mailto:davide.pole...@gmail.com>>:
> Thanks Andy, thanks Peter.
>
> So now OpenSSH is installed:
>
> root@nas01:/root# pkg list | grep ssh
> network/openssh   7.4.1-0.151014
>i--
> network/openssh-server7.4.1-0.151014
>i--
> root@nas01:/root# ssh -V
> OpenSSH_7.4p1, OpenSSL 1.0.2k  26 Jan 2017
>
> Totally my fault in not following the right Release Notes (I thought I
> should have followed the destination version - r151022 - Release Notes
> instead the one from where the upgrade process has to start, r151014 in my
> case).
>
> Thanks again for pointing me on the right track.
>
> Best regards, Davide.
>
> On Mon, Jul 24, 2017 at 4:21 PM, Peter Tribble  mailto:peter.trib...@gmail.com>> wrote:
>
>
> On Mon, Jul 24, 2017 at 2:56 PM, Davide Poletto  mailto:davide.pole...@gmail.com>> wrote:
> Hello all,
>
> I'm facing a strange issue on a pretty standard OmniOS r151014 LTS box
> fully updated (only Global Zone), following the "Upgrading to r151022"
> instructions at https://omnios.omniti.com/wiki.php/Upgrade_to_r151022
> required before any jump to OmniOS r151022 (my final target is OmniOS
> Community Edition r151022i) I found that I'm unable to switch to OpenSSH as
> per "Upgrading to OpenSSH from SunSSH" instructions on the same page:
>
> executing the suggested command:
>
> root@nas01:/root# /usr/bin/pkg install --no-backup-be --reject
> pkg:/network/ssh --reject pkg:/network/ssh/ssh-key --reject
> pkg:/service/network/ssh --reject pkg:/service/network/ssh-common
> pkg:/network/openssh pkg:/network/openssh-server
>
> fails with the message:
>
> pkg install: The following pattern(s) did not match any allowable
> packages.  Try
> using a different matching pattern, or refreshing publisher information:
>
> 

[OmniOS-discuss] Ldap crash causing system to hang fixed in illumos...

[Oliver Weinmann]

Hi Guys,

I'm currently facing this bug under OmniOS 151022 and I just got informed that 
this has been fixed:

https://www.illumos.org/issues/8543

As this bug is causing a complete system hang only a reboot helps. Can this 
maybe be implemented?

Best Regards,
Oliver
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss