[OmniOS-discuss] updating ms-omniti repo fails

[Jens Bauernfeind]

Hello all,

the problem discussed in this old thread
http://lists.omniti.com/pipermail/omnios-discuss/2015-June/005193.html is
still there.
I have running a r151014 machine, the first clone of the ms-omniti repo is
working fine, but updating is impossible.

steps i have done:
zfs create rpool/export/pkgrepo/omnios/ms.omniti.com
pkgrepo create /export/pkgrepo/omnios/ms.omniti.com
pkgrepo set -s /export/pkgrepo/omnios/ms.omniti.com
publisher/prefix=ms.omniti.com
pkgrecv -v -s http://pkg.omniti.com/omniti-ms/ -d
/export/pkgrepo/omnios/ms.omniti.com/ --clone -p ms.omniti.com
pkgrepo refresh -s /export/pkgrepo/omnios/ms.omniti.com

updating:
export PKG_SRC=http://pkg.omniti.com/omniti-ms/
export PKG_DEST=/export/pkgrepo/omnios/ms.omniti.com/
pkgrecv -v '*' --clone -p ms.omniti.com

while updating, the following error message appears:

PROCESS ITEMSGET (MB)   SEND
(MB)
network/iftop  0/2016  0/9765
0/30694
pkgrecv: 'open' failed for transaction ID
'1374267709_pkg%3A%2F%2Fms.omniti.com%2Fnetwork%2Fiftop%401.0.2%2C5.11-0.151
006%3A20130719T210149Z': The specified FMRI,
'pkg://ms.omniti.com/network/iftop@1.0.2,5.11-0.151006:20130719T210149Z',
already exists or has been restricted.

Thanks for help
Jens


smime.p7s
Description: S/MIME cryptographic signature
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] using proxmox, after upgrade KVM does not start

[Michael Rasmussen]

On Mon, 7 Nov 2016 23:33:51 +0100 (CET)
Tobias Oetiker  wrote:

> 
> we found that after the upgrade a few of our luns had disaperaed
> ... since onone else reported this on the list we thought that we
> may have made a mistake ... but maybe there is something more
> 
Strange, had same experience but thought is was a human error. In my
case is was not the Lun gone missing but a few views which was lost.

> just recreate the missing luns ... (we had to pick new lun numbers
> since omni complained that the old luns were already in use)
> 
Did not have to do this; only recreate the views.

> then rescan iscsi on the proxmox host and all should be well.
> 
In proxmox case this is not needed since iscsi connections is made on
demand using libiscsi.

-- 
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:
  I distinctly remember forgetting that. -Clara Barton


pgpwQOpaF9l2G.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] using proxmox, after upgrade KVM does not start

[Tobias Oetiker]

Robert,

Today Robert.fantini wrote:

> Hello
>
> My issue may have nothing to do with the omnios upgrade. It could be due to a 
> mistake I made somewhere else.
>
> After upgrading to :
> OmniOS 5.11 omnios-cac2b76 October 2016
> SunOS sys4 5.11 omnios-cac2b76 i86pc i386 i86pc
>
> our KVM's using iscsi will not start.
> kvm: -drive 
> file=iscsi://10.2.2.41/iqn.2010-09.org.napp-it:1459891666/2,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on:
>
> iSCSI: Failed to connect to LUN : iscsi_service failed with : 
> iscsi_service_reconnect_if_loggedin. Can not reconnect right now.
>
>
> Has anyone seen that?
>
> Or suggest iscsi debugging/testing commands to get more information?

we found that after the upgrade a few of our luns had disaperaed
... since onone else reported this on the list we thought that we
may have made a mistake ... but maybe there is something more

just recreate the missing luns ... (we had to pick new lun numbers
since omni complained that the old luns were already in use)

then rescan iscsi on the proxmox host and all should be well.

cheers
tobi
>
>
> thanks , Robert Fantini

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
www.oetiker.ch t...@oetiker.ch +41 62 775 9902

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

[OmniOS-discuss] using proxmox, after upgrade KVM does not start

[Robert.fantini]

Hello

My issue may have nothing to do with the omnios upgrade. It could be due to a 
mistake I made somewhere else.

After upgrading to :
OmniOS 5.11 omnios-cac2b76 October 2016
SunOS sys4 5.11 omnios-cac2b76 i86pc i386 i86pc

our KVM's using iscsi will not start.
kvm: -drive 
file=iscsi://10.2.2.41/iqn.2010-09.org.napp-it:1459891666/2,if=none,id=drive-virtio0,format=raw,cache=none,aio=native,detect-zeroes=on:

iSCSI: Failed to connect to LUN : iscsi_service failed with : 
iscsi_service_reconnect_if_loggedin. Can not reconnect right now.


Has anyone seen that?

Or suggest iscsi debugging/testing commands to get more information?


thanks , Robert Fantini___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151020 installation via kayak fails with broken curl

[Jaakko Linnosaari]

> On 7 Nov 2016, at 18.27, Dan McDonald  wrote:
>> On Nov 7, 2016, at 11:01 AM, Jaakko Linnosaari 
>>  wrote:
>> 
>> I think it’s from this package: 
>> pkg://omnios/system/install/kayak-kernel@1.1-0.151020:20161102T022316Z
> 
> Yeah, we need to update that package.  We discovered this, fixed it in the 
> download area, but didn't fix it on the IPS server.


Ok, good to know. I got the install to work with the miniroot Dale linked to.

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

Re: [OmniOS-discuss] OmniOS r151020 installation via kayak fails with broken curl

[Dan McDonald]

> On Nov 7, 2016, at 11:01 AM, Jaakko Linnosaari 
>  wrote:
> 
> I think it’s from this package: 
> pkg://omnios/system/install/kayak-kernel@1.1-0.151020:20161102T022316Z
> 

Yeah, we need to update that package.  We discovered this, fixed it in the 
download area, but didn't fix it on the IPS server.

Sorry about that,
Dan

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

Re: [OmniOS-discuss] OmniOS r151020 installation via kayak fails with broken curl

[Jaakko Linnosaari]

> On 7 Nov 2016, at 16.50, Dale Ghent  wrote:
>> On Nov 7, 2016, at 9:08 AM, Jaakko Linnosaari 
>>  wrote:
>> 
>> I’ve upgraded couple of my home servers (with some challenges with 
>> SunSSH/OpenSSH transition) and now tried kayak with our test server 
>> environment. The installation fails when the script tries to fetch 
>> configuration from the kayak server. The correct configuration file is 
>> there, and installation succeeds with r151014. Trying curl manually in the 
>> maintenance shell results in linking error with libnghttp2...
>> 
>> Has anyone had success installing servers with kayak yet?
> 
> What is the source of your miniroot.gz ?

I think it’s from this package: 
pkg://omnios/system/install/kayak-kernel@1.1-0.151020:20161102T022316Z 


> https://omnios.omniti.com/media/miniroot-r151020.gz
> 
> Should work.

Thanks. I’ll give it a try.

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

[Jim Klimov]

6 ноября 2016 г. 1:02:39 CET, Olaf Marzocchi  пишет:
>On 04/11/2016 16:26, Dan McDonald wrote:
>> With SunSSH being end-of-lifed, upgrading to r151020 may be difficult
>for people still using SunSSH.  There's a new upgrading page one can
>get to off the Release Notes:
>>
>>  https://omnios.omniti.com/wiki.php/Upgrade_to_r151020
>
>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.
>
>What I did:
>I used the sshd_config.new as starting point with these changes:
>
>PasswordAuthentication no
>UsePAM yes
>#ChallengeResponseAuthentication yes (untouched, it's the default)
>
>I also tried
>
>AuthenticationMethods publickey keyboard-interactive
>
>but it didn't help.
>
>Then I went to pam.conf and did s/sshd-kbdint/sshd/ as written in the 
>guide. This is what I have now at the very end of said file:
>
># SSH keyboard interactive, so that keys don't ask for verification
>code
>sshd   auth requisite  pam_authtok_get.so.1
>sshd   auth required   pam_dhkeys.so.1
>sshd   auth required   pam_google_authenticator.sonullok
>sshd   auth required   pam_unix_cred.so.1
>sshd   auth required   pam_unix_auth.so.1
>
>When I login via SSH, I'm not asked for the verification code.
>I searched online for similar guides but it looks like I'm doing it 
>right so I don't know how to proceed. Anyone able to help? thanks
>
>Cheers,
>Olaf
>___
>OmniOS-discuss mailing list
>OmniOS-discuss@lists.omniti.com
>http://lists.omniti.com/mailman/listinfo/omnios-discuss

As a tangential help in troubleshooting: you can run the client with 'ssh -v' 
(or several -v's) to boost debugging, and the server too perhaps (might run a 
server on nonstandard port and in foreground, so as to not fiddle with standard 
SMF manifest, at least initially). This can help uncover what methods it tries 
and fails and why.

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] OmniOS r151020 installation via kayak fails with broken curl

[Dale Ghent]

> On Nov 7, 2016, at 9:08 AM, Jaakko Linnosaari 
>  wrote:
> 
> Hi!
> 
> I’ve upgraded couple of my home servers (with some challenges with 
> SunSSH/OpenSSH transition) and now tried kayak with our test server 
> environment. The installation fails when the script tries to fetch 
> configuration from the kayak server. The correct configuration file is there, 
> and installation succeeds with r151014. Trying curl manually in the 
> maintenance shell results in linking error with libnghttp2...
> 
> Has anyone had success installing servers with kayak yet?

What is the source of your miniroot.gz ? 

https://omnios.omniti.com/media/miniroot-r151020.gz

Should work.

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

[OmniOS-discuss] OmniOS r151020 installation via kayak fails with broken curl

[Jaakko Linnosaari]

Hi!

I’ve upgraded couple of my home servers (with some challenges with 
SunSSH/OpenSSH transition) and now tried kayak with our test server 
environment. The installation fails when the script tries to fetch 
configuration from the kayak server. The correct configuration file is there, 
and installation succeeds with r151014. Trying curl manually in the maintenance 
shell results in linking error with libnghttp2...

Has anyone had success installing servers with kayak yet?

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

Re: [OmniOS-discuss] Can't bring up r151020

[Volker A. Brandt]

Hi Gary!


> I'm also open to picking up a new machine like the HP Gen8.  I'm using 
> this as a (very) small SOHO server to do email, web, and file services.  
> The current machine is a 1U unit which has a motherboard similar to the 
> SunFire v20, 4 disks: 2 mirrored 5TB(archive), 2 mirrored ~300GB drives 
> (rpool), and 8 GB of RAM which works well for my purpose.

I can confirm that OmniOS works fine on the HP G8.  The only gotcha is
that if you want to use the HBA in non-RAID mode (which you do :-) AND
you want to install an SSD in place of the DVD, then you will not be
able to boot off said SSD.  This is a stupid design limitation.

I am working on a fix but am not finished yet.  I expect to have 
something in early December.  Basically, you need to install an SD
card and chainload the "real" OS from there.


Regards -- Volker
-- 

Volker A. Brandt   Consulting and Support for Oracle Solaris
Brandt & Brandt Computer GmbH   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513  Schuhgröße: 46
Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"
___
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