Bug 31153

Summary: root partition full: /var/log/Xorg.0.log
Product: Mageia Reporter: Pierre Fortin <pfortin>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: minor    
Priority: Normal CC: davidwhodgins
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Pierre Fortin 2022-11-20 02:50:12 CET
Description of problem: [FYI]  

Xorg.0.log filled root partition
-rw-r--r--  1 root     root            8542097217 Nov 18 13:06 Xorg.0.log
$ grep "_XSERVTransSocketUNIXAccept: accept() failed" Xorg.0.log | wc -l
147,275,819
That's a LOT of socket failures.

CLeared log with:
$ cat > Xorg.0.log
<ctrl+d>

It's not growing any more...  

Version-Release number of selected component (if applicable):


How reproducible: no idea; first occurrence.  
The only issue I've worked on yesterday, was:
https://bugs.kde.org/show_bug.cgi?id=429211


Steps to Reproduce:
1.
2.
3.
Comment 1 Pierre Fortin 2022-11-20 05:07:20 CET
All seemed fine until I applied updates...
-rw-r--r-- 1 root root    8542098909 Nov 19 22:32 Xorg.0.log

Looks like X wrote some messages (1696 bytes) about removing/adding the mouse within about 5 seconds; so I didn't notice anything.  Appears the log is huge again, mostly nulls. Will likely need to restart X to get rid of this file.

Although the file is reported as 8.5G, "df" before this was:
/dev/nvme0n1p2   50G   40G  7.3G  85% /
and it's now:
/dev/nvme0n1p2   50G   40G  7.0G  86% /

So the file is not eating the disk space it claims, for now...
At least, clobbering the original file freed up space for now...

As indicated in the original comment, this is an FYI since it may be related to the KDE panel freeze bug.
Comment 2 sturmvogel 2022-11-20 06:27:24 CET
As Dave Hodgins already noted in another bugreport from you, you are using a desktop system for server purposes (which won't work well as seen on many of your bugreports).

If you google "_XSERVTransSocketUNIXAccept: accept() failed" you will find that this is absolutely not related to KDE.
You simply reached the maximum allowed amount of open files/windows on a desktop system. Dependend on your application in use there are also several solutions available how to increase the maximum allowed open files (but you will for sure be affected by side effects as you are doing this on a desktop and not on a server with proper capabilities...).
Comment 3 Pierre Fortin 2022-11-20 09:07:55 CET
x

Resolution: (none) => OLD
Status: NEW => RESOLVED

Comment 4 Dave Hodgins 2022-11-20 17:53:33 CET
If it is number of files, to increase the limit add a file
to /etc/security/limits.d/ with two lines ...

*               hard    nofile          524288
*               soft    nofile          524288

See "man limits.conf" for details.

and create a file in /etc/sysctl.d/ with one line
fs.file-max = 8388608

See https://www.tecmint.com/increase-set-open-file-limits-in-linux/

I don't remember where I found those numbers, but IIRC those are the max
allowed.

CC: (none) => davidwhodgins