Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. msync - can someone shed some light please? (Chris Knipe)
2. Re: msync - can someone shed some light please? (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Thu, 12 Jun 2025 13:38:46 +0000
From: Chris Knipe <[email protected]>
To: "[email protected]" <[email protected]>
Subject: msync - can someone shed some light please?
Message-ID:
<ct2p275mb0531dfa350e717770c37529add...@ct2p275mb0531.zafp275.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
When adding groups (ctlinnd newgroup...), the following occurs:
2025-06-12T14:14:57.572314+02:00 nntpspool innd: SERVER msync failed
/var/lib/news/active 0x0x7f3f46800000 5062656 Cannot allocate memory
2025-06-12T14:14:57.572335+02:00 nntpspool innd: CNFS: CNFSshutdowncycbuff:
flushing 0
2025-06-12T14:14:57.594777+02:00 nntpspool systemd[1]: inn2.service: Main
process exited, code=exited, status=1/FAILURE
Inn refuses to start up, until I literally remove 1 line from my active file.
As soon as I add them again, the issue reoccurs. The name of the group being
added/removed is of no consequence, the issue is about the amount of groups -
that is what is getting me here, I completely fail to understand how inn can't
start up with ~107K groups in the active file.
root@nntpspool ~ # cat /var/lib/news/active|wc -l
107411
INN 2.7.3
Inn is using about 4GB RAM, the server has 128GB. I am pulling my hair out
here...
Thnx
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20250612/db5793c7/attachment-0001.htm>
------------------------------
Message: 2
Date: Fri, 13 Jun 2025 00:19:41 +0200
From: Julien ?LIE <[email protected]>
To: [email protected], Chris Knipe <[email protected]>
Subject: Re: msync - can someone shed some light please?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Chris,
> When adding groups (ctlinnd newgroup?), the following occurs:
>
> 2025-06-12T14:14:57.572314+02:00 nntpspool innd: SERVER msync failed
> /var/lib/news/active 0x0x7f3f46800000 5062656 Cannot allocate memory
>
> Inn refuses to start up, until I literally remove 1 line from my active
> file.? As soon as I add them again, the issue reoccurs.? The name of the
> group being added/removed is of no consequence, the issue is about the
> amount of groups ? that is what is getting me here, I completely fail to
> understand how inn can?t start up with ~107K groups in the active file.
>
> root@nntpspool ~ # cat /var/lib/news/active|wc -l
> 107411
>
> INN 2.7.3
What operating system are you using?
Do you build from sources? If that is the case, may you try to change
in lib/mmap.c:
char *start = (char *) ((uintptr_t) p & mask);
char *end = (char *) (((uintptr_t) p + length + pagesize) & mask);
to:
char *start = (char *) ((size_t) p & mask);
char *end = (char *) (((size_t) p + length + pagesize) & mask);
It is the only recent change (in 2023) in the code dealing with
mmap/msync. Though I am unsure it would solve the memory allocation
issue, it may be the first thing to test.
Otherwise, I am sorry I do not have any other clue right now.
The wanted allocation is 5,062,656 bytes according to the log, so it
should have worked on your server with 128 GB of RAM...
--
Julien ?LIE
??On ne va jamais si loin que lorsque l'on ne sait pas o? l'on va.??
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 166, Issue 1
*******************************************
