• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    Mango not starting ! Disk is full.

    Scheduled Pinned Locked Moved Mango Automation general Discussion
    20 Posts 4 Posters 8.4k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Offline
      stensma
      last edited by

      Hi all !
      Mango still has some issues.
      There was not room for the temp files needed in the commands.
      What is wrong ? Where do I find space?

      mango@stensmango:/$ sudo du -ahx / | sort -rh | head -20
      [sudo] password for mango:
      Sorry, try again.
      [sudo] password for mango:
      sort: cannot create temporary file in ‘/tmp’: No space left on device
      ot local0_1479906901198_Backup.tiff

      0_1479906979486_Interna metrics.tiff

      Filesystem from Webmin:
      0_1479907094278_FS.tiff

      1 Reply Last reply Reply Quote 0
      • phildunlapP Offline
        phildunlap
        last edited by phildunlap

        Weird... why does / report as only being 47% full if the disk is full? I would restart the device if I saw that.

        You could see if there's an abundance of logging from something else

        sudo du -sh /var/log/*
        
        S 1 Reply Last reply Reply Quote 0
        • JoelHaggarJ Offline
          JoelHaggar
          last edited by

          I would check your /opt/mango/backup folder. You may have a lot of NoSQL database backups which you can delete to free up space. You can turn off incremental backups on the system settings page under the NoSQL settings.

          1 Reply Last reply Reply Quote 0
          • S Offline
            stensma
            last edited by

            Hi this pictures was taken right after a cold boot.
            And ALL backup are moved to an external disk.

            1 Reply Last reply Reply Quote 0
            • S Offline
              stensma @phildunlap
              last edited by

              @phildunlap
              0_1479935503665_Var_log.tiff

              1 Reply Last reply Reply Quote 0
              • S Offline
                stensma
                last edited by

                Result with Find size

                mango@stensmango:/opt/mango/logs$ sudo find / -size +100M
                find: /proc/26770/task/26770/fd/5': No such file or directory find: /proc/26770/task/26770/fdinfo/5': No such file or directory
                find: /proc/26770/fd/5': No such file or directory find: /proc/26770/fdinfo/5': No such file or directory

                1 Reply Last reply Reply Quote 0
                • S Offline
                  stensma
                  last edited by

                  SSH picture
                  0_1479937347472_SSH.tiff

                  1 Reply Last reply Reply Quote 0
                  • phildunlapP Offline
                    phildunlap
                    last edited by

                    Can you check the output of df -i as it may be there are no more inodes. If that is the case that they're 100% utilized, you'll have to find some files (and directories) to delete. They can be any files of any size, but you should of course exercise care.

                    A useful command may be:

                    #count the number of files and directories in /path/to/dir
                    find /path/to/dir | wc -l
                    
                    1 Reply Last reply Reply Quote 0
                    • S Offline
                      stensma
                      last edited by stensma

                      0_1479971824621_FS1.tiff

                      After :
                      0_1479972783363_fs2.tiff

                      Then I am able to run basic Webmin functions, but what is creating the problem?
                      I have tried no to run apt-get purge and autoremove but there is nothing to clean out.

                      Now I work with following command.
                      $ for i in /*; do echo $i; find $i |wc -l; done
                      This lists the folders and inode number.
                      and I fount that /var had over 300k nodes
                      I will dig deeper on where exactly
                      0_1479973339313_fs3.tiff

                      What is creating the files in /var/spool/exim4/input ??
                      0_1479973648956_fs4.tiff

                      1 Reply Last reply Reply Quote 0
                      • S Offline
                        stensma
                        last edited by

                        I have now removed the files in the /var/spool/exim4/input.
                        Now the resources is back on track, but still what is creating the files?
                        0_1479974922559_fs5.tiff
                        0_1479974958382_fs6.tiff

                        1 Reply Last reply Reply Quote 0
                        • S Offline
                          stensma
                          last edited by stensma

                          New files are created all the time.
                          There two different contents one is:0_1479975653561_spool.tiff

                          The other has following content:
                          0_1479975737787_spool2.tiff

                          I have now created an empty log.txt file in the missing mango-backups folder,
                          lets see if this does the trick...

                          1 Reply Last reply Reply Quote 0
                          • S Offline
                            stensma
                            last edited by stensma

                            I found the bad guy !
                            A Cron Job create all the files in /var/spool/exim4/input.
                            When I disable this task, the folder is quiet .
                            But why is this job there ? and what is it suppose to do?
                            0_1479977770085_Cron_job.tiff

                            1 Reply Last reply Reply Quote 0
                            • phildunlapP Offline
                              phildunlap
                              last edited by phildunlap

                              It was supposed to be constructing a file in /opt/systeminfo/ (I believe, might be /opt/info/ or something like that) which would then be read by a preconfigured ASCII File Data Source for system information like remaining disk space. You can certainly deactivate it without much loss, and you may as well disable the ASCII data source that was preloaded. I will definitely investigate if other MangoES's are having a problem with it creating files in /var/spool/

                              1 Reply Last reply Reply Quote 0
                              • M Offline
                                mihairosu
                                last edited by

                                I used this command straight from the terminal to list inodes and found it easier:

                                find / -xdev -printf '%h\n' | sort | uniq -c | sort -k 1 -n

                                1 Reply Last reply Reply Quote 0
                                • M Offline
                                  mihairosu
                                  last edited by mihairosu

                                  This issue has happened again, and the same folder caused the problem.

                                  ASCII File Reader has been off for a long time, so that did not prevent the issue from re-occurring.

                                  edit: This is happening on Mango v3, but not on Mango v1 or on an Ubuntu install.

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post