#2079

Can you run du -h /var/log and post the output here?

#2081

I ended up nuking daemon.log, kern.log and messages, which got me back 1.5 GB. Keeping an eye on them for now.

Terminal output below for ref (post-cleanup). I’m on 191028 btw.

10.42.0.1 /var/log $ ls -l 

total 18776
-rw-r--r-- 1 root root       0 Nov  1 06:25 alternatives.log
-rw-r--r-- 1 root root     364 Jan 14  2019 alternatives.log.1
-rw-r--r-- 1 root root     500 May 23  2018 alternatives.log.2.gz
drwxr-xr-x 2 root root    4096 Nov  1 06:25 apt
-rw-r----- 1 root adm   804749 Nov 17 00:02 auth.log
-rw-r----- 1 root adm    32393 Nov  1  2018 auth.log.2.gz
-rw-r--r-- 1 root root    3885 May 14  2018 boot.log
-rw-r--r-- 1 root root       0 Apr 18  2018 bootstrap.log
-rw------- 1 root utmp    2304 Nov 16 19:49 btmp
-rw------- 1 root utmp    1920 Oct 15 20:04 btmp.1
-rw-r----- 1 root adm   208292 Nov 17 00:03 daemon.log
-rw-r----- 1 root adm  9728743 Nov  1  2018 daemon.log.1
-rw-r----- 1 root adm    97927 Nov 17 00:01 debug
-rw-r----- 1 root adm     7546 Nov  1  2018 debug.2.gz
-rw-r--r-- 1 root root       0 Nov  1 06:25 dpkg.log
-rw-r--r-- 1 root root   27645 Jan 14  2019 dpkg.log.1
-rw-r--r-- 1 root root   12677 Nov  1  2018 dpkg.log.2.gz
-rw-r--r-- 1 root root    2640 May 15  2018 faillog
-rw-r----- 1 root adm    68840 Nov 17 00:02 kern.log
-rw-r----- 1 root adm   454236 Nov  1  2018 kern.log.2.gz
-rw-rw-r-- 1 root utmp  292292 Nov 17 00:02 lastlog
-rw-r----- 1 root adm   184952 Nov 17 00:02 messages
-rw-r----- 1 root adm   249476 Nov  1  2018 messages.2.gz
drwxr-x--- 2 root adm     4096 Mar  5  2018 samba
-rw-r----- 1 root adm  1052617 Nov 17 00:01 syslog
-rw-r----- 1 root adm  2890973 Oct 31 22:54 syslog.1
-rw-r----- 1 root adm  1092478 Nov  1  2018 syslog.2.gz
-rw-r----- 1 root adm  1947641 Nov 17 00:02 user.log
-rw-r----- 1 root adm     5002 Nov  1  2018 user.log.2.gz
-rw-rw-r-- 1 root utmp   20352 Nov 17 00:03 wtmp
-rw-rw-r-- 1 root utmp  225024 Oct 31 22:56 wtmp.1

10.42.0.1 /var/log $ du -h /var/log

48K	/var/log/apt
4.0K	/var/log/samba
19M	/var/log
10.42.0.1 /var/log $
#2082

Sorry if i’m just nothing but problems lately…

I did make it through the gig on Thursday.
:stuck_out_tongue:

just wired everything up again and got a ton of issues…

  • that business with having to remove every single connected device to norns is always happening now when i first set both norns up. i have to remove every instance of them under devices then add them back (sometimes have to reboot norns) and then launch the script.

  • when norns boots up to the last script that was running it is never immediately usable. i have to re-launch the script.

  • one of the norns got stuck on the LOADING screen and i had to use the little reset button on the bottom.

  • both norns will NOT respond to EXTernal MIDI clock from either an e-rm Multiclock or a Deluge over an iConnect box. They worked fine on Thursday but they just will not respond now after several attempts at removing the device, re-booting norns and adding the iConnect box back to the device list. Tried multiple USB and MIDI cables.

Both norns are responding to Grids, FaderFox and 16n.

  • first norns has a MIDI to USB connection, GRID and a 16n
  • second norns has a MIDI to USB connection, GRID and a FaderFox

i’m giving up for the night.

#2083

dang i am super sorry about all the problems.

  • have you tried SYSTEM > RESET in the menu in attempt to solve any problems?
  • which script is not immediately usable? what is the symptom?
  • do the midi sync devices just not work at all, ie, no midi at all from Deluge, or just sync is not working?

i can throw together a midi debug script which might be helpful… basically a midi monitor.

but, more generally: when you’re encountering problems, be sure to turn on maiden and check for error messages… there very likely is something there, and it’ll let us fix it quick.

#2084

tried that and SLEEP several times while trying to get things running.
also had to use the kill button on the bottom once or twice when one of them would just lock up.

one norns had VIALS and the other had MANGL at first.
i then switched to running VIALS on both of the norns.

norns would boot up to a script but there would not be any sound or the ability to control it.

MIDI controls would work from the FaderFox PC12 and the 16n.
it was just clock that both of the norns would not respond to.
tried multiple sources of clock and even changed out cables.

i will run maiden more frequently…
is there anything i need to open up or set in maiden to view all these errors?

#2085

running maiden…

i finally acquired MIDI EXT sync with Vials and switched to ZELLEN for a bit to test with another script.

looks like i had to remove absolutely everything from the MIDI list under DEVICES.

i figured since the 16n and FaderFox were both working that i shouldn’t have to remove them.

however…once i cleaned everyone out of the DEVICES pool and added the iConnect box in the first slot it immediately reacted to EXT MIDI clock.
i then added the 16n and it started reacting.

now it’s doing something else really weird.
it’s ignoring MIDI CC #34 and #35 from the 16n.
(it did this before with fader CC#35 but not with more of them)
it will not “learn” them and will not respond if they are added manually.
i checked the 16n on the Mac with a MIDI scanner and it’s working correctly.

all other faders are acting properly and i can see and hear the changes.

one thing i noticed in Maiden…
when i look at the norns system state…it lists that the iConnect is listed in slot one but the 16n does not show up even though norns is responding to it.
(maybe i’m not looking in the right place?)

here’s a pic of maiden showing norns state:

26%20AM
26%20AM958×818 119 KB

#2086

Vials author here, sorry if it turns out that its causing some grief here. In truth its likely in need of a refactor although its been recently quite stable for me. I will see if I can pinpoint some weak spots that might be causing these problems when I have some spare time

1 Like
#2087

main thing you want to look for are errors in the bottom right window.

nothing says error?

1 Like
#2088

once i had maiden open both norns were not acting up as much.
(hmmm…suspicious…)
:stuck_out_tongue:

anyhow…
no crashes last night.
:partying_face:
just the weird ignoring of some MIDI CC (as stated in the above post) and maidens didn’t update to see the 16n even though norns was working with it.

i’m sure i’ll break something else soon…
:stuck_out_tongue:

1 Like
#2089

SFTP question (searched and not found an answer): I can upload some wav files but not others. I understand that Play expects a 48kHz stereo file, and I can load up some 21.1 BIT rate samples and not others (all wav files). Any idea why? I would not have expected Norns to reject certain types of files but rather, just have issues with certain types of files usages.

[can’t view sample rate, but i’m sure they’re all the same so I don’t think that’s the issue]

#2090

super weird – what exactly happens when you try to upload through STFP? screenshots/error messages + the exact files would be super helpful, feel free to email help@monome.org :slight_smile:

#2091

There’s no error. Nothing.
It just won’t let me.
No transfer happens.

It IS connected though, because if I move on to a different file, it will upload.
Here’s an example of something that WON’T upload.
Here’s an example of something that WILL upload.

Can’t view sample rate on those files, but as I noted I’m nearly certain they’re the same.

EDIT: This is using Cyberduck as recommended.

#2092

hmm. working on my side:

39%20PM
39%20PM2200×1034 221 KB

so, Cyberduck is just not showing the transfer initializing? this is on a factory norns + is your norns software up to date?

#2093

Wow.
That’s very odd! I’ve rebooted Norns (several times) and my computer!
Yes, factory Norns and up to date.

Cyberduck just doesn’t do anything. It’s as if I never even tried to transfer it. Maybe I’ll try a different app.

#2094

wild! have you received the same results with drag + drop as well as the menu Action > Upload?
and you’ve confirmed that the file isn’t populating on norns and perhaps just not showing the transfer?

#2095

Aha! I think I figured out the issue.
It’s not a file problem actually. It appears that either Norns (or, more likely, Cyberduck) doesn’t like super-multi-leveled folder structures. If I pull out the troublesome files from their original folder and try to upload it will work. If I do it from the multi-leveled folder (ie. folders within folders), Cyberduck won’t do any transfer. Very odd.

Same issue w drag and drop or manual selection.

#2096

woah, how deep? useful data point!

#2097

It looks like 10 is the limit for Norns or Cyberduck :slight_smile:

1 Like
#2098

Well, this was a weird one: working with norns here in the studio, walked away for 5min, came back and screen would not display anything. The activity LED was active, could connect via Cyberduck to the file system, but could not get it to restart or do anything else. I tried ;restart command via browser, but it said “not connected to matron” and would not refresh. Finally had to use the bottom button to force it to shut down.

#2099

Is it possible to SSH in via Android? I keep receiving a “permission denied” error using the same credentials I used yesterday on a PC terminal.