search

monome / norns

norns is many sound instruments.
http://monome.org
GNU General Public License v3.0
630 stars 145 forks source link

norns goes unresponsive when router turns off #385

Closed pq closed 6 years ago

pq commented 6 years ago

twice today my norns has gone unresponsive after the router it was connected to was turned off. i'm guessing this would be easily reproducible with these steps:

  1. connect to lan (or in my case phone hotspot)
  2. turn off router
  3. wait a bit

another data point: in my case I was on the meters page so i guess it's possible that menu has something to do with it.

possibly related to: #312

tehn commented 6 years ago

difficult to debug without starting matron via a screen connection (where wifi isn't required)

pq commented 6 years ago

thinking ahead to when we have time to debug a repro, consider launching matron from a screen session and triggering the crash so we can what we see. hopefully matron will tell us something interesting.

forward-pointer (so i don't forget):

./crone.sh > /dev/null &
build/matron/matron
catfact commented 6 years ago

it seems plausible (?) that this is related to scsynth freaking out / crashing when network time sync produces a big jump in the system clock. not clear how to fix that yet.

in any case, for debugging you might want to look at the output of sclang, which means running sclang directly in a separate screen (instead of ./crone.sh > /dev/null

catfact commented 6 years ago

also, are you running with -s in the jackd configuration? that seems to prevent jackd from crashing on xruns from ALSA. the latter is likely to occur when network configuration changes and scsynth gets momentarily clogged up with UDP packets (or something)

pq commented 6 years ago

also, are you running with -s in the jackd configuration?

yep.

in any case, for debugging you might want to look at the output of sclang, which means running sclang directly in a separate screen

when i have a little more time and get to do some script hacking i'll set myself up that way and see if i can catch a crash.

tehn commented 6 years ago

this (and SYNC and UPDATE) seem like good candidates to deactivate the current script and shutdown crone.

simonvanderveldt commented 6 years ago

@pq does this still happen/reproduce on the 180603 update?

pq commented 6 years ago

@simonvanderveldt : hasn't recurred. optimistically closing. 🤞