02-10-2018 11:13 PM
dear all
We have RT Crashing Periodically problem, we fail to solve the problem, try to find help from you.
LV version 2014 sp1 with some 2015 software package
run RT.rexe in Crio9039
#OSName: Linux#OSVers: 3.14.40-rt37-3.0.0f1#OSBuild: 200232#AppName: lvrt#Version: 14.0.1
During running the RT program in Crio9039 RT Crashing Periodically. The RT will restart automatically.
path: \var\volatile\log\auth.log file suggest the RT reboot crash and reboot cause of session closed for user lvuser
2018-02-10T21:35:01.000+08:00 NI-cRIO-9039-01B76F67 crond[23159]: pam_unix(crond:session): session opened for user root by (uid=0)2018-02-10T21:35:01.000+08:00 NI-cRIO-9039-01B76F67 CROND[23159]: pam_unix(crond:session): session closed for user root2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[1984]: pam_unix(su:session): session closed for user lvuser2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[23238]: Successful su for lvuser by admin2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[23238]: + ??? admin:lvuser2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[23238]: pam_unix(su:session): session opened for user lvuser by (uid=0)2018-02-10T21:40:01.000+08:00 NI-cRIO-9039-01B76F67 crond[23531]: pam_unix(crond:session): session opened for user root by (uid=0)2018-02-10T21:40:01.000+08:00 NI-cRIO-9039-01B76F67 CROND[23531]: pam_unix(crond:session): session closed for user root
after reboot /var/local/natinst/log/lvrt_14.0.1_lvuser_cur.txt show some strange waring
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 1 processorsInitExecSystem() call to GetNumProcessors() reports: 4 processorsInitExecSystem() will use: 1 processors <DEBUG_OUTPUT>02/10/18 下午 09时38分15.066秒DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality./builds/penguin/labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp(748) : DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality.$Id: //labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp#2 $ </DEBUG_OUTPUT>*** Dumping Bread Crumb Stack ***#** Loading: "/home/lvuser/natinst/bin/startup.rtexe/new_Crio9039 RT 4ch Program.vi"*** End Dump *** <DEBUG_OUTPUT>02/10/18 下午 09时38分15.066秒DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality./builds/penguin/labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp(748) : DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality.$Id: //labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp#2 $ </DEBUG_OUTPUT>*** Dumping Bread Crumb Stack ***#** Loading: "/home/lvuser/natinst/bin/startup.rtexe/new_Crio9039 RT 4ch Program.vi"*** End Dump *** <DEBUG_OUTPUT>02/10/18 下午 09时38分15.066秒DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality./builds/penguin/labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp(748) : DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality.$Id: //labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp#2 $ </DEBUG_OUTPUT>*** Dumping Bread Crumb Stack ***#** Loading: "/home/lvuser/natinst/bin/startup.rtexe/new_Crio9039 RT 4ch Program.vi"*** End Dump ***
also we find some warning on RT:
lvrt:/builds/penguin/labviewrt/Core/rt_exec/trunk/7.10/os_extensions/
lvalarms_linux/priorityMapper.cpp:255: void {anonymous}::adjustLinPriorities(const tLinThreadList&,int32_t):Assertion `tparams.__sched_priority >=30 && tparams.__sched_priority <=89~ failed
In the attachement i send the files mentioned include the core_dump file. We really need the help.
Solved! Go to Solution.
02-10-2018 10:55 PM
dear all
We have RT Crashing Periodically problem, we fail to solve the problem, try to find help from you.
LV version 2014 sp1 with some 2015 software package
run RT.rexe in Crio9039
#OSName: Linux #OSVers: 3.14.40-rt37-3.0.0f1 #OSBuild: 200232 #AppName: lvrt #Version: 14.0.1
During running the RT program in Crio9039 RT Crashing Periodically. The RT will restart automatically.
path: \var\volatile\log\auth.log file suggest the RT reboot crash and reboot cause of session closed for user lvuser
2018-02-10T21:35:01.000+08:00 NI-cRIO-9039-01B76F67 crond[23159]: pam_unix(crond:session): session opened for user root by (uid=0) 2018-02-10T21:35:01.000+08:00 NI-cRIO-9039-01B76F67 CROND[23159]: pam_unix(crond:session): session closed for user root 2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[1984]: pam_unix(su:session): session closed for user lvuser 2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[23238]: Successful su for lvuser by admin 2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[23238]: + ??? admin:lvuser 2018-02-10T21:38:09.000+08:00 NI-cRIO-9039-01B76F67 su[23238]: pam_unix(su:session): session opened for user lvuser by (uid=0) 2018-02-10T21:40:01.000+08:00 NI-cRIO-9039-01B76F67 crond[23531]: pam_unix(crond:session): session opened for user root by (uid=0) 2018-02-10T21:40:01.000+08:00 NI-cRIO-9039-01B76F67 CROND[23531]: pam_unix(crond:session): session closed for user root
after reboot /var/local/natinst/log/lvrt_14.0.1_lvuser_cur.txt show some strange waring
InitExecSystem() call to GetCurrProcessNumProcessors() reports: 1 processors InitExecSystem() call to GetNumProcessors() reports: 4 processors InitExecSystem() will use: 1 processors <DEBUG_OUTPUT> 02/10/18 下午 09时38分15.066秒 DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality. /builds/penguin/labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp(748) : DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality. $Id: //labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp#2 $ </DEBUG_OUTPUT> *** Dumping Bread Crumb Stack *** #** Loading: "/home/lvuser/natinst/bin/startup.rtexe/new_Crio9039 RT 4ch Program.vi" *** End Dump *** <DEBUG_OUTPUT> 02/10/18 下午 09时38分15.066秒 DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality. /builds/penguin/labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp(748) : DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality. $Id: //labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp#2 $ </DEBUG_OUTPUT> *** Dumping Bread Crumb Stack *** #** Loading: "/home/lvuser/natinst/bin/startup.rtexe/new_Crio9039 RT 4ch Program.vi" *** End Dump *** <DEBUG_OUTPUT> 02/10/18 下午 09时38分15.066秒 DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality. /builds/penguin/labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp(748) : DWarnInternal 0x00000000: CPU information collection failed! Assuming minimal functionality. $Id: //labview/components/CPUInfo/trunk/14.0/source/lib/CPUInfo.cpp#2 $ </DEBUG_OUTPUT> *** Dumping Bread Crumb Stack *** #** Loading: "/home/lvuser/natinst/bin/startup.rtexe/new_Crio9039 RT 4ch Program.vi" *** End Dump ***
also we find some warning on RT:
lvrt:/builds/penguin/labviewrt/Core/rt_exec/trunk/7.10/os_extensions/
lvalarms_linux/priorityMapper.cpp:255: void {anonymous}::adjustLinPriorities(const tLinThreadList&,int32_t):Assertion `tparams.__sched_priority >=30 && tparams.__sched_priority <=89~ failed
In the attachement i send the files mentioned include the core_dump file. We really need the help.
02-23-2018 10:09 AM - edited 02-23-2018 10:10 AM
From the logs it looks like the get CPU Usage vi may be having an issue.
Are you using this vi or are you trying to get CPU usage in another way?
If you remove that code does the crash resolve?
Are you using a localized version of labview (non english)? just curious, might be a library name is being manipulated. If you have access to a english only computer can you try deploying your app from there if the above is true?
You might be able to spin your own library in C to get CPU info, or call into system exec and run top or something.
02-23-2018 05:57 PM
Hello KHartley,
we will try to install english version to deploy, at first i will try to remove the CPU usage vi and see the result.
do you have idea about some warning on RT monitor? does some priority mapper (used by timed structures) problem?
lvalarms_linux/priorityMapper.cpp:255: void {anonymous}::adjustLinPriorities(const tLinThreadList&,int32_t):Assertion `tparams.__sched_priority >=30 && tparams.__sched_priority <=89~ failed
02-27-2018 07:44 AM
I had something simular as you could see on the forum.
Now I rebuild my application using all the arrays with a pre defined length. And since I don't have the problem anymore.
It looked that my problem was a memory leak.
Kind regards
Joris