[Forgive the google posting, but my nntp host is dead.]

I'm building (well, built) a new box that is a clean install of FreeBSD 12.2, with a current port of innd.

However starting inn leads to (in a few seconds) a syslog of:

kernel: pid 39316 (innd), jid 0, uid 8: exited on signal 11 (core dumped)

(core dumps are nowhere to be found.)

For comparison, I updated my (previously good innd) 11.4 box (which the new is to replace) to all currents ports, and I get the same. This even though the innd version has not changed.

Is there a current problem that I should have heard of?

In article <3a7f139e-98a7-4ac0-8668-a957dd402e9bn@googlegroups.com>,
Drew Lawson <drewlawson42@gmail.com> wrote:
>[Forgive the google posting, but my nntp host is dead.]
>
>I'm building (well, built) a new box that is a clean install of FreeBSD
>12.2, with a current port of innd.
>
>However starting inn leads to (in a few seconds) a syslog of:
>
>kernel: pid 39316 (innd), jid 0, uid 8: exited on signal 11 (core dumped)
>
>(core dumps are nowhere to be found.)
>
>For comparison, I updated my (previously good innd) 11.4 box (which the
>new is to replace) to all currents ports, and I get the same. This even
>though the innd version has not changed.
>
>Is there a current problem that I should have heard of?
>
>

Nope. I use the daily snapshot of Inn no problem.

Are you using clang 11 ?
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b
Let yourself not be duped out of a fast car for a slower one. -unknown

On Monday, May 10, 2021 at 9:09:50 AM UTC-4, YouKnowWho!! wrote:
> In article <3a7f139e-98a7-4ac0...@googlegroups.com>,
> Drew Lawson <drewla...@gmail.com> wrote:
> >[Forgive the google posting, but my nntp host is dead.]
> >
> >I'm building (well, built) a new box that is a clean install of FreeBSD
> >12.2, with a current port of innd.
> >
> >However starting inn leads to (in a few seconds) a syslog of:
> >
> >kernel: pid 39316 (innd), jid 0, uid 8: exited on signal 11 (core dumped)

Well, a completely clean install (without my config changes and spool) is running fine.
I'm putting my stuff in one piece at a time and hoping it goes well.
'makehistory -O' was also crashing, so I'm guessing something was wonky in my overview.

> Are you using clang 11 ?

clang -v
FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
Target: x86_64-unknown-freebsd12.2
Thread model: posix
InstalledDir: /usr/bin

Just the version that installed with 12.2.
Thanks for confirming that it *should* work.

In article <67680b5d-4578-4506-ba82-bc306630fe84n@googlegroups.com>
Drew Lawson <drewlawson42@gmail.com> writes:
>On Monday, May 10, 2021 at 9:09:50 AM UTC-4, YouKnowWho!! wrote:
>> In article <3a7f139e-98a7-4ac0...@googlegroups.com>,
>> Drew Lawson <drewla...@gmail.com> wrote:
>> >[Forgive the google posting, but my nntp host is dead.]
>> >
>> >I'm building (well, built) a new box that is a clean install of FreeBSD
>> >12.2, with a current port of innd.
>> >
>> >However starting inn leads to (in a few seconds) a syslog of:
>> >
>> >kernel: pid 39316 (innd), jid 0, uid 8: exited on signal 11 (core dumped)
>
>Well, a completely clean install (without my config changes and spool) is running fine.
>I'm putting my stuff in one piece at a time and hoping it goes well.
>'makehistory -O' was also crashing, so I'm guessing something was wonky in my overview.

I put back everything in ~news/etc, ~news/db/active, and
~news/spool/articles. Ran 'makehistory -O' and it starts up and
runs just fine.

I knew the overview from a different machine/disk would be invalid,
but I didn't expect it to break things. Something learned for the
month.

Another thing learned is that the core dump was in ~news/spool.

--
Drew Lawson

I only came in search of answers, never planned to sell my soul
I only came in search of something left that I could call my own

In article <s7bi1i$260v$1@raid2.furrfu.com>,
Drew Lawson <drew@furrfu.invalid> wrote:
>In article <67680b5d-4578-4506-ba82-bc306630fe84n@googlegroups.com>
> Drew Lawson <drewlawson42@gmail.com> writes:
>>On Monday, May 10, 2021 at 9:09:50 AM UTC-4, YouKnowWho!! wrote:
>>> In article <3a7f139e-98a7-4ac0...@googlegroups.com>,
>>> Drew Lawson <drewla...@gmail.com> wrote:
>>> >[Forgive the google posting, but my nntp host is dead.]
>>> >
>>> >I'm building (well, built) a new box that is a clean install of FreeBSD
>>> >12.2, with a current port of innd.
>>> >
>>> >However starting inn leads to (in a few seconds) a syslog of:
>>> >
>>> >kernel: pid 39316 (innd), jid 0, uid 8: exited on signal 11 (core dumped)
>>
>>Well, a completely clean install (without my config changes and spool)
>is running fine.
>>I'm putting my stuff in one piece at a time and hoping it goes well.
>>'makehistory -O' was also crashing, so I'm guessing something was wonky
>in my overview.
>
>I put back everything in ~news/etc, ~news/db/active, and
>~news/spool/articles. Ran 'makehistory -O' and it starts up and
>runs just fine.
>
>I knew the overview from a different machine/disk would be invalid,
>but I didn't expect it to break things. Something learned for the
>month.
>
>Another thing learned is that the core dump was in ~news/spool.
>

There we go.

Mind you I tried to migrate from BSD/OS to FreeBSD 6 years
ago.

ever thought to type service innd start to get the process going.

BTW if you need a peer, just e-mail me at doctor@doctor.nl2k.ab.ca .

>
>--
> Drew Lawson
>
> I only came in search of answers, never planned to sell my soul
> I only came in search of something left that I could call my own

--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b
Let yourself not be duped out of a fast car for a slower one. -unknown

On 5/10/21 8:04 AM, Drew Lawson wrote:
> In article <67680b5d-4578-4506-ba82-bc306630fe84n@googlegroups.com>
> Drew Lawson <drewlawson42@gmail.com> writes:
>> On Monday, May 10, 2021 at 9:09:50 AM UTC-4, YouKnowWho!! wrote:
>>> In article <3a7f139e-98a7-4ac0...@googlegroups.com>,
>>> Drew Lawson <drewla...@gmail.com> wrote:
>>>> [Forgive the google posting, but my nntp host is dead.]
>>>>
>>>> I'm building (well, built) a new box that is a clean install of FreeBSD
>>>> 12.2, with a current port of innd.
>>>>
>>>> However starting inn leads to (in a few seconds) a syslog of:
>>>>
>>>> kernel: pid 39316 (innd), jid 0, uid 8: exited on signal 11 (core dumped)
>>
>> Well, a completely clean install (without my config changes and spool) is running fine.
>> I'm putting my stuff in one piece at a time and hoping it goes well.
>> 'makehistory -O' was also crashing, so I'm guessing something was wonky in my overview.
>
> I put back everything in ~news/etc, ~news/db/active, and
> ~news/spool/articles. Ran 'makehistory -O' and it starts up and
> runs just fine.
>
> I knew the overview from a different machine/disk would be invalid,
> but I didn't expect it to break things. Something learned for the
> month.
>
> Another thing learned is that the core dump was in ~news/spool.
>

This sounds like ino64. I would maybe consider switching to ovsqlite
with this transition, I added an inn-current port with it
https://www.freshports.org/news/inn-current/.

"
These upgrade notes are taken from /usr/ports/UPDATING

2018-12-11

Affects: users of news/inn when upgrading to FreeBSD 12

Author: naddy@FreeBSD.org

Reason:
When upgrading from FreeBSD 11 to 12, a change in the size of the
ino_t type causes a binary incompatibility in the overview
database
if the default tradindexed format is used.

After upgrading the inn package, remove the overview/group.index
file and regenerate the history and overview database with
makehistory(8) before starting innd.

# echo '. /usr/local/news/lib/innshellvars && \
rm -f $OVERVIEWDIR/group.index && \
$NEWSBIN/makehistory -O -s `wc -l <$HISTORY`' | \
su -fm news -c '/bin/sh -s'
"

In article <satmdi$11j1$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Kevin Bowling <kevin.bowling@kev009.com> writes:
>On 5/10/21 8:04 AM, Drew Lawson wrote:
>> In article <67680b5d-4578-4506-ba82-bc306630fe84n@googlegroups.com>
>> Drew Lawson <drewlawson42@gmail.com> writes:

>>> Well, a completely clean install (without my config changes and spool) is running fine.
>>> I'm putting my stuff in one piece at a time and hoping it goes well.
>>> 'makehistory -O' was also crashing, so I'm guessing something was wonky in my overview.
>>
>> I put back everything in ~news/etc, ~news/db/active, and
>> ~news/spool/articles. Ran 'makehistory -O' and it starts up and
>> runs just fine.
>>
>> I knew the overview from a different machine/disk would be invalid,
>> but I didn't expect it to break things. Something learned for the
>> month.
>>
>> Another thing learned is that the core dump was in ~news/spool.
>>
>
>This sounds like ino64.

[snip]

> When upgrading from FreeBSD 11 to 12, a change in the size of the
> ino_t type causes a binary incompatibility in the overview
>database
> if the default tradindexed format is used.

That sounds like exactly the problem.
And a type size change makes perfect sense.

I normally only scane UPDATING for base system issues. It didn't
occur to me to check for port issues. I guess I've gotten lucky
with sloppy methods.

--
Drew Lawson And I know there's more to the story
I know I need to see more
I need to see s'more, hear s'more
feel s'more. I gotta be s'more

On 6/22/21 6:46 PM, Drew Lawson wrote:
> In article <satmdi$11j1$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
> Kevin Bowling <kevin.bowling@kev009.com> writes:
>> On 5/10/21 8:04 AM, Drew Lawson wrote:
>>> In article <67680b5d-4578-4506-ba82-bc306630fe84n@googlegroups.com>
>>> Drew Lawson <drewlawson42@gmail.com> writes:
>
>>>> Well, a completely clean install (without my config changes and spool) is running fine.
>>>> I'm putting my stuff in one piece at a time and hoping it goes well.
>>>> 'makehistory -O' was also crashing, so I'm guessing something was wonky in my overview.
>>>
>>> I put back everything in ~news/etc, ~news/db/active, and
>>> ~news/spool/articles. Ran 'makehistory -O' and it starts up and
>>> runs just fine.
>>>
>>> I knew the overview from a different machine/disk would be invalid,
>>> but I didn't expect it to break things. Something learned for the
>>> month.
>>>
>>> Another thing learned is that the core dump was in ~news/spool.
>>>
>>
>> This sounds like ino64.
>
> [snip]
>
>> When upgrading from FreeBSD 11 to 12, a change in the size of the
>> ino_t type causes a binary incompatibility in the overview
>> database
>> if the default tradindexed format is used.
>
> That sounds like exactly the problem.
> And a type size change makes perfect sense.
>
> I normally only scane UPDATING for base system issues. It didn't
> occur to me to check for port issues. I guess I've gotten lucky
> with sloppy methods.
>

It's somewhat unfortunate the file format uses this kind of system info.
This is one reason to consider switching to ovsqlite.