Request for explanation of error message
Bret Busby
bret.busby at gmail.com
Mon Jul 29 09:17:51 UTC 2019
On 29/07/2019, Mike Marchywka <marchywka at hotmail.com> wrote:
> On Mon, Jul 29, 2019 at 06:12:15AM +0800, Bret Busby wrote:
>> On 29/07/2019, Mike Marchywka <marchywka at hotmail.com> wrote:
>> > On Mon, Jul 29, 2019 at 05:06:16AM +0800, Bret Busby wrote:
>> >> On 29/07/2019, Paul Smith <paul at mad-scientist.net> 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 at 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 at 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.
>> >
>> > If googling the IOPL error did not work there is stuff like this too,
>> >
>> > http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
>> >
>> > you could lsof and grep for the process, check what it has open, or
>> > just
>> > make the changes and see what happens.
>> >
>>
>> At
>> http://openbsd-archive.7691.n7.nabble.com/XSERVTransSocketUNIXAccept-accept-failed-td366623.html
>> is
>>
>> "
>> Thanks to #openbsd's epony and oldlaptop, the resolution is to:
>>
>> 1. increase daemon openfiles-max to 2048 and openfiles-cur to 1024 in
>> /etc/login.conf
>> 2. cap_mkdb /etc/login.conf
>> 3. re-login.
>>
>> Thanks
>> "
>>
>> However, ...
>>
>> "
>> bret at bret-MD34045-2521:~$ sudo cat /etc/login.conf
>> [sudo] password for bret:
>> cat: /etc/login.conf: No such file or directory
>>
>> "
>>
>>
>> > I guess you could itry " ps ax -f | grep lightdm " and see if it is
>> > root or
>> > has the right user for any needed permissions.
>> >
>>
>> "
>> bret at bret-MD34045-2521:~$ ps ax -f | grep lightdm
>> root 1256 1 0 03:29 ? SLsl 0:00 /usr/sbin/lightdm
>> root 1269 1256 2 03:29 tty7 Ssl+ 3:34 /usr/lib/xorg/Xorg
>> -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7
>> -novtswitch
>> root 1458 1256 0 03:29 ? Sl 0:00 lightdm --session-child
>> 13 20
>> bret 15899 5719 0 06:07 pts/0 S+ 0:00 grep --color=auto
>> lightdm
>> bret at bret-MD34045-2521:~$
>> "
>>
>> I do not understand the output.
>
> Well, it is running as root. If googling did not work, you could see if
> it managed to open anything. For example,
>
> sudo netstat -anp | grep lightdm
> unix 3 [ ] STREAM CONNECTED 24081 1191/lightdm
>
> unix 2 [ ] DGRAM 28837 1332/lightdm
>
> unix 3 [ ] STREAM CONNECTED 27936 1191/lightdm
>
> unix 3 [ ] STREAM CONNECTED 24319 1332/lightdm
>
> unix 3 [ ] STREAM CONNECTED 26915 1191/lightdm
>
"
bret at bret-MD34045-2521:~$ sudo netstat -anp | grep lightdm
[sudo] password for bret:
unix 2 [ ] DGRAM 26540 1458/lightdm
unix 3 [ ] STREAM CONNECTED 29759 1458/lightdm
unix 3 [ ] STREAM CONNECTED 24440 1256/lightdm
unix 3 [ ] STREAM CONNECTED 27958 1256/lightdm
unix 3 [ ] STREAM CONNECTED 25119 1256/lightdm
unix 2 [ ] DGRAM 25121 1256/lightdm
bret at bret-MD34045-2521:~$
"
>
>
> with or without the wc,
>
> sudo lsof | grep lightdm | wc
>
"
bret at bret-MD34045-2521:~$ sudo lsof | grep lightdm | wc
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
128 1176 16202
bret at bret-MD34045-2521:~$
"
--
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