Re: slrn broke after power failure

2022-04-20 Thread songbird
Charlie Gibbs wrote: > Thanks, everyone, for all your help. I think I might have found > the solution thanks to songbird: > > > then remove the zero length file and remove the .overview file > > for that group and see if you can then get that message again. > > i think a missing .overview file

Re: slrn broke after power failure

2022-04-19 Thread Charlie Gibbs
Thanks, everyone, for all your help. I think I might have found the solution thanks to songbird: > then remove the zero length file and remove the .overview file > for that group and see if you can then get that message again. > i think a missing .overview file should be regenerated every

Re: slrn broke after power failure

2022-04-19 Thread Tim Woodall
On Tue, 19 Apr 2022, Tim Woodall wrote: On Mon, 18 Apr 2022, Charlie Gibbs wrote: Again, my issue is not with the spool, but why slrn seems to be trying to bypass it and access the server directly. Unless that "server read failed" message is a red herring... So I got interested and went

Re: slrn broke after power failure

2022-04-19 Thread Tim Woodall
On Mon, 18 Apr 2022, Charlie Gibbs wrote: Again, my issue is not with the spool, but why slrn seems to be trying to bypass it and access the server directly. Unless that "server read failed" message is a red herring... So I got interested and went investigating and I confess that I have

Re: slrn broke after power failure

2022-04-19 Thread songbird
Curt wrote: > On 2022-04-18, Charlie Gibbs wrote: >> >> Again, my issue is not with the spool, but why slrn seems to >> be trying to bypass it and access the server directly. Unless >> that "server read failed" message is a red herring... >> > > > > slrn --debug FILE > > Then look in FILE for

Re: slrn broke after power failure

2022-04-19 Thread Curt
On 2022-04-18, Charlie Gibbs wrote: > > Again, my issue is not with the spool, but why slrn seems to > be trying to bypass it and access the server directly. Unless > that "server read failed" message is a red herring... > slrn --debug FILE Then look in FILE for possible edification.

Re: slrn broke after power failure

2022-04-18 Thread Charlie Gibbs
On Mon, 18 Apr 2022 02:50:01 +0200 songbird wrote: [description of .jnewsrc snipped] I've tried fiddling with .jnewsrc, but that doesn't seem to be the problem. I retrieve news with slrnpull, which retrieves articles and updates .jnewsrc accordingly. This has worked properly both before and

Re: slrn broke after power failure

2022-04-17 Thread songbird
Charlie Gibbs wrote: ... > The zero-length files were easy enough to find, and few enough > that I just deleted them by hand. No luck. I've even tried > deleting the entire contents of a group, e.g.: > > rm /var/spool/slrnpull/news/linux/debian/user/* > > Still no luck. The group header window

Re: slrn broke after power failure

2022-04-17 Thread Charlie Gibbs
On Sat, 16 Apr 2022 05:40:02 +0200 songbird wrote: ["Server read failed." when trying to enter a newsgroup] > i have four thoughts. > > first one would be to do a fsck on that file system (after > unmounting it). No joy > second one is to restore from backup or redownload articles > after

Re: slrn broke after power failure

2022-04-15 Thread songbird
Charlie Gibbs wrote: > Running Buster: > Linux cjglap2 4.19.0-20-amd64 #1 SMP Debian 4.19.235-1 (2022-03-17) > x86_64 GNU/Linux > > Today when I tried reading Usenet I ran into problems. I use slrnpull > to fetch news from a server - that part still works. When I run slrn to > read the news,

slrn broke after power failure

2022-04-15 Thread Charlie Gibbs
Running Buster: Linux cjglap2 4.19.0-20-amd64 #1 SMP Debian 4.19.235-1 (2022-03-17) x86_64 GNU/Linux Today when I tried reading Usenet I ran into problems. I use slrnpull to fetch news from a server - that part still works. When I run slrn to read the news, it comes up with the normal list