Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-27 Thread Julien ÉLIE
Hi all, Upon investigating things further, I noticed that /etc/news/inn.conf listed pathrun as /run/news, which doesn't exist. I've recently also came across that issue during the migration of my news server to another one. Thanks Russ for the tip about tmpfiles.d; I confirm it works

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-19 Thread Julien ÉLIE
Hi John, news@news:/var/lib/news$ /usr/lib/news/bin/ovdb_init ovdb_init: OVDB: can not open database unless ovdb_monitor is running Upon investigating things further, I noticed that /etc/news/inn.conf listed pathrun as /run/news, which doesn't exist. Wouldn't it help if the current log

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-05 Thread Russ Allbery
I had forgotten more about this structure than I thought and should have re-read the source. The inode number in question isn't the link between the index and data file; it's between the top-level group.index file and the index file for a specific group. It's still correct that it's used to

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-05 Thread John Goerzen
On Sun, Sep 05 2021, Russ Allbery wrote: We could, but it does indicate an actual problem, so I'd love to understand more about why this is happening. If ZFS does change the inodes on every reboot, another possible solution may be to ensure that expireover fixes the inode references (I'm

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-05 Thread Russ Allbery
Julien ÉLIE writes: >> FWIW, tradindexed uses that inode number as an optimization. When >> expireover rewrites the data file, it does so in a way that changes the >> inode number (and updates that field in the index file), which >> communicates to any other process such as running nnrpd

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-03 Thread Julien ÉLIE
Hi Russ, innd: tradindexed: index inode mismatch for local.test ... expireover: tradindexed: index inode mismatch for control expireover: tradindexed: index inode mismatch for control.cancel expireover: tradindexed: index inode mismatch for control.checkgroups ... FWIW,

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-09-03 Thread Julien ÉLIE
Hi John, news@news:/var/lib/news$ /usr/lib/news/bin/ovdb_init ovdb_init: OVDB: can not open database unless ovdb_monitor is running Upon investigating things further, I noticed that /etc/news/inn.conf listed pathrun as /run/news, which doesn't exist. Wouldn't it help if the current log

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-08-30 Thread Russ Allbery
John Goerzen writes: > Hi Russ! It is good to visit with you again. Thanks for what you do > with inn. Julien does most of the work, but thank you! > So I should mention why I switched. I was getting lines like this in the > news.daily report: > innd: tradindexed: index inode mismatch for

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-08-28 Thread John Goerzen
On Sat, Aug 28 2021, Russ Allbery wrote: John Goerzen writes: Hi Russ! It is good to visit with you again. Thanks for what you do with inn. I run an INN site for an ISP waaay back and am now getting back into it. Given your good point about makehistory, I suspect the right answer

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-08-28 Thread Russ Allbery
John Goerzen writes: > 3) /run/news somehow gets created. > I notice that the debian/inn2.init file does do this. However, on > systemd systems, the debian/inn2.service file doesn't appear to. Also > in situations of needing to run makehistory and such, often innd will > have not been

Bug#993211: inn2: ovdb_monitor/server can't start due to missing /run/news

2021-08-28 Thread John Goerzen
Package: inn2 Version: 2.6.4-2 Severity: normal Hello, I was tracking down an odd problem with trying to get ovdb going: news@news:/var/lib/news$ /usr/lib/news/bin/ovdb_init ovdb_init: OVDB: can not open database unless ovdb_monitor is running ovdb_init: database is active ovdb_init: OVDB: can