Unkillable process

Snv_92 has been entertaining me since I upgraded from quite stable snv_88. I’m hitting a bug after a bug. (See here).

This is the latest – unkillable process, which can’t be killed with kill -9 or zone reboot. Reboot just hangs. Truss ends up with:

xeon# kill -9 22131
xeon# ps -ef | fgrep 22131
root 22728 5471 0 00:49:27 pts/5 0:00 fgrep 22131
alekz 22131 1 0 20:48:30 zoneconsole 0:03 /opt/sfw/lib/firefox/firefox-bin -P Sun –no-remote
xeon# truss -p 22131
^Ctruss: unanticipated system error: 22131

dtrace shows nothing. The only workaround is to reboot the entire system.

See also:

Revenge of the unkillable process
Unkillable process
Bug ID 6455727

3 thoughts on “Unkillable process”

  1. Actually, it’s getting worse. snv_123, snv_125 still have the same problem. It’s mostly firefox in the global zone, but once it was squid in a non-global zone.

    init 6 or reboot simply hang the system.

    The unkillable processes do not load CPU, but apparently still take memory:

    PID USERNAME NLWP PRI NICE SIZE RES STATE TIME CPU COMMAND
    9107 alekz 2 57 4 1147M 912M sleep 248:03 0.00% firefox-bin

Leave a Reply

Your email address will not be published.