Re: 0 byte left on device
I have never noticed huge logs in that folder myself. I did find this page about what that folder is, and how to turn off the logs for certain programs:
http://ifdeflinux.blogspot.com/2012/...g-upstart.html
That being said, I would expect log rotate to move the files and eliminate them before they get so large.
I'd be curious to see the output of:
Code:
cd /var/log/upstart/
du -ch *
Do you have any reason to believe log rotate's default settings would have been modified on your system? How frequently is this lightdm error recorded in the log file? Is the error you pasted above the only significant one, and it is being repeated tons of times, or are there other obvious errors in the log file mentioned?
Re: 0 byte left on device
Here are the output.
Code:
xbmc@Xbmc-Server:~$ cd /var/log/upstart/
xbmc@Xbmc-Server:/var/log/upstart$ du -ch *
4,0K alsa-restore.log.1.gz
4,0K alsa-restore.log.2.gz
4,0K console-setup.log.1.gz
4,0K console-setup.log.2.gz
4,0K console-setup.log.3.gz
4,0K console-setup.log.4.gz
4,0K console-setup.log.5.gz
4,0K console-setup.log.6.gz
4,0K console-setup.log.7.gz
4,0K container-detect.log.1.gz
4,0K container-detect.log.2.gz
4,0K container-detect.log.3.gz
4,0K container-detect.log.4.gz
4,0K container-detect.log.5.gz
4,0K container-detect.log.6.gz
4,0K container-detect.log.7.gz
4,0K cryptdisks-enable.log.1.gz
4,0K cryptdisks-enable.log.2.gz
4,0K cryptdisks-enable.log.3.gz
4,0K cryptdisks-enable.log.4.gz
4,0K cryptdisks-enable.log.5.gz
4,0K cryptdisks-enable.log.6.gz
4,0K cryptdisks-enable.log.7.gz
4,0K cups.log.1.gz
4,0K cups.log.2.gz
4,0K cups.log.3.gz
4,0K cups.log.4.gz
4,0K cups.log.5.gz
4,0K cups.log.6.gz
4,0K cups.log.7.gz
4,0K failsafe-x.log.1.gz
4,0K failsafe-x.log.2.gz
4,0K failsafe-x.log.3.gz
4,0K failsafe-x.log.4.gz
4,0K failsafe-x.log.5.gz
4,0K gssd.log.1.gz
4,0K gssd.log.2.gz
4,0K gssd.log.3.gz
4,0K gssd.log.4.gz
4,0K gssd.log.5.gz
4,0K gssd.log.6.gz
4,0K gssd.log.7.gz
4,0K hybrid-gfx.log.1.gz
4,0K hybrid-gfx.log.2.gz
4,0K hybrid-gfx.log.3.gz
4,0K hybrid-gfx.log.4.gz
4,0K hybrid-gfx.log.5.gz
4,0K hybrid-gfx.log.6.gz
4,0K hybrid-gfx.log.7.gz
104M lightdm.log.1.gz
96M lightdm.log.2.gz
60K lightdm.log.3.gz
52K lightdm.log.4.gz
52K lightdm.log.5.gz
48K lightdm.log.6.gz
12K lightdm.log.7.gz
4,0K modemmanager.log.1.gz
4,0K modemmanager.log.2.gz
4,0K modemmanager.log.3.gz
4,0K modemmanager.log.4.gz
4,0K modemmanager.log.5.gz
4,0K modemmanager.log.6.gz
4,0K modemmanager.log.7.gz
4,0K module-init-tools.log.1.gz
4,0K module-init-tools.log.2.gz
4,0K module-init-tools.log.3.gz
4,0K module-init-tools.log.4.gz
4,0K module-init-tools.log.5.gz
4,0K module-init-tools.log.6.gz
4,0K module-init-tools.log.7.gz
4,0K mysql.log.1.gz
4,0K mysql.log.2.gz
4,0K mysql.log.3.gz
4,0K mysql.log.4.gz
4,0K mysql.log.5.gz
4,0K mysql.log.6.gz
4,0K mysql.log.7.gz
4,0K networking.log.1.gz
4,0K networking.log.2.gz
4,0K networking.log.3.gz
4,0K networking.log.4.gz
4,0K networking.log.5.gz
4,0K networking.log.6.gz
4,0K networking.log.7.gz
4,0K network-interface-eth0.log.1.gz
4,0K network-interface-eth0.log.2.gz
4,0K network-interface-eth0.log.3.gz
4,0K network-interface-eth0.log.4.gz
4,0K network-interface-eth0.log.5.gz
4,0K network-interface-eth0.log.6.gz
4,0K network-interface-eth0.log.7.gz
4,0K network-interface-tap0.log.1.gz
4,0K procps-static-network-up.log.1.gz
4,0K procps-static-network-up.log.2.gz
4,0K procps-static-network-up.log.3.gz
4,0K procps-static-network-up.log.4.gz
4,0K procps-static-network-up.log.5.gz
4,0K procps-static-network-up.log.6.gz
4,0K procps-static-network-up.log.7.gz
4,0K procps-virtual-filesystems.log.1.gz
4,0K procps-virtual-filesystems.log.2.gz
4,0K procps-virtual-filesystems.log.3.gz
4,0K procps-virtual-filesystems.log.4.gz
4,0K procps-virtual-filesystems.log.5.gz
4,0K procps-virtual-filesystems.log.6.gz
4,0K procps-virtual-filesystems.log.7.gz
4,0K rsyslog.log.1.gz
4,0K rsyslog.log.2.gz
4,0K rsyslog.log.3.gz
4,0K rsyslog.log.4.gz
4,0K rsyslog.log.5.gz
4,0K rsyslog.log.6.gz
4,0K rsyslog.log.7.gz
4,0K statd.log.1.gz
4,0K statd.log.2.gz
4,0K statd.log.3.gz
4,0K statd.log.4.gz
4,0K statd.log.5.gz
4,0K statd.log.6.gz
4,0K statd.log.7.gz
4,0K udev-fallback-graphics.log.1.gz
4,0K ureadahead.log.1.gz
8,0K ureadahead.log.2.gz
4,0K ureadahead.log.3.gz
4,0K ureadahead.log.4.gz
4,0K ureadahead.log.5.gz
4,0K ureadahead.log.6.gz
8,0K ureadahead.log.7.gz
4,0K ureadahead-other.log.1.gz
4,0K ureadahead-other.log.2.gz
4,0K ureadahead-other.log.3.gz
4,0K ureadahead-other.log.4.gz
4,0K ureadahead-other.log.5.gz
4,0K ureadahead-other.log.6.gz
4,0K ureadahead-other.log.7.gz
4,0K vsftpd.log.1.gz
4,0K vsftpd.log.2.gz
200M totalt
xbmc@Xbmc-Server:/var/log/upstart$
The wierd thing is that now the 31,6 gb file is gone. I havent done anything.
Now there is only xxxxx.log.x.gz folders. before I had one of each xxxxxx.log.
How is that.
Re: 0 byte left on device
Run this command to show your file system info and drive space USE%, Available, etc... What do you see?
Re: 0 byte left on device
If you want to watch the filesize of the lightdm logs run this command. It will show you any changes happening in realtime / near-realtime to those files.
Code:
cd /var/log/upstart
sudo watch -d "du -ch * | grep -i lightdm"
Re: 0 byte left on device
Quote:
Originally Posted by
spec36
Run this command to show your file system info and drive space USE%, Available, etc... What do you see?
Output of df -h:
Code:
xbmc@Xbmc-Server:~$ df -h
Filsystem Storlek Använt Ledigt Anv% Monterat på
/dev/mapper/Xbmc--Server-root 40G 9,5G 28G 26% /
udev 7,9G 4,0K 7,9G 1% /dev
tmpfs 3,2G 1,2M 3,2G 1% /run
none 5,0M 0 5,0M 0% /run/lock
none 7,9G 80K 7,9G 1% /run/shm
/dev/sde1 228M 153M 64M 71% /boot
overflow 1,0M 56K 968K 6% /tmp
/dev/md0 11T 7,0T 3,3T 69% /media
xbmc@Xbmc-Server:~$
Re: 0 byte left on device
Based off the USE% (Anv%) of your partitions you do not appear to have maxed out any of the partitions. Are you still getting the error?
Re: 0 byte left on device
Quote:
Originally Posted by
spec36
Based off the USE% (Anv%) of your partitions you do not appear to have maxed out any of the partitions. Are you still getting the error?
No. The error is gone. Lets see if it comes back.
Re: 0 byte left on device
As it concerns an SSD, I would issue a manual trim command, to make sure you regain as much space as possible:
https://sites.google.com/site/easyli...-TRIM-manually
Re: 0 byte left on device
Quote:
Originally Posted by
spec36
Run this command to show your file system info and drive space USE%, Available, etc... What do you see?
There is another type of file system storage that can prevent new files from being stored - an inode. Use
to see the available inodes on each file system. I haven't had that issue for a few years, but back in the EXT2 days, running out of inodes was much more common especially on systems with many, many, many tiny files.