[Cura not working - No space left on device]

Quick update: after upgrading to 5.6 I have not had any space or network connectivity issues.

[Cura not working - No space left on device]

Yes this is on an S5. I haven’t had it for a while, so I don’t know how often it’s had this problem. I upgraded it to the latest firmware (5.5?) before the most recent 5.6.

 

It has had space issues since 5.5, but I can’t confirm it had it prior to that.

 

I will say that the network disconnection issues seem to be very related to the space issues.

 

Cura Connect reset works, but if this happens again I’ll try a factory reset.

 

Also I recently upgraded to 5.6 so I will see how that works.

 

Thanks all!

[Cura not working - No space left on device]

I suspect that avahi-daemon is logging too much.  The installed version is 0.6.31, and the very next version — 0.6.32 — fixes these warnings from appearing in logs: https://github.com/lathiat/avahi/blob/master/docs/NEWS#L155

 

The installed version is over four years old :(

 

I can't install it via apt-get, so I disabled avahi-daemon by modifying /etc/default/avahi-daemon and stopping it with update-rc.d avahi-daemon stop

[Cura not working - No space left on device]

For others who want to debug here are some commands you might find useful:

df -h                      # shows disk usage in human-readable terms
journalctl --disk-usage    # shows how much disk space logs are taking
ls -l /var/log/journal/**/ # list all journald logs
rm /var/log/journal/**/*@* # delete all archived logs (logs containing an @ symbol)

Removing those logs saved me a bunch of space.  I also edited /etc/systemd/journald.conf and halved SystemMaxUse to 32M, but that didn't seem to really work.

[Cura not working - No space left on device]

I have the same problem.  I suspect it's avahi-daemon logging too much (see below):

 

- I was printing fine

- after some number of prints Cura Connect would break

- reading logs on the touchscreen showed that no space was left on /

- couldn't enable dev mode to ssh in

- would reset cura connect — losing all my stats — printer would work again for a couple of days, then run out of space again

- this time though I am able to SSH in and can verify that /var/log/journal/** is taking up 89MB of 806 available on /

 

root@ultimakersystem-ccbdd30087d3:/var/log/journal/c9c140d1e794462fbc6facaa6f36863f# ls -l
total 90252
-rw-r-----  1 root systemd-journal   53248 Jan  1  1970 system.journal
-rw-r-----  1 root systemd-journal 8388608 Jan  1  1970 system@00000008ccb660c6-1b488519ed25a7ee.journal~
-rw-r-----  1 root systemd-journal 8388608 May 21 17:32 system@8a780352b4d74a25abba2411be124d36-000000000001d96a-0005a62956cc9fe7.journal
-rw-r-----  1 root systemd-journal 8388608 May 21 21:06 system@8a780352b4d74a25abba2411be124d36-0000000000020038-0005a62be43bd14a.journal
-rw-r-----  1 root systemd-journal 8388608 May 22 00:00 system@8a780352b4d74a25abba2411be124d36-000000000002253e-0005a62ee1b94778.journal
-rw-r-----  1 root systemd-journal 8388608 May 22 00:32 system@8a780352b4d74a25abba2411be124d36-0000000000025072-0005a631525ec98c.journal
-rw-r-----  1 root systemd-journal 8388608 May 22 01:04 system@8a780352b4d74a25abba2411be124d36-0000000000027c8b-0005a631c3fec32d.journal
-rw-r-----  1 root systemd-journal 8388608 May 20 23:35 system@ebae5b2b5a4646dabb9d3c59a8d6fe95-0000000000018b9f-0005a61aead30f5f.journal
-rw-r-----  1 root systemd-journal 8388608 May 21 03:07 system@ebae5b2b5a4646dabb9d3c59a8d6fe95-000000000001b68c-0005a61cd98f111f.journal
-rw-r-----+ 1 root systemd-journal 8388608 May 22 01:08 user-1000.journal
-rw-r-----+ 1 root systemd-journal 8388608 May 22 01:04 user-1000@6376e02ffff348eea29dbb59865292ca-0000000000000000-0000000000000000.journal
-rw-r-----+ 1 root systemd-journal 8388608 May 21 03:07 user-1000@6376e02ffff348eea29dbb59865292ca-000000000001d767-0005a61fba8f8837.journal

 

Tailing logs with journalctl -r, I see that avahi-daemon is spamming useless logs to disk:

Jun 01 21:54:15 ultimakersystem-ccbdd30087d3 avahi-daemon[1214]: Invalid response packet from host 192.168.1.137.
Jun 01 21:54:15 ultimakersystem-ccbdd30087d3 avahi-daemon[1214]: Invalid response packet from host 192.168.1.32.
Jun 01 21:54:15 ultimakersystem-ccbdd30087d3 avahi-daemon[1214]: Invalid response packet from host fe80::4da:c6cf:bdab:6026.
Jun 01 21:54:15 ultimakersystem-ccbdd30087d3 avahi-daemon[1214]: Invalid response packet from host fe80::21:efd5:4317:132e.
Jun 01 21:54:15 ultimakersystem-ccbdd30087d3 avahi-daemon[1214]: Invalid response packet from host fe80::4aa6:b8ff:fe83:bbfc.
Jun 01 21:54:15 ultimakersystem-ccbdd30087d3 avahi-daemon[1214]: Invalid response packet from host 192.168.1.173.

Also other systems are logging too much to STDOUT.