You are here

Please help collect information on your nodes

8 posts / 0 new
Last post
AE6XE
AE6XE's picture
Please help collect information on your nodes

The AREDN firmware currently has workaround logic to clean up 'zombie' processes due to defects in ether linux or a program called 'iw" (a program AREDN frequently uses to obtain information about the RF link).    This logic detects a stuck or zombie process that does not properly terminate when expected and is not freeing up RAM and other resources.    It is possible that upgrades to linux and 'iw' in recent AREDN releases have resolved the root cause defects.   To know, we can check to see if this logic is still triggering to kill these stuck processes.  If it is no longer doing anything, then we can remove this logic in a future release.

Please take a look at your mesh nodes that have been running for extended timeframe (well, more than a week or so.).  Specifically look for a file called /tmp/zombie.log .   Does this file exist?   A 'no' is meaningful information to pass back.  If  a 'yes', please attach this file to your response or send to  ae6xe at arrl dot net.   My tower nodes do not have any 'hits' (/tmp/zombie.log does not exist) demonstrating that this logic is not needed at my sites.  What about your site?

Joe AE6XE 

nc8q
nc8q's picture
/tmp/zombie.log . Does this file exist?

Hi, Joe:

NB613, NC8Q-Centerville-Beavercreek 12 days, No.
NB607, NC8Q-Centerville-Bellbrook 16 days, No.
NB613, NC8Q-Centerville-HuberHeights 13 days, No.
NB613, NC8Q-Centerville-Kettering 12 days, No.
NB607, NC8Q-Centerville-Miamisburg 16 days, No.
NB613, NC8Q-HuberHeights-Centerville 13 days, No.

I did catch a glimpse of clean_zombie.pid occasionally.

I hope this helps,
Chuck

K5DLQ
K5DLQ's picture
It would be good to include

It would be good to include the firmware version as well.  (to determine if newer releases have fixed this)

K6CCC
K6CCC's picture
No zombie.log found

Same as Chuck.  Checked 14 nodes and a few clean_zombie.pid, but no zombie.log  Most of my nodes have an uptime of about 4 1/3 days (you guys keep releasing new nightly builds...)
Nightly 661 on all
 

AJ6GZ
None

Nothing found on various BaseBox2, NSM2 XW/XM, NSM5 XW, PB M5 400's, uptime around 7 days, mostly nightly 648.

Ian

VK3VDP
VK3VDP-GL150 - Uptime 2 weeks

VK3VDP-GL150 - Uptime 2 weeks (was rebooted today due to a SSH Key issu) firmware: 3.21.4.0 No log in /tmp. Will also check my other nodes and post tomorrow.
73's
Darrin

VK3VDP
Zombie

Checked my two other nodes that have been up for weeks and no sign of the log file in /tmp

73's
Darrin
VK3VDP

w6bi
w6bi's picture
Not found

Did a spot check of a half dozen nodes in Ventura County that had been running for a couple of months.   No zombie log files found in /tmp

Orv W6BI
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer