Re: iXorg / xenodm logs fill with errors: "_XSERVTransSocketUNIXAccept: accept() failed"
On Sat, Jul 11, 2020 at 07:38:58PM +0200, Caspar Schutijser wrote: > > > [501037.408] _XSERVTransSocketUNIXAccept: accept() failed > > > ... > > This message may be of interest: > https://marc.info/?l=openbsd-misc&m=155787066627780&w=2 Hi, I must have missed that message - thanks for pointing it out! I've made the changes for daemon in login.conf and restarted. Time will tell ... Thanks again! Cheers, Robb.
Re: iXorg / xenodm logs fill with errors: "_XSERVTransSocketUNIXAccept: accept() failed"
On Fri, Jul 10, 2020 at 04:49:40PM +0200, Why 42? The lists account. wrote: > > Hi All, > > I'm running 6.7 snapshot (6.7 GENERIC.MP#302 amd64) as my main desktop > with Xfce. > > Two or three times now I've noticed that these two files in /var/log have > become unexpectedly huge: > > mjoelnir:log # du -sh xenodm.log Xorg.0.log > > 378Mxenodm.log > > 487MXorg.0.log > > Apart from the usual startup/initialisation messages (below) Xorg.0.log > contains many many instances of this message: > > mjoelnir:log # grep -c '_XSERVTransSocketUNIXAccept: accept() failed' > > Xorg.0.log 8800235 > > The same message is logged to xenodm.log i.e. > > mjoelnir:log # grep -c '_XSERVTransSocketUNIXAccept: accept() failed' > > xenodm.log > > 8800235 > > I don't know why or when this occurs, but I have the impression it occurs > when coming out of lockscreen i.e. when I return to my computer and enter > my password. The whole desktop becomes unresponsive for tens of seconds > at this point, probably busy writing those log messages ... > > I assume that there must be some an issue with xenodm or the X11 > subsystem. A search on the Internet only resulted in a couple of hits, > from 2010 and 2012, at least one of which was related to the Cygwin > platform - so quite different. I ran OpenBSD 6.6 for several months on > this system (Intel NUC 8i5) and didn't notice this issue. > > The only other video error I have noticed is this one in the console or > output of dmesg: > > drm:pid54673:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic > > update failure on pipe A > > I don't know if that is related. > > Any thoughts? Anyone else experienced anything similar? > > > FYI: Excerpt from Xorg.0.log > > [26.343] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem > > (Operation not permitted) > > Check that you have set 'machdep.allowaperture=1' > > in /etc/sysctl.conf and reboot your machine > > refer to xf86(4) for details > > [26.343]linear framebuffer access unavailable > > [26.373] (--) Using wscons driver on /dev/ttyC4 > > [26.386] > > X.Org X Server 1.20.8 > > X Protocol Version 11, Revision 0 > > [26.386] Build Operating System: OpenBSD 6.7 amd64 > > [26.386] Current Operating System: OpenBSD mjoelnir.fritz.box 6.7 > > GENERIC.MP#273 amd64 > > [26.386] Build Date: 15 June 2020 07:46:53PM > > [26.386] > > [26.386] Current version of pixman: 0.38.4 > > [26.386]Before reporting problems, check http://wiki.x.org > > to make sure that you have the latest version. > > [26.386] Markers: (--) probed, (**) from config file, (==) default > > setting, > > (++) from command line, (!!) notice, (II) informational, > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > [26.386] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 16 > > 20:04:24 2020 > > [26.388] (==) Using system config directory > > "/usr/X11R6/share/X11/xorg.conf.d" > > [26.389] (==) No Layout section. Using the first Screen section. > > [26.389] (==) No screen section available. Using defaults. > > [26.389] (**) |-->Screen "Default Screen Section" (0) > > [26.389] (**) | |-->Monitor "" > > [26.390] (==) No monitor specified for screen "Default Screen Section". > > Using a default monitor configuration. > > [26.390] (==) Automatically adding devices > > [26.390] (==) Automatically enabling devices > > [26.390] (==) Not automatically adding GPU devices > > [26.390] (==) Max clients allowed: 256, resource mask: 0x1f > > [26.394] (==) FontPath set to: > > /usr/X11R6/lib/X11/fonts/misc/, > > /usr/X11R6/lib/X11/fonts/TTF/, > > /usr/X11R6/lib/X11/fonts/OTF/, > > /usr/X11R6/lib/X11/fonts/Type1/, > > /usr/X11R6/lib/X11/fonts/100dpi/, > > /usr/X11R6/lib/X11/fonts/75dpi/ > > [26.394] (==) ModulePath set to "/usr/X11R6/lib/modules" > > [26.394] (II) The server relies on wscons to provide the list of input > > devices. > > If no devices become available, reconfigure wscons or disable > > AutoAddDevices. > > [26.394] (II) Loader magic: 0xeed1a3f9000 > > [26.394] (II) Module ABI versions: > > [26.394]X.Org ANSI C Emulation: 0.4 > > [26.394]X.Org Video Driver: 24.1 > &
iXorg / xenodm logs fill with errors: "_XSERVTransSocketUNIXAccept: accept() failed"
Hi All, I'm running 6.7 snapshot (6.7 GENERIC.MP#302 amd64) as my main desktop with Xfce. Two or three times now I've noticed that these two files in /var/log have become unexpectedly huge: > mjoelnir:log # du -sh xenodm.log Xorg.0.log > 378M xenodm.log > 487M Xorg.0.log Apart from the usual startup/initialisation messages (below) Xorg.0.log contains many many instances of this message: > mjoelnir:log # grep -c '_XSERVTransSocketUNIXAccept: accept() failed' > Xorg.0.log 8800235 The same message is logged to xenodm.log i.e. > mjoelnir:log # grep -c '_XSERVTransSocketUNIXAccept: accept() failed' > xenodm.log > 8800235 I don't know why or when this occurs, but I have the impression it occurs when coming out of lockscreen i.e. when I return to my computer and enter my password. The whole desktop becomes unresponsive for tens of seconds at this point, probably busy writing those log messages ... I assume that there must be some an issue with xenodm or the X11 subsystem. A search on the Internet only resulted in a couple of hits, from 2010 and 2012, at least one of which was related to the Cygwin platform - so quite different. I ran OpenBSD 6.6 for several months on this system (Intel NUC 8i5) and didn't notice this issue. The only other video error I have noticed is this one in the console or output of dmesg: > drm:pid54673:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic > update failure on pipe A I don't know if that is related. Any thoughts? Anyone else experienced anything similar? FYI: Excerpt from Xorg.0.log > [26.343] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem > (Operation not permitted) > Check that you have set 'machdep.allowaperture=1' > in /etc/sysctl.conf and reboot your machine > refer to xf86(4) for details > [26.343]linear framebuffer access unavailable > [26.373] (--) Using wscons driver on /dev/ttyC4 > [26.386] > X.Org X Server 1.20.8 > X Protocol Version 11, Revision 0 > [26.386] Build Operating System: OpenBSD 6.7 amd64 > [26.386] Current Operating System: OpenBSD mjoelnir.fritz.box 6.7 > GENERIC.MP#273 amd64 > [26.386] Build Date: 15 June 2020 07:46:53PM > [26.386] > [26.386] Current version of pixman: 0.38.4 > [26.386]Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [26.386] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [26.386] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 16 20:04:24 > 2020 > [26.388] (==) Using system config directory > "/usr/X11R6/share/X11/xorg.conf.d" > [26.389] (==) No Layout section. Using the first Screen section. > [26.389] (==) No screen section available. Using defaults. > [26.389] (**) |-->Screen "Default Screen Section" (0) > [26.389] (**) | |-->Monitor "" > [26.390] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [26.390] (==) Automatically adding devices > [26.390] (==) Automatically enabling devices > [26.390] (==) Not automatically adding GPU devices > [26.390] (==) Max clients allowed: 256, resource mask: 0x1f > [26.394] (==) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > [26.394] (==) ModulePath set to "/usr/X11R6/lib/modules" > [26.394] (II) The server relies on wscons to provide the list of input > devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [26.394] (II) Loader magic: 0xeed1a3f9000 > [26.394] (II) Module ABI versions: > [26.394]X.Org ANSI C Emulation: 0.4 > [26.394]X.Org Video Driver: 24.1 > [26.394]X.Org XInput driver : 24.1 > [26.394]X.Org Server Extension : 10.0 > [26.395] (--) PCI:*(0@0:2:0) 8086:3ea5:8086:2074 rev 1, Mem @ > 0xc000/16777216, 0x8000/1073741824, I/O @ 0x4000/64 > [26.395] (II) LoadModule: "glx" > [26.396] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so > [26.405] (II) Module glx: vendor="X.Org Foundation" > [26.405]compiled for 1.20.8, module version = 1.0.0 > [26.405]ABI class: X.Org Server Extension, version 10
X/xenodm logs: '_XSERVTransSocketUNIXAccept: accept() failed'
Hi All, I'm running 6.7 snapshot version (6.7 GENERIC.MP#273 amd64) as my main desktop with XFCE. A couple of time now I've noticed that these two files in /var/log have become unexpectedly huge: mjoelnir:log 23.06 09:44:15 # du -sh xenodm.log Xorg.0.log 378Mxenodm.log 487MXorg.0.log Apart from the usual startup/initialisation messages (below) Xorg.0.log contains many many instances of this message: > mjoelnir:log 23.06 09:51:59 # grep -c '_XSERVTransSocketUNIXAccept: accept() > failed' Xorg.0.log > 8800235 The same message is logged to xenodm.log i.e. > mjoelnir:log 23.06 09:53:14 # grep -c '_XSERVTransSocketUNIXAccept: accept() > failed' xenodm.log > 8800235 I don't know why or when this occurs, the xenodm messages aren't timestamped, but I assume that there must be some an issue with xenodm or the X11 subsystem. A search on the Internet only resulted in a couple of hits, from 2010 and 2012, at least one of which was related to the Cygwin platform - so quite different. I ran OpenBSD 6.6 for several months on this system (Intel NUC 8i5) and don't recall ever seeing this issue. The only other video issue/error I have noticed is this in the console or output of dmesg: > drm:pid54673:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic > update failure on pipe A I don't know if that is related. FYI: Excerpt from Xorg.0.log > [26.343] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem > (Operation not permitted) > Check that you have set 'machdep.allowaperture=1' > in /etc/sysctl.conf and reboot your machine > refer to xf86(4) for details > [26.343]linear framebuffer access unavailable > [26.373] (--) Using wscons driver on /dev/ttyC4 > [26.386] > X.Org X Server 1.20.8 > X Protocol Version 11, Revision 0 > [26.386] Build Operating System: OpenBSD 6.7 amd64 > [26.386] Current Operating System: OpenBSD mjoelnir.fritz.box 6.7 > GENERIC.MP#273 amd64 > [26.386] Build Date: 15 June 2020 07:46:53PM > [26.386] > [26.386] Current version of pixman: 0.38.4 > [26.386]Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [26.386] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [26.386] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 16 20:04:24 > 2020 > [26.388] (==) Using system config directory > "/usr/X11R6/share/X11/xorg.conf.d" > [26.389] (==) No Layout section. Using the first Screen section. > [26.389] (==) No screen section available. Using defaults. > [26.389] (**) |-->Screen "Default Screen Section" (0) > [26.389] (**) | |-->Monitor "" > [26.390] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [26.390] (==) Automatically adding devices > [26.390] (==) Automatically enabling devices > [26.390] (==) Not automatically adding GPU devices > [26.390] (==) Max clients allowed: 256, resource mask: 0x1f > [26.394] (==) FontPath set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/OTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/X11R6/lib/X11/fonts/75dpi/ > [26.394] (==) ModulePath set to "/usr/X11R6/lib/modules" > [26.394] (II) The server relies on wscons to provide the list of input > devices. > If no devices become available, reconfigure wscons or disable > AutoAddDevices. > [26.394] (II) Loader magic: 0xeed1a3f9000 > [26.394] (II) Module ABI versions: > [26.394]X.Org ANSI C Emulation: 0.4 > [26.394]X.Org Video Driver: 24.1 > [26.394]X.Org XInput driver : 24.1 > [26.394]X.Org Server Extension : 10.0 > [26.395] (--) PCI:*(0@0:2:0) 8086:3ea5:8086:2074 rev 1, Mem @ > 0xc000/16777216, 0x8000/1073741824, I/O @ 0x4000/64 > [26.395] (II) LoadModule: "glx" > [26.396] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so > [26.405] (II) Module glx: vendor="X.Org Foundation" > [26.405]compiled for 1.20.8, module version = 1.0.0 > [26.405]ABI class: X.Org Server Extension, version 10.0 > [26.405] (==) Matched modesetting as autoconfigured driver 0 > [26.405] (==) Assigned the driver to the xf86ConfigLayout > [26.405] (II) LoadModule: "modesetti
_XSERVTransSocketUNIXAccept: accept() failed
Hello, These messages are filling up the Xorg.0.log and xenodm.log to gigabytes and does not allow additional xterm windows to open. I see these messages in /var/log/Xorg.0.log joe:10424$ tail Xorg.0.log [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.045] _XSERVTransSocketUNIXAccept: accept() failed joe:10425$ tail /var/log/xenodm.log _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed 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
Re: _XSERVTransSocketUNIXAccept: accept() failed
> What were you trying to do when you got these messages? This happens when I have a bunch of X apps (with windows) open and I try open another xterm. It appears that there is some limit to the number of X windows that can be opened. When I try to open another one after that limit, I get these messages. I checked 'man login.conf' but nothing seemed relevant. I am not sure if any sysctl values might be responsible for this behaviour though. Thanks
Re: _XSERVTransSocketUNIXAccept: accept() failed
What were you trying to do when you got these messages? On Thu, Feb 14, 2019 at 1:27 PM Joe M wrote: > > Hello, > > I see these messages in /var/log/Xorg.0.log > > joe:10424$ tail Xorg.0.log > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed > [2616181.045] _XSERVTransSocketUNIXAccept: accept() failed > > > joe:10425$ tail /var/log/xenodm.log > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > _XSERVTransSocketUNIXAccept: accept() failed > > > Any suggestions on how to figure out why this is happening. > > Thanks > -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
_XSERVTransSocketUNIXAccept: accept() failed
Hello, I see these messages in /var/log/Xorg.0.log joe:10424$ tail Xorg.0.log [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.044] _XSERVTransSocketUNIXAccept: accept() failed [2616181.045] _XSERVTransSocketUNIXAccept: accept() failed joe:10425$ tail /var/log/xenodm.log _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed _XSERVTransSocketUNIXAccept: accept() failed Any suggestions on how to figure out why this is happening. Thanks
