Mike Kupfer wrote: > I just Live Upgraded a SPARC box from snv_89 to snv_100a. There were several > error message in the upgrade log for SUNWslocal-root: > slocate group has been in default group table(s) since snv_100, Could you please check the /etc/group file to see if slocate group exists. It should be there. > Doing pkgadd of SUNWslocate-root to / > pkgadd: ERROR: unable to create package object </a/var/lib/slocate>. > pathname does not exist > group name <slocate> not found in group table(s) > 1 blocks > pkgadd: ERROR: unable to create package object </a/var/lib/slocate>. > group name <slocate> not found in group table(s) > pkgadd: ERROR: unable to open > </net/netinstall/export/nv/combined.nvs_wos/latest/Solaris_11/Product/SUNWslocate-root/reloc/var/lib/slocate/slocate.db> > for reading: (2) No such file or directory > ERROR: attribute verification of </a/var/lib/slocate> failed > group name <slocate> not found in group table(s) > ERROR: attribute verification of </a/var/lib/slocate/slocate.db> failed > group name <slocate> not found in group table(s) > > Installation of <SUNWslocate-root> partially failed. > pkgadd return code = 2 > > After booting the snv_100a BE, I verified that /var/lib/slocate was group > root (instead of group slocate), and slocate.db was group 98 instead of group > slocate. I fixed those by hand, but it looks like I need to do "slocate -u" > as root before I can actually use slocate for anything. > > Question: would the initial "slocate -u" have fixed the group problems if I > hadn't already fixed them? > I don't think so. The better way should be adding slocate group manually before upgrading.
Jim > -- > This message posted from opensolaris.org > _______________________________________________ > desktop-discuss mailing list > desktop-discuss at opensolaris.org >
