Link to home
Create AccountLog in
Avatar of rdashokraj
rdashokraj

asked on

Many commands aren't working in Solaris 5.9

Hello,

We've a Solaris 5.9 machine running in production. All of a sudden, many of the commands are stopped working but few commands like uname, ps, pwd, prtconf are working.
Whenever I execute commands like ls, cp, swap...it throws the error "Illegal Instruction" and whenever I execute commands like metastat, bash, env...it says "cannot execute"  and when i execute "format", it says "Killed".

Not sure what has happened. Please let me know how to fix this issue.

Thanks,
Ash
 

$ su - root
su: u\242\372\200^G\201$^A^B^B^Q\3648P^_\3038P^_\303H]^YF^L^_\347^]f\260: execute permission denied
su: ^C_^B^Bu\242\373\200^G\201$^A^B^B^R\3528P^_\3038P^_\303H]^YF^L^_\347^]f\270: execute permission denied
su: 3~\252\251^B^Bu\242\372\200\200^G\201$^A^B^B^O\3608P^_\3038P^_\303H]^YF^L^_\347^]f\254^HF: execute permission denied
su: syntax error at line 3: `m_\207\205^B^Bu\242\373\200\200^G\201$^A^B^B^Q\3678P^_\3038P^_\303H]^YF^L^_\347^]g\360' unexpected
$

Open in new window

Avatar of rdashokraj
rdashokraj

ASKER

Some examples:

$ prtconf | grep Mem
Memory size: 4096 Megabytes
$ bash
ksh: bash: cannot execute
$ metastat
ksh: metastat: cannot execute
$ ls
Illegal Instruction
$ mount
Illegal Instruction
$ echo | format
ksh: 25886 Killed
$ format
Killed
$ echo $PATH
/usr/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/ccs/bin:/usr/ucb:/usr/share/bin:/usr/openwin/bin:/usr/dt/bin
$ ls -l
Illegal Instruction
$ pwd
/etc/init.d
$ vi
vi: syntax error at line 1: `\254\261\267\274\301\307\314\322' unexpected
Avatar of rindi
What happens when you boot the System? Do you get any errors when the system wants to load the file systems / partitions? Have you tried a filesystem repair?
SOLUTION
Avatar of Tintin
Tintin

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
I can't reboot the server easily since it is a production box. Just wondering whether the server reboot would certainly fix the problem?
If you are getting errors like you described, your production box is in a very, very sick state and I would recommend rebooting immediately, as you may find whatever app is running on the box will not be running very well.

A wild guess.. Do you run sudo?
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.