Greetings.  A kind release engineer for OpenSolaris suggested
that I write to this alias about the internal error below.

After an install of 2009.06 on SPARC

r...@opensolaris:~# pfexec pkg set-authority -O http://ipkg.sfbay opensolaris.o
rg
Traceback (most recent call last):
 File "/usr/bin/pkg", line 2563, in ?
   __ret = main_func()
 File "/usr/bin/pkg", line 2524, in main_func
   return publisher_set(mydir, pargs)
 File "/usr/bin/pkg", line 1790, in publisher_set
   refresh_allowed=refresh_catalogs)
File "/usr/lib/python2.4/vendor-packages/pkg/client/api.py", line 1297, in update_publisher
   self.img.save_config()
File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 298, in save_config
   self.cfg_cache.write(self.imgdir)
File "/usr/lib/python2.4/vendor-packages/pkg/client/imageconfig.py", line 305, in write
   f = open(thefile, "w")
IOError: [Errno 30] Read-only file system: '/var/pkg/cfg_cache'

pkg: This is an internal error. Please let the developers know about this problem by filing a bug at http://defect.opensolaris.org and including the above traceback and this message. The version of pkg(5) is '02ad3f8f9c38'.

Note that this does NOT actually seem to be a read-only file system:

# pwd
/var/pkg
# touch me
# rm me

But there DOES seem to be something special about that file:

# touch cfg_cache
touch: cannot change times on cfg_cache: Read-only file system

And removing it is not the answer

# mv cfg_cache foo
# pfexec pkg set-authority -O http://ipkg.sfbay opensolaris.org
pkg: No image found.
#

Truss shows this about the file open just before death:

open64("/var/pkg/cfg_cache", O_WRONLY|O_CREAT|O_TRUNC, 0666) Err#30 EROFS

[... time passes ... ]

OK, I now understand HOW it was that I got to this point.
The last thing from my window from yesterday was

Please refer to /tmp/install_log file  for details
After reboot it will be located at  /var/sadm/system/logs/install_log

So when I logged in this morning I thought it was post-reboot.
I did _not_ understand that it was up to me to do the reboot.
In fact, we were still in the installation environment:

Filesystem             size   used  avail capacity  Mounted on
/devices/ramdisk-root:a
                       160M   154M   5.1M    97%    /

So it was my "fault" for not noticing that this install procedure relies
on me to do the reboot (which differs from what I was used to!)

Nevertheless, it shouldn't die with "internal error", should it?

     -john


_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to