from the irlp status page
Current Node Status: Unknown for 0 days, 1 hours, 49 minutes, 51 seconds
troubleshhot-irlp gives me some wired errors
DNS not set corectly
ports 2074 through 2090 not forwared ( in DMZ zone)
Pots 073 8873 1000 15425 15426 15427 not forwared again in DMZ zone
Running Centos 5.7 (from the IRLP dl server)
I hope this helps figure out why this is going on

I am going to guess at this one, and say that your hard drive is full. If this error comes up, it means the node you are trying to call does not have a key in the keyring. If the keyring is corrupted because of lack of space, it will cause this error.

I can't think of anything else that would come up and cause that error.

After reading the email again, it sounds like it is not even connected to the internet. When you are logged in and try to run a command like:

ping irlp.net

what kind of reply do you get?

Dave Cameron



--- In irlp@yahoogroups.com, "Richard s" <va3rzs2@> wrote:

the PGP sec (key or filefile is being updated please try later

is the message I get when I try to dial out

thats after I log in and type reboot

before that every connection times out and no one can call into me ..
thought it was a router problem but node is in the DMZ right now

I did have to get a new PGP key over 6 months ago when the node went down and my back up was bad

HELP please

this is such a pain after running for years with no problems and now its one thing after another

Thanks for any and all help to get node 2120 back up and running !

Rick-va3rzs

are u using a netgear router?
ka3vgm

the PGP sec (key or filefile is being updated please try later

is the message I get when I try to dial out

thats after I log in and type reboot

before that every connection times out and no one can call into me ..
thought it was a router problem but node is in the DMZ right now

I did have to get a new PGP key over 6 months ago when the node went down and my back up was bad

HELP please

this is such a pain after running for years with no problems and now its one thing after another

Thanks for any and all help to get node 2120 back up and running !

Rick-va3rzs

Sorry, I don't recall the error exactly. No help, I know.... As I
recall, as it was read to me, said invallid boot option and then 00
00/1b0. I should have had my cousin write it down exactly but he was in
a hurry and I figured if I restored an image, things would be o.k.
Image was from old system, so yes, I may have just restored the error.
Is there any way I can log this or run it over the network so I can tell
what is going on?
Thanks.
73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Wed, 11 Jan 2012, John wrote:

Butch wrote

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

--->>>
Need to know what scandisk reports. Can "shutdown -F -r now"
be told to write a log file..DaveC & DaveG ??
WHAT was that 'invalid boot option error' ?
Which image did you restore? The one from the old machine?
That would have had incorrect data, including any cron job errors.

"I can't log in once it locks up. It isn't seen on the network, nor does
it respond to dtmf codes. All I can do is power down and reboot."

-->>>
These are the same symptoms I had with a flaky HD 2 years ago.

73 John
6163

My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive.

Maybe a newbie question can help ;-)

Isn't that the time the node is supposed to shutdown and update. Then
comes back on 1 hour later?

Honestly, I dont even think about my node at 4am! Maybe you should sleep
through it instead <grin>.

73/Phillip/N8AYE
-. ---.. .- -.-- .
node: 3538

John said the following on 1/10/2012 4:19 PM:

Butch wrote

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

--->>>

Butch wrote

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

--->>>
Need to know what scandisk reports. Can "shutdown -F -r now"
be told to write a log file..DaveC & DaveG ??
WHAT was that 'invalid boot option error' ?
Which image did you restore? The one from the old machine?
That would have had incorrect data, including any cron job errors.

"I can't log in once it locks up. It isn't seen on the network, nor does
it respond to dtmf codes. All I can do is power down and reboot."

-->>>
These are the same symptoms I had with a flaky HD 2 years ago.

73 John
6163

Did you run troubleshoot-irlp? If not, do that and tell us what it reports.

su - repeater
troubleshoot-irlp

-k9dc

On Jan 10, 2012, at 2:48 PM, Richard s wrote:

the PGP sec (key or filefile is being updated please try later

is the message I get when I try to dial out

thats after I log in and type reboot

before that every connection times out and no one can call into me ..
thought it was a router problem but node is in the DMZ right now

I did have to get a new PGP key over 6 months ago when the node went down and my back up was bad

HELP please

this is such a pain after running for years with no problems and now its one thing after another

Thanks for any and all help to get node 2120 back up and running !

Rick-va3rzs

Yes, this is the drive I transplanted as the other pc wouldn't boot. I
can do that eventually, but will have to get sighted help and I'll lose
a lot of custom stuff I have such as pine. I was hoping someone could
take a look and see what program is crashing the system as it is the
exact same time each day.

Thanks.
73
Butch
WA0VJR
Node 3148
Wallace, ks.


BTW, it is fc3 if that matters.

On Tue, 10 Jan 2012, ve7ltd wrote:

Is this the drive you took from another PC and transplanted?

I would suggest that there is something with this hardware that the configuration from the old PC does not like. In theory, this should work, but not always.

I think your best course of action is to create a backup of your node, and reinstall fresh with CentOS 4 on this PC.

Dave

--- In irlp@yahoogroups.com, Butch Bussen <butchb@> wrote:

As I mentioned before, when it locks up, I have no access over the
network. It locked up again at four again this morning. Here is from
my messages file. Aparently when it locks up, doesn't write anything to
messages.

Any help or suggestions appreciated. If someone wants to take a look, I
can send password and port. Here is from my messages file.

Jan 9 22:13:24 localhost sysctl: kernel.sysrq = 0
Jan 9 22:13:24 localhost sysctl: kernel.core_uses_pid = 1
Jan 9 22:13:24 localhost rc.sysinit: Configuring kernel parameters:
succeeded
Jan 10 05:13:24 localhost date: Tue Jan 10 05:13:24 MST 2012
Jan 10 05:13:24 localhost rc.sysinit: Setting clock (localtime): Tue
Jan 10 05:13:24 MST 2012 succeeded
Jan 10 05:13:24 localhost rc.sysinit: Loading default keymap succeeded
Jan 10 05:13:24 localhost rc.sysinit: Setting hostname
localhost.localdomain: succeeded

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On
Mon, 9 Jan
2012, ve7ltd wrote:

Since the computer seems to be sort of "soft locking" (you can still communicate with it through the network), it may be logging the problems in

/var/log/messages

The contents of the folder

/etc/cron.daily/

are also run around that time every day.

Dave

--- In irlp@yahoogroups.com, Butch Bussen <butchb@> wrote:

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Fri, 6 Jan 2012, John wrote:

Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:

I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four

mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.

the PGP sec (key or filefile is being updated please try later

is the message I get when I try to dial out

thats after I log in and type reboot

before that every connection times out and no one can call into me ..
thought it was a router problem but node is in the DMZ right now

I did have to get a new PGP key over 6 months ago when the node went down and my back up was bad

HELP please

this is such a pain after running for years with no problems and now its one thing after another

Thanks for any and all help to get node 2120 back up and running !

Rick-va3rzs

Is this the drive you took from another PC and transplanted?

I would suggest that there is something with this hardware that the configuration from the old PC does not like. In theory, this should work, but not always.

I think your best course of action is to create a backup of your node, and reinstall fresh with CentOS 4 on this PC.

Dave

--- In irlp@yahoogroups.com, Butch Bussen <butchb@...> wrote:

As I mentioned before, when it locks up, I have no access over the
network. It locked up again at four again this morning. Here is from
my messages file. Aparently when it locks up, doesn't write anything to
messages.

Any help or suggestions appreciated. If someone wants to take a look, I
can send password and port. Here is from my messages file.

Jan 9 22:13:24 localhost sysctl: kernel.sysrq = 0
Jan 9 22:13:24 localhost sysctl: kernel.core_uses_pid = 1
Jan 9 22:13:24 localhost rc.sysinit: Configuring kernel parameters:
succeeded
Jan 10 05:13:24 localhost date: Tue Jan 10 05:13:24 MST 2012
Jan 10 05:13:24 localhost rc.sysinit: Setting clock (localtime): Tue
Jan 10 05:13:24 MST 2012 succeeded
Jan 10 05:13:24 localhost rc.sysinit: Loading default keymap succeeded
Jan 10 05:13:24 localhost rc.sysinit: Setting hostname
localhost.localdomain: succeeded

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On
Mon, 9 Jan
2012, ve7ltd wrote:

Since the computer seems to be sort of "soft locking" (you can still communicate with it through the network), it may be logging the problems in

/var/log/messages

The contents of the folder

/etc/cron.daily/

are also run around that time every day.

Dave

--- In irlp@yahoogroups.com, Butch Bussen <butchb@> wrote:

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Fri, 6 Jan 2012, John wrote:

Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:

I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four

mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.

As I mentioned before, when it locks up, I have no access over the
network. It locked up again at four again this morning. Here is from
my messages file. Aparently when it locks up, doesn't write anything to
messages.

Any help or suggestions appreciated. If someone wants to take a look, I
can send password and port. Here is from my messages file.

Jan 9 22:13:24 localhost sysctl: kernel.sysrq = 0
Jan 9 22:13:24 localhost sysctl: kernel.core_uses_pid = 1
Jan 9 22:13:24 localhost rc.sysinit: Configuring kernel parameters:
succeeded
Jan 10 05:13:24 localhost date: Tue Jan 10 05:13:24 MST 2012
Jan 10 05:13:24 localhost rc.sysinit: Setting clock (localtime): Tue
Jan 10 05:13:24 MST 2012 succeeded
Jan 10 05:13:24 localhost rc.sysinit: Loading default keymap succeeded
Jan 10 05:13:24 localhost rc.sysinit: Setting hostname
localhost.localdomain: succeeded

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On
Mon, 9 Jan
2012, ve7ltd wrote:

Since the computer seems to be sort of "soft locking" (you can still communicate with it through the network), it may be logging the problems in

/var/log/messages

The contents of the folder

/etc/cron.daily/

are also run around that time every day.

Dave

--- In irlp@yahoogroups.com, Butch Bussen <butchb@> wrote:

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Fri, 6 Jan 2012, John wrote:

Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:

I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four

mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.

Since the computer seems to be sort of "soft locking" (you can still communicate with it through the network), it may be logging the problems in

/var/log/messages

The contents of the folder

/etc/cron.daily/

are also run around that time every day.

Dave

--- In irlp@yahoogroups.com, Butch Bussen <butchb@...> wrote:

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Fri, 6 Jan 2012, John wrote:

Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:

I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four

mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.