[nos-bbs] JNOS Crash

Jerome Schatten romers at shaw.ca
Fri Nov 15 23:51:07 EST 2013

On the CentOs there is a copy of libc.so6 in the same relative position 
on the /lib tree as in the arm system, so I'm reasonably sure that's OK. 
I don't think the copy in /lib is the problem either -- it's probably 
peculiar to CentOs.

  Can you see anything in the jnos log file when  jnos fails?  Is it 
always crashing during a forward cycle or some other notable event? In 
other words, does it fail doing the same operation each time? What does 
the log file say just before the crash?


On 13-11-15 07:39 PM, Ray Quinn wrote:
> On 11/15/2013 10:03 AM, Jerome Schatten wrote:
>> Only a guess.... but if it were I, I would look on the pi setup to 
>> see where libc.so.6 lived, and then look and see if it's
>> in the same place in the system that's crashing. If not, on the 
>> crashing machine, stick  a copy of libc.so.6 into the same directory 
>> as it is on the pi machine, and see what happens.
> On the Pi:
> root at visbbs:/# locate libc.so.6
> /lib/arm-linux-gnueabihf/libc.so.6
> On CentOs
> [root at nos jnos2_headless]# locate libc.so.6
> /lib/libc.so.6
> /lib/i686/nosegneg/libc.so.6
> [root at nos jnos2_headless]#
> They are in different places, most likely, in my opinion, because of 
> different architecture. As you probably know, the Pi is ARM based. 
> Could it be because there is two copies of libc.so.6 in different 
> directories?

More information about the nos-bbs mailing list