#1708

Thanks for the reply. Is include even part of lua?

https://www.lua.org/manual/5.3/

I don’t see it in the manual and Google didn’t help.

#1709

no, include is a norns function

it is provided exactly because require has a cache

it is referenced in this scripting doc but sadly doesn’t have an anchor reference
https://monome.org/docs/norns/script-reference/

2 Likes
#1710

Thanks! sorry I missed that. Is there a time when I should use require over include? like when the module is not in the local directory? Or is include always the right choice?

#1711

they do different things. i made a FAQ:

TL/DR: use require for system modules you won’t edit and when you don’t want to copy the system state when your script is run. use include for simply breaking your local script’s code into separate files for usability.

3 Likes
#1712

I’m sorry to ask such a basic question, I’m sure it’s been asked, but the archive is getting so vast it’s difficult to find…

I’m confused how to get my grid work with norns. For example at awake I get the lights blinking, but I can not use grid to change the patterns.

#1713

be sure your grid is selected properly in slot 1 of SYSTEM > DEVICES > GRID

secondarily, also make sure your software is up to date (which are you on?), and you have the newest version of AWAKE installed (by copying the newest via SFTP)

#1714

thanks. the problem seemed to be i had grid selected on all slots… :blush: works now

#1715

So, here’s a weird one…Norns was working untill: I “cyberducked” into Norns and tried to update Zellen with the new Zellen 1.2 script, but kept getting error messages that it couldn’t create the folder…So then I figured I should run the latest update (I haven’t untill now)…and then I got an error message saying that I don’t have enough disk space. Sure enough, when I check the system page on the norns screen it says I have 0 Mb left. However, before this attempt, I had >1gb of space. I checked with cyberduck to see if any huge files somehow got transferred, but couldnt find anything. The largest file is a tape reel thats 9 Mb…I also deleted the whole Zellen folder from Dust/Code via cyberduck, but I’m still getting the error. Have tried both Sleep and Hard Reset with same results

HELP! Was stoked to be able to use Norns for an upcoming performance…(mental note, take heed of the warning I’ve seen before, never update before a show!)

#1716

@gnome666 this update copies very little and IMHO is not a likely direct cause of the issue.

more likely the filesystem was already full.

i suspect a buildup of log files as described/addressed earlier in this thread.

log into norns (screen will work for this if you can’t network), then:.
du -h /var/log to see if logfiles are big
ls -lahS /var/log to see more specifically what files are big

then you probably want, e.g.
sudo rm -rf /var/log/syslog
sudo rm -rf /var/log/kern.log

or even the big hammer
sudo rm -rf /var/log/*

… but this is ultimately a quick fix. if indeed that is the problem, we should see what is filling up the logs, and/or rotate/cull them more aggressively. (which i dn’t know how to do but maybe e.g. @simonvanderveldt does)

…i’ll check that crone isn’t printing a lot of debug junk or something

#1717

Do you mean log in with cyber duck? Or maiden? If it’s terminal level stuff it’s a bit outta my league :frowning:

#1718

its terminal level stuff but you can do it

open terminal
ssh we@norns.local
password: sleep (unless you’ve changed it, which in fact i recommend doing)

then the other stuff above

#1719

will give it a go now. if it helps, turns out that the dustv1 folder is bigger than dust folder on norns…can it be deleted? my total we folder is about 600mb

25%20PM
Screen Shot 2019-08-09 at 8.46.25 PM.png1044×794 78.5 KB
45%20PM
Screen Shot 2019-08-09 at 8.45.45 PM.png1058×804 93.8 KB

#1720

yea, back up things you want (like audio)

#1721

looks like kern.log is taking up 1.4 GB? can that be right?18%20PM

11%20PM
Screen Shot 2019-08-09 at 8.50.11 PM.png826×1144 191 KB

#1722

btw, i can still run all the installed scripts on my norns with no problem. it seems like its purely a storage issue of not having enough space to do the update procedure

#1723

delete the kern.log
sudo rm -rf /var/log/kern.log

(if you want to be extra helpful, see upthread for how to send us a snippet of kern.log before delting it so we can try and see what is doing that… but it will surely continue to happen so no worries there)

it’s “right” in the sense of, yes, it really is taking up that much space

it’s “wrong” in every other sense.

@tehn et al we should probably address this behavior. i can pitch in with eliminating excess logging from crone and matron. it seems like log rotation should be preventing this in any case, but i don’t know enough about it.

#1724

Thanks for all the help. I’m logged off and away from Norns, but will definitely try to get you some info before I delete the kern.log :+1:

#1725

Can someone suggest a “stress-test” script that uses lots of CPU?

I’m curious about monitoring/charting CPU% and Temperature levels with the pi 4

#1726

we actually did a ton of log reduction last time we had this problem and i haven’t seen it emerge again. i can check on kern.log on my system to see if it’s growing.

#1727

i’d suggest just doing this using stress on the command line, not via the norns software stack.

2 Likes