SAM crashed

[dictum9]

I am telneting to this 4640 running 11.23 box via remote console and I was trying to run sam to configure some networks. Well, sam is timing out, it's not displaying anything and has apparently crashed. I cannot get back the prompt, it's just hanging there.
Since I don't have networking enabled, I cannot telnet to the box and kill -9 this bad process. SAM has been down for 12 minutes thus far with no sign of coming back, or releasing the prompt.
Surely I am not expected to do control-b and resetting the box? I can afford to do that at this point, but still...


Interesting. I've never seen SAM crash, let alone deny access to the prompt.
I wonder if it has something to do with me setting the TERM incorrectly (I think I chose vt100)

[Torsten. · Accepted solution]

You wrote:

"...telneting to this [rx]4640 ... configure some networks..."

Are you sure you doesn't disable the NIC you are connected to? I guess you did.

Better to connect to the MP and configure network from there.

[Steven E. Protter]

Shalom etc

Sam has proven over the years to be really bad at configuring networks.

I've had it create duplicate /etc/hosts entries, disabling networking on the whole box.

That was about 9 years ago, when I stopped using it for networking. Now I barely use it.

any number of things could have happened, including sam actually crashing and you needing the latest sam patch.

If the box is still accessible on the network and services are running you may be able to get away with doing nothing.

But you seem to report the box is a brick now anyway, so why not ctrl-b and reset the box.

I think you may need to boot into single user mode and clean up the /etc/hosts and /etc/rc.config.d/netconf files

Time to wean yourself from sam maybe.

Good Luck.

SEP

[Torsten.]

Regarding the TERM settings - this depends on your terminal emulation program. The telnet of win is worst.
But in this case just try TAB key - might help.

[dictum9]

Weird, I never actually got to the point of doing anything with it. The last thing I remember, I went into the "NIC" section, and from that point on, the screen got blank and stayed so for 10-15 minutes until I reset the whole box. Luckily, I can afford to play with it like that now.

I never used sam before for anything and this reaffirms my thinking. I will look at its logs to try to figure out what happened.