Request for explanation of error message

Bret Busby bret.busby at gmail.com
Sun Jul 28 17:01:03 UTC 2019


On 28/07/2019, Mike Marchywka <marchywka at hotmail.com> wrote:
> On Sun, Jul 28, 2019 at 06:06:23AM +0800, Bret Busby wrote:
>> On 28/07/2019, Mike Marchywka <marchywka at hotmail.com> wrote:
>> > On Sun, Jul 28, 2019 at 04:06:45AM +0800, Bret Busby wrote:
>> >> On 28/07/2019, Mike Marchywka <marchywka at hotmail.com> wrote:
>> >> > On Sat, Jul 27, 2019 at 09:26:41PM +0200, Oliver Grawert wrote:
>> >> >>
>> >> >> dpkg -l | grep logrotate
>> >
>> > I thought you had dirs there, I always use du -sbc on directories to
>> > hunt
>> > down :)
>> >
>> > Installation is not the same as functioning, you should be able to see
>> > the
>> > old
>> > versions gzipped if it is working and configured right. Again though
>> > burning through that much disk space that fast and having a file that
>> > big
>> > for "normal" usage is odd although I don't know your history.
>> >
>> >
>> >> > These are the directory sizes, while logrotate can compress old ones
>> >> > there
>> >> > is not
>> >> > a good reason for Gb of log messages.
>> >>
>> >> In /var/log/lightdm , is
>> >> x-0.log
>> >> size: 48.2GB
>> >>
>
> I guess these logs are rw user only, my system seems to work like this,
>
>
>  ls -al /var/log/lightdm
> total 152
> drwxr-xr-x  2 root root   4096 Jul 21 07:35 .
> drwxrwxr-x 13 root syslog 4096 Jul 27 07:35 ..
> -rw-------  1 root root      0 Jul 21 07:35 lightdm.log
> -rw-------  1 root root   1363 Jul 20 20:41 lightdm.log.1.gz
> -rw-------  1 root root   1369 Jul  8 17:34 lightdm.log.2.gz
> -rw-------  1 root root   5428 Jul  5 18:48 lightdm.log.3.gz
> -rw-------  1 root root   6688 Jul  5 05:53 lightdm.log.4.gz
> -rw-------  1 root root   6764 Jul  4 06:46 lightdm.log.5.gz
> -rw-------  1 root root   5954 Jul  3 06:03 lightdm.log.6.gz
> -rw-------  1 root root   4075 Jul  2 06:39 lightdm.log.7.gz
>
>
> The older gz files are rotated by logrotate but I thought
> they were all world readable.
>
> In any case the huge log files probably have repetitive error
> messages that will give you some idea where it is stuck.
> If /tmp is rw for you you would have to find some other reason
> it can't make a lock file. In any case if you can find the repeating
> error loop in the log files post that. The tails you posted I'm
> not sure if they got a full cycle.
>
>
>
>> >>
>> >>
>> >>
>> >>
>> >> The pci problem suggests
>> >> > an infinite mesage loop -I used to get that all the time from
>> >> > misconfigured nullmaileri this may be a hardware issue. Just tail the
>> >> > most
>> >> > recent file in the directories
>> >> > and see if it is a repeated message.
>> >>
>> >> "
>> >> bret at bret-MD34045-2521:~$ tail /var/log/lightdm/x-0.log
>> >> tail: cannot open '/var/log/lightdm/x-0.log' for reading: Permission
>> >> denied
>> >> bret at bret-MD34045-2521:~$ sudo tail /var/log/lightdm/x-0.log
>> >> [sudo] password for bret:
>> >> xorg-server 2:1.19.6-1ubuntu4.3 (For technical support please see
>> >> http://www.ubuntu.com/support)
>> >> Current version of pixman: 0.34.0
>> >> 	Before reporting problems, check http://wiki.x.org
>> >> 	to make sure that you have the latest version.
>> >> Markers: (--) probed, (**) from config file, (==) default setting,
>> >> 	(++) from command line, (!!) notice, (II) informational,
>> >> 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> >> (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 28 02:49:58 2019
>> >> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> >> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>> >> bret at bret-MD34045-2521:~$ sudo tail -30 /var/log/lightdm/x-0.log
>> >> 	 at http://wiki.x.org
>> >>  for help.
>> >> (EE)
>> >> (EE)
>> >> Fatal server error:
>> >> (EE) Could not write pid to lock file in /tmp/.tX0-lock
>> >
>> > I'm not really sure what to make of this as bad locks can lead to
>> > bizarre
>> > problems
>> > .   I guess you could check the obvious,
>> > the logs should be readable by all too,
>> >
>> > ls -al /var/log | grep X
>> > -rw-r--r--  1 root              root    37198 Jul 20 20:41 Xorg.0.log
>> > -rw-r--r--  1 root              root    42732 Jul  8 17:35
>> > Xorg.0.log.old
>> > -rw-r--r--  1 root              root    32892 Jul  5 17:52 Xorg.1.log
>> > -rw-r--r--  1 root              root    32892 Jul  5 17:14
>> > Xorg.1.log.old
>> > marchywka at happy:/home/documents/latex/proj/happyheart$ ls -al /tmp |
>> > head -n
>> > 2
>> > total 1164
>> > drwxrwxrwt 19 root      root      1081344 Jul 27 17:01 .
>> >
>> >
>> > And I'm not sure the Xorg thing is rotated by default,
>> >
>> > more /etc/logrotate.d/
>> > apport               iptraf-ng            speech-dispatcher
>> > apt                  lightdm              ufw
>> > cups-daemon          pm-utils             unattended-upgrades
>> > dpkg                 ppp                  upstart
>> > hibernate            rsyslog
>> >
>> >
>> >
>>
>>
>> "
>> bret at bret-MD34045-2521:~$ more /etc/logrotate.d/
>>
>> *** /etc/logrotate.d/: directory ***
>>
>> bret at bret-MD34045-2521:~$ ls -al /var/log | grep X
>> -rw-r--r--   1 root              root               46756 Jul 28 02:50
>> Xorg.0.log
>>
>> bret at bret-MD34045-2521:~$ ls -al /tmp | head -n 2
>> total 80
>> drwxrwxrwt 18 root root 4096 Jul 28 04:46 .
>> "
>>


And, as I got a no free space warning, although I can't find where
there is no free space, apart from the snap (?) area,

"
bret at bret-MD34045-2521:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
udev             16G     0   16G   0% /dev
tmpfs           3.2G  1.6M  3.2G   1% /run
/dev/sda7        92G   58G   30G  67% /
tmpfs            16G  469M   16G   3% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs            16G     0   16G   0% /sys/fs/cgroup
/dev/loop0      128K  128K     0 100% /snap/software-boutique/39
/dev/loop1      8.0M  8.0M     0 100% /snap/pulsemixer/23
/dev/loop7       88M   88M     0 100% /snap/core/5328
/dev/loop2      161M  161M     0 100% /snap/midori/451
/dev/loop3       72M   72M     0 100% /snap/software-boutique/31
/dev/loop4       87M   87M     0 100% /snap/ubuntu-mate-welcome/335
/dev/loop5       89M   89M     0 100% /snap/core/7270
/dev/loop8      8.0M  8.0M     0 100% /snap/pulsemixer/250
/dev/loop6       88M   88M     0 100% /snap/ubuntu-mate-welcome/199
/dev/sda1        96M   31M   66M  32% /boot/efi
/dev/sda8        92G   63G   25G  73% /home
tmpfs           3.2G   64K  3.2G   1% /run/user/1000
/dev/sda9        92G   61M   87G   1% /media/bret/Data1
/dev/sda10       92G   61M   87G   1% /media/bret/Data2
"


so I looked in the /var area, I noticed that the 48GB log file has
much smaller zipped predecessors;

"
bret at bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
-rw------- 1 root root 48233766147 Jul 28 02:49 /var/log/lightdm/x-0.log
-rw------- 1 root root     9770700 Jul 23 03:45 /var/log/lightdm/x-0.log.3.gz
-rw------- 1 root root    26392833 Jul 22 23:42 /var/log/lightdm/x-0.log.4.gz
-rw------- 1 root root         768 Jul 16 20:13 /var/log/lightdm/x-0.log.5.gz
-rw------- 1 root root         784 Jul 15 16:42 /var/log/lightdm/x-0.log.6.gz
-rw------- 1 root root         144 Jul 14 21:33 /var/log/lightdm/x-0.log.7.gz
-rw------- 1 root root         100 Jul 13 01:14 /var/log/lightdm/x-0.log.8.gz
"

Weirdness abounds.

I note that, in the /var/log/lightdm directory, the other log files
have log1.gz and log2.gz , but, that one does not;

"
bret at bret-MD34045-2521:~$ ls -l /var/log/lightdm/
total 47138780
-rw------- 1 root root           0 Jul 28 02:53 lightdm.log
-rw------- 1 root root        2822 Jul 28 02:50 lightdm.log.1.gz
-rw------- 1 root root        2130 Jul 23 03:46 lightdm.log.2.gz
-rw------- 1 root root         121 Jul 22 23:42 lightdm.log.3.gz
-rw------- 1 root root        2252 Jul 16 20:13 lightdm.log.4.gz
-rw------- 1 root root        1747 Jul 15 16:43 lightdm.log.5.gz
-rw------- 1 root root        1691 Jul  7 01:09 lightdm.log.6.gz
-rw------- 1 root root        1673 Jul  6 23:23 lightdm.log.7.gz
-rw------- 1 root root           0 Jul 28 02:53 seat0-greeter.log
-rw------- 1 root root        2294 Jul 28 02:50 seat0-greeter.log.1.gz
-rw------- 1 root root        1912 Jul 23 03:46 seat0-greeter.log.2.gz
-rw------- 1 root root        1934 Jul 16 20:13 seat0-greeter.log.3.gz
-rw------- 1 root root        1459 Jul 15 16:43 seat0-greeter.log.4.gz
-rw------- 1 root root        1501 Jul  7 01:09 seat0-greeter.log.5.gz
-rw------- 1 root root        1432 Jul  6 23:23 seat0-greeter.log.6.gz
-rw------- 1 root root        1429 Jul  6 23:33 seat0-greeter.log.7.gz
-rw------- 1 root root 48233766147 Jul 28 02:49 x-0.log
-rw------- 1 root root     9770700 Jul 23 03:45 x-0.log.3.gz
-rw------- 1 root root    26392833 Jul 22 23:42 x-0.log.4.gz
-rw------- 1 root root         768 Jul 16 20:13 x-0.log.5.gz
-rw------- 1 root root         784 Jul 15 16:42 x-0.log.6.gz
-rw------- 1 root root         144 Jul 14 21:33 x-0.log.7.gz
-rw------- 1 root root         100 Jul 13 01:14 x-0.log.8.gz
"

So, I am assuming that that file corrupted, on or about 23 July, or,
whatever automatically compacts and archives it, and, starts a new log
file, failed, at about that time.

-- 
Bret Busby
Armadale
West Australia
..............

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992

....................................................




More information about the ubuntu-users mailing list