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

Comicscan Id 【PRO • 2025】

Two comics have the same ID, but they are different files. Solution: This is a "ID collision." The original scanner likely released a V2 (version 2). Manually append -V2 or -REPACK to the ID to differentiate.

In the ever-expanding universe of digital comic book collecting, organization is paramount. With thousands of issues spanning decades of publication history, from Golden Age rarities to modern variant covers, collectors rely on sophisticated metadata to keep their libraries sane and searchable. Among the most discussed—yet often misunderstood—pieces of this digital puzzle is the Comicscan ID .

These groups needed a way to track their releases across FTP servers and torrent sites. Thus, the was born. Initially, it was a simple filename. However, as databases like Comic Vine and the Grand Comics Database (GCD) grew, the ID evolved into a structured metadata field. comicscan id

My software (Komga) ignores the Comicscan ID. Solution: Ensure the ID is stored in a recognized field. Some software only reads Series , Number , and Volume . Use ComicTagger to map your custom Comicscan ID to a standard field like Notes or Tags .

Marvel and DC do not officially recognize the Comicscan ID. In fact, their proprietary apps actively strip such metadata. Nevertheless, for personal backups and private libraries, the ID remains an invaluable tool. For advanced users, maintaining a local database of Comicscan IDs allows for lightning-fast search and organization. Here is how to build one: Step 1: Standardize Your Naming Choose a convention and stick to it. The most universally accepted format is: Series Name Issue Number (Year) (Source) (Group Tag) Two comics have the same ID, but they are different files

Amazing Spider-Man 001 (2022) (Digital) (Zone-Empire).cbz

Think of it as a digital fingerprint for a specific release of a comic. While the ISBN (International Standard Book Number) identifies a trade paperback, and the UPC identifies a physical floppy, the Comicscan ID identifies a specific digital manifestation —including the scanner group, the resolution, the color correction applied, and the specific release version. Typically, a Comicscan ID follows a predictable naming convention embedded in the file’s metadata or filename itself. A standard example might look like this: In the ever-expanding universe of digital comic book

Whether you are a seasoned archivist converting longboxes to CBZ files or a casual reader using a tablet, understanding what a Comicscan ID is, how it works, and why it matters can transform your digital reading experience from a chaotic folder of files into a professional-grade library. At its core, a Comicscan ID is a unique alphanumeric identifier embedded within the metadata of a scanned or digitally born comic book file. It is not an official Marvel, DC, or Image Comics designation. Instead, it originates from the grassroots world of comic book scanning and digital preservation communities, often referred to as "the scene."

crash.logcomicscan id



 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.