The volume /opt/vyatta/etc/config is at 100% full

,
1

Hi Everyone,
I am running into an issue with the volume /opt/vyatta/etc/config. This got filled up quickly and I am not able to find out what. Here’s what I see:

    Filesystem            Size  Used Avail Use% Mounted on
    overlayfs             3.9G  3.7G   16M 100% /
    tmpfs                 2.0G     0  2.0G   0% /lib/init/rw
    udev                  2.0G  144K  2.0G   1% /dev
    tmpfs                 2.0G  4.0K  2.0G   1% /dev/shm
    /dev/xvda1            3.9G  3.7G   16M 100% /live/image
    /dev/xvda1            3.9G  3.7G   16M 100% /live/cow
    tmpfs                 2.0G     0  2.0G   0% /live
    tmpfs                 2.0G   84K  2.0G   1% /tmp
    /dev/xvda1            3.9G  3.7G   16M 100% /opt/vyatta/etc/config  <----- this is 100% full. It has 4GB.

Run this command - sudo du -a /opt/vyatta/ | sort -rn | head -40

nmoua@VyOS-AMI:/var$ sudo du -a /opt/vyatta/ | sort -rn | head -40
16779 /opt/vyatta/
9984 /opt/vyatta/config
8320 /opt/vyatta/config/tmp
4715 /opt/vyatta/share
2655 /opt/vyatta/share/vyatta-cfg
2637 /opt/vyatta/share/vyatta-cfg/templates
1664 /opt/vyatta/config/tmp/new_config_30910
1664 /opt/vyatta/config/tmp/new_config_20785
1664 /opt/vyatta/config/tmp/new_config_17965
1664 /opt/vyatta/config/tmp/new_config_13569
1664 /opt/vyatta/config/tmp/new_config_13029
1664 /opt/vyatta/config/active
1526 /opt/vyatta/share/vyatta-cfg/templates/interfaces
1404 /opt/vyatta/config/tmp/new_config_30910/vpn/ipsec
1404 /opt/vyatta/config/tmp/new_config_30910/vpn
1404 /opt/vyatta/config/tmp/new_config_20785/vpn/ipsec
1404 /opt/vyatta/config/tmp/new_config_20785/vpn
1404 /opt/vyatta/config/tmp/new_config_17965/vpn/ipsec
1404 /opt/vyatta/config/tmp/new_config_17965/vpn
1404 /opt/vyatta/config/tmp/new_config_13569/vpn/ipsec
1404 /opt/vyatta/config/tmp/new_config_13569/vpn
1404 /opt/vyatta/config/tmp/new_config_13029/vpn/ipsec
1404 /opt/vyatta/config/tmp/new_config_13029/vpn
1404 /opt/vyatta/config/active/vpn/ipsec
1404 /opt/vyatta/config/active/vpn
1394 /opt/vyatta/share/vyatta-op
1359 /opt/vyatta/share/vyatta-op/templates
1319 /opt/vyatta/sbin
788 /opt/vyatta/share/vyatta-op/templates/show
724 /opt/vyatta/config/tmp/new_config_30910/vpn/ipsec/site-to-site/peer
724 /opt/vyatta/config/tmp/new_config_30910/vpn/ipsec/site-to-site
724 /opt/vyatta/config/tmp/new_config_20785/vpn/ipsec/site-to-site/peer
724 /opt/vyatta/config/tmp/new_config_20785/vpn/ipsec/site-to-site
724 /opt/vyatta/config/tmp/new_config_17965/vpn/ipsec/site-to-site/peer
724 /opt/vyatta/config/tmp/new_config_17965/vpn/ipsec/site-to-site
724 /opt/vyatta/config/tmp/new_config_13569/vpn/ipsec/site-to-site/peer
724 /opt/vyatta/config/tmp/new_config_13569/vpn/ipsec/site-to-site
724 /opt/vyatta/config/tmp/new_config_13029/vpn/ipsec/site-to-site/peer
724 /opt/vyatta/config/tmp/new_config_13029/vpn/ipsec/site-to-site
724 /opt/vyatta/config/active/vpn/ipsec/site-to-site/peer

I didn’t see anything there could haven’t taken the spaces.

Any idea? I’m pretty new to this and any help would appreciated.

Thanks,
-N

2

Hello @nmoua, can you provide an output of the following command:
sudo find /opt/vyatta/ -size +10M

3

HI Dmitry,
I ran the provided command but no result, see below.

nmoua@VyOS-AMI:/$ sudo find /opt/vyatta/ -size +10M

nmoua@VyOS-AMI:/$

Did I type the command wrong?

-N

4

It seems they’re not files largest more 10 Mb. Which VyOS version running?

show version
5

Below is the version I’m running.

Version: VyOS 1.1.7
Description: VyOS 1.1.7 (helium)
Copyright: 2016 VyOS maintainers and contributors
Built by: maintainers@vyos.net
Built on: Wed Feb 17 09:57:31 UTC 2016
Build ID: 1602170957-4459750
System type: x86 64-bit
Boot via: image
Hypervisor: Xen hvm
HW model: HVM domU
HW S/N: ec2c881b-1c87-d75c-4183-ea3a824a9f13
HW UUID: 1B882CEC-871C-5CD7-4183-EA3A824A9F13
Uptime: 18:11:50 up 9:42, 1 user, load average: 0.23, 0.14, 0.08

6

You should REALLY update, since that version is 4 years old

7

PirateGhost,

Thank you. I noticed it and planning to update next year. In meantime I am trying to figure what’s been using disk spaces, so I can find a way to clean up.

-N