Originally posted by: Tin_Cup

After YUM update /usr/sbin/updtvpkg gives following output:

/usr/sbin/updtvpkg
Please wait...rpm_share: 0645-007 ATTENTION: whichfs() returned an unexpected result.
rpm_share: 0645-007 ATTENTION: get_rpm_inst_root_list() returned an unexpected result.
rpm_share: 0645-007 ATTENTION: update_inst_root() returned an unexpected result.
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Sjgaea
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Sngaeb
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.Srgaec
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
Processing files: AIX-rpm-7.2.4.0-15.ppc
Wrote: /opt/freeware/src/packages/SRPMS/AIX-rpm-7.2.4.0-15.src.rpm
Wrote: /opt/freeware/src/packages/RPMS/ppc/AIX-rpm-7.2.4.0-15.aix7.2.ppc.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.S4gaed
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0

yum check:

Loaded plugins: list-data, versionlock
check all

 oslevel -s
7200-04-01-1939
 

why these messages and how to fix this?

Originally posted by: sangameshm

These kind of errors are mostly appear if we are having symbolic link to non-existence path as part of an rpm package.

Or path in which where we are trying to install a file doesn't exists.

You can verify the installed rpm packages if they are fine and all files and paths are correct.

Thanks,

Sangamesh 

Originally posted by: Tin_Cup

I did a rpm -V <rpm> of all the RPM's into output file

 grep ^missing /tmp/RPM-verify.txt

missing   c /etc/puppetlabs/code/environments/production/hiera.yaml
missing   c /etc/puppetlabs/puppet/hiera.yaml
 

That is on all our servers the same, so i see no reason for this issue

Originally posted by: sangameshm

whichfs failure is related to not able to get the correct filesystem a file or directory belongs.

may also have a look at this https://www.ibm.com/mysupport/s/question/0D50z00006LKtNnCAL/aix-72-bash-installation-error-unexpected-result?language=en_US

is this being tried on wpar or chrooted environment ?

Thanks,

Sangamesh

Originally posted by: Tin_Cup

Hi Sandamesh,

This a regular AIX lpar, no WPAR or chrooted.

all command output i gave was okay, no strange thing with bash or /opt. (i can't upload output, it is SPAM it says)

How to find out what is missing?

regards, Emiel

Originally posted by: sangameshm

I think better here is to debug /usr/lib/instl/baselib_sh script.

If you can add "set -x" to the get_rpm_inst_root_list() function which would give little more idea regarding which file is not getting the correct file system information.

Thanks,

Sangamesh

Originally posted by: Tin_Cup

output (part)  from script:

FS=/
+ is_path_in_root_part /
+ [[ 0 -eq 0 ]]
+ echo /etc/rc.d/rc2.d/Khttpd
+ continue
+ read NODE
+ check_node /etc/rc.d/rc2.d/Knmbd
+ + whichfs /etc/rc.d/rc2.d/Knmbd
rpm_share: 0645-007 ATTENTION: whichfs() returned an unexpected result.
FS=
+ eval pmerror "get_rpm_inst_root_list()"; return 1
+ pmerror get_rpm_inst_root_list()
rpm_share: 0645-007 ATTENTION: get_rpm_inst_root_list() returned an unexpected result.
+ return 1
rpm_share: 0645-007 ATTENTION: update_inst_root() returned an unexpected result.
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.6braea
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.6fraeb
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.6jraec
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
Processing files: AIX-rpm-7.2.4.0-17.ppc
Wrote: /opt/freeware/src/packages/SRPMS/AIX-rpm-7.2.4.0-17.src.rpm
Wrote: /opt/freeware/src/packages/RPMS/ppc/AIX-rpm-7.2.4.0-17.aix7.2.ppc.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.6vraed
+ umask 022
+ cd /opt/freeware/src/packages/BUILD
+ exit 0
 

ls -als /etc/rc.d/rc2.d
total 48
   8 drwxr-xr-x    2 root     system         4096 Apr 08 12:05 .
   8 drwxr-xr-x   11 root     system         4096 Feb 26 2016  ..
   0 lrwxrwxrwx    1 root     system           14 Sep 03 2019  K00cups -> ../init.d/cups
   0 lrwxrwxrwx    1 root     system           24 May 20 2019  K100nimbus -> /opt/nimsoft/bin/niminit
   0 lrwxrwxrwx    1 root     system           15 Apr 08 12:05 Khttpd -> ../init.d/httpd
   0 lrwxrwxrwx    1 root     system           14 Apr 08 12:04 Knmbd -> ../init.d/${i}
   0 lrwxrwxrwx    1 root     system           14 Apr 08 12:04 Ksmbd -> ../init.d/${i}
   8 -r-xr-xr-x    1 root     system          325 Apr 08 10:08 Ksshd
   0 lrwxrwxrwx    1 root     system           14 Apr 08 12:04 Kwinbindd -> ../init.d/${i}
   8 -r-x------    1 root     system         2534 Feb 26 2016  Kwpars
   8 -rwxr-xr-x    1 root     system          165 Apr 08 10:46 S00ct_boot
   0 lrwxrwxrwx    1 root     system           33 Apr 08 11:19 S01cloud-init-local -> /etc/rc.d/init.d/cloud-init-local
   0 lrwxrwxrwx    1 root     system           27 Apr 08 11:19 S02cloud-init -> /etc/rc.d/init.d/cloud-init
   0 lrwxrwxrwx    1 root     system           29 Apr 08 11:19 S03cloud-config -> /etc/rc.d/init.d/cloud-config
   0 lrwxrwxrwx    1 root     system           28 Apr 08 11:19 S04cloud-final -> /etc/rc.d/init.d/cloud-final
   0 lrwxrwxrwx    1 root     system           21 Apr 08 12:05 S90sudo -> /etc/rc.d/init.d/sudo
   0 lrwxrwxrwx    1 root     system           24 May 20 2019  S990nimbus -> /opt/nimsoft/bin/niminit
   0 lrwxrwxrwx    1 root     system           14 Sep 03 2019  S99cups -> ../init.d/cups
   0 lrwxrwxrwx    1 root     system           15 Apr 08 12:05 Shttpd -> ../init.d/httpd
   0 lrwxrwxrwx    1 root     system           14 Apr 08 12:04 Snmbd -> ../init.d/${i}
   0 lrwxrwxrwx    1 root     system           14 Apr 08 12:04 Ssmbd -> ../init.d/${i}
   8 -r-xr-xr-x    1 root     system          326 Apr 08 10:08 Ssshd
   0 lrwxrwxrwx    1 root     system           14 Apr 08 12:04 Swinbindd -> ../init.d/${i}
 

Originally posted by: AyappanP

There were some issues with symbolic linking in Samba 4.10.6. It is fixed in Samba 4.10.13. Please update it. 

Originally posted by: Tin_Cup

yes, thanks, that did fix it!