#1912

Ran into the no space left on device issue today. Seems like the issue is with /var/log/daemon.log, and lots of entries of the form:

Nov 4 00:35:10 norns crone[337]: softcut: setting voice output level 0: 1
Nov 4 00:35:10 norns crone[337]: softcut: setting voice output level 1: 1

#1913

oops. those prints were cleaned up in the recent update.

but i don’t know why our log rotation schedule isn’t working.

#1914

Out of curiosity, how much space should be free?

Filesystem Size Used Avail Use% Mounted on
/dev/root 3.6G 3.3G 75M 98% /
devtmpfs 486M 0 486M 0% /dev
tmpfs 490M 83M 408M 17% /dev/shm
tmpfs 490M 6.5M 484M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 490M 0 490M 0% /sys/fs/cgroup
/dev/mmcblk0p1 43M 34M 8.9M 80% /boot
tmpfs 98M 0 98M 0% /run/user/1000

And one other thing I’ve noticed of late is that my Norns seems to start up with no script selected. I don’t think that used to be the case? Running 190801.

#1915

I also ran into this awhile back, and it was an issue with the log and kernal files being too big. I deleted them via Cyberduck and it fixed the problem. I don’t remember which version was running at the time or if I update since then, but haven’t run into the problem since.

#1916

OK, I know about the logs. What kernel files can deleted/from where?

#1917

I don’t remember exactly and I’m away from my Norns right now…I tried searching these forums, but I cant even find the posts where I got the answer :man_shrugging:

#1918

okay, found it

with fix here:

#1919

Nope, that looks ok on my Norns.

#1920

ok— back on log investigation— surprised this re-emerged.

you can also delete the daemon logs

sudo rm /var/log/daemon.*
#1921

I already have. Just wondering if there are other places I should look to tidy up? It would be helpful to know what a clean Norns should have in terms of available user space.

#1922

i think the logs are the only wily disk fill.

unless you ran up some TAPE?

#1923

FWIW, I just tried to update and my disk was full again. This time it was the daemon.log files (last time it was kern.log). not sure if that helps trouble shooting at all. 20%20PM

02%20PM
Screen Shot 2019-10-01 at 5.27.02 PM.png954×1222 211 KB

after deleting the 2 biggest log files, I was able to easily update via wifi from the Norns menu.

(here are the instructions @zebra provided before, kindly walking me through terminal stuff for those following this thread who are in the same boat)

41%20PM
Screen Shot 2019-10-01 at 5.29.41 PM.png1136×172 10.5 KB
51%20PM
Screen Shot 2019-10-01 at 5.29.51 PM.png1528×516 35.7 KB
26%20PM
Screen Shot 2019-10-01 at 5.29.26 PM.png1440×350 22.8 KB

#1924

daemon.log contains all the output from the crone process, among other things.

in the previous release there was some debug crud left in there. didn’t realize it would be an issue. in the last release i believe that should be gone.

sorry i don’t understand off top of head, enough about how to set more aggressive systemd service log rotation.

1 Like
#1925

Hello, apologies if this has been covered before, is there somewhere where I can read documentation on each of the engines? I’m having trouble parsing the immense amounts of discussion here as a mode for learning Norns.

3 Likes
#1926

You might realize this already but they generally each have their own thread here, and should have documentation in their README. Some attempt at centralizing this information that isn’t too much of a maintenance nightmare seems like a good idea, though.

4 Likes
#1927

I have a potential fix for this, but it has some issues. I would greatly appreciate a code review. PR here: https://github.com/monome/norns/pull/886

1 Like
#1928

Troubleshooting Wifi connectivity issues. I’ve searched through previous posts, but it seems earlier issues were perhaps solved with an update. Previously I’ve had no issues with updating Norns via Wifi or SSH connectivity via Wifi.

I’m running Norns 190817, and am trying to update to this most recent update. It won’t get past STATUS: activating. Doesn’t get an IP or any SIGNAL strength. My laptop / other devices connect to Wifi just fine.

I bought a new Wifi nub today, with same specs as the one included, but still the same issue persists.

Anyone else encounter this suddenly / randomly?

Fates - a DIY norns DAC board for Raspberry Pi
#1929

Have you ruled out signal strength by getting close to your wireless router? When I’ve seen this it was in places where my phone and computer connected fine, but I needed to move closer w/norns to get it to connect.

#1930

Yes, thank you for pointing that out. I’ve tried right next to the router, no luck.

The network name will appear briefly, then disappear. Status doesn’t change (from activating), and no register IP or Signal strength.

A couple times, Norns has locked up with no ability to control, requiring long wait times until I can put to sleep and wake up.

UPDATE: wifi working now! Perhaps it was @license tip to reboot router, although that didn’t work immediately. 24 hrs later, with my new wifi nub, wifi connected and update ran seamlessly. Old wifi nub couldn’t complete the update. Thanks for all of your help!

1 Like
#1931

Rats. I haven’t seen similar behavior. I’m sure someone else will chime in.

1 Like