[OmniOS-discuss] Ang: Re: Wiki is slightly broken

2016-04-25 Thread Johan Kragsterman 

Hi!


-"OmniOS-discuss"  skrev: -
Till: Jacob Vosmaer 
Från: Eric Sproul 
Sänt av: "OmniOS-discuss" 
Datum: 2016-04-25 22:01
Kopia: omnios-discuss 
Ärende: Re: [OmniOS-discuss] Wiki is slightly broken

On Mon, Apr 25, 2016 at 3:50 PM, Jacob Vosmaer  wrote:
> https://chromium.googlesource.com/chromium/src/+/41f8478faaf6c41b2b484e167b3dbb6a95674839/net/http/transport_security_state_static.json#5796
>
> I suspect somebody submitted omniti.com via https://hstspreload.appspot.com/

I've passed that along.  If you go directly to
http://omnios.omniti.com/wiki.php/WikiStart do you get forced to
https?  I don't (Chrome 49, OSX 10.9) but I'm curious.

Eric


I get forced to https as well. Chrome Version 50.0.2661.86 (64-bit) on Linux.

Need to use firefox instead...

/J


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



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

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Michael Rasmussen 
On Mon, 25 Apr 2016 22:06:05 +0200
Jacob Vosmaer  wrote:

> 
> Chrome 50.0.2661.86 (64-bit), OS X 10.11.4.
> 
> If omniti.com was added to the HSTS preload list very recently it may not
> be hard-coded in Chrome 49 yet?
> 
Same here:
Chrome Version 50.0.2661.86 (64-bit), OS Debian Sid.

Works with Opera 36 which is based on Chrome/49.0.2623.110 

-- 
Hilsen/Regards
Michael Rasmussen

Get my public GnuPG keys:
michael  rasmussen  cc
http://pgp.mit.edu:11371/pks/lookup?op=get=0xD3C9A00E
mir  datanom  net
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE501F51C
mir  miras  org
http://pgp.mit.edu:11371/pks/lookup?op=get=0xE3E80917
--
/usr/games/fortune -es says:
Humorists always sit at the children's table.
-- Woody Allen


pgp5LU6rnI2LU.pgp
Description: OpenPGP digital signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Eric Sproul 
On Mon, Apr 25, 2016 at 4:06 PM, Jacob Vosmaer  wrote:
> Chrome 50.0.2661.86 (64-bit), OS X 10.11.4.
>
> If omniti.com was added to the HSTS preload list very recently it may not be
> hard-coded in Chrome 49 yet?

That could well be.  Lucky me, I guess.
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Eric Sproul 
On Mon, Apr 25, 2016 at 3:50 PM, Jacob Vosmaer  wrote:
> https://chromium.googlesource.com/chromium/src/+/41f8478faaf6c41b2b484e167b3dbb6a95674839/net/http/transport_security_state_static.json#5796
>
> I suspect somebody submitted omniti.com via https://hstspreload.appspot.com/

I've passed that along.  If you go directly to
http://omnios.omniti.com/wiki.php/WikiStart do you get forced to
https?  I don't (Chrome 49, OSX 10.9) but I'm curious.

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

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Jacob Vosmaer 
When I load that HTTP link with the 'Network' tab of the Chrome dev tools
open I first see a '307 internal redirect response' which takes me to
https://omnios.omniti.com/wiki.php/WikiStart , which then loads without CSS
(i.e. the 'broken' state). If I click where the Green Lock of Trust should
be I read 'Your connection to this site is private, but someone on the
network might be able to change the look of the page.'

Chrome 50.0.2661.86 (64-bit), OS X 10.11.4.

If omniti.com was added to the HSTS preload list very recently it may not
be hard-coded in Chrome 49 yet?

2016-04-25 21:59 GMT+02:00 Eric Sproul :

> On Mon, Apr 25, 2016 at 3:50 PM, Jacob Vosmaer 
> wrote:
> >
> https://chromium.googlesource.com/chromium/src/+/41f8478faaf6c41b2b484e167b3dbb6a95674839/net/http/transport_security_state_static.json#5796
> >
> > I suspect somebody submitted omniti.com via
> https://hstspreload.appspot.com/
>
> I've passed that along.  If you go directly to
> http://omnios.omniti.com/wiki.php/WikiStart do you get forced to
> https?  I don't (Chrome 49, OSX 10.9) but I'm curious.
>
> Eric
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Jacob Vosmaer 
Hi Eric,

All may not be well after all: I was having a hard time clearing omniti.com
from my Chrome's local HSTS list... turns out omniti.com is hard-coded in
Chromium(!).

https://chromium.googlesource.com/chromium/src/+/41f8478faaf6c41b2b484e167b3dbb6a95674839/net/http/transport_security_state_static.json#5796

I suspect somebody submitted omniti.com via https://hstspreload.appspot.com/
.


2016-04-25 21:16 GMT+02:00 Eric Sproul :

> On Mon, Apr 25, 2016 at 2:55 PM, Jacob Vosmaer 
> wrote:
> > Thanks Eric!
> >
> > It seems like I accidentally took this thread off-list. I think the
> summary
> > for everyone else is: HSTS on omniti.com accidentally trickled down to
> > omnios.omniti.com, affecting visitors who loaded up omnios.omniti.com at
> > just the right (wrong) time. HSTS headers should have been fixed now.
>
> Thanks for the summary Jacob-- can you confirm that you're no longer
> seeing the issue?  If so, we can call this one "explained".  :)
>
> Eric
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Eric Sproul 
On Mon, Apr 25, 2016 at 2:55 PM, Jacob Vosmaer  wrote:
> Thanks Eric!
>
> It seems like I accidentally took this thread off-list. I think the summary
> for everyone else is: HSTS on omniti.com accidentally trickled down to
> omnios.omniti.com, affecting visitors who loaded up omnios.omniti.com at
> just the right (wrong) time. HSTS headers should have been fixed now.

Thanks for the summary Jacob-- can you confirm that you're no longer
seeing the issue?  If so, we can call this one "explained".  :)

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

Re: [OmniOS-discuss] Wiki is slightly broken

2016-04-25 Thread Jacob Vosmaer 
Thanks Eric!

It seems like I accidentally took this thread off-list. I think the summary
for everyone else is: HSTS on omniti.com accidentally trickled down to
omnios.omniti.com, affecting visitors who loaded up omnios.omniti.com at
just the right (wrong) time. HSTS headers should have been fixed now.

2016-04-25 20:46 GMT+02:00 Eric Sproul :

> Hi Jacob,
> The OmniTI folks did roll out HSTS recently, but (as I'm sure many
> others have) quickly realized that including all subdomains wasn't
> feasible.  They now no longer set that for omniti.com, and have set
> the max-age parameter to 1 second.  I'm not sure how you go about
> clearing the HSTS info from your browser, but if you do that, you
> should be good.
>
> Eric
>
> On Mon, Apr 25, 2016 at 10:35 AM, Eric Sproul 
> wrote:
> > On Mon, Apr 25, 2016 at 10:26 AM, Jacob Vosmaer 
> wrote:
> >> Thanks Eric.
> >>
> >> I am not using HTTPS Everywhere. According to
> chrome://net-internals/#hsts
> >> omnios.omniti.com my Chrome thinks omnios.omniti.com wants 'Strict
> Transport
> >> Security'.
> >>
> >> static_sts_domain: omniti.com
> >> static_upgrade_mode: STRICT
> >> static_sts_include_subdomains: true
> >> static_sts_observed: 1461128400
> >>
> >> That timestamp is about five days ago. Could it be that OmniTI
> temporarily
> >> deployed HSTS and I got unlucky?
> >
> > Interesting... I'll ask my OmniTI colleagues.
> >
> > Eric
>
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] R151018: kernel panic when iSCSI target goes south

2016-04-25 Thread Stephan Budach 

Hi Dan,

Am 25.04.16 um 16:23 schrieb Dan McDonald:

This one is a NULL pointer dereference. If you're still running with kmem_flags 
= 0xf, the dump will be especially useful.

Dan

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


On Apr 25, 2016, at 3:27 AM, Stephan Budach  wrote:

Hi,

I have been struck by kernel panics on my OmniOS boxes lateley, when any one of 
the target hosts, where the system get it's LUNs from, experiences a kernel 
panic itself. When this happens, my RSF-1 node immediately panics as well. 
Looking at the vmdump, it shows this:

root@zfsha02gh79:/var/crash/unknown# mdb -k unix.0 vmcore.0
Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc apix 
scsi_vhci zfs sata sd ip hook neti sockfs arp usba stmf stmf_sbd mm md lofs 
random idm crypto cpc kvm ufs logindmux nsmb ptm smbsrv nfs ipc mpt mpt_sas 
pmcs emlxs ]

::status

debugging crash dump vmcore.0 (64-bit) from zfsha02gh79
operating system: 5.11 omnios-r151018-ae3141d (i86pc)
image uuid: 18d57565-8b91-46ea-9469-fb0518d35e30
panic message: BAD TRAP: type=e (#pf Page fault) rp=ff00f8b5e590 addr=10 occurred in 
module "scsi_vhci" due to a NULL pointer dereference
dump content: kernel pages only

::stack

vhci_scsi_reset_target+0x75(ff2c7b200b88, 1, 1)
vhci_recovery_reset+0x7d(ff2c7ac9d080, ff2c7b200b88, 1, 2)
vhci_pathinfo_offline+0xe5(ff21d3288550, ff2273530838, 0)
vhci_pathinfo_state_change+0xd5(ff21d3288550, ff2273530838, 4, 0, 0)
i_mdi_pi_state_change+0x16a(ff2273530838, 4, 0)
mdi_pi_offline+0x39(ff2273530838, 0)
iscsi_lun_offline+0xb3(ff21f1bd4580, ff2c084f5d60, 0)
iscsi_sess_offline_luns+0x4d(ff27fea82000)
iscsi_sess_state_failed+0x6f(ff27fea82000, 3, 2a)
iscsi_sess_state_machine+0x156(ff27fea82000, 3, 2a)
iscsi_login_end+0x18f(ff286c8d6000, 15, ff22724e1158)
iscsi_login_start+0x318(ff22724e1158)
taskq_thread+0x2d0(ff2270a7cb50)
thread_start+8()
The vmdump is really big, approx 5GB compressed, but I could share that if 
necessary.

Thanks,
Stephan


I sure do, if you'd grant me an upload token, I will upload that zip 
file of 4GB. This will expand to a 18GB vmdump…


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

Re: [OmniOS-discuss] R151018: kernel panic when iSCSI target goes south

2016-04-25 Thread Dan McDonald 
This one is a NULL pointer dereference. If you're still running with kmem_flags 
= 0xf, the dump will be especially useful.

Dan

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

> On Apr 25, 2016, at 3:27 AM, Stephan Budach  wrote:
> 
> Hi,
> 
> I have been struck by kernel panics on my OmniOS boxes lateley, when any one 
> of the target hosts, where the system get it's LUNs from, experiences a 
> kernel panic itself. When this happens, my RSF-1 node immediately panics as 
> well. Looking at the vmdump, it shows this:
> 
> root@zfsha02gh79:/var/crash/unknown# mdb -k unix.0 vmcore.0
> Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc apix 
> scsi_vhci zfs sata sd ip hook neti sockfs arp usba stmf stmf_sbd mm md lofs 
> random idm crypto cpc kvm ufs logindmux nsmb ptm smbsrv nfs ipc mpt mpt_sas 
> pmcs emlxs ]
> > ::status
> debugging crash dump vmcore.0 (64-bit) from zfsha02gh79
> operating system: 5.11 omnios-r151018-ae3141d (i86pc)
> image uuid: 18d57565-8b91-46ea-9469-fb0518d35e30
> panic message: BAD TRAP: type=e (#pf Page fault) rp=ff00f8b5e590 addr=10 
> occurred in module "scsi_vhci" due to a NULL pointer dereference
> dump content: kernel pages only
> > ::stack
> vhci_scsi_reset_target+0x75(ff2c7b200b88, 1, 1)
> vhci_recovery_reset+0x7d(ff2c7ac9d080, ff2c7b200b88, 1, 2)
> vhci_pathinfo_offline+0xe5(ff21d3288550, ff2273530838, 0)
> vhci_pathinfo_state_change+0xd5(ff21d3288550, ff2273530838, 4, 0, 0)
> i_mdi_pi_state_change+0x16a(ff2273530838, 4, 0)
> mdi_pi_offline+0x39(ff2273530838, 0)
> iscsi_lun_offline+0xb3(ff21f1bd4580, ff2c084f5d60, 0)
> iscsi_sess_offline_luns+0x4d(ff27fea82000)
> iscsi_sess_state_failed+0x6f(ff27fea82000, 3, 2a)
> iscsi_sess_state_machine+0x156(ff27fea82000, 3, 2a)
> iscsi_login_end+0x18f(ff286c8d6000, 15, ff22724e1158)
> iscsi_login_start+0x318(ff22724e1158)
> taskq_thread+0x2d0(ff2270a7cb50)
> thread_start+8()
> >
> 
> The vmdump is really big, approx 5GB compressed, but I could share that if 
> necessary.
> 
> Thanks,
> Stephan
> ___
> 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] R151018: kernel panic when iSCSI target goes south

2016-04-25 Thread Stephan Budach 

Hi,

I have been struck by kernel panics on my OmniOS boxes lateley, when any 
one of the target hosts, where the system get it's LUNs from, 
experiences a kernel panic itself. When this happens, my RSF-1 node 
immediately panics as well. Looking at the vmdump, it shows this:


root@zfsha02gh79:/var/crash/unknown# mdb -k unix.0 vmcore.0
Loading modules: [ unix genunix specfs dtrace mac cpu.generic uppc apix 
scsi_vhci zfs sata sd ip hook neti sockfs arp usba stmf stmf_sbd mm md 
lofs random idm crypto cpc kvm ufs logindmux nsmb ptm smbsrv nfs ipc mpt 
mpt_sas pmcs emlxs ]

> ::status
debugging crash dump vmcore.0 (64-bit) from zfsha02gh79
operating system: 5.11 omnios-r151018-ae3141d (i86pc)
image uuid: 18d57565-8b91-46ea-9469-fb0518d35e30
panic message: BAD TRAP: type=e (#pf Page fault) rp=ff00f8b5e590 
addr=10 occurred in module "scsi_vhci" due to a NULL pointer dereference

dump content: kernel pages only
> ::stack
vhci_scsi_reset_target+0x75(ff2c7b200b88, 1, 1)
vhci_recovery_reset+0x7d(ff2c7ac9d080, ff2c7b200b88, 1, 2)
vhci_pathinfo_offline+0xe5(ff21d3288550, ff2273530838, 0)
vhci_pathinfo_state_change+0xd5(ff21d3288550, ff2273530838, 4, 0, 0)
i_mdi_pi_state_change+0x16a(ff2273530838, 4, 0)
mdi_pi_offline+0x39(ff2273530838, 0)
iscsi_lun_offline+0xb3(ff21f1bd4580, ff2c084f5d60, 0)
iscsi_sess_offline_luns+0x4d(ff27fea82000)
iscsi_sess_state_failed+0x6f(ff27fea82000, 3, 2a)
iscsi_sess_state_machine+0x156(ff27fea82000, 3, 2a)
iscsi_login_end+0x18f(ff286c8d6000, 15, ff22724e1158)
iscsi_login_start+0x318(ff22724e1158)
taskq_thread+0x2d0(ff2270a7cb50)
thread_start+8()
>

The vmdump is really big, approx 5GB compressed, but I could share that 
if necessary.


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