NetWorker crashing a Sun box

[chuckster43]

Has anyone ever heard of the NetWorker daemons crashing a SunFire box? I don't believe it could have, however I need some back up info before going before a client to let them know that bringing their system backup after the in-house engineers couldn't accomplish a console login and fix the box, that they would probably get charged for the call.

Any thoughts?

Thanks,

 

[TDun]

Not familiar with the SunFire box. If it is Unix, then you should have a dump from thecrash.
If you look at that, it will tell you what caused the crash.

If it did not take the whole system down, it may have failed and left a core fiel behind (called either core or core.xxxx, where xxxx is the pid of the failed process).
Do a search for core* on the system and check dates/times against the failure. If you find one at the right time, look at it (do a man core to find the right tool) to identify the process.

 

[605]

You may also check the file /var/adm/messages .

 

[andrew1011]

We had something that might be similar with our install of Legato 6.1.2 on a SUN V880 (SunFire) with Solaris 9. The problem was not really with the box crashing. Legato by default logs to console... so if your console's buffer gets overflowed with data... it will prevent the users from doing an su - root or login as root from anywhere. Sometimes the box will hang. The solution is to edit your syslog.conf so that it does not log to /dev/console.... just point it to either messages or a log file somewhere.

 

[chuckster43]

Many thanks for the inputs. Upon research, it was discovered that the client had a share mounted from one system to another and when the client's engineer kicked the power cord from the one server it of course corrupted the filesystem on the other bringing down both servers. So, this was not a Legato issue, but a bigfoot issue.
Again, thanks for the help.