Wisdm segfault loop

edit: gateway is RAK7285C

while looking at something else this floated across the logs:

Tue Aug 27 21:07:03 2024 kern.info kernel: [ 4897.772027] do_page_fault(): sending SIGSEGV to wisdm for invalid write access to 77777da4
Tue Aug 27 21:07:03 2024 kern.info kernel: [ 4897.788491] epc = 77de2e78 in libc.so[77d66000+9c000]
Tue Aug 27 21:07:03 2024 kern.info kernel: [ 4897.798536] ra  = 0040cb70 in wisdm[400000+116000]
Tue Aug 27 21:07:03 2024 user.info restify: 127.0.0.1 - - [27/Aug/2024 21:07:03] "GET /diag/syslog HTTP/1.0" 200 -
Tue Aug 27 21:07:05 2024 user.info restify: 127.0.0.1 - - [27/Aug/2024 21:07:05] "GET /diag/syslog HTTP/1.0" 200 -
Tue Aug 27 21:07:05 2024 user.info wisdm[1087]: AWS IoT SDK Version 3.0.1-
Tue Aug 27 21:07:05 2024 user.info wisdm[1087]: WisDM Agent Version 1.2.5
Tue Aug 27 21:07:05 2024 user.info wisdm[1087]: ThingName 9181011E6040521001
Tue Aug 27 21:07:05 2024 user.info wisdm[1087]: Starting WisDM Agent…

the pc is in libc w/o a stack trace. the startup scripts are restarting wisdm so it appears that things are working ok, but it might not be great to loop that way.

1 Like

Hi @peter.chang which version of the WisGateOS2 is used? What is the main connectivity to the internet? Is that getaway registered to WisDM?

sorry, i thought that i pasted the fw version w/ the model. it’s curently running WisGateOS_2.2.2_RAK.

What is the main connectivity to the internet?

its upstream connection is via ethernet and seems to be working enough to get data to/from aws.

Is that getaway registered to WisDM?

yes, according to the web dashboard, but i haven’t been checking that.