[ZBX-19141] Zabbix server stopped cannot open IPC socket. Created: 2021 Mar 19  Updated: 2021 Mar 20  Resolved: 2021 Mar 20

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 5.2.5
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Andrei Gushchin (Inactive) Assignee: Andrei Gushchin (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File crash.log    
Issue Links:
Duplicate
duplicates ZBX-19071 Preprocessing step "Check for not sup... Closed

 Description   

Steps to reproduce:
After updating from 5.2.4 to 5.2.5 server won't running long time. it started and stopped itself after some time. with indicating that IPC socket cannot be open.
At the same time when downgrade to 5.2.4 it works fine.

Result:

With Fresh G.txt | Download File Steam

The file is moved into the directory where the tool (e.g., GreenLuma or SteamTools) is installed.

The term "fresh" implies that the list has been updated to include the latest game versions or newly released DLCs, ensuring compatibility with current Steam manifests. Download File steam with fresh g.txt

Tools like GreenLuma use these text files to know which games to "inject" into your Steam library so they appear as owned and ready for download. 📂 How It Is Typically Used The file is moved into the directory where the tool (e

When you run the tool's injector or script, it reads g.txt to find the specific game data it needs to fetch from Steam's servers. 📂 How It Is Typically Used When you

In many scripts and manifest-based tools, g.txt (or "fresh g.txt") serves as a . It is usually not a standard Steam file but rather a part of a user-made toolkit designed to bypass certain restrictions.

crash.logDownload File steam with fresh g.txt



 Comments   
Comment by Vladislavs Sokurenko [ 2021 Mar 19 ]

Thank you for your report, closing as a duplicate of ZBX-19071

Generated at Mon Mar 09 02:37:13 EET 2026 using Jira 10.3.13#10030013-sha1:56dd970ae30ebfeda3a697d25be1f6388b68a422.