Tab Complete Cannot Create Temp File for Here-document Read-only File System

1. cannot create temp file for here-document: No space left on device

   Hello,

   I'm more than of a beginner when it comes to Ubuntu, so forgive me for any stupid questions.

   Anyways, a couple of weeks ago, I upgraded my personal home Ubuntu server from 14.04 --> 16.04 because I noticed the server was getting slow and unresponsive and didn't know what was causing information technology.

   During the initial set up I let the default Ubuntu xvi.04 prepare the partitions and fix the sizes/allocations of deejay space, and once the initial set up was and re-added all my drives, set up Samba, and moved some large files across some of my hard drives.

   But now when type a command and hit "Tab' to car-complete the control, I become the following error

   -bash: cannot create temp file for hither-document: No space left on device

   I checked to meet what disk or partition could exist full:

   Code:

   ricky@flynt:~$ df Filesystem                  1K-blocks       Used  Available Use% Mounted on udev                          3892124          0    3892124   0% /dev tmpfs                          782460       9264     773196   2% /run /dev/mapper/flynt--vg-root   49156404   46671652          0 100% / tmpfs                         3912288          iv    3912284   1% /dev/shm tmpfs                            5120          four       5116   i% /run/lock tmpfs                         3912288          0    3912288   0% /sys/fs/cgroup /dev/sdb                   1922729864  134337500 1690700252   8% /media/2TB /dev/sda1                      482922     157200     300788  35% /boot /dev/sdc1                  2113655724 1809132080  197133132  91% /media/3TB tmpfs                          782460          0     782460   0% /run/user/1000

   So I can meet that the /dev/mapper/flynt--vg-root partition is full and when I check Webmin, I take the following fault message:

   

   Since I'm a newbie, I don't know what I should do to try to clear that /dev/mapper.. partition or free upwardly that 46.88GB file organization.

   ---

2. Re: cannot create temp file for here-document: No space left on device

   Well, what's on there that'south taking up so much infinite?
   If you take a Desktop Environment, look for the 'Disk Usage Analyzer' application

   ---

3. Re: cannot create temp file for here-certificate: No infinite left on device

   I wrote this about 8 years ago nearly how to clarify and recover lost disk infinite. I think information technology still applies:
   https://ubuntuforums.org/showthread.php?t=1122670

   ---

4. Re: cannot create temp file for here-certificate: No space left on device

   Originally Posted by ian-weisser

   Well, what's on at that place that'south taking up so much space?
   If you lot have a Desktop Environs, look for the 'Disk Usage Analyzer' awarding

   Unfortunately my Ubuntu server is "headless" and then all I have is the CLI, so all I know right now is using "du" and "df" to clarify my deejay usage right now.

   Originally Posted past drs305

   I was able to follow some steps in clearing some infinite. And now I'm able to use "Tab" to machine-consummate some commands now, which is what I wanted.

   All the same this whole escape has me worried with the fact that my root directory "/" is still nearly 100% and I looked through everything in your guide and I'chiliad still non able to figure out how to gratis up that 46GB of space.

   ---

5. Re: cannot create temp file for hither-document: No space left on device

   Originally Posted past abc617

   all I have is the CLI, so all I know right now is using "du" and "df" to clarify my deejay usage correct now.

   du is all you need. This command volition list the largest files and directories at the lesser:
   

   Code:

   $ du -a / | sort -n

   Bear witness usa the biggest 10 or 15.

   ---

6. Re: cannot create temp file for hither-document: No space left on device

   Originally Posted by ian-weisser

   du is all you need. This command will list the largest files and directories at the bottom:

   Code:

   $ du -a / | sort -n

   Testify us the biggest 10 or 15.

   Thanks for your help. I was able to observe what was eating upwards all my space doing some more than earthworks. I establish that in the "/var/log" directory, my "syslog" file were eating up all my available space ( 30G for the syslog file ).

   I establish the post-obit the instructions which helped out: https://askubuntu.com/questions/7465...nitely-in-size and https://askubuntu.com/questions/7465...nitely-in-size

   I checked out the syslog file and I didn't find strange entries, but I didn't look as well in depth because information technology was thousands of lines long. Anyways i just followed the instructions in the links above and I stock-still it by just writing cypher to the syslog files

   Code:

   sudo su > /var/log/syslog

   Later on rebooting, I my syslog file shrank from 30G to 707M. That's withal a big log file, merely it cleaned upwardly a lot of the space in my root directory.

   ---

7. Re: cannot create temp file for here-document: No space left on device

   That is still a large file if you merely deleted it. Keep an center on it - at some point you are probably going to take to open it upwardly and find out where the problem is. If you lot find a recurring fault/entry y'all can post it on these forums and nosotros can help you troubleshoot it.

   ---

8. Re: cannot create temp file for here-document: No space left on device

   Normally a cron job automatically rotates logs, compresses older ones, and beyond a certain point deletes them. Either check your syslog to see what is growing information technology, or maybe why /etc/cron.daily/logrotate is not running daily like it should.

   I simply noticed that my logs are existence loaded upwardly with compiz for some reason regularly reporting my refresh rate, udisksd non ignoring (repeatedly reporting) an unmounted bulldoze intentionally in standby when doing its smart check, and something that appears to be from Steam or a Steam game that should not even exist in syslog (Steam normally logs to files in /tmp).

   Lawmaking:

   ~$ ls -fifty /var/log/syslog* -rw-r----- 1 syslog adm  30368 Oct 29 xi:02 /var/log/syslog -rw-r----- 1 syslog adm 176746 Oct 29 07:35 /var/log/syslog.1 -rw-r----- one syslog adm   9332 Oct 28 07:35 /var/log/syslog.2.gz -rw-r----- 1 syslog adm  11140 Oct 27 07:35 /var/log/syslog.3.gz -rw-r----- ane syslog adm  42358 Oct 26 07:35 /var/log/syslog.4.gz -rw-r----- 1 syslog adm  15241 Oct 25 07:35 /var/log/syslog.5.gz -rw-r----- 1 syslog adm   9114 Oct 24 07:35 /var/log/syslog.six.gz -rw-r----- 1 syslog adm   7777 Oct 23 07:35 /var/log/syslog.7.gz

   Last edited by efflandt; October 29th, 2017 at 05:25 PM.

   i5 650 iii.ii GHz upgraded to i7 870, 16 GB 1333 RAM, nvidia GTX 1060, 32" 1080p & assorted older computers

   ---

manleyelons1972.blogspot.com

Source: https://ubuntuforums.org/showthread.php?t=2375924

Share this post