Re: [OmniOS-discuss] Recommend any FC Gen 5 or Gen 6 HBAs?

[Andy Fiddaman]

On Tue, 23 Oct 2018, Phil Forrest wrote:

; I found another Fibre Channel card that does not work in OmniOS CE r151026: 
Qlogic QLE2740
;
; root@claw:~# prtconf -D | grep pci1077
; pci1077,299

...

; My failures so far:
;
; Qlogic QLE2672
; Emulex LPe32000 (Lancer)
; Qlogic QLE2740
;

Just to close the loop on this one, thanks to Phil's assistance with access
to hardware for development and testing, the recently released OmniOS r151028
includes new support for all three cards listed above.

https://github.com/omniosorg/omnios-build/blob/r151028/doc/ReleaseNotes.md#hardware-support

~A.

-- 
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] bhyve pkg's

[Andy Fiddaman]

On Fri, 26 Oct 2018, Johan Kragsterman wrote:

; Hi!
;
; I know that bhyve is going to be included in 028, but I just saw the pkg: 
pkg:/system/bhyve@0.5.11-0.151026
;
; So I installed it.
;
; Though it seems it also requires a brand information, perhaps a package 
something like: pkg:/system/zones/brand/bhyve ?

bhyve in r151026 works, but you have to drive it by hand. The instructions
for doing that can still be found at:

https://github.com/omniosorg/omniosorg.github.io/blob/727c2b047d6bcc0a692226084d3f21bed80bba0c/_docs/info/bhyve.md

; Yeah, guess I have to wait some more weeks...

9 days now.. :)
Bhyve testing has been very positive so far!

~A.
-- 
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] Ang: Re: bhyve zonepath?

[Andy Fiddaman]

On Wed, 17 Oct 2018, Johan Kragsterman wrote:

; Okay, thanks, I understand that, but where is that? /data??? Or is it just an 
example, can I put this where I want it? I wouldn't want it in rpool...
;
; And as well, I suppose this is this a zfs path, so that it should start with 
a pool? Maybe your example starts with the pool: /data?

It's just a filesystem path. On test servers with a single rpool, I usually
do:

zfs create -o mountpoint=/data rpool/data
zfs create rpool/data/zone

Then put my zones in /data/zone/. Others create a /zones mount.

A.

-- 
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] bhyve zonepath?

[Andy Fiddaman]

On Wed, 17 Oct 2018, Johan Kragsterman wrote:

; Hi!
;
;
; I'm doing my first experiments with bhyve, and I'm a bit confused by 
something in the omniosce site about bhyve:
;
; https://omniosce.org/info/bhyve_kvm_brand.html
;
;
; In the example of configuring a bhyve zone is this:
;
; set zonepath=/data/zone/bhyve
;
; Could someone explain that to me? I mean the pointer to the disk device is 
another, so what is this zonepath pointing at and why? Am I just stupid, or 
what have I missed...?

It's pointing at the filesystem used for the zone itself; the thing that is
populated when you run `zoneadm -z  install`. For a bhyve zone, this is
just a handful of files and some loopback mounts but the zone needs something
to mount on / during boot.

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] Support for AD join when SMBv1 is disabled?

[Andy Fiddaman]

On Sun, 14 Oct 2018, Andries Annema wrote:

; Hi Andy,
;
; According to for example this thread, and the links provided there, Illumos 
supports SMB2 for about three years now: 
https://forums.servethehome.com/index.php?threads/smb-2-1-long-paths-better-ad-support-for-illumos-oi-omnios-smartos.7384/
;
; Isn't it therefore implemented in OmniOS since r151018 or so?
;
; Just trying to clear up some confusion on my end at least. Thanks.

illumos (and OmniOS) has general SMB2 support but specifically not the client
part; it still can only act as an SMB1 client.

There's a pull request open at https://github.com/illumos/illumos-gate/pull/37
that is working on adding SMB 2.1 client support and it's making good progress.
Once that gets merged, we will likely get it into at least the upcoming
r151028.

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] Support for AD join when SMBv1 is disabled?

[Andy Fiddaman]

On Thu, 11 Oct 2018, Omen Wild wrote:

; Quoting Guenther Alka  on Thu, Oct 11 21:15:
; >
; > You should add this to
; > https://www.illumos.org/issues/9735
; >
; > as this can be fixed at Illumos only.
;
; Ah, I see. Thank you for the pointer, we had not been able to find that
; with our Google searches. Looks like we will have to switch to Samba.

Yes, unfortunately illumos does not yet support SMB 2 - however there is
currently an active review of a change to add this so support may appear
in the next month or so, and will likely be backported to at least
OmniOS r151028 which will be released at the start of November.

A.

-- 
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] screnrc or terminfo/termcap definitions changed in 151026

[Andy Fiddaman]

On Tue, 11 Sep 2018, P?SZTOR Gy?rgy wrote:

; Hi!
;
; Can someone tell me, what changed in screenrc or termcap between 151022 and
; 151026?

According to the release notes at https://omniosce.org/releasenotes

o The /etc/screenrc file delivered by the screen package is now based on the
  recommended global template as delivered by the authors; you may wish to check
  that it still meets your needs. If you have previously customised this file
  then it will not be updated but the new template file will be installed as
  /etc/screenrc.new.

o screen is now linked against ncurses in order to support more terminal
  types (e.g. iterm)

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] Panic on OmniOS CE r151022ay

[Andy Fiddaman]

On Thu, 30 Aug 2018, Schweiss, Chip wrote:

; > panicstack = unix:real_mode_stop_cpu_stage2_end+b203 () |
; > unix:trap+a70 () | unix:cmntrap+e6 () | zfs:zfs_getattr+1a0 () |
; > genunix:fop_getattr+a8 () | genunix:xattr_dir_getattr+16c () |
; > genunix:fop_getattr+a8 () | nfssrv:rfs4_delegated_getattr+20 () |
; > nfssrv:acl3_getxattrdir+102 () | nfssrv:common_dispatch+5ab () |
; > nfssrv:acl_dispatch+2d () | rpcmod:svc_getreq+1c1 () | rpcmod:svc_run+e0 ()
; > | rpcmod:svc_do_run+8e () | nfs:nfssys+111 () | unix:brand_sys_sysenter+1d3

That does look quite similar to issue 8806 that was fixed earlier in the
year. Can you check that the fix is in place on your box since you're
running a version of OmniOS from May.

If this produces any output, then the fix is missing, otherwise it's something
else.

mdb -ke xattr_dir_inactive::dis | grep mutex

Please can you open an issue for this at
https://github.com/omniosorg/illumos-omnios/issues/new
in the first instance as it may be OmniOS-specific?

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] OmniOS stable r151026 released

[Andy Fiddaman]

The OmniOS Community Edition Association is proud to announce the
availability of the second Community release of OmniOS - r151026

The new release comes 6 months after the the first community release back
in November 2017. As per the published release schedule the previous stable
version is supported for a further six months to allow time for
upgrades and the LTS r151022 version remains supported untilMay 2020. We
encourage anyone on the stable r151024 release to begin planning their
upgrade to r151026.

The release notes for can be found athttps://omniosce.org/releasenotes and
instructions for upgrading at https://omniosce.org/upgrade - AWS images
have also been pushed out to all regions.

For more information, please see our full release announcement at
https://omniosce.org/article/release-026

About OmniOS Community Edition Association - this Swiss Association is
responsible for the ongoing development and maintenance of OmniOS, having
been established in Summer 2017 after OmniTI announced their withdrawal
from the project.

OmniOSce Association
Aarweg 17, 4600 Olten, Switzerland
i...@omniosce.org
-- 
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] xnf panic

[Andy Fiddaman]

Al, that's great thanks. The fix will be in Monday's update - the same as
the hotfix you already have.

Thanks for reporting this, it's likely to hit people as Amazon upgrade
their platform.

Regards,

Andy

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi Andy,
;
; OK, I booted a t2.micro instance from my AMI (Original OmniOS CE r151022
; HVM).  Updated pkg and then updated to r151022as.
;
; Then shut the instance down, changed the type to m4.large, then started
; the instance.  A panic/reboot loop ensued.  Stopped the instance.
;
; Changed the instance back to t2.micro and booted.  Applied the hotfix
; and rebooted.  Rebooted fine.
;
; Stopped the instance, changed instance type to m4.large, and started the
; instance.  The instance started and I could log in just fine.
;
; To be sure, I stopped and restarted the instance a few times. It always
; came back up ok.
;
; So, the patch looks good to me.  If you can think of any more tests you
; would like me to run, I'll give them a go for you.
;
; Thank you for the speedy fix.
;
; regards
;
; Al
;
;
; On 09/04/18 18:05, Al Slater wrote:
; > Hi Andy,
; >
; > Wow, that was fast.  I will test this when I have fed the family.
; >
; > I have my own AMI, so I can spin a server as a T2 instance, apply the
; > fix and then restart after changing to an M4.
; >
; > regards
; >
; > Al
; >
; > On 09/04/18 16:04, Andy Fiddaman wrote:
; >>
; >> Al,
; >>
; >> I've prepared a hot-fix containing this driver update if you'd like to
; >> test. I tried to test it myself on AWS but can't provision any type of
; >> machine from that unofficial CE r151022 AMI in London. Just snapshot the
; >> EBS volume first in case of problems.
; >>
; >> To install:
; >>
; >>   pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p
; >>
; >> which will create a new boot-environment, and reboot.
; >>
; >> Assuming it looks ok, this update will be part of next Monday's release.
; >>
; >> Regards,
; >>
; >> Andy
; >>
; >> On Mon, 9 Apr 2018, Al Slater wrote:
; >>
; >> ; Hi,
; >> ;
; >> ; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; >> ; r151022 since the initial CE release?
; >> ;
; >> ; I have an instance in AWS that they required me to stop and start again
; >> ; due to host patching.  When I started it again the instance went into a
; >> ; panic/reboot loop.  The stack dump looked similar to the one in the
; >> ; error report.
; >> ;
; >> ; I managed to get the instance started by changing the instance type from
; >> ; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
; >> ; > 4 in london region.  I don't know how long until the t2 hosts are 
updated.
; >> ;
; >> ; regards
; >> ;
; >> ;
; >>
; >
; > ___
; > 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
;
-- 
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] xnf panic

[Andy Fiddaman]

Al,

I've prepared a hot-fix containing this driver update if you'd like to
test. I tried to test it myself on AWS but can't provision any type of
machine from that unofficial CE r151022 AMI in London. Just snapshot the
EBS volume first in case of problems.

To install:

  pkg apply-hot-fix https://downloads.omniosce.org/pkg/r151022/7186-xnf.p5p

which will create a new boot-environment, and reboot.

Assuming it looks ok, this update will be part of next Monday's release.

Regards,

Andy

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi,
;
; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; r151022 since the initial CE release?
;
; I have an instance in AWS that they required me to stop and start again
; due to host patching.  When I started it again the instance went into a
; panic/reboot loop.  The stack dump looked similar to the one in the
; error report.
;
; I managed to get the instance started by changing the instance type from
; m4.large to t2.large.  Presumably AWS are migrating towards Xen versions
; > 4 in london region.  I don't know how long until the t2 hosts are updated.
;
; regards
;
;
-- 
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] xnf panic

[Andy Fiddaman]

On Mon, 9 Apr 2018, Al Slater wrote:

; Hi,
;
; Has the fix for 7186 (xnf: panic on Xen 4.x) been integrated into
; r151022 since the initial CE release?

Hi Al,

No, that one was not selected for back-porting. I'll get it added to the list
for the next weekly release.

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] [zfs] FMD fails to run

[Andy Fiddaman]

Chip,

Try this hot-fix:

# pkg apply-hot-fix --be-name=9317 \
https://downloads.omniosce.org/pkg/r151024/9317-ses2.p5p

If it fixes your problem I'll work on upstreaming this fix to illumos-gate
and it will definitely be in the upcoming OmniOS r151026 as well as
being backported to r151022 & r151024.

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] [zfs] FMD fails to run

[Andy Fiddaman]

On Mon, 19 Mar 2018, Schweiss, Chip wrote:

; You might be on to something.  I was suspicious of Element 96 when
; examining via sg_ses.  This JBOD has 96 slots and no display panel.  The
; vendor suspected other issues.

Well, it's this element:

value='IO Module   PCA-00610-01-A  USE2600052CMK0162B'

which has no PHYs:

ses2_aes_descr_sas1_impl_t {
uint8_t sadsi_n_phy_descriptors = 0
unsigned char _reserved1 :6 = 0
unsigned char sadsi_descriptor_type :2 = 0x1
uint8_t [2] _reserved2 = [ 0, 0 ]
ses2_aes_phy1_descr_impl_t [1] sadsi_phys = [
ses2_aes_phy1_descr_impl_t {
uint8_t sapdi_phy_identifier = 0x16
uint8_t _reserved1 = 0x6e
uint8_t sapdi_connector_element_index = 0
uint8_t sapdi_other_element_index = 0x74
uint64_t sapdi_sas_address = 0xd29300504030
},
]
}

I'm building the hot-fix now - takes about an hour.

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] [zfs] FMD fails to run

[Andy Fiddaman]

On Mon, 19 Mar 2018, Schweiss, Chip wrote:

; On Mon, Mar 19, 2018 at 9:19 AM, Andy Fiddaman <omn...@citrus-it.net> wrote:
;
; >
; > I'll have a look at this for you and get a hot-fix built. I have the core
; > file that you made available so just need to go through and work out why
; > it thinks there are 0 phys somewhere.
; >
; >
; Many thanks!
;
; In discusscussion with JBOD vendor support, this JBOD has two SAS
; expanders, which are linked together.  One is likely incorrectly reporting
; 0 and should be ignored.

The device is identifying as ESC_ELECTRONICS rather than a SAS_EXPANDER but
I'll do some more digging.

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] [zfs] FMD fails to run

[Andy Fiddaman]

On Mon, 19 Mar 2018, Schweiss, Chip wrote:

; Looks like I'm dead in the water to make this work with Illumos until this
; bug is fixed.

Chip,

I'll have a look at this for you and get a hot-fix built. I have the core
file that you made available so just need to go through and work out why
it thinks there are 0 phys somewhere.

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] 8806 back port

[Andy Fiddaman]

On Tue, 13 Mar 2018, Schweiss, Chip wrote:

; pkg set-publisher: Could not refresh the catalog for omnios
;
; file protocol error: code: E_FAILED_INIT (2) reason: Package archive
; /root/8806-backport_r22.p5p does not contain the requested package file(s):
; publisher/omnios/catalog/catalog.attrs.
; Repository URL: 'file:///root/8806-backport_r22.p5p'. (happened 4 times)

Hi Chip,

This error message actually looks like you still have the publisher set
from the last time you applied the fix by hand. Can you check the output
of 'pkg publisher'?

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] 8806 back port

[Andy Fiddaman]

On Tue, 13 Mar 2018, Schweiss, Chip wrote:

; The 8806 backport will no longer apply to r151022ap.
; No updates available for this image.

I think this is the relevant message - we need to look at why you got the
additional errors but ignore them for now.

; Some things are not clear about hot-fixes.
;
; Do they need to be reapplied after each update?

No. A hotfix usually updates a specific package; 'system/kernel' in the
case of 8806.

If a weekly update includes a new version of that package, then it will also
include the rolled-up hotfix. If a weekly update does not include that
package then you keep the hot-fixed version in place.

; Are they only compatible with the release they are built against?

No, but they won't apply if you have the same or a newer version of the
affected package installed already.

HTH.

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] issue 8984 (fix for 6764 breaks ACL inheritance)

[Andy Fiddaman]

On Thu, 8 Mar 2018, Paul B. Henson wrote:

; > From: Andries Annema
; > Sent: Thursday, March 8, 2018 8:06 AM
; >
; > But the issue seems unresolved when:
; >
; > - using rsync to copy stuff over from one dataset to another.
;
; I don't think rsync understands ZFS ACLs? So it is most likely trying to 
duplicate the mode bits while copying, using chmod...

rsync explicity does do that, it tries to make the permissions on the target
file match the source, including ACLs where it can (I'm also not sure if it
supports NFSv4 ACLs).

>From the man page:

To give new files the destination-default permissions,
make sure that the --perms option is off and use
--chmod=ugo=rwX (which ensures that all non-masked bits get
enabled).

So, give this a go:

 rsync -a --no-p --no-g --chmod=ugo=rwX src/ dst/

The extra options need to come after -a.

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] [developer] [call for testing] KPTI images (fwd)

[Andy Fiddaman]

Joyent's illumos fix for the Meltdown vulnerability is nearing
completion and so we  have produced some test images and, along with
Openindiana and SmartOS, are asking people to install and test on as wide a
range of machines as possible.

We've provided this as a hotfix so it can easily be installed into a new
BE by anyone running OmniOS bloody. Have a look at
https://omniosce.org/article/kpti for instructions and some useful mdb
commands to check the installation afterwards.

Please see the original announcement message that was posted to other
lists. If you can, please test and provide feedback.

Thanks,

Andy

-- Forwarded message --
Date: Mon, 5 Mar 2018 13:46:50 +
From: John Levon <john.le...@joyent.com>
Reply-To: illumos-developer <develo...@lists.illumos.org>
To: oi-...@openindiana.org, develo...@lists.illumos.org,
smartos-disc...@lists.smartos.org
Subject: [developer] [call for testing] KPTI images

Hi all, please see below for test images for the various
distributions. These images include the KPTI (and PCID) work done by
Joyent up to the current kpti-squash branch. They are non-DEBUG except
as noted.

As before, any and all testing is useful, especially with "weird"
things like LDT-using code, older machines, etc.

Thanks to Aur?lien Larcher and Andy Fiddaman for building the OI and
OmniOS images below.

thanks
john

OpenIndiana:

http://dlc-int.openindiana.org/users/aurelien/kpti/

OmniOSce (bloody):

# pkg update pkg
# pkg apply-hot-fix --be-name=kpti
https://downloads.omniosce.org/pkg/bloody/kpti.p5p
# init 6

or for DEBUG bits:

# pkg apply-hot-fix --be-name=kpti
https://downloads.omniosce.org/pkg/bloody/kpti-DEBUG.p5p

SmartOS:

https://us-east.manta.joyent.com/jlevon/public/bits/kpti/platform-20180305T101513Z.iso
https://us-east.manta.joyent.com/jlevon/public/bits/kpti/platform-20180305T101513Z.tgz

--
illumos: illumos-developer
Permalink: 
https://illumos.topicbox.com/groups/developer/discussions/T4c9a8fdfb8301f10-Mdd69563eb3591402853dce82
Delivery options: https://illumos.topicbox.com/groups
-- 
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] Including fix for 8680 into r151022ce or r151024?

[Andy Fiddaman]

Hugh,

This fix has been included in the latest updates for r151022 & r151024
- see https://www.omniosce.org/article/releases-022ao-024q.html

Andy

On Fri, 23 Feb 2018, Andy Fiddaman wrote:

; On Fri, 23 Feb 2018, Hugh McIntyre wrote:
;
; ; I am seeing the same TOC clock bug described in #8680 ("Time of Day clock
; ; error"), in my case on an older non-Ryzen AMD motherboard. although NTP 
seems
; ; to fix the clock, it's annoying that some files early in boot may get
; ; incorrect dates.
; ;
; ; This is on r151022ce although OmniOSCE github repository contains the fixed
; ; version of usr/src/uts/i86pc/io/todpc_subr.c, so I assume this will exist in
; ; bloody releases.
; ;
; ; Can I expect this will show up in r151022ce (LTS) or r151024 automatically
; ; after some soak time though, or can I request this?  It's not clear if the
; ; Gitter lobby or IRC is preferred for requests like this ...
;
;
; Hi Hugh,
;
; I'll have a look at this and see whether it can be backported. Either way
; we will be able to provide an installable hot-fix for you early next week.
;
; The process that we use is to pull in changes from illumos gate and from
; Joyent's illumos fork weekly and then assess the changes for back-port, so
; if this is already in our bloody branch then it will not automatically appear
; in older versions; it was presumably not selected.
;
; The Gitter lobby is preferred for general support requests but we're also
; around on IRC and check the mailing list from time to time. The core team
; is all in Europe so there can be some latency due to time difference.
;
; 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] Including fix for 8680 into r151022ce or r151024?

[Andy Fiddaman]

On Fri, 23 Feb 2018, Hugh McIntyre wrote:

; I am seeing the same TOC clock bug described in #8680 ("Time of Day clock
; error"), in my case on an older non-Ryzen AMD motherboard. although NTP seems
; to fix the clock, it's annoying that some files early in boot may get
; incorrect dates.
;
; This is on r151022ce although OmniOSCE github repository contains the fixed
; version of usr/src/uts/i86pc/io/todpc_subr.c, so I assume this will exist in
; bloody releases.
;
; Can I expect this will show up in r151022ce (LTS) or r151024 automatically
; after some soak time though, or can I request this?  It's not clear if the
; Gitter lobby or IRC is preferred for requests like this ...


Hi Hugh,

I'll have a look at this and see whether it can be backported. Either way
we will be able to provide an installable hot-fix for you early next week.

The process that we use is to pull in changes from illumos gate and from
Joyent's illumos fork weekly and then assess the changes for back-port, so
if this is already in our bloody branch then it will not automatically appear
in older versions; it was presumably not selected.

The Gitter lobby is preferred for general support requests but we're also
around on IRC and check the mailing list from time to time. The core team
is all in Europe so there can be some latency due to time difference.

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] Cannot install Non-Global Zone

[Andy Fiddaman]

On Mon, 19 Feb 2018, Software Information wrote:

; Hi All
; I have been trying to understand the reason for an error I have been
; getting when I try to install a non-global zone. The error is below
;
; pkg install: The following pattern(s) did not match any allowable
; packages.  Try
; using a different matching pattern, or refreshing publisher information:
;
; entire@11-0.151022:20180108T221634Z
; ERROR: failed to install package

Could you provide the output of the following commands from the global
zone?

  pkg publisher
  pkg list -afv entire

If you would like to debug this more interactively, feel free to join our
gitter chat at https://gitter.im/omniosorg/Lobby or our IRC channel on
freenode https://webchat.freenode.net/ - channel #omnios

Thanks,

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] issue 8984 (fix for 6764 breaks ACL inheritance)

[Andy Fiddaman]

On Sun, 18 Feb 2018, Andries Annema wrote:

; Playing around with r151022, I may have bumped into the same issue here.
; The ACE's that I set on the parent directory are nicely inherited, but
; on top of that, another ACE for owner@, group@ and everyone@ is added.

Hi,

This does sound like the same issue and we have a fix for this currently in
testing for OmniOS r151022 which we plan to upstream when it's ready.

If you want to test the hot-fix, a package archive containing an updated
zfs pachage is available for download at:

https://downloads.omniosce.org/pkg/8984_r151022.p5p

to install please proceed as follows (assuming the downloaded archive
is in /root):

# pkg set-publisher -g /root/8984_r151022.p5p omnios
# pkg update -v --be-name=...
# init 6
# pkg set-publisher -G /root/8984_r151022.p5p omnios

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] problems running omni cmd..

[Andy Fiddaman]

On Tue, 13 Feb 2018, Brad Walker wrote:

; But, now I'm having a problem with building media..
;
; pkg install: The following pattern(s) did not match any allowable
; packages.  Try
; using a different matching pattern, or refreshing publisher information:
;
; illumos-gate@11-0.151024
; omnios-userland@11-0.151024

Have you built both the core illumos and OmniOS userland bits?

That's:

omni build_illumos
omni build_omnios

It looks like you're missing the second (userland) part.

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] problems running omni cmd..

[Andy Fiddaman]

On Mon, 12 Feb 2018, Brad Walker wrote:

; In addition, I would make the strong suggestion the following dependencies
; get added to the website..
;
; illumos-omnios
; omnios-build
; kayak

Hi Brad,

The instructions on the web page you mentioned already say to do that.

"First, create a GitHub account if you don't have one already and then use the
 web interface to fork the five repositories listed above.

 Once that's done
"

Had you not forked them at all or had you forked them from OmniTI's area
by mistake?

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] NTP Service error

[Andy Fiddaman]

On Thu, 25 Jan 2018, Software Information wrote:

; I ran
; # zonecfg -z zonename set limitpriv="proc_priocntl"
;
; But it resulted in:
; zonename:* invalid privilege: sys_mount*

You need to add the privilege, not replace what's already there:

# zonecfg -z zonename set limitpriv=default,proc_priocntl,sys_time

-- 
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] NTP Service error

[Andy Fiddaman]

On Thu, 25 Jan 2018, Software Information wrote:

; Hi. Thanks for replying.
;
; Running zonecfg -z zone_name info | grep limitpriv results in:
; limitpriv: default,dtrace_proc,dtrace_user,
;
; *sys_time*
; So that's still there

Try adding proc_priocntl too. Seems it's also needed by NTP.

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] NTP Service error

[Andy Fiddaman]

On Wed, 24 Jan 2018, Software Information wrote:

; Hi All
; Today I made the switch updating my r151020 box to omniosce in production
; and I am now left with just two issues.
;
; ntp won't start on one zone. All the dependent services are online.
;
; The log says:
; [ Jan 24 19:04:50 Method "start" exited with status 96. ]
; [ Jan 24 19:49:39 Enabled. ]
; [ Jan 24 19:49:40 Executing start method ("/lib/svc/method/ntp start"). ]
; [ Jan 24 19:49:40 svc.startd could not set context for method:  ]
; setppriv: Not owner

To run NTP in a zone, the zone needs the sys_time privilege. Is that
still present in the zone config?

# zonecfg -z ntp0 info | grep limitpriv
limitpriv: default,proc_priocntl,sys_time

I can't think why it would have gone away during an upgrade but it's
the first thing to check.

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] OmniOSce installer rpool slicing

[Andy Fiddaman]

On Fri, 5 Jan 2018, Schweiss, Chip wrote:

; I didn't think about that.  Thanks!
;
; On Fri, Jan 5, 2018 at 9:11 AM, Volker A. Brandt  wrote:
;
; > Yes.  Just drop to the shell from the installation menu and create your
; > rpool using fdisk, format, and zpool create.  Exit the shell and select
; > "use existing pool".

Some more hints on this at 
https://lists.omniti.com/pipermail/omnios-discuss/2017-November/009402.html

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] Renaming an interface

[Andy Fiddaman]

On Tue, 19 Dec 2017, Software Information wrote:

; Hi All
; I tried to rename an interface with the command *dladm rename-link e1000g0
; net0*
; and I got the error *rename operation failed: link busy. *This happens even
; after I down or disable the interface either with* ifconfig e1000g0* down
; or *ipadm disable-addr -t e1000g0/v4*
;
; How can I work around this issue or is it something I am overlooking?

You will have to delete both the address and the interface via ipadm.

For example:

ipadm delete-addr e1000g0/v4
ipadm delete-if e1000g0
dladm rename-link e1000g0 net0
ipadm create-if net0
ipadm create-addr -T static -a local=x.x.x.x/xx net0/v4

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] Best way to share files with Mac?

[Andy Fiddaman]

The package is now called just ‘gcc5’
gcc51 is there as a renamed package. 

> On 24 Nov 2017, at 20:28, Geoff Nordli  wrote:
> 
> That is what I am currently running.
> 
> #cat /etc/release
>   OmniOS v11 r151024c
>   Copyright 2017 OmniTI Computer Consulting, Inc. All rights reserved.
>   Copyright 2017 OmniOS Community Edition (OmniOSce) Association.
>   All rights reserved. Use is subject to license terms.
> 
> #pkg publisher
> PUBLISHER   TYPE STATUS P LOCATION
> extra.omniosorigin   online F 
> https://pkg.omniosce.org/r151024/extra/
> omnios  origin   online F 
> https://pkg.omniosce.org/r151024/core/
> 
> 
> I think i am missing something though, because it seems that it is installed
> 
> #sudo pkg install gcc51
> No updates necessary for this image.
> 
> It seems there is a gcc51 available in the catalog.
> 
> # pkg search gcc51
> INDEX  ACTION VALUE  PACKAGE
> pkg.fmri   setomnios/developer/gcc51 pkg:/developer/gcc51@5.1.0-0.151024
> 
> 
> but when I list the packages, it doesn't show up
> 
> pkg list | grep gcc5
> developer/gcc5 (omnios) 5.5.0-0.151024 i--
> developer/gcc5/libgmp-gcc5 (omnios) 6.1.2-0.151024 i--
> developer/gcc5/libmpc-gcc5 (omnios) 1.0.3-0.151024 i--
> developer/gcc5/libmpfr-gcc5 (omnios) 3.1.5-0.151024 i--
> 
> 
> any ideas?
> 
> thanks!!
> 
> 
> 
>> On 2017-11-24 11:49 AM, Manuel Oetiker wrote:
>> hi Geoff
>> 
>> you should switch to https://omniosce.org
>> 
>> cheers Manuel
>> 
>> 
>> - Original Message -
>>> From: "Geoff Nordli" 
>>> Cc: "omnios-discuss" 
>>> Sent: Friday, November 24, 2017 7:52:27 PM
>>> Subject: Re: [OmniOS-discuss] Best way to share files with Mac?
>>> I am trying to build it, but it uses gcc51.
>>> 
>>> That package isn't in the Omniosce core or extra repository.
>>> 
>>> Are you using the https://pkg.omniti.com/omnios/r151022 repo?
>>> 
>>> 
 On 2017-11-23 11:33 PM, Manuel Oetiker wrote:
 Hi
 
 We are using samba and it works well with macos.
 
 you can download our smb package from pkg.oetiker.ch or just run the 
 compilation
 by your selfe.
 we store our build script under
 https://github.com/oposs/pkg.oetiker.ch-build/tree/master/build/samba4
 
 disabling thumbnails preview helps speed up finder ...
 http://osxdaily.com/2013/01/10/disable-finder-icon-thumbnails-previews-mac-os-x/
 
 cheers Manuel
 
 - Original Message -
> From: "Geoff Nordli" 
> To: "omnios-discuss" 
> Sent: Friday, November 24, 2017 3:56:01 AM
> Subject: [OmniOS-discuss] Best way to share files with Mac?
> Hi.
> 
> I have to support a few mac machines connecting to a few file shares
> running Omnios.
> 
> They are reporting problems with the speed when using the "finder".
> 
> I see there is a netatalk package I can download and compile off of
> sourceforge, which looks fairly current.
> 
> Any suggestions on the best way forward to support Mac machines?
> 
> thanks,
> 
> Geoff
> 
> ___
> 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
> 
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

-- 
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] sudo update

[Andy Fiddaman]

On Thu, 23 Nov 2017, Al Slater wrote:

; Hi,
;
; I have just updated a number of my omniosce boxes to r151022y, bringing
; in the sudo updates in r151022u.
;
; All my machines have BSM auditing enabled, and now I am seeing the
; following when using sudo
;
; sudo: au_preselect: Bad file number

Hi, this is something we specifically tested along with the sudo update
since auditing was an area that changed quite a bit. Could you please check
that all of your packages are up-to-date (particularly SUNWcs) and that the
output of the following commands matches on your system?

r151022% auditrecord -e AUE_sudo

sudo
  program sudo See sudo(1m)
  event ID6650 AUE_sudo
  class   lo,ua,as (0x00061000)
  header
  subject
  exec_arguments   command args
  [text]   error message (failure only)
  return

r151022% grep sudo /etc/security/audit_event /usr/lib/audit/audit_record_attr
/etc/security/audit_event:# sudo event
/etc/security/audit_event:6650:AUE_sudo:sudo(1m):lo,ua,as
/usr/lib/audit/audit_record_attr:label=AUE_sudo

If the problem persists, please post the audit configuration that you're
using so we can try and replicate (auditconfig -getflags)

Thanks,

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] crash after upgrading to 151024

[Andy Fiddaman]

On Sun, 19 Nov 2017, Natxo Asenjo wrote:

; hi,
;
; I upgraded our home nas from the old stable ce to the new stable one. The
; process went ok, but after rebooting it has crashed twice:
;
; panicstack = unix:die+df () | unix:trap+e08 () |
; unix:_cmntrap+e6 () | unix:strncpy+28 () | lx_brand:lx_prctl+48a () |
; lx_brand:lx_syscall_enter+16f () | unix:brand_sys_syscall+1bd () |

This looks like a bug in the lx support in r151024 with a commit that came
in fairly recently (so wouldn't have been in r151022). Send me the crash
dump as per the private email I've sent you but I think I can see where
this is (and the problem) just from the above. The crash dump will confirm
and then we'll get it fixed in the next r151024 update.

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] r151104 to r151022 upgrade problem due to library/security/openssl

[Andy Fiddaman]

On Thu, 9 Nov 2017, Hugh McIntyre wrote:

;
; I have an old backup server at home which I'm trying to finally upgrade from
; r151014 to r151022 and then OmniOSCE.  There are no zones.
;
; I have followed the instructions under
; https://www.omniosce.org/legacy/upgrade_to_r151022.html, including "pkg
; update" before switching publisher, then set-publisher to r151022, and
; removing all ms/omniti.com and perl.omniti.com packages after initial
; problems.  But it still fails.  In case it makes a difference, ca-bundle and
; SunSSH->OpenSSH were already upgraded some time ago.
... snip ...
;
; Am I stuck needing a clean re-install, or is there a way to upgrade this box?

The first thing I would try is uninstalling the entire and omnios-userland
packages and then doing a full update.

# pkg uninstall entire omnios-userland
# pkg update --be-name=x
# init 6
# pkg install entire omnios-userland

Removing omnios-userland removes the specific version constraints but as it
is a dependency of entire you need to (temporarily) remove both.

The re-installation after reboot may fail depending on what the exact
cause of your problem is in which case leave them uninstalled until you
have completed the move to OmniOSce and then they should work.

If you want to chat as you work through this, come on over to the lobby
at https://gitter.im/omniosorg/Lobby

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] wiki problems at omniti

[Andy Fiddaman]

On Wed, 8 Nov 2017, Jeff Stockett wrote:

; I've got a few servers still running r151020 I was going to upgrade - but the 
wiki/download link seems to have a problem:
; Proxy Error
; The proxy server could not handle the request GET 
/wiki.php/Installation.
;
; Reason: Error during SSL Handshake with remote server
; Is this a permanent thing or just temporary?  Is there a way to upgrade to 
omniosCE without first upgrading to R151022?

Our import of the OmniTI wiki is up at http://wiki.omniosce.org/
It's safest to go via OmniTI r151022 since that's the process that we
have tested.

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] PERL booleans?

[Andy Fiddaman]

On Tue, 7 Nov 2017, Dan McDonald wrote:
;
; > On Nov 7, 2017, at 10:26 AM, Andy Fiddaman <omn...@citrus-it.net> wrote:
; >
; > Note that BOOL was deprecated a long, long time ago in glib. I haven't been
; > able to find an exact reference but it's showing up as deprecated in the
; > documentation from 15 years ago.
;
; So it sounds like if this change is upstreamed nobody with older build 
environments will care?
;
; If I'm right, would you please file an illumos issue to push that upstream.  
I'll be reviewer #1.

If nobody objects in the next day or two, I'll start the upstream process.
It's on our upstream candidate list but the dust is still settling from the
release.

Thanks,

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] PERL booleans?

[Andy Fiddaman]

On Tue, 7 Nov 2017, Dan McDonald wrote:

; I upgraded my HDC to OmniOSce r151024, and did some nightly builds.  After 
re-rewhacking PERL_VERS, I managed to get a MOSTLY clean build save for:
;
; >  Build warnings (non-DEBUG) 
; >
; > WARNING: The token "BOOL" is deprecated; use "BOOLEAN" instead
;
; The file $SRC/cmd/hal/hald/hald_marshal.list uses "BOOL" and under an updated 
glib (which is in the new OmniOS) should be "BOOLEAN".

Note that BOOL was deprecated a long, long time ago in glib. I haven't been
able to find an exact reference but it's showing up as deprecated in the
documentation from 15 years ago.

Glib recently rewrote the marshal generator in python and now it emits
these deprecation warnings, hence the change in output.

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] weird issue with active BE on new Omnios CE install

[Andy Fiddaman]

On Tue, 12 Sep 2017, Joseph Boren wrote:

; Greetings,
;
; Had a strange thing happen with a new server build today.  Installing
; r151022q on a new Supermicro X11SSH-CTF motherboard, downloaded the flash
; drive image, burned to a 64Gb USB flash drive, installed just fine,
; rebooted, all is well.  Installed napp-it, which creates a new BE and sets
; it active.  Rebooted and let it try to boot into the new BE and got this:
;
; Loading now
; can't find 'now'
; can't find 'now'

How are you rebooting?
If you are using 'reboot now' then it will result in this behaviour.

Use just 'reboot' or 'init 6' - it isn't Linux : )

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] [zfs] SAS 9305-16e HBA support in Illumos

[Andy Fiddaman]

On Fri, 8 Sep 2017, Schweiss, Chip wrote:

; Robert,
;
; That is awesome.   I'd definitely be interested in testing this.
;
; I'll get my feet wet with building OmniOS CE with it.

Hi Chip,

If you don't already know about it you might want to take a look at
https://github.com/omniosorg/omni/ which makes building OmniOS on
OmniOS nice and easy, globally or in a zone.

You won't need to build the userland bits so the whole process should
take around an hour.

If you run into trouble, come and chat to us at
https://gitter.im/omniosorg/Lobby

Cheers,

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] "pkg set-publisher" looking for certificates in /etc/openssl/certs

[Andy Fiddaman]

On Tue, 29 Aug 2017, Olaf Marzocchi wrote:

; Unable to contact valid package repository:
; https://pkg.omniosce.org/r151022/core
; Encountered the following error(s):
; Transport errors encountered when trying to contact repository.
; Reported the following errors:
; Unable to locate a CA directory: /etc/openssl/certs
; Secure connection is not available.
; ...
; Could you please give me some hints?

Yes, try:

# pkg set-property ca-path /etc/ssl/certs

then set the publishers again. You're the second person to have reported
this problem and I don't know why your package root would have the
wrong CA path on it.
If you need any more help with this, please log onto our gitter Lobby
at https://gitter.im/omniosorg/Lobby

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] failure in set-publisher for a zone to the new omniosce repository

[Andy Fiddaman]

On Fri, 25 Aug 2017, Paul Jochum wrote:

; ca-path/etc/openssl/certs

pkg -R /... set-property ca-path /etc/ssl/certs

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] failure in set-publisher for a zone to the new omniosce repository

[Andy Fiddaman]

What is the trust-anchor-directory property set to on the image root?

% pkg property trust-anchor-directory
PROPERTY   VALUE
trust-anchor-directory etc/ssl/pkg

(or pkg -R /rpool/zones/lss-ganglia02/root property)

Andy

On Fri, 25 Aug 2017, Paul Jochum wrote:

; Hi John and Andy:
;
; I tried it from the host, and received the same error message (output
; below).  I know the host has internet connectivity, since I was able to use
; nearly the same command (without the -R option of the zone name/path), to set
; the publisher on the host.  In the example below, the wget command copies the
; new cert to *.pem.1, (since I had previously used wget to set-publisher on the
; host), and that file is identical to the omniosce-ca.cert.pem file I used to
; set-publisher on the host.
;
; # zoneadm list -cv
;   ID NAME STATUS PATH BRANDIP
;0 global   running/ ipkg shared
;1 lss-ganglia02running/rpool/zones/lss-ganglia02 lipkgshared
; # zoneadm -z lss-ganglia02 halt
; # zoneadm -z lss-ganglia02 detach
; # /usr/bin/wget -P /etc/ssl/pkg
; https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem
; --2017-08-25 08:19:59--
; https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem
; 
; Length: 2175 (2.1K) [application/x-x509-ca-cert]
; Saving to: '/etc/ssl/pkg/omniosce-ca.cert.pem.1'
;
; omniosce-ca.cert.pe 100%[===>]   2.12K --.-KB/sin 0s
;
; 2017-08-25 08:20:00 (209 MB/s) - '/etc/ssl/pkg/omniosce-ca.cert.pem.1' saved
; [2175/2175]
;
; # /usr/bin/pkg -R /rpool/zones/lss-ganglia02/root set-publisher -P -g
; https://pkg.omniosce.org/r151022/core/ omnios
; pkg set-publisher: The origin URIs for 'omnios' do not appear to point to a
; valid pkg repository.
; Please verify the repository's location and the client's network
; configuration.
; Additional details:
;
; Unable to contact valid package repository
; Encountered the following error(s):
; Unable to contact any configured publishers.
; This is likely a network configuration problem.
; Unable to locate a CA directory: /etc/openssl/certs
; Secure connection is not available.
;
; Thanks,
; Paul
;
; On 08/24/2017 07:03 PM, John D Groenveld wrote:
; > In message , Paul Jochum
; > writes
; > :
; > > configuration.
; > > Additional details:
; > >
; > > Unable to contact valid package repository
; > > Encountered the following error(s):
; > > Unable to contact any configured publishers.
; > > This is likely a network configuration problem.
; > > Unable to locate a CA directory: /etc/openssl/certs
; > > Secure connection is not available.
; > >
; > > This worked fine on the host of that zone, and on other zones (located
; > > on other hosts, but all at the same level of software). Any suggestions
; > > on how to fix this?  (And I checked, there is no /etc/openssl directory
; > > on this or any of my other omnios machines, but there is the
; > > /etc/ssl/certs directory and it looks very similar to other
; > > /etc/ssl/certs on machine which did not have a problem updating the
; > > publisher)
; > Shot in the dark assuming lipkg brand zone:
; > # zoneadm -z $zone halt
; > # zoneadm -z $zone detach
; > # /usr/bin/wget -P $zonepath/root/etc/ssl/pkg \
; > https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem
; > # pkg -R $zonepath/root set-publisher -P \
; > -g https://pkg.omniosce.org/r151022/core/ omnios
; > # zoneadm -z $zone attach -U
; >
; > John
; > groenv...@acm.org
; > ___
; > 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
;
-- 
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] failure in set-publisher for a zone to the new omniosce repository

[Andy Fiddaman]

On Thu, 24 Aug 2017, Paul Jochum wrote:

; Hi All:
;
; I am working on updating a number of omnios machines from r151022 (under
; OmniOS TI) to R151022 (under OmniOS CE).  I am having problems updating one of
; my zones.  I am at the point now where I have unset all of the publishers in
; that zone, but I can not add the omniosce publisher.
;
; # pkg publisher
; PUBLISHER   TYPE STATUS P LOCATION
; #
; # /usr/bin/pkg set-publisher -P -g https://pkg.omniosce.org/r151022/core/
; omnios

Try setting it from the global zone. This looks like the zone doesn't have
direct Internet connectivity.

global% pkg -R /path/to/zone/root set-publisher ...

Andy

-- 

For OmniOSce Support, join us at https://gitter.im/omniosorg/Lobby

-- 
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] install GNUHEALTH

[Andy Fiddaman]

On Fri, 18 Aug 2017, Dirk Willems wrote:

; Hello,
;
;
; I try to install GNUHEALTH on OmniOSCE
;
;
; fatal error: limits.h: No such file or directory
;  #include_next   /* recurse down to the real one */
;^~
; compilation terminated.
; error: command 'gcc' failed with exit status 1

Have you installed the system/header package?

To make sure you have everything needed for compilation check the wiki
page at http://wiki.omniosce.org/DevEnv.html

Regards,

Andy

-- 

For OmniOSce support, please visit the lobby at:
https://gitter.im/omniosorg/Lobby

-- 
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

[OmniOS-discuss] ANNOUNCEMENT - OmniOSce r151022k is out

[Andy Fiddaman]

OmniOSce r151022k update now available.

This is the weekly update for w/c 31st of July 2017 and contains security
updates for the ncurses and bind userland packages. A reboot is not required
although any applications using the ncurses or bind libraries should be
restarted to pick up the changes.

Full release notes can be found at

https://github.com/omniosorg/omnios-build/blob/r151022/doc/ReleaseNotes.md

Any problems or questions, please get in touch via the Lobby at

https://gitter.im/omniosorg/Lobby

Happy updating,

Andy and the rest of the OmniOSce team.

-- 
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 CE question: will there be a LTS stable release?

[Andy Fiddaman]

On Wed, 26 Jul 2017, Peter Tribble wrote:

; Now the current release (151022) is marked as LTS. So at least you're in
; a reasonably stable place right now and have options, with no need to
; commit to anythjing for a few months.

Just to be clear, r151022 was marked as LTS by OmniTI. Those three letters
did make it into one of our announcements (the second one I think) but we
are not currently considering r151022 to be an LTS release.

r151024 is currently pencilled in for late November (6 months after the
release of r151022) and once it arrives, r22 will continue to be
supported for 6 months, until r26 lands. We would encourage people to move
to r24 during that time rather than waiting until r22 stops being supported.

As Tobi has said, we're open to discussion and interested in people's views
https://gitter.im/omniosorg/Lobby

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

[Andy Fiddaman]

On Mon, 24 Jul 2017, Davide Poletto wrote:

; 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:
;
; pkg:/service/network/ssh-common

The release notes for r151014
( https://omnios.omniti.com/wiki.php/ReleaseNotes/r151014 )
say to run this command to achieve the switch and I remember doing this
successfully when it first came out.

/usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject 
pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh pkg:/network/openssh 
pkg:/network/openssh-server

This assumes you are still on the r151014 publisher.

Your second command was close but you should remove the --reject at well as
the ssh-common component.

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] Local zone regression in CE bloody

[Andy Fiddaman]

On Fri, 21 Jul 2017, Ryan Zezeski wrote:

; I couldn't find any specific instructions for moving to bloody so I kind
; of made them up based on the previous omnios upgrade instructions. I
; went ahead and set the signature-policy to ignore and now I'm good.

Sorry for the delay, timezone difference!

Yes, Dan's right, we haven't changed the signing policy for bloody, it
is not signed.

Note that we have reverted this so if you want to install the broken version
you will have to explicitly install
  pkg://omnios/SUNWcs@0.5.11-0.151023:20170718T063046Z

Some more analysis can be found in our issue at

https://github.com/omniosorg/illumos-omnios/issues/18

and here's some more dtrace output with the broken version.

bloody# ./dl.d
dtrace: script './dl.d' matched 3 probes
CPU IDFUNCTION:NAME
  6  88316   dlmgmt_setzoneid:entry
  dlmgmtd`dlmgmt_setzoneid
  dlmgmtd`dlmgmt_handler+0x96
  libc.so.1`__door_return+0x3d
Zone ID: 0
New zone id: 0

  6  88318  dlmgmt_setzoneid:return
Old zone id: 1
Err: 17

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] Local zone regression in CE bloody

[Andy Fiddaman]

On Fri, 21 Jul 2017, Jim Klimov wrote:

; Hi all,
;
; I have an OmniOS bloody box that was last running 151023. Yesterday I updated 
it to latest available original omnios from May 15 or so, and updated that BE 
to omniosce bloody. Between the two, zone shutdown stopped working for me (both 
ipkg and lx), with the ce variant claiming that "datalinks remain in zone after 
shutdown / unable to unconfigure network interfaces in zone / unable to destroy 
zone".
;
; When the zone boots it seems okay and usable, but when trying to halt it - 
becomes "down" and I can not change the state (no boot/mount/ready/... options 
succeed); killing its zoneadmd and wiping then/var/run/zones also does not help 
- only GZ reboot.

Thanks Jim, confirmed here too.
We are building a new bloody at the moment so will test with that and then
work on a fix. I've opened an issue for this at

https://github.com/omniosorg/illumos-omnios/issues/18

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] Upgrade from r151020 to r151022 - python conflicts and fails.

[Andy Fiddaman]

On Thu, 13 Jul 2017, Svavar ?rn Eysteinsson wrote:

; As anyone encounter a upgrade fail from 20 to 22 ?
; I'm unable and get conflicts regarding python.
;
; Current system is :
; OmniOS v11 r151020
; OmniOS 5.11 omnios-r151020-4151d05  March 2017
;
; Before I did as the upgrade instructions stated, :
;
;
; /usr/bin/pkg unset-publisher omnios
; /usr/bin/pkg set-publisher -P --set-property 
signature-policy=require-signatures -g https://pkg.omniti.com/omnios/r151022/ 
omnios
;
;
; And my current publishers are :
;
; PUBLISHER   TYPE STATUS P LOCATION
; omnios  origin   online F 
https://pkg.omniti.com/omnios/r151022

What are the versions of of your web/ca-bundle ad package/pkg packages?
Does this system have any zones? If so, what brand?

It is worth making sure that 'pkg' is up-to-date before attempting the upgrade:

   > pkg install pkg:/package/pkg

and the release notes state that web/ca-bundle must be up-to-date.

   > https://omnios.omniti.com/wiki.php/Upgrade_to_r151022

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] Questions about - End the uncertainty -

[Andy Fiddaman]

On Wed, 5 Jul 2017, Guenther Alka wrote:

; - Is there an option to fix serious bugs or problems in OmniOS for a limited
; time like 1 year or at least end of the year? This would help until a sucessor
; (less likely OmniOS 151024, maybe next OpenIndiana snap with a stable subset)
; is available. LX would then remain an OmniOS option in the meantime (I would
; not dare to ask about an upstream).

OmniOSce (community edition) is gaining momentum. I would expect updated
r151022 and bloody repositories to be online in the next few weeks and
an r151024 to follow in due course. It's early days and the release model
hasn't been discussed in detail yet but join in at
https://gitter.im/omniosorg/Lobby

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] Bug ?

[Andy Fiddaman]

On Sun, 2 Jul 2017, Tobias Oetiker wrote:

; not to join forces seem to be a pitty ... how about hosting that fork on
; https://github.com/omniosorg and starting to accept PRs there

At the moment the fork is very much driven by our requirements and not
considering a wider community. We're ignoring fixes that don't directly
affect us and pulling others that would historically only have made it
into bloody.

I do think we need to set up a fork on github.com/omniosorg but this one
probably isn't it. I'm on the gitter chat but the last thing you said on
there was "I have also on purpose NOT forked the omnios repo into the omnios
org thing yet". I'll take the conversation over there.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Bug ?

[Andy Fiddaman]

On Thu, 29 Jun 2017, Guenther Alka wrote:

; Unless there are news regarding OmniOS my stance is
;
; - OmniOS 151022 is a freeze of current Illumos + LX. At the moment it is the
; most stable and feature rich free Illumos general use server distribution with
; the addition LX zones. As there is no repo and development outside OmniTi it
; is freezed. There are no signs from OmniTi to add any fixes. As packages are
; signed it does not work outside OmniTi. As OmniOS 151023 is identical without
; signed packages a community based repo based on it with possible fixes as
; 151022ce (community edition) is a suggestion (but sadly I am not an OS
; developer).

Momentum does appear to be lacking unfortunately. Here at Citrus we have
forked the OmniOS repositories and are continuing to maintain them for
internal use while we consider options.

We have kept omnios-build packages up-to-date where there are security
fixes (two Bind updates, 7-zip CVE patch, OpenSSL [IIRC]) and backported a
handful of illumos changes that are relevant to us. We can keep going like
this for a good while and I still hope that a community OmniOS will get
going (we've offered to contribute engineering resource as have others)
and we can make the switch.

Since we use LX zones to an extent, SmartOS is the other route we are
evaluating at the moment.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] p7zip: CVE 2016-9296

[Andy Fiddaman]

On Fri, 9 Jun 2017, Aur?lien Larcher wrote:

; Hi,
; when I bumped p7zip in oi-userland I noticed that CVE 2016-9296 still
; affects 16.02: we had this patch against 15.14.1 and I was surprised that
; it was still valid, then I checked it on the usual websites.
; Out of curiosity I looked if you have it in omnios-build and it is
; apparently missing.
; Kind regards,
;
; Aur?lien

Thanks for this, I've updated my fork of omnios-build. I could raise a pull
request against omnios-build but I don't think anyone is looking at these
yet.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] To the OmniOS Community

[Andy Fiddaman]

On Thu, 1 Jun 2017, qutic development wrote:

; Hi Theo,
;
; that is a word!
;
; > I was hoping not to be the first, but I will attempt to lead by example. 
I'll pledge my time to do required security package publications on 014 and 
022. As security issues with packages in core arise, I will update the build 
system, re-roll the packages and publish them.
;
; There are a few security related releases since Dan left:
;
; - sudo
; - openssl (bugfix)
; - openjdk 7
; - bind 9
; - ldap
;
; As 014 and 022 have signed packages, nobody else than OmniTi can build 
packages for these, right?

I have added a pull request for the openssl update to omnios-build, just to
see if anyone was picking these up.

https://github.com/omniti-labs/omnios-build/pull/105

I've updated my local omnios r22 package mirror and updated our servers too
but I've obviously had to disable package signatures.

Seems we don't currently have a maintained package repository although
people (including me) have volunteered to maintain it.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Oddity following upgrade to r151022

[Andy Fiddaman]

On Sun, 14 May 2017, Dan McDonald wrote:

; > On May 14, 2017, at 5:33 PM, Andy Fiddaman <omn...@citrus-it.net> wrote:
; >
; > but svc:/system/metainit:default is still there and is maintenance on
; > all servers.
;
; I did multiple 020 to 022 (no-zones) upgrade tests, and I didn't see this.
;
; > bonnet# svcprop metainit | grep manifest
; > 
manifestfiles/code_omnios-151006_illumos-omnios_usr_src_cmd_lvm_util_metainit_xml
 astring /code/omnios-151006/illumos-omnios/usr/src/cmd/lvm/util/metainit.xml
; > manifestfiles/lib_svc_manifest_system_metainit_xml astring 
/lib/svc/manifest/system/metainit.xml
; >
; > although I seem to have these on a few other services too, all
; > with 'omnios-151006' as part of the name.
;
; Yeah... this may explain things.  Not unlike the bootenv.rc report from 
earlier, maybe having customizations in these caused some problems?

We have't made any local modifications to this though. The servers were
originally built on r151006 and then upgraded to each even release as it
came out. That's the only reason I can think of for the different
experience between this and upgrading from a vanilla r151020.

Anyway, 'svccfg delete metainit; svccfg delete rpc/smserver' got me back
up and running although I still can't explain the strange ZFS mount order
(child filesystems mounting before parents). That seems to be ok now
though; I'll try and replicate it again when I update the other data
centre.

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Interesting Nessus Scan Result

[Andy Fiddaman]

On Thu, 20 Apr 2017, Software Information wrote:

; Thanks for replying. I used the advanced scan (please see screenshot below)
;  and just to note also, this showed up after I updated Nessus to version
; 6.10.4 yesterday and ran the scan again.

I'm running 6.10.5 here, not sure when that was released. I'll try another
scan with the default advanced settings and see if I can replicate what
you're seeing.

Andy


-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] VirtualBox 5.1 - Missing dependencies

[Andy Fiddaman]

On Sun, 9 Apr 2017, Geoff Nordli wrote:

;
; Hi Andy.
;
; Any thoughts on why changing the autoresponse file is still triggering the
; dependency error?
;
; # /usr/sbin/pkgadd -r autoresponse -d
; VirtualBox\-5.1.18\-SunOS\-amd64\-r114002.pkg all
;
; Processing package instance  from
; VirtualBox-5.1.18-SunOS-amd64-r114002.pkg>
;
; Oracle VM VirtualBox(i386) 5.1.18,REV=2017.03.15.16.41.114002
; Oracle Corporation
; ## Executing checkinstall script.
; Checking package dependencies...
; ## Missing packages:
; ## IPS :  system/library/gcc/gcc-c++-runtime or system/library/gcc-45-runtime
; system/library/gcc/gcc-c-runtime or system/library/gcc-45-runtime
; ## SVr4:  SUNWPython SUNWPython-devel
; ##
; ## Please install either the IPS or SVr4 packages before installing
; VirtualBox.
; pkgadd: ERROR: checkinstall script did not complete successfully
;
; Installation of  failed.
; No changes were made to the system.

Ah, it's because I did the test installation in a zone. The checkinstall
exits with success if the zone name is not 'global'.

Try this:

build# pkgtrans VirtualBox-5.1.18-SunOS-amd64-r114002.pkg . all
Transferring  package instance
build# rm SUNWvbox/install/checkinstall
build# sed -i /checkinstall/d SUNWvbox/pkgmap
build# pkgadd -d . SUNWvbox

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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 User Survey

[Andy Fiddaman]

On Wed, 5 Apr 2017, Dan McDonald wrote:

; OmniTI would like to hear from OmniOS users.  We have a survey that we'd 
appreciate you taking.

Q3. I just put the slider somewhere near the right place (4 years) which
resulted in 72 appearing in the box. (I see the question is fixed now).

Q4. In answering this one I didn't consider things which are my favourite
features of /illumos/ (zones, dtrace, crossbow, smf, zfs, ...) - wouldn't
have been able to choose just one anyway. That left me with what
OmniOS-specific features I like.  Hope that's what you were after!

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Ang: LX Zones question: Do you miss ipadm(1M)?

[Andy Fiddaman]

On Thu, 30 Mar 2017, Dan McDonald wrote:

;
; > On Mar 30, 2017, at 5:11 PM, Brian Hechinger  wrote:
; >
; > I'd like to see a way that network configuration can be disabled from 
within the zone so that it's set by the host admin and not the zone admin 
(assuming they are different people).
;
; I thought more people would be in agreement with you, but that appears not to 
be the case.
;
; Rewriting lxinit & friends to allow this sort of admin model is going to be 
harder than I thought, and since r151022 is already late relative to prior 
releases (it's a cadence-breaker thanks to Loader, Python2.7, and 
Kayak-for-ISO), I don't know if getting ipadm(1M) for LX zones would work.  
You're the strongest endorser of doing it so far.

I read Brian's comment as wanting to stop network configuration from within
the zone => no ipadm. That's what I want too - if I set up a Linux zone and
hand control over, I don't want the zone root user to be able to change
the IP address.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Ang: LX Zones question: Do you miss ipadm(1M)?

[Andy Fiddaman]

On Thu, 30 Mar 2017, Ludovic Orban wrote:

; I personally don't need ipadm in my LX zones, nerver missed it and I'm
; pretty certain I wouldn't use it even if it was available.

Same here.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] VirtualBox 5.1 - Missing dependencies

[Andy Fiddaman]

On Wed, 29 Mar 2017, Geoff Nordli wrote:

; Hi.
;
; Anyone have any luck installing VBox 5.1 on Omnios?
;
; I am missing:
;
; IPS :  system/library/gcc/gcc-c++-runtime or system/library/gcc-45-runtime
; system/library/gcc/gcc-c-runtime or system/library/gcc-45-runtime

# gtar zxvf ~/dl/VirtualBox-5.1.18-114002-SunOS.tar.gz
# ls
LICENSE
ReadMe.txt
VirtualBox-5.1.18-SunOS-amd64-r114002.pkg
autoresponse

# sed -i 's/quit/nocheck/' autoresponse
# pkgadd -r autoresponse -d VirtualBox-5.1.18-SunOS-amd64-r114002.pkg all

Binaries seem to run, didn't look any further.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Loader serial console

[Andy Fiddaman]

In case anyone else is experimenting with the new loaded in bloody and
uses a serial console (or serial redirection), this is what I've done to
my test server to continue using the serial console:

Create new file /boot/conf.d/serial and add:

boot_multicons="YES"
boot_serial="YES"
comconsole_speed="115200"
osconsole="ttya,text"
console="ttya,text"
ttya-mode="115200,8,n,1,-"


I'm not entirely sure if all of this is necessary - I borrowed some of
it from BSD tutorials - but it works for me.

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Improved, but still alpha, ISO installer

[Andy Fiddaman]

On Tue, 7 Mar 2017, Dan McDonald wrote:

;
; > On Mar 7, 2017, at 11:28 AM, Andy Fiddaman <omn...@citrus-it.net> wrote:
; >
; > I'm a bit late to the party but I've downloaded this and burned it to a
; > CD (old school, I know) and tried booting a Dell R620. It hangs just after
; > printing:
; >
; > loading ficl string class
; > /
; >
; > With just that / on the last line.
; >
; > Tried a few times but it always hangs at the same place.
; >
; > Anything useful I can try?
;
; Hmmm... I wonder if the .iso image is a bit too large for an actual physical 
CD?
;
; Can you burn it onto a dvd?

Morning,

Same result with a DVD unfortunately.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Improved, but still alpha, ISO installer

[Andy Fiddaman]

On Wed, 1 Mar 2017, Dan McDonald wrote:

; Please refresh your copy by downloading here:
;
;   http://kebe.com/~danmcd/webrevs/r151021-kayak.iso

I'm a bit late to the party but I've downloaded this and burned it to a
CD (old school, I know) and tried booting a Dell R620. It hangs just after
printing:

loading ficl string class
/

With just that / on the last line.

Tried a few times but it always hangs at the same place.

Anything useful I can try?

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] On pkg(1) behavior in r151022

[Andy Fiddaman]

On Mon, 20 Feb 2017, Dan McDonald wrote:

; a.) Accept "-r" as a requirement, and document to users that the behavior 
between 014-020 and 022-beyond will change.

This one gets my vote. It will actually improve our workflow here!

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Kernel panel

[Andy Fiddaman]

Anyone interested in more information from a kernel panic this morning?

OmniOS v11 r151020

carolina# (24) uname -a
SunOS carolina 5.11 omnios-bed3013 i86pc i386 i86pc

> ::status
debugging crash dump vmcore.0 (64-bit) from carolina
operating system: 5.11 omnios-bed3013 (i86pc)
image uuid: 5e489eff-62c1-4ce7-deb5-c8b48d8aec0f
panic message:
BAD TRAP: type=e (#pf Page fault) rp=d00042bccb10 addr=30 occurred in
module
 "ip" due to a NULL pointer dereference
dump content: kernel pages only
> ::stack
ip_quiesce_conn+0x2a(d00d413e7a00)
udp_do_close+0x40(d00d413e7a00)
udp_close+0x19(d00d413e7a00, 83, d00d86e21a88)
so_close+0x7a(d00d21f315a0, 83, d00d86e21a88)
socket_close_internal+0x1b(d00d21f315a0, 83, d00d86e21a88)
socket_vop_close+0xe8(d00d21f34440, 83, 1, 0, d00d86e21a88, 0)
fop_close+0x61(d00d21f34440, 83, 1, 0, d00d86e21a88, 0)
closef+0x5e(d02783669850)
closeandsetf+0x398(38, 0)
close+0x13(38)
sys_syscall+0x196()

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] uname -v change

[Andy Fiddaman]

No problem - easily worked around.

Andy

On Wed, 4 Jan 2017, Dan McDonald wrote:

; It was a build accident, not intentional.
;
; Next time kernels get updated, it'll be fixed. If this is breaking scripts, 
I'll push an update that fixes it (at the cost of requiring another reboot).
;
; I'm very sorry about it.  It's my fault for making build environment 
assumptions.  A very recent omnios-build push will prevent things like this 
going forward.
;
; Sorry,
; Dan
;
; Sent from my iPhone (typos, autocorrect, and all)
;
; > On Jan 4, 2017, at 4:01 AM, Andy Fiddaman <omn...@citrus-it.net> wrote:
; >
; > Morning,
; >
; > Just finished updating servers after last week's update to r151020 and
; > noticed that the uname -v output has lost the revision information.
; >
; > Before:
; >
; > SunOS carolina 5.11 omnios-r151020-b5b8c75 i86pc i386 i86pc
; >
; > After:
; >
; > SunOS reaper 5.11 omnios-bed3013 i86pc i386 i86pc
; >
; > Was that deliberate?
; >
; > Thanks,
; >
; > Andy
; > --
; > Citrus IT Limited | +44 (0)870 199 8000 | 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

[OmniOS-discuss] uname -v change

[Andy Fiddaman]

Morning,

Just finished updating servers after last week's update to r151020 and
noticed that the uname -v output has lost the revision information.

Before:

SunOS carolina 5.11 omnios-r151020-b5b8c75 i86pc i386 i86pc

After:

SunOS reaper 5.11 omnios-bed3013 i86pc i386 i86pc

Was that deliberate?

Thanks,

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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 r151020 is now out!

[Andy Fiddaman]

On Sun, 6 Nov 2016, Olaf Marzocchi wrote:

; Hi Andy,
; thanks for the help, especially on Sunday!
;
; I blindly followed the instructions provided on
; https://omnios.omniti.com/wiki.php/Upgrade_to_r151020 but yes, the
; recommendation of s/sshd-kbdint/sshd/ was (at least in my case) wrong and by
; reverting to sshd-kbdint I got the 2FA back.

That's strange because the advice in the wiki came from me originally!
I definitely needed to update my pam.conf when I first switched to
OpenSSH...

reaper# (38) pkg history -l | ggrep -B5 -A5 openssh | head -7
New Boot Env. UUID: (None)
  Snapshot: (None)
Start Time: 2015-11-20T12:58:24
  End Time: 2015-11-20T12:58:43
Total Time: 0:00:19
   Command: /usr/bin/pkg install --no-backup-be --reject pkg:/network/ss
h --reject pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh pkg:/netwo
rk/openssh pkg:/network/openssh-server
 Release Notes: No

That was in November 2015 but there's a patch at 
https://github.com/omniti-labs/omnios-build/blob/master/build/openssh/patches/0011-PAM-enhancements-for-Solaris.patch
 which looks like it changes the pam service back to sshd-kbdint (assuming 
default options in sshd_config). That was commited in March 2016 so it seems 
that the pam.conf update is no longer required.

Regards,

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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 r151020 is now out!

[Andy Fiddaman]

On Sun, 6 Nov 2016, Olaf Marzocchi wrote:

; Hi,
; I started updating my server, therefore OpenSSH first. After that one I
; restarted the server.
; I can login with my pass but two factor authentication doesn't work anymore,
; I'm never asked for it.

I've just checked one of my servers that uses 2FA and I have both
sshd-kbdint and sshd at the end of pam.conf. Perhaps you need both?

sshd-kbdint auth requisite  pam_authtok_get.so.1
sshd-kbdint auth required   pam_dhkeys.so.1
sshd-kbdint auth required   pam_unix_cred.so.1
sshd-kbdint auth required   pam_unix_auth.so.1
sshd-kbdint auth required   /opt/CITotp/lib/pam_mobile_otp.so

sshdauth requisite  pam_authtok_get.so.1
sshdauth required   pam_dhkeys.so.1
sshdauth required   pam_unix_cred.so.1
sshdauth required   pam_unix_auth.so.1
sshdauth required   /opt/CITotp/lib/pam_mobile_otp.so


Debug output from sshd says:

debug3: /etc/ssh/sshd_config:100 setting UsePAM yes
/etc/ssh/sshd_config line 100: ignoring UsePAM option value. This option is 
always on.
debug3: PAM service is sshd-none
debug3: PAM service is sshd-pubkey
debug3: PAM service is sshd-kbdint

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] [developer] OmniOS r151020 is now out!

[Andy Fiddaman]

On Fri, 4 Nov 2016, Dan McDonald wrote:
;   - VIM 8.0

Thanks Dan - we've now upgraded half of our servers without zones on them
without any problems.

One note for anyone who has created their own system-wide vimrc file -
/usr/share/vim/vimrc - vim8 will override options set in there with
the defaults in /usr/share/vim/vim80/defaults.vim. That's a change
in behaviour from earlier vim versions.

To stop the defaults.vim file from being used at all, add this to the system
vimrc:

let skip_defaults_vim=1

Another solution for anyone who wants to load the system defaults but then
override specific options is the following. In this example I want to
turn off the 'ruler' option for everyone by default but still take
advantage of the defaults.

# cat /usr/share/vim/vimrc
unlet! skip_defaults_vim
source $VIMRUNTIME/defaults.vim
let skip_defaults_vim=1
set noruler

Regards,

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] NEED FEEDBACK: VIM8 and "vi" behavior

[Andy Fiddaman]

On Tue, 18 Oct 2016, Dan McDonald wrote:

; VIM8 is in the omnios-build master branch for next-bloody and r151020.
;
; VIM8's defaults are more VIM-like and less classic-VI like.
;
; Would it kill people if I made "vi" act like "vim -C"?  Or would that be MORE 
surprising?

No preference here. We replace /usr/share/vim/vimrc with our own version
anyway.

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Pre-018 bloody now out

[Andy Fiddaman]

Just one oddity:

# pkg update
No updates available for this image.
zsh: exit 4 pkg update
# pkg list -u
NAME (PUBLISHER)  VERSIONIFO
developer/gnu-binutils2.25-0.151017  i--


On Wed, 13 Apr 2016, Andy Fiddaman wrote:

;
; On Wed, 13 Apr 2016, Dan McDonald wrote:
;
; ; In anticipation of r151018's release, the bloody that will essentially 
comprise r151018 is now available for "pkg update" and for ISO/USB/Kayak 
download from the OmniOS Installation page:
; ;
; ; http://omnios.omniti.com/wiki.php/Installation
;
; Thanks Dan, I've just upgraded one of our test servers to this with no
; problems using the following process. I'll do some more testing but it
; looks good so far. There are no non-global zones on this server however.
;
;   beadm create bloody
;   mkdir /tmp/bloody
;   beadm mount bloody /tmp/bloody
;   pkg -R /tmp/bloody set-publisher \
; -G http://pkg.omniti.com/omnios/r151016/ \
; -g http://pkg.omniti.com/omnios/bloody/ \
;   --unset-property signature-policy \
;   omnios
;   pkg -R /tmp/bloody update
;   beadm umount bloody
;   beadm activate bloody
;
; Andy
;
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Pre-018 bloody now out

[Andy Fiddaman]

On Wed, 13 Apr 2016, Dan McDonald wrote:

; In anticipation of r151018's release, the bloody that will essentially 
comprise r151018 is now available for "pkg update" and for ISO/USB/Kayak 
download from the OmniOS Installation page:
;
;   http://omnios.omniti.com/wiki.php/Installation

Thanks Dan, I've just upgraded one of our test servers to this with no
problems using the following process. I'll do some more testing but it
looks good so far. There are no non-global zones on this server however.

  beadm create bloody
  mkdir /tmp/bloody
  beadm mount bloody /tmp/bloody
  pkg -R /tmp/bloody set-publisher \
-G http://pkg.omniti.com/omnios/r151016/ \
-g http://pkg.omniti.com/omnios/bloody/ \
--unset-property signature-policy \
omnios
  pkg -R /tmp/bloody update
  beadm umount bloody
  beadm activate bloody

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] LSI3108

[Andy Fiddaman]

On Thu, 3 Mar 2016, Dan McDonald wrote:

;
; > On Mar 3, 2016, at 9:17 AM, Martin Dojcak  wrote:
; >
; > Hi,
; >
; > look at illumos Hardware Compatibility List:
; >
; > http://illumos.org/hcl/
; >
; > there is support for LSI 3008 and 3108 hba
;
; Note that the 3108 is HW-RAID and uses the mr_sas(7D) driver, while 3008 
(with IT firmware) is a simpler HBA and uses the mpt_sas(7D) driver.

We are running some Dell R730s with PERC H730s (using LSI 3108) in
pass-through mode with the mr_sas driver. No problems here but I'd still
recommend choosing something that works with mpt_sas as that has been
better maintained and is well tried and tested.

reaper# (132) megacli -AdpAllInfo -a0
...
Versions

Product Name: PERC H730 Mini
Serial No   : 4CF00C5
FW Package Build: 25.2.2-0004
...
Direct PD Mapping: Yes

dmesg:

mr_sas0: 0x1000:0x5d 0x1028:0x1f49, irq:15 drv-ver:6.503.00.00ILLUMOS
mr_sas0: TBOLT device detected
mr_sas0: msi_enable = 1
mr_sas0: enable_fp = 1
mr_sas0: ctio_enable = 1
mr_sas0 PCI Express-device: pci1028,1f49@0, mr_sas0
mr_sas0 is /pci@0,0/pci8086,2f02@1/pci1028,1f49@0
scsi: [ID 583861 kern.info] sd0 at mr_sas0: target 0 lun 1
mr_sas0: Phys. device found: tgt 0 dtype 0: SEAGATE ST300MP0005
scsi: [ID 583861 kern.info] sd1 at mr_sas0: target 1 lun 1
mr_sas0: Phys. device found: tgt 1 dtype 0: SEAGATE ST300MP0005
...


-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] PCRE now updated for OmniOS

[Andy Fiddaman]

On Wed, 2 Dec 2015, Dan McDonald wrote:

; Several CVEs have been filed against PCRE (Perl Compatible Regular 
Expressions).  All supported versions of OmniOS (r151006, r151014, and r151016) 
have updates of PCRE to version 8.38.
;
; This is a non-reboot-needed update, but you may need to restart certain 
services, especially those not provided by the system.

Thanks Dan. Quick as ever!

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] PCRE version

[Andy Fiddaman]

Whilst playing around with the latest version of ClamAV I notice that it
now prints this warning:

configure: WARNING: The installed pcre version may contain a security bug.
Please upgrade to 8.38 or later: http://www.pcre.org.

There is some information on the security fixes in 8.38 at
https://blog.fuzzing-project.org/29-Heap-Overflow-in-PCRE.html but I
couldn't find anything specific on the Exim mailing list.

May be worth bumping the PCRE version.

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Bloody // mailwrapper & mta mediator

[Andy Fiddaman]

On Thu, 5 Nov 2015, Dan McDonald wrote:
;
; Next update of 016 (and first release of 017 bloody) will have sendmail set 
to dependency=group.  It'll install, but if you "pkg uninstall sendmail" just 
once it'll stay uninstalled throughout future updates.  (Will need to be 
uninstalled on your non-global zones as well.)

Thanks for this Dan, we've now finished upgrading all of our servers to
016 with no issues encountered. The 'avoid' we already have in place for the
sendmail package worked fine with this change.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Bloody // mailwrapper & mta mediator

[Andy Fiddaman]

On Thu, 5 Nov 2015, Paul B. Henson wrote:

; > From: Andy Fiddaman
; > Sent: Wednesday, November 04, 2015 2:45 PM
; >
; > Not directly. I install my own Sendmail package (which lives in
; > /opt/sendmail/ and use the mta mediator to link it from /usr/lib/sendmail
; > etc., replacing mailwrapper.
;
; Out of curiosity, as long as you are installing a replacement MTA, why stick
; with Sendmail instead of one of the other more modern alternatives?

I've lots of experience with Sendmail (both the open source MTA and the
commercial offerings) and our main application is built around it. The
flexibility that the rulesets provide (over and above what can be done
with milters) is important to us.
We did experiment with Postfix a few years back when it gained a milter
interface of its own but stuck with Sendmail.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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 r151016 is now out!

[Andy Fiddaman]

On Tue, 3 Nov 2015, Dan McDonald wrote:

; Say hello to OmniOS r151016:
;
;   - New installs get OpenSSH by default, and OpenSSH is now easier to 
switch to or from.  (Thanks to Lauri "lotheac" Tirkkonen for this!)

Thanks for this, we've finished switching over to OpenSSH across our servers
now (and can finally drop the local SunSSH patches that we've been running!)

Two things that might be worth adding to the Release Notes wiki page in
addition to the SSH migration notes already there:

To continue allowing connections from SunSSH (during migration for example),
add:

KexAlgorithms +diffie-hellman-group1-sha1

to sshd_config.

Remember to update any entries in /etc/pam.conf

We needed:

s/sshd-kbdint/sshd/

to re-enable our two-factor authentication.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Bloody // mailwrapper & mta mediator

[Andy Fiddaman]

On Wed, 4 Nov 2015, Dan McDonald wrote:

;
; > On Nov 4, 2015, at 5:44 PM, Andy Fiddaman <omn...@citrus-it.net> wrote:
; >
; >
; > Would a 'group' dependency give the desired result of the package being
; > installed by default but still avoidable to those of us who don't want
; > it?
;
; That's actually an interesting idea.  I was thinking of "optional" as one 
possibility, but I'm noticing that type=group and type=optional appear, in 
practice, to be the same.  Apparently when you uninstall a group package, it's 
added to the image's avoid list.  For you anti-sendmail types, that may be a 
feature.  :)

sendmail is already an optional dependency of mailwrapper which is itself
required by SUNWcs. So if fresh installs aren't getting sendmail then
optional is not doing what you want here :(
I'm not sure if group would be any better.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Bloody // mailwrapper & mta mediator

[Andy Fiddaman]

On Wed, 4 Nov 2015, Dan McDonald wrote:

; Does the *presence* of sendmail in a default install actually prevent folks 
from using their preferred MTAs with the mediator (which still works from what 
I can tell)?

Not directly. I install my own Sendmail package (which lives in
/opt/sendmail/ and use the mta mediator to link it from /usr/lib/sendmail
etc., replacing mailwrapper.

Other than a desire for a minimal system, I don't have a major problem
with some unecessary files hanging around in /usr/lib/smtp/sendmail, but
I don't want the sendmail SMF service, the files in /etc/mail/ and
particularly not /etc/init.d/sendmail which is just a wrapper to the
(wrong - for me) SMF service. I also end up with some non-mediated
Sendmail-specific stuff in /usr/bin like makemap and libmilter which
I'd rather be without.

Up until now I have uninstalled the default sendmail package and configured
my images to 'avoid' it. With this change I can no longer do either.

I don't want Sendmail to be a mandatory package but if you do decide to
leave it that way, please consider removing it from entire and changing
the dependency in mailwrapper back from optional to require instead. It
would be easier for me to create a shadow mailwrapper package than to
mess with entire - and that syncs you back up with Illumos gate too.

Would a 'group' dependency give the desired result of the package being
installed by default but still avoidable to those of us who don't want
it?

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] (no subject)

[Andy Fiddaman]

On Mon, 14 Sep 2015, Paul B. Henson wrote:

; > From: Omen Wild
; > Sent: Monday, September 14, 2015 3:10 PM
; >
; > Mostly we are wondering how to clear the corruption off disk and worried
; > what else might be corrupt since the scrub turns up no issues.
;
; While looking into possible corruption from the recent L2 cache bug it seems
; that running 'zdb -bbccsv' is a good test for finding corruption as it looks
; at all of the blocks and verifies all of the checksums.

zpool scrub is fine but I get lots of messages like this when I run zdb
-bbccsv

zdb_blkptr_cb: Got error 50 reading <3077, 212, 0, 52>
DVA[0]=<0:14d528f8200:1ce00> [L0 ZFS plain file] fletcher4 lz4 LE
contiguous unique single size=2L/13200P birth=3708038L/3708038P fill=1
cksum=1717c7d38f62:374184e099ada9b:a86cf60db2f68605:2be4a1817f9f4b1d --
skipping

Is this an indicator of corruption in the pool?
It's going to be a right royal pain to rebuild them if I need to!

Thanks,

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] [developer] HEADS UP -- illumos-gate can now be built on OmniOS r151014 or later

[Andy Fiddaman]

I haven't managed to get to the bottom of this.

Could someone please send me a nightly.log from a build of the Illumos
gate on an OmniOS system so I can look for differences?

Any comments on the previous message below appreciated too.

Thanks,

Andy

On Fri, 10 Jul 2015, Andy Fiddaman wrote:

;
; On Thu, 9 Jul 2015, Dan McDonald wrote:
;
; ; Are you missing these files?  That's the explanation off the top of my head.
; ;
; ; Otherwise I'd have to look at the whole nightly.log, and I won't be able to 
do that at all today, possibly this week.
;
; I am not getting much further with finding the root cause of this. It does
; seem to be a fault in the build process but in that case I don't understand
; why I don't see it when building on OI. I might have to try and recover my
; OI machine to compare.
;
; Here's what I've found so far:
;
; Once nightly is finished, the OpenSSL licence file is present in
; proto/root_i386/licenses/usr/src/common/openssl/LICENSE
;
; and the nightly log says that it failed to build it once then didn't need
; to after that:
;
; build-env# (154) grep openssl/LICEN ~/log/log.2015-07-10.12:47/nightly.log
; dmake: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
; make: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
; 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
 is up to date.
; 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
 is up to date.
; 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
 is up to date.
; 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
 is up to date.
;
; If I run the make command that builds the file by hand, it says it is
; up-to-date:
;
; build-env# (146) pwd
; /root/illumos/illumos-gate/usr/src/pkg
; build-env# (147) make -e -f Makefile.lic \
; PKGDEBUG= LICROOT=$PARENT_WS/proto/root_i386/licenses \
; $PARENT_WS/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
; 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
 is up to date.
;
; but if I remove it and attempt to rebuild it:
;
; build-env# (148) rm 
/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
; build-env# (149) make -e -f Makefile.lic \
; PKGDEBUG= LICROOT=$PARENT_WS/proto/root_i386/licenses \
; $PARENT_WS/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
; make: Fatal error: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
;
; This is because the stage-licenses target just tries to copy the licence
; file from the usr/src tree and there is no usr/src/common/openssl in the
; gate.
;
; So I understand why it is failing but not yet what process ends up creating
; proto/root_i386/licenses/usr/src/common/openssl/LICENSE nor why I am not
; getting a clean build here. It looks like it might be the order in which
; things are built - it would be interesting to see the output of
; grep openssl/LIC from someone else's nightly.log to compare.
;
; I'll keep digging but any help appreciated,
;
; Thanks,
;
; Andy
;
;
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] [developer] HEADS UP -- illumos-gate can now be built on OmniOS r151014 or later

[Andy Fiddaman]

On Thu, 9 Jul 2015, Dan McDonald wrote:

; Are you missing these files?  That's the explanation off the top of my head.
;
; Otherwise I'd have to look at the whole nightly.log, and I won't be able to 
do that at all today, possibly this week.

I am not getting much further with finding the root cause of this. It does
seem to be a fault in the build process but in that case I don't understand
why I don't see it when building on OI. I might have to try and recover my
OI machine to compare.

Here's what I've found so far:

Once nightly is finished, the OpenSSL licence file is present in
proto/root_i386/licenses/usr/src/common/openssl/LICENSE

and the nightly log says that it failed to build it once then didn't need
to after that:

build-env# (154) grep openssl/LICEN ~/log/log.2015-07-10.12:47/nightly.log
dmake: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
make: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
 is up to date.
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
 is up to date.
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
 is up to date.
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
 is up to date.

If I run the make command that builds the file by hand, it says it is
up-to-date:

build-env# (146) pwd
/root/illumos/illumos-gate/usr/src/pkg
build-env# (147) make -e -f Makefile.lic \
PKGDEBUG= LICROOT=$PARENT_WS/proto/root_i386/licenses \
$PARENT_WS/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
 is up to date.

but if I remove it and attempt to rebuild it:

build-env# (148) rm 
/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
build-env# (149) make -e -f Makefile.lic \
PKGDEBUG= LICROOT=$PARENT_WS/proto/root_i386/licenses \
$PARENT_WS/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
make: Fatal error: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'

This is because the stage-licenses target just tries to copy the licence
file from the usr/src tree and there is no usr/src/common/openssl in the
gate.

So I understand why it is failing but not yet what process ends up creating
proto/root_i386/licenses/usr/src/common/openssl/LICENSE nor why I am not
getting a clean build here. It looks like it might be the order in which
things are built - it would be interesting to see the output of
grep openssl/LIC from someone else's nightly.log to compare.

I'll keep digging but any help appreciated,

Thanks,

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] [developer] HEADS UP -- illumos-gate can now be built on OmniOS r151014 or later

[Andy Fiddaman]

On Tue, 5 May 2015, Dan McDonald wrote:

; With the pushes of 4719, 5878, and 5879, one may now build stock illumos-gate
; on OmniOS, revisions r151014 or later.

Dan,

I'm finally getting around to trying this on one my r151014 zones - good
timing since my OI KVM instance isn't booting any more for some reason and
I have a few sets of mr_sas patches I want to push.

It's mostly looking good but I'm getting errors in mail_msg for openssl
components. Do you know if this s something to do with my environment
or a problem with the gate at the moment?

Thanks,

Andy


 Nightly distributed build started:   Wed Jul  8 21:44:56 UTC 2015 
 Nightly distributed build completed: Wed Jul  8 22:42:56 UTC 2015 

 Total build time 

real0:57:59

 Build environment 

/usr/bin/uname
SunOS build 5.11 omnios-170cea2 i86pc i386 i86pc

/opt/SUNWspro/bin/dmake
dmake: Sun Distributed Make 7.9 SunOS_i386 2009/06/03
number of concurrent jobs = 4

32-bit compiler
/opt/onbld/bin/i386/cw -_gcc
cw version 1.30 (SHADOW MODE DISABLED)
primary: /opt/gcc-4.4.4//bin/gcc
gcc (GCC) 4.4.4

64-bit compiler
/opt/onbld/bin/i386/cw -_gcc
cw version 1.30 (SHADOW MODE DISABLED)
primary: /opt/gcc-4.4.4//bin/gcc
gcc (GCC) 4.4.4

/usr/java/bin/javac
openjdk full version 1.7.0_76-b31

/usr/bin/as
as: Sun Compiler Common 12 SunOS_i386 snv_121 08/03/2009

/usr/ccs/bin/ld
ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1750 (illumos)

Build project:  user.root
Build taskid:   450834

 Nightly argument issues 


 Build version 

illumos-gate

 Make clobber ERRORS 


 Make tools clobber ERRORS 


 Tools build errors 


 Build errors (non-DEBUG) 

The following command caused the error:
dmake: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
dmake: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
dmake: Warning: Target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/cmd/acpihpd/THIRDPARTYLICENSE'
 not remade because of errors
The following command caused the error:
dmake: Warning: Target `stage-licenses' not remade because of errors
The following command caused the error:
dmake: Warning: Target `install' not remade because of errors

 Build warnings (non-DEBUG) 

dmake: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE'
dmake: Warning: Don't know how to make target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE.descrip'
dmake: Warning: Target 
`/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/cmd/acpihpd/THIRDPARTYLICENSE'
 not remade because of errors
dmake: Warning: Target `stage-licenses' not remade because of errors
dmake: Warning: Target `install' not remade because of errors

 Elapsed build time (non-DEBUG) 

real18:27.1
user  1:29:38.5
sys 11:02.9

 Build noise differences (non-DEBUG) 


 Build errors (DEBUG) 


 Build warnings (DEBUG) 


 Elapsed build time (DEBUG) 

real15:45.3
user  1:21:10.0
sys  8:52.1

 Build noise differences (DEBUG) 


 package build errors (DEBUG) 


 'dmake lint' of src ERRORS 


 Elapsed time of 'dmake lint' of src 

real15:32.1
user44:44.1
sys  6:02.6

 lint warnings src 


 lint noise differences src 


 cstyle/hdrchk errors 


 Find core files 


 Check lists of files 


-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] [developer] HEADS UP -- illumos-gate can now be built on OmniOS r151014 or later

[Andy Fiddaman]

On Thu, 9 Jul 2015, Dan McDonald wrote:
; Are you missing these files?  That's the explanation off the top of my head.
;

No, they seem to be built and there too.

build# (7) ls -l
/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE
-rw-r--r--   1 root 81906.1K Aug 18  2010
/root/illumos/illumos-gate/proto/root_i386/licenses/usr/src/common/openssl/LICENSE

I'll track it down - just hoped it would be something you'd seen before.

Thanks for the reply,

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] KVM Performance Update

[Andy Fiddaman]

Thanks Dan, and just before I was about to migrate my kvms across to
r151014 too!

Andy

On Tue, 12 May 2015, Dan McDonald wrote:

;
;  On May 11, 2015, at 11:48 AM, Dan McDonald dan...@omniti.com wrote:
; 
; 
;  1.) Revert illumos-kvm to the pre-VND level as well.
; 
;  2.) Keep up to date with illumos-kvm and illumos-kvm-cmd, but explicitly 
revert the VND changes in BOTH.
; 
;  I'm strongly leaning toward committing solution #2. Regardless of which, I 
will be issuing an update for r151014 later this week that will push KVM 
performance back to its pre-VND-bump levels.
;
; I chose option #2:
;
;   
https://github.com/omniti-labs/omnios-build/commit/0268a2ff04b1cbed2324054cb97a0f36c58989b0
;
; There's now an update for r151014 that has the updated system/kvm 
(qemu/userland) and driver/virtualization/kvm (kernel KVM driver) on the repo 
server.  A pkg update will update your packages AND boot archive without.  I 
do recommend, however, you power down your KVM instances and pkill qemu prior 
to running the update.
;
; Along with this update is a small fix to onu(1) for illumos developers who 
are working with r151014 as their base system for ONU-ing.
;
; Thank you all again for your patience,
; Dan
;
; ___
; OmniOS-discuss mailing list
; OmniOS-discuss@lists.omniti.com
; http://lists.omniti.com/mailman/listinfo/omnios-discuss
;
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] package/pkg/depot dependencies

[Andy Fiddaman]

Just moving our IPS repo over to a new r151014 server and mistakenly tried
to install package/pkg/depot along the way. I don't need this package but I
did notice that it has a couple of dependencies on non-existent apache-22
packages; at least non-existent in the main omnios repo.

vault# (22) pkg install depot
Creating Plan (Solver setup): -
pkg install: No matching version of package/pkg/depot can be installed:
  Reject:
pkg://omnios/package/pkg/depot@0.5.11,5.11-0.151014:20150402T184310Z
  Reason:  A version for 'require' dependency on pkg:/web/server/apache-22
cannot be found
zsh: exit 1 pkg install depot

vault# (23) pkg contents -rm depot | grep '^depend' | grep -v pkg:
depend fmri=web/server/apache-22 type=require
depend fmri=web/server/apache-22/module/apache-wsgi-26 type=require

Should this package be in the main repo?

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] SMART info

[Andy Fiddaman]

On Thu, 9 Apr 2015, Kyle Bruene wrote:

; Could anyone give me info on getting SMART info about SATA SSD's connected 
via expanders to an LSI controller in IT mode? I am trying to find how worn 
these are. Thanks.

I've found the need to add '-d sat,12' to the smartctl arguments in the
past. That might be able to get some more information from the drive.

Andy

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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 as web server: what good/best practices to follow?

[Andy Fiddaman]

On Wed, 8 Apr 2015, Davide Poletto wrote:

; Hello list,
;
; I'm planning to use OmniOS 151014 as base OS for a Web Server in order to
; deploy a little Intranet-in-a-Box project based on a Drupal 7
; distribution called Open Atrium 2 (other required mandatory components
; are PHP and MySQL).

I run web servers on OmniOS using Apache 2.2 in NGZs - no problems*.
I package apache for /opt/apache with the configuration files in
/etc/opt/apache (--prefix=/opt/apache --sysconfdir=/etc/opt/apache) which
puts both in the BE. I have mixed feelings about that but as long as you
are aware of the implications it isn't a problem either way.

The data is on a separate delegated ZFS data-set outside of the BE and
mounted elsewhere and I set exec=off, setuid=off, devices=off for that.
Apache is configured to write log files to the same data-set.

Andy

* - I did see performance issues the last time I tried Apache 2.4 but
haven't had the time to go back and investigate.

-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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] Problem with VNIC in KVM

[Andy Fiddaman]

On Tue, 7 Apr 2015, Michael Rasmussen wrote:

; On Mon, 6 Apr 2015 23:42:55 + (UTC)
; Andy Fiddaman omn...@citrus-it.net wrote:
;
; 
;  I've just tried it on and off and no difference (host and VM).
;  The annoying thing is that I've had this working fine in the lab before
;  the machine was rebuilt and put into production. Must be missing
;  something!
; Ok. Could it be some missing ipf?

Kstat in the OI VM was showing packets being received, they just weren't
making it through the IP stack for some reason. Wasn't IPF but it has
started working since I increased the number of virtual CPUs allocated to
the VM. I haven't conclusively proven the link but I have a working system
now so I'm going to leave it at that as I have some Illumos builds to get
done!

Thanks for the suggestions. If I work out any conclusive links I'll post
back.

Andy
-- 
Citrus IT Limited | +44 (0)870 199 8000 | 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