Skip to end of metadata
Go to start of metadata

Upgrading to a more recent release may require using a new repository and may require a few update steps to satisfy intermediate dependencies.

Remove extra or legacy publishers

opensolaris.org publisher

If you currently have the opensolaris.org publisher set, we would highly recommend unsetting it by running:

If you use SFE packages, you may need to uninstall them and unset the publishers as such packages may not satisfy dependencies required with newer repositories.

Upgrade to the latest revision of the current repository

If you are currently running OpenIndiana oi_147 or oi_148, the main publisher should be set to:

If you are currently running OpenIndiana Hipster 2015, the main publisher should be set to:

Before upgrading from a new release repository, your system should be updated to the latest revision of the current release:

For example, if your system uses the 'hipster-2015' repository, you need to update to the latest revision before updating to more recent ''hipster'.

Set the publisher to the new repository

If your openindiana.org publisher is set to a different URI, for example http://pkg.openindiana.org/dev/ (the development branch), you can correct this with:

Upgrade

You may want to update your packages fully in case of a bad pkg cache:

You can now identify what will be upgraded by issuing the command:

The -n flag specifies to perform no action (i.e. perform a trial run), and the -v flag is the verbose option, to provide additional output.

If you are satisfied with the actions to be taken, you can perform the upgrade by typing:

You may want to consider also passing the "--be-name" flag to give the new boot environment created a more memorable name, such as hipster-201610.

Known issues

SSH

Update may fail due to a conflict triggered by a bug in pkg(5):

Edit /etc/ssh/sshd_config (for example, add empty line) and retry updating.

Reference:

https://www.openindiana.org/2016/08/29/possible-ssh-update-issue/

CIFS

NOTE: After booting into the new BE, for servers running the in-kernel CIFS service (svc:/network/smb/server:default) in conjunction with AD, the service may fail to connect to your Active Directory domain controller running Windows Server 2008 R2, and thus clients will not be able to connect to network shares.

The solution is to set the lmauthlevel to 4:

sharectl set -p lmauth_level=4 smb

(previously on b148 and lower this needed to be set to level 2 to work correctly with Win2K8R2)

 

Labels:
None
Edit Labels

20 Comments

Hide/Show Comments

  1. Sep 14, 2011

    Anonymous

    when i tried to update from oi 151 (without a) and /devil publisher, i got an error:
    pkg(5) appears out of date and should be updated

    it worked after a pkg install package/pkg

  2. Sep 14, 2011

    Anonymous

    Hmm just followed the instructions and upgraded my oi_147.
    runs fine, just do the pkg install mentioned above.
    but why does the upgrade end with this ?
    ---------------------------------------------------------------------------
    NOTE: Please review release notes posted at:

    http://docs.sun.com/doc/821-1479
    ---------------------------------------------------------------------------
    It ends at http://download.oracle.com/docs/cd/E19963-01/

    Thought it was based on Illumos and not direct from Oracle.

  3. Sep 14, 2011

    Anonymous

    The first command "pkg publisher" does not need privilege escalation so the "pfexec" can be deleted.

    There is also a conflict between the # and pfexec, either use root logon (# prompt) or an elevated command $ pfexec

  4. Sep 15, 2011

    Anonymous

    worked flawlessly from oi_148, thanks guys

    /Per

  5. Sep 29, 2011

    Anonymous

    After upgrade boot screen shows oi_148b.

    Confirmed w/uname

    gjohnson@theta:~$ uname -v
    oi_148b
    gjohnson@theta:~$

    Is it an error? Or did it fail to update the kernel to 151?

    1. Oct 14, 2011

      Anonymous

      Did you remember to boot over to the new be??

      Mine shows oi_151a for uname -v.

  6. Nov 16, 2011

    Anonymous

    Hi,
    I'm trying to upgrade from oi_148 to oi_151a but have no success.
    There is always the error "http protocol error: code: 403 reason: Forbidden" with all pkg-Mirrors mentioned in the FAQ.

    Anny Ideas about that?
    thx in advance
    Alexander
    fua@gmx.net

    root@sunw27u # uname -a
    SunOS sunw27u 5.11 oi_148 i86pc i386 i86pc
    root@sunw27u # pkg image-update -v --be-name oi_151a
    .
    .
    .
    Download: system/locale/mt ... Done
    Download: x11/server/xorg/driver/xorg-video-i128 ... Done
    Download: compatibility/packages/SUNWxwplt ... Done
    Download: consolidation/gnome_l10n/gnome_l10n-incorporation ... Done
    Download: library/audio/gstreamer ...
    Errors were encountered while attempting to retrieve package or file data for
    the requested operation.
    Details follow:

    http protocol error: code: 403 reason: Forbidden
    URL: 'http://pkg-1.dk.openindiana.org/dev/file/1/180f8ea5fcb093d7600264890956da9c94cdbcc3'.

    1. Nov 17, 2011

      Anonymous

      Looks like repo isn't working.
      Try original publisher:
      pkg publisher -a
      PUBLISHER TYPE STATUS URI
      openindiana.org (preferred) origin online http://pkg.openindiana.org/dev/
      sfe origin online http://pkg.openindiana.org/sfe/
      sfe-encumbered origin online http://pkg.openindiana.org/sfe-encumbered/

      1. Nov 17, 2011

        Anonymous

        Hi,
        thx for the advise, the result with the repository on http://pkg.openindiana.org/dev is exactly the same.
        HTTP error 403 while downloading library/audio/gstreamer.

        Maybe it's a problem with my environment (sitting behind a firewall, proxy, ...) i try to check this out
        and post my result here if i have success.
        br
        Alexander

        1. Nov 20, 2011

          Anonymous

          I am experiencing the following problem with the repository:
          Unable to contact valid package repository
          Encountered the following error(s):
          Unable to contact any configured publishers.
          This is likely a network configuration problem.
          Framework error: code: 6 reason: Couldn't resolve host 'pkg.openindiana.org'
          URL: 'http://pkg.openindiana.org/dev'. (happened 4 times)

          However, basic dig testing reveals DNS is working as expected:
          ;; QUESTION SECTION:
          ;pkg.openindiana.org. IN A

          ;; ANSWER SECTION:
          pkg.openindiana.org. 3600 IN CNAME pkg-origin.openindiana.org.
          pkg-origin.openindiana.org. 3600 IN A 91.194.74.166

          ;; Query time: 275 msec
          ;; SERVER: 4.2.2.3#53(4.2.2.3)
          ;; WHEN: Sun Nov 20 13:00:48 2011
          ;; MSG SIZE rcvd: 78

          Not sure if this is a configuration issue, but thought it may be relevant to your problem.

    2. Dec 05, 2011

      Anonymous

      Hi all,

      found the reason for my problem:
      A very popular server based anti virus solution identifies the gstreamer pkg as the virus "Heuristic.BehavesLike.Exploit.CodeExec.NLK" and blocks the access ....
      (sad)

      br
      Alexander

  7. Nov 26, 2011

    Anonymous

    Thanks a bunch! I was able to upgrade mine to 151a today. I had some issues, but it was all self induced.

    I had a static IP set, it had problems resolving the FQDN of the update server. Fixed - DHCP
    Could not run all the commands in napp-it (does nto support interactive commands) - Putty in and run from console.

    Now running:
    OpenIndiana appliance v. 0.6i nightly Nov.17.2011
    SunOS OI 5.11 oi_151a i86pc i386 i86pc
    Pool: 9.06T
    Free: 790G - guess I have another upgrade to do now.... off to newegg.

  8. Nov 28, 2011

    Anonymous

    Hi,

    I am trying to upgrade from oi_148 to oi_151a and keep getting the following error.

    Does it means the repo doesn't work anymore?

    Thanks
    Peter

    DOWNLOAD PKGS FILES XFER (MB)
    system/font/xorg/iso8859-1 111/608 4729/20207 47.5/324.7

    Errors were encountered while attempting to retrieve package or file data for
    the requested operation.
    Details follow:

    1: Framework error: code: 28 reason: Operation too slow. Less than 1024 bytes/sec transfered the last 30 seconds
    URL: 'http://pkg.openindiana.org/dev/file/1/e574d4804a9d4708039053b696a48cfca86e66df'. (happened 4 times)
    2: Framework error: code: 28 reason: Operation too slow. Less than 1024 bytes/sec transfered the last 30 seconds
    URL: 'http://pkg.openindiana.org/dev/file/1/b3b293018ed0fb85cb70379dc306c09a52480a20'. (happened 4 times)
    3: Framework error: code: 28 reason: Operation too slow. Less than 1024 bytes/sec transfered the last 30 seconds
    URL: 'http://pkg.openindiana.org/dev/file/1/b1e7273633231b93e8d64965b4a67420c3457552'. (happened 4 times)

  9. Mar 25, 2012

    gpatrick

    pfexec doesn't work for me with OpenIndiana; I have to su to root.  However, using pfexec as a user always worked in OpenSolaris.

     

    1. Apr 03, 2012

      Carsten Grzemba

       # usermod -P "Primary Administrator" <your_login>

      should help.

  10. Apr 16, 2012

    halpha line

    Hi, Folks

    I am not able to upgrade from oi148 due to some invalid pkg metadata. Any idea what is going on? Thanks!

    $ pfexec pkg image-update -nv
    Creating Plan \                        
    pkg: The requested operation cannot be completed due to invalid package metadata.  Details follow:

    invalid action in package pkg://openindiana.org/library/python-2/pybonjour@1.1.1,5.11-0.151.1.3:20120329T222048Z: depend fmri=library/python-2/pybonjour-26@1.1.1,5.11-0.151.1.3 predicate=runtime/python-26 type=conditional: Unknown type (conditional) in depend action

    1. Apr 16, 2012

      halpha line

      Oops! looks like somebody just reported this bug an hour ago.Hope there can be a quick fix soon. Here's the link,

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

    2. May 04, 2012

      Lee Thornhill

      Problem still exists.

       

      pkg: The requested operation cannot be completed due to invalid package metadata.  Details follow:

      invalid action in package pkg://openindiana.org/library/python-2/pybonjour@1.1.1,5.11-0.151.1.3:20120329T222048Z: depend fmri=library/python-2/pybonjour-26@1.1.1,5.11-0.151.1.3 predicate=runtime/python-26 type=conditional: Unknown type (conditional) in depend action

       

       

  11. Jun 06, 2012

    Sam Gridley

     

    I have same problem as 'lee' and 'halpha' and others - (even when trying to update as root) sadly questions on how to mitigate this issue on many of the support sites: illumos.org and openindiana-discuss go unanswered. Its quite a shame looks like a very nice OS, and love the ZFS support, but lack of support is casting doubt on this as serious OS.
    https://www.illumos.org/issues/2629
    https://www.illumos.org/issues/2664
    http://www.mail-archive.com/openindiana-discuss@openindiana.org/msg07536.html
    http://echelog.com/logs/browse/openindiana/1329951600     (Mosh @ 13:13:40 )
    http://mail.opensolaris.org/pipermail/pkg-discuss/2011-June/027040.html
    http://openindiana.org/pipermail/openindiana-discuss/2011-June/004328.html
    http://wiki.openindiana.org/oi/Package+Repositories  (Anonymous @ Oct 17, 2011) , (P.S. Robinson @ Feb 29, 2012)
    http://defect.opensolaris.org/bz/show_bug.cgi?id=1133
    http://defect.opensolaris.org/bz/show_bug.cgi?id=2714
     
    But on 2 boxes w/ oi_151a always same issue - same error :
    <begin>
    Preparing...
    Ensuring Update Manager is up to date...
    Refreshing catalog openindiana.org
    Finished refreshing catalog openindiana.org
    Gathering package information

    Error:
    Please check the network connection.
    Is the repository accessible?

    Invalid content: manifest hash failure: fmri: pkg://openindiana.org/gnome/locale/es@0.5.11,5.11-0.151.1.4:20120502T223653Z
    expected: d362c005a319bff92a0e3135f3330368c1c4fbe4 computed: 60f6b2e359e02f6d0368c1572a5385ae75714789. (happened 4 times)
    <end>
    Other pertinent facts:
    Active publisher :  http://pkg.openindiana.org/dev/    openindiana.org
    seems there are a lot of problems with pkg manager pkg
    (perhaps this live image problem compounding issue??)
    http://openindiana.org/pipermail/openindiana-discuss/2011-September/005291.html
    http://openindiana.org/pipermail/pkg-team/2011-September/000048.html
    http://openindiana.org/pipermail/openindiana-discuss/2011-June/004294.htm
    http://openindiana.org/pipermail/pkg-team/2011-May/000017.html
    http://wiki.openindiana.org/oi/Troubleshooting+image-update+failures
    The only reason we are going with OI is for native ZFS support , perhaps time to evaluate the new FreeBSD or Gentoo distros. (sad)

  12. Jun 08, 2012

    Lee Thornhill

    Sam, your post prompted me to get back working on this little project. The solution for me:

    pkg rebuild-index

    After that the upgrade went smoothly.