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 s
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 time
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 i
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
abs
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 po
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.
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 a
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 s
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
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, i
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
On Thu, Jul 19, 2018 at 12:47 PM Brad Rogers wrote:
> On Thu, 19 Jul 2018 18:14:19 +0200
> deloptes wrote:
>
> >why not use something more decent like ext3 or ext4? we are in 2018 ;-)
>
> (your smiley noted)
> Ken gave no indication of time-frame, other than in the past. Could've
> been last we
On Thu, Jul 19, 2018 at 06:45:16PM -0400, Felix Miata wrote:
Cheap is a relative term. It's only "cheap" if it's cheap enough for a
particular context to enjoy. Even if a HD was only a dollar a TB, it wouldn't be
cheap to someone with 0 dollars.
Well, you can't buy any storage with zero dollars
deloptes composed on 2018-07-20 00:00 (UTC+0200):
> Felix Miata wrote:
>> 1: /boot is functionally readonly except during kernel installation and
>> removal
> not really an argument - the system did not boot for this reason
>> 2: journals consume disk space
> not really an argument - the syste
Felix Miata wrote:
> 1: /boot is functionally readonly except during kernel installation and
> removal
>
not really an argument - the system did not boot for this reason
> 2: journals consume disk space
not really an argument - the system did not boot for this reason and space
in MBs is cheap
deloptes composed on 2018-07-19 18:14 (UTC+0200):
> why not use something more decent like ext3 or ext4? we are in 2018 ;-)
1: /boot is functionally readonly except during kernel installation and removal
2: journals consume disk space
I would be spending an enormous amount of time rescuing file
On Thu, 19 Jul 2018 18:14:19 +0200
deloptes wrote:
Hello deloptes,
>why not use something more decent like ext3 or ext4? we are in 2018 ;-)
(your smiley noted)
Ken gave no indication of time-frame, other than in the past. Could've
been last week, could've been twenty years ago.
--
Regards
Kenneth Parker wrote:
> My worst, was kind of "mild", though scary: I had to rebuild /boot (on
> ext2), because the last action was placing a copy of the Linux Kernel on
> /boot.
why not use something more decent like ext3 or ext4? we are in 2018 ;-)
regards
On Thu, Jul 19, 2018, 8:09 AM Brad Rogers wrote:
> On Thu, 19 Jul 2018 07:56:34 -0400
> Kenneth Parker wrote:
>
> Hello Kenneth,
>
> >My worst, was kind of "mild", though scary: I had to rebuild /boot (on
> >ext2), because the last action was placing a copy of the Linux Kernel on
> >/boot.
>
>
On Thu, 19 Jul 2018 07:56:34 -0400
Kenneth Parker wrote:
Hello Kenneth,
>My worst, was kind of "mild", though scary: I had to rebuild /boot (on
>ext2), because the last action was placing a copy of the Linux Kernel on
>/boot.
It was the fear of such an issue (an inability to boot) that finally
On Thu, Jul 19, 2018, 2:20 AM Brad Rogers wrote:
>
> Worst I had happen as a result of power failure was that disk the
> journal couldn't recover everything required, such that sector errors
> were reported on every boot. A reformat got around that. Tiresome, but
> no
her" operating system or
Worst I had happen as a result of power failure was that disk the
journal couldn't recover everything required, such that sector errors
were reported on every boot. A reformat got around that. Tiresome, but
not fatal.
I have had hardware get fried (a printer
Richard Hector wrote:
> On 02/03/18 03:09, Marc Auslander wrote:
>>> I think you can usually set the power-on behaviour in the BIOS (or EFI,
>>> presumably) - independently of the OS or any shutdown process.
>>>
>>> Richard
>> So here's the issue - maybe I'm missing something.
>>
>> If I configur
Richard Hector wrote:
> I confess I've never set up a ups for all this before, but I've read
> about it ... I'm pretty sure you can instruct the ups to shut down, but
> I don't know whether you can tell it to come back as soon as the power
> is stable (possibly immediately).
perhaps no, but I hav
On 02/03/18 03:09, Marc Auslander wrote:
>> I think you can usually set the power-on behaviour in the BIOS (or EFI,
>> presumably) - independently of the OS or any shutdown process.
>>
>> Richard
> So here's the issue - maybe I'm missing something.
>
> If I configure apcupsd to shutdown on power f
(Was Were is gapcmon?)
>>
>> I've always use apcupsd which still works in stretch. My use is pretty
>> trivial - just reports - I don't do anything automatic on power fail
>> since I can't figure out how to do anything that will always wind up
>> with my machine running when the power comes back!
In <4d49816b.1040...@alcor.concordia.ca>, David Gaudine wrote:
>I have one more question, just out of curiousity so bottom priority.
>Why does this work? mdadm.conf is in the initramfs which is in /boot
>which is on /dev/md0, but /dev/md0 doesn't exist until the arrays are
>assembled, which requir
On 11-01-31 8:47 PM, Andrew Reid wrote:
The easy way out is to boot from a rescue disk, fix the mdadm.conf
file, rebuild the initramfs, and reboot.
The Real Sysadmin way is to start the array by hand from inside
the initramfs. You want "mdadm -A /dev/md0" (or possibly
"mdadm -A -u") to s
rong choice.
>
> The cause of the problem is, I set up my system under a temporary hostname
> and then changed the hostname. The hostname appeared at the end of each
> ARRAY line in mdadm.conf, and I didn't know whether I should change it there
> because I didn't know if whet
t booted fine. I did the same thing on another
computer, and I'm sure I restarted that one successfully several times.
So, I foolishly thought I was safe. After the power failure it wouldn't
boot. After following your advice I was sufficiently inspired to edit
mdadm.conf back to the
Hello,
dav...@alcor.concordia.ca a écrit :
> My system went down because of a power failure, and now it won't start. I
> use RAID 1, and I don't know if that's related to the problem. The screen
> shows the following.
>
> Loading, please wait...
> Gave up
On Monday 31 January 2011 10:51:04 dav...@alcor.concordia.ca wrote:
> I posted in a panic and left out a lot of details. I'm using Squeeze, and
> set up the system about a month ago, so there have been some upgrades. I
> wonder if maybe the kernel or Grub was upgraded and I neglected to install
>
My system went down because of a power failure, and now it won't start. I
use RAID 1, and I don't know if that's related to the problem. The screen
shows the following.
Loading, please wait...
Gave up waiting for rood device. Common problems:
- Boot args (cat /proc/cmdline)
-
oc/modules
does show md_mod.
David
Original Message
Subject: Can't reboot after power failure (RAID problem?)
From:dav...@alcor.concordia.ca
Date:Mon, January 31, 2011 10:18 am
To: debian-u
On Fri, Dec 12, 2008 at 01:01:08PM +0800, rjubio wrote:
> I found a file in the /etc partition called nologin. I just removed it.
> Voila! I got connected.
The root problem really isn't solved. Who put the nologin file that
said powerfail (or whatever) there in the first place? What was its
tim
On Fri, Dec 12, 2008 at 12:55:25PM +0800, Rod James Bio wrote:
> Well that's a problem. I am using a Mac X server that doesnt have a VGA
> behind it. What I tried though was to unmount the harddisk manually and
> mount it on another X server that I have. I know that a lock file of some
> sort has t
I found a file in the /etc partition called nologin. I just removed it.
Voila! I got connected.
Thanks for the help
Jeff D wrote:
On Fri, 12 Dec 2008, rjubio wrote:
I am experiencing some kind of error regarding a recent power failure in our
campus.
When I try sshing to on of our server
35 PM, Jeff D wrote:
> On Fri, 12 Dec 2008, rjubio wrote:
>
> > I am experiencing some kind of error regarding a recent power failure in
> our
> > campus.
> >
> > When I try sshing to on of our server I get an error message:
> >
> > POWER FAILURE
> >
On Fri, 12 Dec 2008, rjubio wrote:
> I am experiencing some kind of error regarding a recent power failure in our
> campus.
>
> When I try sshing to on of our server I get an error message:
>
> POWER FAILURE
> then I get thrown back to the login prompt.
>
> Any su
I am experiencing some kind of error regarding a recent power failure in
our campus.
When I try sshing to on of our server I get an error message:
POWER FAILURE
then I get thrown back to the login prompt.
Any suggestions how to go on this.
Thanks!
ROD
--
To UNSUBSCRIBE, email to debian
On Wed, 14 Nov 2007 11:38:52 -0800, David Brodbeck wrote:
> On Nov 14, 2007, at 8:49 AM, Hendrik Boom wrote:
>> Would anyone be able to suggest what's failing, and what to do
>> about it?
>> Or what information I need to gather to diagnose the situation?
>
> Try transferring a file between apri
On Nov 14, 2007, at 8:49 AM, Hendrik Boom wrote:
Would anyone be able to suggest what's failing, and what to do
about it?
Or what information I need to gather to diagnose the situation?
Try transferring a file between april and the problem machines with
FTP. Both directions. Sometimes ne
On Wed, 14 Nov 2007 16:49:29 +, Hendrik Boom wrote:
> I have not changed any
> configurations or made any upgrades since they were all working yesterday.
I may not have made changes, but something has to be different. I'm
hoping someone can help me track down what has happened.
-- hendrik
\
Last night power went off for several hours.
In the morning there appeared to be no network communication between
machines on my LAN when I booted them. A bit of experimentation localized
it to one particular ethernet hub (two of the machines did not need that
hub to communicate with each other,
haoniukun wrote:
I have a create SB 5.1 soundcard with the chip emu10k1x.
The soundcard worked excellently for me before the power failure.
But after a power failure this afternoon, it doesn't work for me.:(
Message at the boot time indicates that alsa fail to initialize with error cod
Dear all debian users,
I have a create SB 5.1 soundcard with the chip emu10k1x.
The soundcard worked excellently for me before the power failure.
But after a power failure this afternoon, it doesn't work for me.:(
Message at the boot time indicates that alsa fail to initialize with
Guillaume TESSIER wrote:
"power failure during upgrade"
Damn...
Actually, it was faulty hardware. My fault entirely.
Maybe while being disapointed and sending all damnation on the power
plant, you forgot to modify your sources.lists
No. I shouldn't have to touch the
Joe Mc Cool wrote:
in order to upgrade from woody to sarge I did:
apt-get update
apt-get dist-upgrade
off it went, but unfortunately I had a power failure during the
upgrade and my system got hosed. (I repeated the above steps, but my
system would then boot only with a ro root
in order to upgrade from woody to sarge I did:
apt-get update
apt-get dist-upgrade
off it went, but unfortunately I had a power failure during the upgrade
and my system got hosed. (I repeated the above steps, but my system
would then boot only with a ro root filesystem.)
So, coward
Fred Sloniker wrote:
Hey, everybody. First-time Linux user here (well, sort of; I've struggled before with getting either Debian or SuSE installed, unsuccessfully). So far, I like what I've seen of Debian (mostly installation screens and documentation); not only do I like the actual freeness o
Please turn your line wraps on to 72 columns, your paragraphs are
coming through as one giant line each.
On Wed, Nov 27, 2002 at 11:08:49AM -0800, Fred Sloniker wrote:
> I know that powering the system off manually is a Bad Thing (tm),
> but I live in Cowville, so a black-out is always a possibil
Fred Sloniker wrote:
Hey, everybody. First-time Linux user here (well, sort of; I've struggled
before with getting either Debian or SuSE installed, unsuccessfully). So far,
I like what I've seen of Debian (mostly installation screens and documentation);
not only do I like the actual freeness of
"Timmo" <[EMAIL PROTECTED]> writes:
> About 2 years ago, the last time I tried to get linux off the ground, I had
> an accidental power interruption and the box was totally hosed from it.
>
> I've had one occur recently, and the file system checker did it's thing but
> things were never quite righ
John M Flinchbaugh said:
> on the subject of journalled filesystems. i've been using reiserfs. i've
> noticed that invariably, some files will get corrupted,
> especially logs. they end up looking like 2 files spliced together.
what kernel and what version of resier? any software raid?
I've had
on the subject of journalled filesystems. i've been using reiserfs.
i've noticed that invariably, some files will get corrupted,
especially logs. they end up looking like 2 files spliced together.
anytime inn doesn't get to shutdown properly, i end up having to
rebuild all its history db's, etc,
Timmo said:
> So I'm also very curious about what happens, aside from the file system
> which seems to be able to fix itself.
this entirely depends on how the system lost power. If the system
lost power in a clean way, that being something such as a UPS cut
the power(e.g. going from 110V to 0V in
Fred Sloniker said:
> my attempts to educate her on computer no-nos. What do I need to do, if
> anything, to make sure my hard drive isn't hosed after a power-off? Is
> there an equivalent to the Windows Scandisk-after-crash thing?
there is nothing you can do to be sure a filesystem that is mou
About 2 years ago, the last time I tried to get linux off the ground, I had
an accidental power interruption and the box was totally hosed from it.
I've had one occur recently, and the file system checker did it's thing but
things were never quite right again. I ended up deleting and recreating
e
On Wed, Nov 27, 2002 at 11:08:49AM -0800, Fred Sloniker wrote:
> I know that powering the system off manually is a Bad Thing (tm), but
> I live in Cowville, so a black-out is always a possibility. It's also
> possible that my mom would turn the computer off out of ignorance,
> despite my attempts
Fred Sloniker wrote:
Hey, everybody. First-time Linux user here (well, sort of; I've struggled before with getting either Debian or SuSE installed, unsuccessfully). So far, I like what I've seen of Debian (mostly installation screens and documentation); not only do I like the actual freeness of
o:[EMAIL PROTECTED]]
Sent: Wednesday, November 27, 2002 11:09 AM
To: [EMAIL PROTECTED]
Subject: What should I do after a power failure?
Hey, everybody. First-time Linux user here (well, sort of; I've struggled
before with getting either Debian or SuSE installed, unsuccessfully). So
far, I
Hey, everybody. First-time Linux user here (well, sort of; I've struggled before with
getting either Debian or SuSE installed, unsuccessfully). So far, I like what I've
seen of Debian (mostly installation screens and documentation); not only do I like the
actual freeness of it (SuSE, for insta
]> wrote:
> "Michael K. O'Brien" wrote:
> >
> > Hola~
> >
> > After a power failure, my network did not come
> back. The network driver loads,
> > but ifconfig isn't really happy:
> >
> > % ifconfig lo 127.0.0.1
> >
Nate Amsden wrote:
>
> "Michael K. O'Brien" wrote:
> >
> > Hola~
> >
> > After a power failure, my network did not come back. The network driver
> > loads,
> > but ifconfig isn't really happy:
> >
> > % ifconfig lo 1
"Michael K. O'Brien" wrote:
>
> Hola~
>
> After a power failure, my network did not come back. The network driver loads,
> but ifconfig isn't really happy:
>
> % ifconfig lo 127.0.0.1
> SIOCSIFADDR: Bad file descriptor
>
> ifconfig
Hola~
After a power failure, my network did not come back. The network driver loads,
but ifconfig isn't really happy:
% ifconfig lo 127.0.0.1
SIOCSIFADDR: Bad file descriptor
ifconfig to eth0 returns the same error.
Also, I'm getting "neighbour table overflow" mess
Will Trillich wrote:
> restricting queries is kinda goofy for an internet nameserver, huh?
yes it can be :)
> thanks for your response. good thing my isp is acting as secondary
> nameserver... your stuff is getting through, and visitors are finding
> my websites...
my stuff wouldn't of gotten t
On Wed, Aug 23, 2000 at 11:31:10AM -0700, Nate Amsden wrote:
> Will Trillich wrote:
> > [i've got debian 2.2/potato running as a router/ipmasq/firewall
> > box for my home intranet, with named 8.2.2-P5-NOESW]
> >
> > unapproved query from [207.63.39.40].1671 for "serensoft.com"
> >
Will Trillich wrote:
> [i've got debian 2.2/potato running as a router/ipmasq/firewall
> box for my home intranet, with named 8.2.2-P5-NOESW]
>
> unapproved query from [207.63.39.40].1671 for "serensoft.com"
> unapproved query from [198.69.131.5].1648 for "serensoft.com"
>
short version:
of all TM, which Fing one should i go R?
long version:
lost power for about two hours last night, and now i'm
getting some odd 'named' log entries...
even after finding
man named.conf
i'm still in the dark (metaphorically, tho the power is back on :)...
[i've got debian 2.
Hi Didi,
I did exactly as you suggest except I added the ipfwadm commands to
/etc/init.d/network itself. I love seeing my linux box get up over 100 days
without needing a reboot so it was with some misgivings I simulated a power
failure. All worked a treat.
Thank you!
Patrick
> -Origi
Patrick Kirk [EMAIL PROTECTED] wrote:
> Hi all,
>
> A fuse blew last night taking out the power supply to the server with my new
> debian linux installation.:-(
>
> On reboot this morning, the second NIC wasn't present so I had to modprobe
> /lib/...tulip.o, then ifconfig eth1, then route add, th
Hi all,
A fuse blew last night taking out the power supply to the server with my new
debian linux installation.:-(
On reboot this morning, the second NIC wasn't present so I had to modprobe
/lib/...tulip.o, then ifconfig eth1, then route add, then ipfwadm -F -p deny
and finally ipfwadm -F -a m -S
Joe Chung wrote:
> I came home yesterday and found out my debian machine had been rebooted
> around noon for the first time in a long time. My wife denied everything, so
> [snip] ^
Am I to understand that you allow your wife physical
I came home yesterday and found out my debian machine had been rebooted
around noon for the first time in a long time. My wife denied everything, so
I figured it was a power blackout or brownout that caused it, but nothing in
/var/log tells me that the file systems were not unmounted cleanly. How d
75 matches
Mail list logo
