04-04-2013 09:06 AM
ugh.. don't know what systemd wants there..
Anyway, that nipal script needs an argument, either start, stop, restart, etc..
Try 'nipal start' as root user. Then make sure /dev/nipalk is there, then try lsdaq again?
This way we'll bypass (hopefully) systemd.
04-04-2013 07:23 PM
Hi irwan
It seems there is a problem running the script, or the script simply doesnt create /dev/nipalk
linux-z992:/etc/init.d # ./nipal stop
linux-z992:/etc/init.d # ./nipal start
linux-z992:/etc/init.d # ls /dev/ -l |grep ni
prw------- 1 root root 0 Apr 3 10:34 initctl
pr-------- 1 rosmini tty 0 Apr 5 05:03 xconsole
I looked inside /etc/init.d/nipal and it appeared to be empty, perhaps the nipal in the iso was broken or simply empty? Would you happen to have a copy of the file on hand? or provide what was meant to be inside the nipal scrip?
04-05-2013 05:48 AM
Well, if nipal script is totally empty, that might explain why systemd was complaining. OpenSUSE 12.1 is supported, so we tested on that distrib before.
Sorry, giving you content of nipal script seems futile. It depends on what version you have in your installer. And if that script didn't install properly, I don't know what other files might be corrupted/missing.
I suggest fully uninstall and rerunning the installer there. Or maybe also re-downloading the latest one. Version 3.6 seems to be the latest: http://joule.ni.com/nidu/cds/view/p/id/3436/lang/en
04-07-2013 06:34 PM
Hi irwan
Uninstalling and reinstalling was the first thing that we tried. I have been implementing version 3.6 since its the version which is provided as the most recent on the NI website but the error remains the same.
I uninstall NIVISA too,I believe I've tried the reinstall at least 3 times.
04-08-2013 07:23 AM
ok, but if there's installation problem, debugging runtime is unproductive.
Are you sure /etc/init.d/nipal is empty ? it's supposed to be a soft-link to the nipal script under /usr/loca/natinst/nipal/ somewhere. Is the nipal script under that dir empty as well ? If not, try running that script.
If it still doesn't work, try running the commands manually from the start() function .. see where the problem occurs.
Sorry, I don't know what else to tell you at this point.. It could have something to do with the HW you're installing this on ? AFAIK, none of our test HW for OpenSuSE uses macmini. We use standard x86 platform.. But it should just work, since macmini is similar to x86, but I have no idea.
04-08-2013 08:20 PM
Hi irwan
Those are the scripts which are under that directory, I tried running the linipalu.so.2.8.1 but got a segmentation fault?
linux-z992:/usr/local/natinst/nipal # ls sbin/
nipalsm
linux-z992:/usr/local/natinst/nipal # ls bin/
nipaliInstallerUtility.sh nipalps readInfFiles
nipalkiInstallerUtility.sh palModuleMgr.sh
linux-z992:/usr/local/natinst/nipal # ls lib/
libnipalu.so.2.8.1
Running the nipalsm script comes up with the following message
linux-z992:/usr/local/natinst/nipal # ./sbin/nipalsm
Usage: ./sbin/nipalsm [-d] path/serviceLibrary
-d indicates debug mode and will not call daemon()
The others ran but didnt really do anything, noticable.
04-09-2013 09:50 AM
> cd /usr/local/natinst/nipal
> find -type f | grep nipal
AFAIK, there should be the nipal script under etc under that dir
libnipalu.so is a shared library, not something you can just run.
04-09-2013 09:03 PM
I ran the command you recommended and recieved the following:
linux-z992:/usr/local/natinst/nipal # find -type f |grep nipal
./sbin/nipalsm
./lib/libnipalu.so.2.8.1
./src/objects/nipalk-unversioned.o
./etc/errors/ChineseS/nipal-errors.txt
./etc/errors/English/nipal-errors.txt
./etc/errors/Japanese/nipal-errors.txt
./etc/errors/French/nipal-errors.txt
./etc/errors/German/nipal-errors.txt
./etc/errors/Korean/nipal-errors.txt
./etc/nipal.dir
./etc/init.d/nipal
./bin/nipaliInstallerUtility.sh
./bin/nipalps
./bin/nipalkiInstallerUtility.sh
looks like the only scripts are the nipalsm, nipalps, and the empty nipal script.
04-10-2013 11:07 AM
Look at nivisa installer that you've downloaded from ni. If you look inside the iso file, there's a file called nivisa-runtime-...tar.gz.
Here's the list of commands I used to extract files under nipali rpm, so hopefully you can get the right nipal script to install to the correct place.
irwand@linux-nskq:~/Downloads> tar xzvf nivisa-runtime-5.3.0f0.tar.gz
rpms/
rpms/niorbki-3.0.0-f0.x86_64.rpm
rpms/nipalki-2.9.1-f0.x86_64.rpm
rpms/nivisak-5.3.0-f0.i386.rpm
rpms/nivisak-5.3.0-f0.x86_64.rpm
rpms/niorbki-3.0.0-f0.i386.rpm
rpms/nipali-2.9.1-f0.i386.rpm
rpms/niorbi-3.0.0-f0.i386.rpm
rpms/nimdnsresponder-2.1.1-f0.i386.rpm
rpms/nirpci-4.3.0-f0.i386.rpm
rpms/nikali-2.3.0-f0.noarch.rpm
rpms/nipalki-2.9.1-f0.i386.rpm
rpms/nipalerri-2.9.1-f0.i386.rpm
rpms/nivisa-5.3.0-f0.i386.rpm
bin/
bin/README.gpl
bin/rpm
bin/rpmq
bin/rpm2cpio
bin/installerUtility.sh
bin/cpio
irwand@linux-nskq:~/Downloads> cd rpms/
irwand@linux-nskq:~/Downloads/rpms> mkdir nipali.files
irwand@linux-nskq:~/Downloads/rpms> cd nipali.files/
irwand@linux-nskq:~/Downloads/rpms/nipali.files> rpm2cpio ../nipali-2.9.1-f0.i386.rpm | cpio -idmv
./usr/local/natinst
./usr/local/natinst/nipal
./usr/local/natinst/nipal/bin
./usr/local/natinst/nipal/bin/nipaliInstallerUtility.sh
./usr/local/natinst/nipal/bin/nipalps
./usr/local/natinst/nipal/bin/readInfFiles
./usr/local/natinst/nipal/etc
./usr/local/natinst/nipal/etc/bootdrivers
./usr/local/natinst/nipal/etc/inf
./usr/local/natinst/nipal/etc/init.d
./usr/local/natinst/nipal/etc/init.d/nipal
./usr/local/natinst/nipal/etc/services
./usr/local/natinst/nipal/lib
./usr/local/natinst/nipal/lib/libnipalu.so.2.9.1
./usr/local/natinst/nipal/sbin
./usr/local/natinst/nipal/sbin/nipalsm
1305 blocks
Look at nipal script there, to make sure it's not empty, and replace the file in /usr/local/natinst/nipal/etc/init.d/nipal
This is so weird. If the nipal script extracted from the rpm isn't empty, seems like there's something else going on in your system. I don't have any confidence that none of the other files aren't corrupted from installing ni visa. Is your disk space full or something? what's the output of 'df' command?
04-10-2013 04:28 PM
One thing to do would be to run, as root,
# rpm -qVa nipali nipalki
That command will validate the files on your system against what the rpm database says they should be. When I run it on one of my test systems, I see:
S.5....T. /usr/local/natinst/nipal/etc/nipal.dir
If you look in the rpm man page, it documents what each of those values on the left means. In this case, all files passed the verification test except for /usr/local/natinst/nipal/etc/nipal.dir
S file Size differs
M Mode differs (includes permissions and file type)
5 MD5 sum differs
D Device major/minor number mismatch
L readLink(2) path mismatch
U User ownership differs
G Group ownership differs
T mTime differs
P caPabilities differ
The size, contents, and modification time of that one file is different than what was in the rpm.
For that one file to be different is ok - that file actually gets touched by the postinstall scripts. There might be others that in the normal course of events can differ from what rpm says, but nonetheless, I expect it to tell us something useful about whether your files are what they should be.