From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Linux Users

cancel
Showing results for 
Search instead for 
Did you mean: 

uninstall NI-VISA 17 in Linux hang in Pre Uninstallation %postun(niiotracei-17.0.0-f0.x86_64) scriptlet failed, signal 2

I need help understanding how to uninstall  NI-VISA  17  on  Redhat 7 Linux.    When I tried to do it as the root user  it hung in the pre uninstallation  as shown below.   Also shown are the RPMs

 

*****************************************************************************
NI-VISA for Linux
version 17.0.0f1 for Linux
*****************************************************************************

rpm found
dpkg Not found in current path
dpkg not available, uninstall will not be using dpkg.
NI-VISA for Linux version 17.0.0f1
is about to be uninstalled using rpm at /usr/local/natinst

Continue? [Yn] Y

Uninstalling NI-VISA for Linux version 17.0.0f1...
cat: /etc/natinst/linux/linux.dir: No such file or directory
Pre Uninstallation .........................................................................

 

^C

warning: %postun(niiotracei-17.0.0-f0.x86_64) scriptlet failed, signal 2

 

[emssuser@sqalrh3 ~]$ rpm -qa | grep ^ni
ni-mdbg-nikalmod-17.0.0.49152-0+f0.x86_64
nisvcloc-17.0.0-1.noarch
ni-visa-sysapi-17.0.0.49152-0+f0.x86_64
ni-pal-17.0.0.49152-0+f0.i386
nivisak-17.0.0-f0.x86_64
nitdmsi-32bit-16.0.0-f0.x86_64
nirocoerri-17.0.0-f1.i386
nisyscfgi-17.0.0-f0.i386
nisslcerts-17.0.0-3.0.noarch
nicurli-16.0.0-f0.i386
nidimki-17.0.0-f0.x86_64
ni-pxirm-resources-17.0.0.49155-0+f3.noarch
nicurli-16.0.0-f0.x86_64
ni-pxipf-errors-17.0.0.49152-0+f0.noarch
ni-pal-nikalmod-17.0.0.49152-0+f0.x86_64
ni-pxirm-nikalmod-17.0.0.49155-0+f3.x86_64
nipalki-17.0.0.49152-0+f0.noarch
nissli-16.0.0-f0.i386
ni-mdbg-errors-17.0.0.49152-0+f0.noarch
ni-visa-sysapi-17.0.0.49152-0+f0.i386
nispyi-2.8.1-f0.i386
nipxipfki-17.0.0.49155-0+f3.noarch
nissli-32bit-16.0.0-f0.x86_64
ni-apal-errors-17.0.0.49152-0+f0.noarch
ni-mxdf-nikalmod-17.0.0.49152-0+f0.x86_64
nispylogsupp-17.0.0-f0.i386
nitdmsi-16.0.0-f0.x86_64
ni-orb-errors-17.0.0.49152-0+f0.noarch
ni-orb-17.0.0.49152-0+f0.i386
nitargetcfgi-3.0.0-f1.x86_64
niiotracei-17.0.0-f0.x86_64
nispylogsupp-17.0.0-f0.x86_64
nitdmsi-16.0.0-f0.i386
ni-mxdf-errors-17.0.0.49152-0+f0.noarch
nicurli-32bit-16.0.0-f0.x86_64
ni-kal-17.0.0.49152-0+f0.noarch
nimdnsresponder-17.0.0-f0.i386
ni-orb-nikalmod-17.0.0.49152-0+f0.x86_64
nivisa-17.0.0-f0.i386
nivisaserver-17.0.0-f0.i386
nissli-16.0.0-f0.x86_64
ni-pal-errors-17.0.0.49152-0+f0.noarch

 

Brad Whaley
LabVIEW Certified Engineer
0 Kudos
Message 1 of 2
(2,614 Views)

*facepalm*

 

Despite the fact that pre/post scriptlets are *rarely* needed in the first place, these of course have to cope w/ broken installations (otherwise defeats the whole idea of package management).

 

You can remove the packages manually by calling rpm directly - w/ '--noscripts' flag.

(might leave some garbage that the scripts supposed to clean up)

 

@NI: is it really so hard getting some experienced devops engineers for the linux packaging ? Last time I had a call w/ NI folks, they told they only have 1..2 people (IIRC even just part time) for the Linux stuff. Obviously this can't work. 

Folks, if you need help, just call me. I can even arrange a larger team of experts

if needed.

Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
0 Kudos
Message 2 of 2
(2,482 Views)