Request for explanation of error message

classic Classic list List threaded Threaded
74 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Sun, Jul 28, 2019 at 06:06:23AM +0800, Bret Busby wrote:

> On 28/07/2019, Mike Marchywka <[hidden email]> wrote:
> > On Sun, Jul 28, 2019 at 04:06:45AM +0800, Bret Busby wrote:
> >> On 28/07/2019, Mike Marchywka <[hidden email]> 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@bret-MD34045-2521:~$ tail /var/log/lightdm/x-0.log
> >> tail: cannot open '/var/log/lightdm/x-0.log' for reading: Permission
> >> denied
> >> bret@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@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@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@bret-MD34045-2521:~$ more /etc/logrotate.d/
>
> *** /etc/logrotate.d/: directory ***
>
> bret@bret-MD34045-2521:~$ ls -al /var/log | grep X
> -rw-r--r--   1 root              root               46756 Jul 28 02:50
> Xorg.0.log
>
> bret@bret-MD34045-2521:~$ ls -al /tmp | head -n 2
> total 80
> drwxrwxrwt 18 root root 4096 Jul 28 04:46 .
> "
>
> --
> 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
>
> ....................................................
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 28/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Sun, Jul 28, 2019 at 06:06:23AM +0800, Bret Busby wrote:
>> On 28/07/2019, Mike Marchywka <[hidden email]> wrote:
>> > On Sun, Jul 28, 2019 at 04:06:45AM +0800, Bret Busby wrote:
>> >> On 28/07/2019, Mike Marchywka <[hidden email]> 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@bret-MD34045-2521:~$ tail /var/log/lightdm/x-0.log
>> >> tail: cannot open '/var/log/lightdm/x-0.log' for reading: Permission
>> >> denied
>> >> bret@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@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@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@bret-MD34045-2521:~$ more /etc/logrotate.d/
>>
>> *** /etc/logrotate.d/: directory ***
>>
>> bret@bret-MD34045-2521:~$ ls -al /var/log | grep X
>> -rw-r--r--   1 root              root               46756 Jul 28 02:50
>> Xorg.0.log
>>
>> bret@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@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@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@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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Mon, Jul 29, 2019 at 01:01:03AM +0800, Bret Busby wrote:

> 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@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;

This is probably log rotate. From the sizes, absent some activity you know about,
things probably went bad between 16th and 22nd and then escalated.

>
> "
> bret@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@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.

Again, that is probably logrotate but the easiest thing to do is look at the last few lines
in any of the larger files and find similar lines farther up to establish a period of
error messages ( while they could all be unrelated as if being attacked likely it is in an
infinite loop trying to get something restarted ). Once you have a full period it
may be obvious what the problem is. Alternative, if you unzip the x-0.log.4.gz file to the
console and just "more" it probably a few lines in you will see whatver started it
as the earlier gzip files are quite small.

If you boot in single user mode and have the console messages pop up, you may
be able to execute some of the failed steps by hand and see if it triggers any error messages.

>
> --
> 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
>
> ....................................................
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Mon, Jul 29, 2019 at 01:01:03AM +0800, Bret Busby wrote:
>> 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@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;
>
> This is probably log rotate. From the sizes, absent some activity you know
> about,
> things probably went bad between 16th and 22nd and then escalated.
>
>>
>> "
>> bret@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@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.
>
> Again, that is probably logrotate but the easiest thing to do is look at the
> last few lines
> in any of the larger files and find similar lines farther up to establish a
> period of
> error messages ( while they could all be unrelated as if being attacked
> likely it is in an
> infinite loop trying to get something restarted ). Once you have a full
> period it
> may be obvious what the problem is. Alternative, if you unzip the
> x-0.log.4.gz file to the
> console and just "more" it probably a few lines in you will see whatver
> started it
> as the earlier gzip files are quite small.
>
> If you boot in single user mode and have the console messages pop up, you
> may
> be able to execute some of the failed steps by hand and see if it triggers
> any error messages.
>

Whatever is happeing, I now have

"
bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
-rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
"

and no space left on the / partition.

So, whatever is happening, the file, as it stands, has to be deleted,
as it has rendered the system unusable.

--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Bret Busby <[hidden email]> wrote:

> On 29/07/2019, Mike Marchywka <[hidden email]> wrote:
>> On Mon, Jul 29, 2019 at 01:01:03AM +0800, Bret Busby wrote:
>>> 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@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;
>>
>> This is probably log rotate. From the sizes, absent some activity you
>> know
>> about,
>> things probably went bad between 16th and 22nd and then escalated.
>>
>>>
>>> "
>>> bret@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@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.
>>
>> Again, that is probably logrotate but the easiest thing to do is look at
>> the
>> last few lines
>> in any of the larger files and find similar lines farther up to establish
>> a
>> period of
>> error messages ( while they could all be unrelated as if being attacked
>> likely it is in an
>> infinite loop trying to get something restarted ). Once you have a full
>> period it
>> may be obvious what the problem is. Alternative, if you unzip the
>> x-0.log.4.gz file to the
>> console and just "more" it probably a few lines in you will see whatver
>> started it
>> as the earlier gzip files are quite small.
>>
>> If you boot in single user mode and have the console messages pop up, you
>> may
>> be able to execute some of the failed steps by hand and see if it
>> triggers
>> any error messages.
>>
>
> Whatever is happeing, I now have
>
> "
> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
> "
>
> and no space left on the / partition.
>
> So, whatever is happening, the file, as it stands, has to be deleted,
> as it has rendered the system unusable.
>


And, after having run
sudo rm /var/log/lightdm/x-0.log
whilst the file no longer shows as being present, the space has not
been freed; still no free space in the / partition.

In going through the folders displayed by caja, in the / partition, I
note that proc shows as having about 875,000 items, "totalling 140.7TB
(0 bytes on disk)" (magic?).

The size of the HDD is 1TB.

/root and /lost+found are both unreadable when I try to find their
Properties, and, I can't find the deleted file anywhere else, to free
up its space, to provide free space in the / partition.


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Paul Smith-2
In reply to this post by Bret Busby-2
On Mon, 2019-07-29 at 02:51 +0800, Bret Busby wrote:

> Whatever is happeing, I now have
>
> "
> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
> "
>
> and no space left on the / partition.
>
> So, whatever is happening, the file, as it stands, has to be deleted,
> as it has rendered the system unusable.

I haven't been following this thread, but I mean, have you looked at
the contents of that file to see what it says?

You can view the last 20 lines, for example, by opening a terminal
window and running:

  tail -n20 /var/log/lightdm/x-0.log

It could be that it's spewing errors or warnings to that file, which
could lead you to a poorly-behaving program on your system or warn you
about some hardware or configuration issue.

I don't use lightdm (I use standard gdm) so I can't say for sure but
it's possible simply deleting that file won't solve your disk space
problem: if lightdm keeps the file open to write to it then removing it
via "sudo rm -f /var/log/lightdm/x-0.log" won't actually free the disk
space: on POSIX systems disk space is only cleaned up when there are no
more references to the file.  If you try to delete it and you're still
out of space you'll have to at least log out and log back in to restart
the display manager, and/or possibly kill the process.

In general those log files are for your information, for helping to
track down issues.  The system itself doesn't need them for proper
operation so if you need to delete them you should feel free to do so.
It won't break anything.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Sun, Jul 28, 2019 at 03:22:06PM -0400, Paul Smith wrote:

> On Mon, 2019-07-29 at 02:51 +0800, Bret Busby wrote:
> > Whatever is happeing, I now have
> >
> > "
> > bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
> > -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
> > "
> >
> > and no space left on the / partition.
> >
> > So, whatever is happening, the file, as it stands, has to be deleted,
> > as it has rendered the system unusable.
>
> I haven't been following this thread, but I mean, have you looked at
> the contents of that file to see what it says?
>
> You can view the last 20 lines, for example, by opening a terminal
> window and running:
>
>   tail -n20 /var/log/lightdm/x-0.log
>
> It could be that it's spewing errors or warnings to that file, which
> could lead you to a poorly-behaving program on your system or warn you
> about some hardware or configuration issue.
>
> I don't use lightdm (I use standard gdm) so I can't say for sure but
> it's possible simply deleting that file won't solve your disk space
> problem: if lightdm keeps the file open to write to it then removing it
> via "sudo rm -f /var/log/lightdm/x-0.log" won't actually free the disk
> space: on POSIX systems disk space is only cleaned up when there are no
> more references to the file.  If you try to delete it and you're still
> out of space you'll have to at least log out and log back in to restart
> the display manager, and/or possibly kill the process.

 I keep suggesting to find an entire loop to post- he posted last
few lines before but it may help to get an entire period or go back
to first logfile that seemed too big and start there too.
Although deleting it and catching the new one starting to fill
may be easier. One of problems was inability to get a /tmp/x-lock or
something similar that may have simple explanation.


That is a good point though- I remember with the nullmailer problem
I had to do something like a service restart but yeah you should be able
to see it with "lsof | grep filename " although fixing the problem
may require more drastic action anyway or at least a restart to
change a configuration.



>
> In general those log files are for your information, for helping to
> track down issues.  The system itself doesn't need them for proper
> operation so if you need to delete them you should feel free to do so.
> It won't break anything.
>
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

ubuntu-users mailing list
In reply to this post by Paul Smith-2
FWIW those are the log file sizes of my several years old Ubuntu 16.04:

[root@archlinux rocketmouse]# ls -hAl /mnt/moonstudio/var/log/lightdm/
total 17M
-rw------- 1 root root  14M Jul 28 20:56 lightdm.log
-rw------- 1 root root 7.4K Jul  7  2016 lightdm.log.old
-rw------- 1 root root 241K Jul 22 13:55 seat0-greeter.log
-rw------- 1 root root  12K Jul 11  2016 x-0-greeter.log
-rw------- 1 root root  645 Jul  7  2016 x-0-greeter.log.old
-rw------- 1 root root 2.3M Jul 28 20:56 x-0.log
-rw------- 1 root root 1.1K Jul  7  2016 x-0.log.old
-rw------- 1 root root 1.2K Sep 10  2015 x-1-greeter.log
-rw------- 1 root root 1.2K Sep  9  2015 x-1-greeter.log.old
-rw------- 1 root root 1.3K Sep 10  2015 x-1.log
-rw------- 1 root root 1.3K Sep  9  2015 x-1.log.old

And this are the log file sizes of my several years old Arch Linux:

[root@archlinux rocketmouse]# ls -hAl /var/log/lightdm/
total 96K
-rw------- 1 root root 9.3K Jul 28 15:42 lightdm.log
-rw------- 1 root root 6.3K Jul 28 15:20 lightdm.log.old
-rw------- 1 root root  16K Jul 28 15:42 seat0-greeter.log
-rw------- 1 root root  16K Jul 28 15:20 seat0-greeter.log.old
-rw------- 1 root root  14K Jun 28  2016 x-0-greeter.log
-rw------- 1 root root  14K Jun 27  2016 x-0-greeter.log.old
-rw------- 1 root root 1.9K Jul 28 15:42 x-0.log
-rw------- 1 root root 1.9K Jul 28 15:42 x-0.log.old
-rw------- 1 root root 2.1K Feb 11 18:43 x-1.log

If nothing is broken, the log files are very small.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Paul Smith-2
In reply to this post by Bret Busby-2
On Mon, 2019-07-29 at 03:19 +0800, Bret Busby wrote:
> And, after having run
> sudo rm /var/log/lightdm/x-0.log
> whilst the file no longer shows as being present, the space has not
> been freed; still no free space in the / partition.

See my other email.  Try logging out and back in.  If that doesn't help
then you'll have to kill the lightdm process by hand.  Or you can try
rebooting: normally that's what I would suggest as the simplest
solution but if your root partition is full then when you reboot it may
(probably not, but may) have a problem.
 
> In going through the folders displayed by caja, in the / partition, I
> note that proc shows as having about 875,000 items, "totalling 140.7TB
> (0 bytes on disk)" (magic?).

/proc is not a real directory: it's exported directly from the kernel.
It doesn't actually take up any space on any disk partition and its
size is not real.  You should ignore it for the purposes of finding
space usage.

Same with /sys.

If you want to be able to see all files using space you will, of
course, have to be root else you won't be able to view any files and
directories that only root can view (such as the root user's home
directory, /root).


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Paul Smith-2
On 29/07/2019, Paul Smith <[hidden email]> wrote:

> On Mon, 2019-07-29 at 02:51 +0800, Bret Busby wrote:
>> Whatever is happeing, I now have
>>
>> "
>> bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
>> -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
>> "
>>
>> and no space left on the / partition.
>>
>> So, whatever is happening, the file, as it stands, has to be deleted,
>> as it has rendered the system unusable.
>
> I haven't been following this thread, but I mean, have you looked at
> the contents of that file to see what it says?
>
> You can view the last 20 lines, for example, by opening a terminal
> window and running:
>
>   tail -n20 /var/log/lightdm/x-0.log
>
> It could be that it's spewing errors or warnings to that file, which
> could lead you to a poorly-behaving program on your system or warn you
> about some hardware or configuration issue.
>
> I don't use lightdm (I use standard gdm) so I can't say for sure but
> it's possible simply deleting that file won't solve your disk space
> problem: if lightdm keeps the file open to write to it then removing it
> via "sudo rm -f /var/log/lightdm/x-0.log" won't actually free the disk
> space: on POSIX systems disk space is only cleaned up when there are no
> more references to the file.  If you try to delete it and you're still
> out of space you'll have to at least log out and log back in to restart
> the display manager, and/or possibly kill the process.
>
> In general those log files are for your information, for helping to
> track down issues.  The system itself doesn't need them for proper
> operation so if you need to delete them you should feel free to do so.
> It won't break anything.
>
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>

I had previously posted tail -30 of the log file, which showed nothing useful.

A PCI error is in the system, and, the log files within lightdm simply
attack the system, by growing, and, as one gets deleted, another
starts growing.

It is like a viral attack by the log files.

My system had frozen, after I deleted the file, and, I had to do a
dirty reboot - switching off the power on the computer, waiting a
minute, then booting up again.

After that, the file manager (caja) shows 59GB of free space in the / partition.

So, deleting the file that was 64GB, freed up only 59GB.

It is like that old proverb - no matter how big is the hard drive, it
will get eaten up - this time, by the operating system, that
apparently needs a terabyte or so, for the root partition.


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Mike Marchywka
On 29/07/2019, Mike Marchywka <[hidden email]> wrote:

> On Sun, Jul 28, 2019 at 03:22:06PM -0400, Paul Smith wrote:
>> On Mon, 2019-07-29 at 02:51 +0800, Bret Busby wrote:
>> > Whatever is happeing, I now have
>> >
>> > "
>> > bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
>> > -rw------- 1 root root 64086904832 Jul 29 02:49 /var/log/lightdm/x-0.log
>> > "
>> >
>> > and no space left on the / partition.
>> >
>> > So, whatever is happening, the file, as it stands, has to be deleted,
>> > as it has rendered the system unusable.
>>
>> I haven't been following this thread, but I mean, have you looked at
>> the contents of that file to see what it says?
>>
>> You can view the last 20 lines, for example, by opening a terminal
>> window and running:
>>
>>   tail -n20 /var/log/lightdm/x-0.log
>>
>> It could be that it's spewing errors or warnings to that file, which
>> could lead you to a poorly-behaving program on your system or warn you
>> about some hardware or configuration issue.
>>
>> I don't use lightdm (I use standard gdm) so I can't say for sure but
>> it's possible simply deleting that file won't solve your disk space
>> problem: if lightdm keeps the file open to write to it then removing it
>> via "sudo rm -f /var/log/lightdm/x-0.log" won't actually free the disk
>> space: on POSIX systems disk space is only cleaned up when there are no
>> more references to the file.  If you try to delete it and you're still
>> out of space you'll have to at least log out and log back in to restart
>> the display manager, and/or possibly kill the process.
>
>  I keep suggesting to find an entire loop to post- he posted last
> few lines before but it may help to get an entire period or go back
> to first logfile that seemed too big and start there too.
> Although deleting it and catching the new one starting to fill
> may be easier. One of problems was inability to get a /tmp/x-lock or
> something similar that may have simple explanation.
>

I have previously posted, a number of times, a copy of a repeating
error that loops.

>
> That is a good point though- I remember with the nullmailer problem
> I had to do something like a service restart but yeah you should be able
> to see it with "lsof | grep filename " although fixing the problem
> may require more drastic action anyway or at least a restart to
> change a configuration.
>
>
>
>>
>> In general those log files are for your information, for helping to
>> track down issues.  The system itself doesn't need them for proper
>> operation so if you need to delete them you should feel free to do so.
>> It won't break anything.
>>
>>
>> --
>> ubuntu-users mailing list
>> [hidden email]
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
> --
>
> mike marchywka
> 306 charles cox
> canton GA 30115
> USA, Earth
> [hidden email]
> 404-788-1216
> ORCID: 0000-0001-9237-455X
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Bret Busby <[hidden email]> wrote:

> On 29/07/2019, Mike Marchywka <[hidden email]> wrote:
>> On Sun, Jul 28, 2019 at 03:22:06PM -0400, Paul Smith wrote:
>>> On Mon, 2019-07-29 at 02:51 +0800, Bret Busby wrote:
>>> > Whatever is happeing, I now have
>>> >
>>> > "
>>> > bret@bret-MD34045-2521:~$ ls -l /var/log/lightdm/x*.*
>>> > -rw------- 1 root root 64086904832 Jul 29 02:49
>>> > /var/log/lightdm/x-0.log
>>> > "
>>> >
>>> > and no space left on the / partition.
>>> >
>>> > So, whatever is happening, the file, as it stands, has to be deleted,
>>> > as it has rendered the system unusable.
>>>
>>> I haven't been following this thread, but I mean, have you looked at
>>> the contents of that file to see what it says?
>>>
>>> You can view the last 20 lines, for example, by opening a terminal
>>> window and running:
>>>
>>>   tail -n20 /var/log/lightdm/x-0.log
>>>
>>> It could be that it's spewing errors or warnings to that file, which
>>> could lead you to a poorly-behaving program on your system or warn you
>>> about some hardware or configuration issue.
>>>
>>> I don't use lightdm (I use standard gdm) so I can't say for sure but
>>> it's possible simply deleting that file won't solve your disk space
>>> problem: if lightdm keeps the file open to write to it then removing it
>>> via "sudo rm -f /var/log/lightdm/x-0.log" won't actually free the disk
>>> space: on POSIX systems disk space is only cleaned up when there are no
>>> more references to the file.  If you try to delete it and you're still
>>> out of space you'll have to at least log out and log back in to restart
>>> the display manager, and/or possibly kill the process.
>>
>>  I keep suggesting to find an entire loop to post- he posted last
>> few lines before but it may help to get an entire period or go back
>> to first logfile that seemed too big and start there too.
>> Although deleting it and catching the new one starting to fill
>> may be easier. One of problems was inability to get a /tmp/x-lock or
>> something similar that may have simple explanation.
>>
>
> I have previously posted, a number of times, a copy of a repeating
> error that loops.
>

See the first message in the thread.


>>
>> That is a good point though- I remember with the nullmailer problem
>> I had to do something like a service restart but yeah you should be able
>> to see it with "lsof | grep filename " although fixing the problem
>> may require more drastic action anyway or at least a restart to
>> change a configuration.
>>
>>
>>
>>>
>>> In general those log files are for your information, for helping to
>>> track down issues.  The system itself doesn't need them for proper
>>> operation so if you need to delete them you should feel free to do so.
>>> It won't break anything.
>>>
>>>
>>> --
>>> ubuntu-users mailing list
>>> [hidden email]
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>
>> --
>>
>> mike marchywka
>> 306 charles cox
>> canton GA 30115
>> USA, Earth
>> [hidden email]
>> 404-788-1216
>> ORCID: 0000-0001-9237-455X
>>
>> --
>> ubuntu-users mailing list
>> [hidden email]
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>>
>
>
> --
> 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
>
> ....................................................
>


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Paul Smith-2
In reply to this post by Mike Marchywka
On Sun, 2019-07-28 at 19:31 +0000, Mike Marchywka wrote:
>  I keep suggesting to find an entire loop to post- he posted last
> few lines before but it may help to get an entire period or go back
> to first logfile that seemed too big and start there too.
> Although deleting it and catching the new one starting to fill
> may be easier.

Maybe.  In my experience the last lines in the log file are more
relevant and useful than the first ones.  The first ones are usually
just the normal startup information, etc.

It's the last lines that tell you what's wrong now.

Bret Busby wrote:
> See the first message in the thread.

That's the output from /var/log/syslog.  That may or may not be
helpful.  What we need to see is the output from the file that is huge
and keeps growing: /var/log/lightdm/x-0.log

OK I finally found the message:

https://lists.ubuntu.com/archives/ubuntu-users/2019-July/297830.html

All this discussion of logrotate is not useful.  That's for a system
that is behaving normally.  Your system is not behaving normally.

Also the output in /var/log/syslog may or may not be relevant.  We
should ignore it for now.

The important output is what is seen in your ever-growing log file (the
really big one).

There are two things we need to do:

First, get your system back to working.  The only way to do that is get
rid of these huge log files and free up space on the root partition.
I've discussed how to do that: remove the huge file, then log out and
back in or, of that doesn't work, try rebooting.

However that is only a temporary solution if your log file continues to
grow like this: the disk will just fill up again.  The only way to get
it to stop is to figure out why it's constantly getting those errors.

I saw two messages in the output of the message above:
  (EE) Could not write pid to lock file in /tmp/.tX0-lock
and:
  xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

The first one is simple enough.  It might have been because your disk
is full, in which case it's a symptom not a cause.  What are the
permissions on these files?  Run this command:

  ls -ald /tmp /tmp/.tX0-lock

and let us know the results.

The second error also appears to be a permissions problem: I googled
for that message and came across a number of issues discussing starting
the X server without root privileges.  However all of them seem to be
from 5+ years ago.  Modern X servers don't require root privileges to
start.

Unfortunately I don't know much about lightdm (I guess you're using
Xubuntu or something like that not standard Ubuntu which uses gdm) so I
can't provide any direct advice.  Maybe your distro still requires root
privileges to start X.

If, after you reboot and your disk is no longer full, you watch the
size of the /var/log/lightdm/x-0.log file and it continues to grow,
please get the last 50 or so lines and send those along; it doesn't
look like 20 or 30 lines will be enough.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
In reply to this post by Bret Busby-2
On Mon, Jul 29, 2019 at 03:45:13AM +0800, Bret Busby wrote:
> >
> > I have previously posted, a number of times, a copy of a repeating
> > error that loops.
> >
>
> See the first message in the thread.
>

At this point it may help just to check again and find the whole loop,
not just the last 30 or was that at least one entire loop?
The things I remember was unable to set the lock fil in /tmp
but you posted /tmp was writable by all. So, right now,
that is about all we have to go on. Either it is full, someone else
is deleting it, or the code that is supposed to create it never executes.
I guess someone else could be writing it, preventing the complainer
from locking but you could look to see if it is there or shows up in lsof.

That may be easy to try, if it is stillcomplaining about a lock
file,

lsof | grep offending-file-name

and see if it held by another.





--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Paul Smith-2
On 29/07/2019, Paul Smith <[hidden email]> wrote:

> On Sun, 2019-07-28 at 19:31 +0000, Mike Marchywka wrote:
>>  I keep suggesting to find an entire loop to post- he posted last
>> few lines before but it may help to get an entire period or go back
>> to first logfile that seemed too big and start there too.
>> Although deleting it and catching the new one starting to fill
>> may be easier.
>
> Maybe.  In my experience the last lines in the log file are more
> relevant and useful than the first ones.  The first ones are usually
> just the normal startup information, etc.
>
> It's the last lines that tell you what's wrong now.
>
> Bret Busby wrote:
>> See the first message in the thread.
>
> That's the output from /var/log/syslog.  That may or may not be
> helpful.  What we need to see is the output from the file that is huge
> and keeps growing: /var/log/lightdm/x-0.log
>
> OK I finally found the message:
>
> https://lists.ubuntu.com/archives/ubuntu-users/2019-July/297830.html
>
> All this discussion of logrotate is not useful.  That's for a system
> that is behaving normally.  Your system is not behaving normally.
>
> Also the output in /var/log/syslog may or may not be relevant.  We
> should ignore it for now.
>
> The important output is what is seen in your ever-growing log file (the
> really big one).
>
> There are two things we need to do:
>
> First, get your system back to working.  The only way to do that is get
> rid of these huge log files and free up space on the root partition.
> I've discussed how to do that: remove the huge file, then log out and
> back in or, of that doesn't work, try rebooting.
>
> However that is only a temporary solution if your log file continues to
> grow like this: the disk will just fill up again.  The only way to get
> it to stop is to figure out why it's constantly getting those errors.
>
> I saw two messages in the output of the message above:
>   (EE) Could not write pid to lock file in /tmp/.tX0-lock
> and:
>   xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>
> The first one is simple enough.  It might have been because your disk
> is full, in which case it's a symptom not a cause.  What are the
> permissions on these files?  Run this command:
>
>   ls -ald /tmp /tmp/.tX0-lock
>
> and let us know the results.
>

"
bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
ls: cannot access '/tmp/.tX0-lock': No such file or directory
drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
bret@bret-MD34045-2521:~$
"

> The second error also appears to be a permissions problem: I googled
> for that message and came across a number of issues discussing starting
> the X server without root privileges.  However all of them seem to be
> from 5+ years ago.  Modern X servers don't require root privileges to
> start.
>
> Unfortunately I don't know much about lightdm (I guess you're using
> Xubuntu or something like that not standard Ubuntu which uses gdm) so I
> can't provide any direct advice.  Maybe your distro still requires root
> privileges to start X.
>
> If, after you reboot and your disk is no longer full, you watch the
> size of the /var/log/lightdm/x-0.log file and it continues to grow,
> please get the last 50 or so lines and send those along; it doesn't
> look like 20 or 30 lines will be enough.
>
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Paul Smith-2
On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:

> > The first one is simple enough.  It might have been because your disk
> > is full, in which case it's a symptom not a cause.  What are the
> > permissions on these files?  Run this command:
> >
> >    ls -ald /tmp /tmp/.tX0-lock
> >
> > and let us know the results.
>
> "
> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
> ls: cannot access '/tmp/.tX0-lock': No such file or directory
> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp

This looks correct.  That most likely means that this error is a
symptom of your disk being full, and not the cause of the problem.

After you have cleared out space on your disk, please keep an eye on
the size of the /var/log/lightdm/x-0.log file.  If it continues to
grow, send along the last 50 or so lines of output from that file and
we'll see what it has to say.

Also, you did show you're using an 18.04.2 based system, but if you're
using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
the output of the "lsb_release -a" command which would tell us (I
think) if you're using a spin or similar.

What distribution did you actually install here?


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Mike Marchywka
On Sun, Jul 28, 2019 at 04:35:18PM -0400, Paul Smith wrote:

> On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
> > > The first one is simple enough.  It might have been because your disk
> > > is full, in which case it's a symptom not a cause.  What are the
> > > permissions on these files?  Run this command:
> > >
> > >    ls -ald /tmp /tmp/.tX0-lock
> > >
> > > and let us know the results.
> >
> > "
> > bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
> > ls: cannot access '/tmp/.tX0-lock': No such file or directory
> > drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>
> This looks correct.  That most likely means that this error is a
> symptom of your disk being full, and not the cause of the problem.


Oh, I thought he got that before the disk filled up again :)
The rotated logs were all small, back around the 22nd there
was a big one- normal entries were probably a dozen lines followed
by the presumed loop.


>
> After you have cleared out space on your disk, please keep an eye on
> the size of the /var/log/lightdm/x-0.log file.  If it continues to
> grow, send along the last 50 or so lines of output from that file and
> we'll see what it has to say.
>
> Also, you did show you're using an 18.04.2 based system, but if you're
> using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
> the output of the "lsb_release -a" command which would tell us (I
> think) if you're using a spin or similar.
>
> What distribution did you actually install here?
>
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--

mike marchywka
306 charles cox
canton GA 30115
USA, Earth
[hidden email]
404-788-1216
ORCID: 0000-0001-9237-455X

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
In reply to this post by Paul Smith-2
On 29/07/2019, Paul Smith <[hidden email]> wrote:

> On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
>> > The first one is simple enough.  It might have been because your disk
>> > is full, in which case it's a symptom not a cause.  What are the
>> > permissions on these files?  Run this command:
>> >
>> >    ls -ald /tmp /tmp/.tX0-lock
>> >
>> > and let us know the results.
>>
>> "
>> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
>> ls: cannot access '/tmp/.tX0-lock': No such file or directory
>> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>
> This looks correct.  That most likely means that this error is a
> symptom of your disk being full, and not the cause of the problem.
>
> After you have cleared out space on your disk, please keep an eye on
> the size of the /var/log/lightdm/x-0.log file.  If it continues to
> grow, send along the last 50 or so lines of output from that file and
> we'll see what it has to say.
>

I have posted a message, that is awaiting moderation - a few kB too large.

If you look at this output;

"
bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
#60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
vt.handoff=1
Build Date: 03 June 2019  08:10:35AM
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: Mon Jul 29 03:29:50 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
_XSERVTransSocketUNIXAccept: accept() failed
"

that last line is an endless loop.

> Also, you did show you're using an 18.04.2 based system, but if you're
> using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
> the output of the "lsb_release -a" command which would tell us (I
> think) if you're using a spin or similar.
>
> What distribution did you actually install here?
>

I had posted the output, in response to a previous post by Ralf;

"
bret@bret-MD34045-2521:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic
"

It is UbuntuMATE - I believe that had posted that way much earlier in
the thread.

Also,

"
"
uname -v
#60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
bret@bret-MD34045-2521:~$ uname -a
Linux bret-MD34045-2521 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
"
"

Now, I need to see what I can do before the log file crashes my system again.

I think that a defect exists in the creating of the log -file -
whatever is inputting to the log file should not be in an endless
loop. It ism destructive.

>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Bret Busby <[hidden email]> wrote:

> On 29/07/2019, Paul Smith <[hidden email]> wrote:
>> On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
>>> > The first one is simple enough.  It might have been because your disk
>>> > is full, in which case it's a symptom not a cause.  What are the
>>> > permissions on these files?  Run this command:
>>> >
>>> >    ls -ald /tmp /tmp/.tX0-lock
>>> >
>>> > and let us know the results.
>>>
>>> "
>>> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
>>> ls: cannot access '/tmp/.tX0-lock': No such file or directory
>>> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>>
>> This looks correct.  That most likely means that this error is a
>> symptom of your disk being full, and not the cause of the problem.
>>
>> After you have cleared out space on your disk, please keep an eye on
>> the size of the /var/log/lightdm/x-0.log file.  If it continues to
>> grow, send along the last 50 or so lines of output from that file and
>> we'll see what it has to say.
>>
>
> I have posted a message, that is awaiting moderation - a few kB too large.
>
> If you look at this output;
>
> "
> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>
> X.Org X Server 1.19.6
> Release Date: 2017-12-20
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
> vt.handoff=1
> Build Date: 03 June 2019  08:10:35AM
> 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: Mon Jul 29 03:29:50 2019
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> _XSERVTransSocketUNIXAccept: accept() failed
> "
>
> that last line is an endless loop.
>
>> Also, you did show you're using an 18.04.2 based system, but if you're
>> using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
>> the output of the "lsb_release -a" command which would tell us (I
>> think) if you're using a spin or similar.
>>
>> What distribution did you actually install here?
>>
>
> I had posted the output, in response to a previous post by Ralf;
>
> "
> bret@bret-MD34045-2521:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:    Ubuntu 18.04.2 LTS
> Release:        18.04
> Codename:       bionic
> "
>
> It is UbuntuMATE - I believe that had posted that way much earlier in
> the thread.
>
> Also,
>
> "
> "
> uname -v
> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
> bret@bret-MD34045-2521:~$ uname -a
> Linux bret-MD34045-2521 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
> 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> "
> "
>
> Now, I need to see what I can do before the log file crashes my system
> again.
>
> I think that a defect exists in the creating of the log -file -
> whatever is inputting to the log file should not be in an endless
> loop. It ism destructive.
>

"
bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
-rw------- 1 root root 130020644 Jul 29 04:53 /var/log/lightdm/x-0.log
"


--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|

Re: Request for explanation of error message

Bret Busby-2
On 29/07/2019, Bret Busby <[hidden email]> wrote:

> On 29/07/2019, Bret Busby <[hidden email]> wrote:
>> On 29/07/2019, Paul Smith <[hidden email]> wrote:
>>> On Mon, 2019-07-29 at 04:14 +0800, Bret Busby wrote:
>>>> > The first one is simple enough.  It might have been because your disk
>>>> > is full, in which case it's a symptom not a cause.  What are the
>>>> > permissions on these files?  Run this command:
>>>> >
>>>> >    ls -ald /tmp /tmp/.tX0-lock
>>>> >
>>>> > and let us know the results.
>>>>
>>>> "
>>>> bret@bret-MD34045-2521:~$ ls -ald /tmp /tmp/.tX0-lock
>>>> ls: cannot access '/tmp/.tX0-lock': No such file or directory
>>>> drwxrwxrwt 19 root root 4096 Jul 29 03:57 /tmp
>>>
>>> This looks correct.  That most likely means that this error is a
>>> symptom of your disk being full, and not the cause of the problem.
>>>
>>> After you have cleared out space on your disk, please keep an eye on
>>> the size of the /var/log/lightdm/x-0.log file.  If it continues to
>>> grow, send along the last 50 or so lines of output from that file and
>>> we'll see what it has to say.
>>>
>>
>> I have posted a message, that is awaiting moderation - a few kB too
>> large.
>>
>> If you look at this output;
>>
>> "
>> bret@bret-MD34045-2521:~$ sudo head -25 /var/log/lightdm/x-0.log
>>
>> X.Org X Server 1.19.6
>> Release Date: 2017-12-20
>> X Protocol Version 11, Revision 0
>> Build Operating System: Linux 4.4.0-148-generic x86_64 Ubuntu
>> Current Operating System: Linux bret-MD34045-2521 4.15.0-55-generic
>> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
>> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
>> root=UUID=1d3945d6-b596-4d57-8151-d2eef48a56b8 ro quiet splash
>> vt.handoff=1
>> Build Date: 03 June 2019  08:10:35AM
>> 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: Mon Jul 29 03:29:50 2019
>> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> _XSERVTransSocketUNIXAccept: accept() failed
>> "
>>
>> that last line is an endless loop.
>>
>>> Also, you did show you're using an 18.04.2 based system, but if you're
>>> using lightdm it won't be out-of-the-box vanilla Ubuntu.  I didn't see
>>> the output of the "lsb_release -a" command which would tell us (I
>>> think) if you're using a spin or similar.
>>>
>>> What distribution did you actually install here?
>>>
>>
>> I had posted the output, in response to a previous post by Ralf;
>>
>> "
>> bret@bret-MD34045-2521:~$ lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:    Ubuntu 18.04.2 LTS
>> Release:        18.04
>> Codename:       bionic
>> "
>>
>> It is UbuntuMATE - I believe that had posted that way much earlier in
>> the thread.
>>
>> Also,
>>
>> "
>> "
>> uname -v
>> #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
>> bret@bret-MD34045-2521:~$ uname -a
>> Linux bret-MD34045-2521 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
>> 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
>> "
>> "
>>
>> Now, I need to see what I can do before the log file crashes my system
>> again.
>>
>> I think that a defect exists in the creating of the log -file -
>> whatever is inputting to the log file should not be in an endless
>> loop. It ism destructive.
>>
>
> "
> bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
> -rw------- 1 root root 130020644 Jul 29 04:53 /var/log/lightdm/x-0.log
> "
>

"
bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
-rw------- 1 root root 130020644 Jul 29 04:53 /var/log/lightdm/x-0.log
bret@bret-MD34045-2521:~$ sudo rm  /var/log/lightdm/x-0.log
bret@bret-MD34045-2521:~$ sudo ls -l /var/log/lightdm/x-0.log
ls: cannot access '/var/log/lightdm/x-0.log': No such file or directory
'

--
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

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

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
1234