Hi,
        I had been using a Solaris 11 151a server that was providing http pkg 
access for a few weeks without a single
issue, about 4-5 svcadm restarts a day due to changing the repo on disk.  I 
started getting the following errors today


.


 tried a svcadm restart  pkg/server and disable followed by enable
 built a new file system for the server to point at and attached it to the 
server
 Looked in defect.opensolaris.org

Unable to understand if recent Glassfish activities have caused the issue

Some comments from Shawn about the only change I recently made with the 
packaging system.

>>> -bash-4.0# pkg authority
>>> PUBLISHER                             TYPE     STATUS   URI
>>> contrib.glassfish.sun.com (non-sticky, preferred) origin   online   
>>> http://pkg.sun.com/glassfish/v3/contrib/
>>> stable.glassfish.org     (non-sticky) origin   online   
>>> http://pkg.glassfish.org/v3/stable/
>>> contrib.glassfish.org    (non-sticky) origin   online   
>>> http://pkg.glassfish.org/v3/contrib/
>>> dev.glassfish.org        (non-sticky) origin   online   
>>> http://pkg.glassfish.org/v3/dev/
>>> release.javaeesdk.sun.com (non-sticky) origin   online   
>>> http://pkg.sun.com/javaeesdk/6/release/
>>> -bash-4.0#
>>> 
>>> 
>>> That concerns me. It requires previous knowledge of where you were 
>>> pointing? I guess I am asking if there is a way
>>> to revert to safe mode.
>> 
>> What does "pkg -R / publisher" say?
>> 
>> It looks to me like you're using the image glassfish created.
> 
> bash-4.0# pkg -R / publisher
> PUBLISHER                             TYPE     STATUS   URI
> solaris                  (preferred)  origin   online   
> http://pkg.oracle.com/solaris/release/
> JDS                                   origin   online   
> http://bursrotst07.east.sun.com/
> -bash-4.0#
> 
> This is what I was expecting to see.
> 
> I don't understand what state I am in.


1) In older builds (pre-155), pkg(1) would silently attempt to discover
  images to use for packaging starting from the *current working
  directory* and go up to '/' until it found an image.  Once it found
  the image, it would silently use that one.  In 155+, it will exit
  with an error and tell you to specify which image you wanted to use.

2) The glassfish team distributes their own user image which the
  glassfish update center tool can be used to manage.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to