Re: A Debian Lenny machine declined to work
Jari Fredriksson
On 22.11.2009 22:09, Jari Fredriksson wrote:
> It boots, finds the hard disk, and loads stuff. Last stuff it prints on
> screen is usual boot stuff, and in addition to that Arno's Firewall
> output. I think that is normally printed to screen console. All logging
> should be logged via syslog to my main server, but nothing happends now.
>
I think that is normally *NOT* printed to screen console.
Q: What is purple and concord the world?
A: Alexander the Grape.
Jari Fredriksson
I write this to here, while it is probable that no one will have any ideas.
I had a Lenny PC as my router to internet, having 2 NICs and an ADSL
modem in bridged mode in one, and another in my switch.
Suddenly my network died, and when I rebooted the router this happened.
It boots, finds the hard disk, and loads stuff. Last stuff it prints on
screen is usual boot stuff, and in addition to that Arno's Firewall
output. I think that is normally printed to screen console. All logging
should be logged via syslog to my main server, but nothing happends now.
The console does not show login prompt, and the machine seems to be dead
or otherwise dead after the boot. It does not route network, and does
not allow me to log in and study logs.
If only the NIC was broken it should allow me to log in from console, right?
What might cause this? It boots but not fully. No error messages in
console. It just does not do anything useful.
Good news. Ten weeks from Friday will be a pretty good day.
Andrew Sackville-West
[..]
>
> It boots, finds the hard disk, and loads stuff. Last stuff it prints on
> screen is usual boot stuff, and in addition to that Arno's Firewall
> output. I think that is normally printed to screen console. All logging
> should be logged via syslog to my main server, but nothing happends now.
>
> The console does not show login prompt, and the machine seems to be dead
> or otherwise dead after the boot. It does not route network, and does
> not allow me to log in and study logs.
does it respond to pings? can you ssh in?
have you tried booting into single-user mode?
is it locked up hard or does the keyboard (capslock, numlock) respond?
Any response from the magic Alt-SysRq?
>
> If only the NIC was broken it should allow me to log in from
> console, right?
if it previously allowed console login, I would assume it would
continue to do so unless, in general.
>
> What might cause this? It boots but not fully. No error messages in
> console. It just does not do anything useful.
if it is locked hard that would point to some hardware problem,
otherwise I would look for recent updates for a clue. Some boot
process is failing to terminate.
A
Jari Fredriksson
On 22.11.2009 23:14, Andrew Sackville-West wrote:
> On Sun, Nov 22, 2009 at 10:09:55PM +0200, Jari Fredriksson wrote:
>
> [..]
>
>>
>> It boots, finds the hard disk, and loads stuff. Last stuff it prints on
>> screen is usual boot stuff, and in addition to that Arno's Firewall
>> output. I think that is normally printed to screen console. All logging
>> should be logged via syslog to my main server, but nothing happends now.
>>
>> The console does not show login prompt, and the machine seems to be dead
>> or otherwise dead after the boot. It does not route network, and does
>> not allow me to log in and study logs.
>
> does it respond to pings? can you ssh in?
No, ping says "no route to ..."
>
> have you tried booting into single-user mode?
Yes, same issue. No login prompt or anything.
>
> is it locked up hard or does the keyboard (capslock, numlock) respond?
> Any response from the magic Alt-SysRq?
I have not tried those. But Ctrl-Alt-Del does not do anything, that I
tested. Dead meat.
>
>
>
>>
>> If only the NIC was broken it should allow me to log in from
>> console, right?
>
> if it previously allowed console login, I would assume it would
> continue to do so unless, in general.
>
>>
>> What might cause this? It boots but not fully. No error messages in
>> console. It just does not do anything useful.
>
> if it is locked hard that would point to some hardware problem,
> otherwise I would look for recent updates for a clue. Some boot
> process is failing to terminate.
>
I believe it is a hardware problem. But still disk works, it loads
scripts from /etc/init.d. At least /etc/init.d/arno-firewall as it
printes the output to console.
Strange.
Stop! There was first a game of blindman's buff. Of course there was.
And I no more believe Topper was really blind than I believe he had eyes
in his boots. My opinion is, that it was a done thing between him and
Scrooge's nephew; and that the Ghost of Christmas Present knew it. The
way he went after that plump sister in the lace tucker, was an outrage
on the credulity of human nature.
Stan Hoeppner
> I believe it is a hardware problem. But still disk works, it loads
> scripts from /etc/init.d. At least /etc/init.d/arno-firewall as it
> printes the output to console.
>
> Strange.
A corrupt filesystem can cause a hard lock on boot as well. Please
provide the last dozen lines or so on the screen. That may help
immensely in troubleshooting this problem.
--
Stan
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jari Fredriksson
On 23.11.2009 5:50, Jari Fredriksson wrote:
>
>
> On 22.11.2009 23:34, Stan Hoeppner wrote:
>> Jari Fredriksson put forth on 11/22/2009 3:27 PM:
>>
>>> I believe it is a hardware problem. But still disk works, it loads
>>> scripts from /etc/init.d. At least /etc/init.d/arno-firewall as it
>>> printes the output to console.
>>>
>>> Strange.
>>
>> A corrupt filesystem can cause a hard lock on boot as well. Please
>> provide the last dozen lines or so on the screen. That may help
>> immensely in troubleshooting this problem.
>>
>
> Thanks... But that is hard to provide, as I can't ssh into it. Had to
> copy those info by hand from another monitor.
>
> I got my net working by switchin the modem to routing mode with NAT and
> setting its IP to the address of the Linux router.
>
> Have to work on that machine later... I lost my firewall, as well as
> amavisd-new (with ClamAV, F-Prot and BitDefender), they were working on
> that machine, can can't setup those on any other machine (inefficient RAM..)
>
I'll propably boot that machine with a Knoppix CD, and try to check the
disks. And find logs..
... A solemn, unsmiling, sanctimonious old iceberg who looked like he
was waiting for a vacancy in the Trinity.
-- Mark Twain
Jari Fredriksson
On 22.11.2009 23:34, Stan Hoeppner wrote:
> Jari Fredriksson put forth on 11/22/2009 3:27 PM:
>
>> I believe it is a hardware problem. But still disk works, it loads
>> scripts from /etc/init.d. At least /etc/init.d/arno-firewall as it
>> printes the output to console.
>>
>> Strange.
>
> A corrupt filesystem can cause a hard lock on boot as well. Please
> provide the last dozen lines or so on the screen. That may help
> immensely in troubleshooting this problem.
>
Thanks... But that is hard to provide, as I can't ssh into it. Had to
copy those info by hand from another monitor.
I got my net working by switchin the modem to routing mode with NAT and
setting its IP to the address of the Linux router.
Have to work on that machine later... I lost my firewall, as well as
amavisd-new (with ClamAV, F-Prot and BitDefender), they were working on
that machine, can can't setup those on any other machine (inefficient RAM..)
--
Jari Fredriksson
On 23.11.2009 5:52, Jari Fredriksson wrote:
>
>
> On 23.11.2009 5:50, Jari Fredriksson wrote:
>>
>>
>> On 22.11.2009 23:34, Stan Hoeppner wrote:
>>> Jari Fredriksson put forth on 11/22/2009 3:27 PM:
>>>
>>>> I believe it is a hardware problem. But still disk works, it loads
>>>> scripts from /etc/init.d. At least /etc/init.d/arno-firewall as it
>>>> printes the output to console.
>>>>
>>>> Strange.
>>>
>>> A corrupt filesystem can cause a hard lock on boot as well. Please
>>> provide the last dozen lines or so on the screen. That may help
>>> immensely in troubleshooting this problem.
>>>
>>
>> Thanks... But that is hard to provide, as I can't ssh into it. Had to
>> copy those info by hand from another monitor.
>>
>> I got my net working by switchin the modem to routing mode with NAT and
>> setting its IP to the address of the Linux router.
>>
>> Have to work on that machine later... I lost my firewall, as well as
>> amavisd-new (with ClamAV, F-Prot and BitDefender), they were working on
>> that machine, can can't setup those on any other machine (inefficient RAM..)
>>
>
> I'll propably boot that machine with a Knoppix CD, and try to check the
> disks. And find logs..
>
RESOLVED! :/
It booted fine from a Knoppix CD, and everything looked good. The
problem was my late editing of an init script, which went waiting input
from user (a typo). Pressing Ctrl-C continued and finally I found the
bug in the script.
Q: "What is the burning question on the mind of every dyslexic
existentialist?"
A: "Is there a dog?"