sunfire 100 network interface not coming up

[itayemi]

Hi All, I have a sunfire 100 that comes up without setting up its 2 network interfaces -even lo doesnt come up
at the point where it is trying to configure the interfaces,
i just get the message ifconfig can not find /usr/lib/ld.so.1 killed repeated about 6 times or so.

Also I noticed the file .name_service_door in /etc - is it normal or has the system been hacked.

I finally was able to use the 2 commands
"ifconfig dmfe0 plumb" and "ifconfig dmfe0 89.0.1.101 netmask 255.255.255.0 up" to at least temporarily bring up the interface but then when I tried to telnet into it fromanothet box I got thrown out with the message "telnetd: could not grant slave pty."

Any ideas? Please help as the box hosts mail for about 60 domains and it is not up at the moment.

Regards,
Tunde I.

 

[AllenV]

Check your ld.so.1 file against a known good version - it sounds like this file was corrupted. With sun many of the base service files are statically linked, so they would not easily fail, but most files will rely on ld.so.1 - which would easily make your telnet fail.

It is not QUITE as deadly to a machine as redirecting over "sh" but it's close.

 

[itayemi]

Hi AllenV,

I finally fixed the box by putting the network config commands below into the /etc/rc2.d/S69inet file:
ifconfig lo0 plumb
ifconfig lo0 127.0.0.1 netmask 255.0.0.0 up
ifconfig dmfe0 plumb
ifconfig dmfe0 217.144.10.12 netmask 255.255.255.0 up
route add default 217.144.10.1

It worked. the ld.so.1 file seems OK. Also if it is corrupt, then I should think other commands such as cd, cp, mv etc that makes use of it should not work either?

Something else I noticed is that once the system comes up you can use the ifconfig commands without getting the error message above?

Also what is the meaning of "redirecting over "sh" " and why is it deadly to a machine?
Of course I would still like to fix the problem permanently rather than in the way I have done. Thanks a lot.

 

[AllenV]

It depends as statically linked versions of all of these files can be installed optionally. It's an installation choice.

You might note your Solaris version, mine (as a comparison) is a 2.6 installation on a very old SPARCServer 1000. If yours was the same, I would post the procedure that mine uses to plumb and configure it's interfaces. Namely - setting interface names indide "hostname.le0", "hostname.hme1" files. And making sure those hostnames are present in the /etc/hosts file (as they won't normally come up otherwise.

All in all - I'm guessing that something drastic changed if your system worked and then suddenly didn't.

Also - on Sun (and HP) certain updates and patches have been known to overwrite configuration files... sometimes important ones. Did you do anything like that recently?

On every system I configure, I create a directory called /var/CHANGES. In there I add a CHANGES.TXT file, and write down EVERY SINGLE thing I do to set up the system. I also keep a copy of any changed configuration file in that same directory. This way, when I need the information again in a year or two, I can review the things that I changed from system defaults.