Some quick Solaris 10 Fault Manager Daemon notes

fmd - fault manager daemon commands:

# Display current faults:
fmdump faulty

# View fault files:
fmdump

# View error log files:
fmdump -e

# View previous log file:
fmdump /var/fmd/fmd/errlog.1

# Rotate log files - you may have to stop and start fmd if the process is
# too busy to rotate the files. This could be a catch 22, the fmd process
# must be running to rotate the files.

# Rotate error log files:
fmadm rotate errlog

# Rotate fault log files:
fmadm rotate fltlog

# Log files:
/var/fm/fmd
root@yourbox# ll
root sys 3 dir rwx------ 512 16:32:06 06/25/2009 ckpt
root root 1 file rw-r--r-- 44,427,432 12:55:28 11/18/2009 errlog
root root 1 file rw-r--r-- 1,774,698 12:05:24 11/18/2009 fltlog
root sys 2 dir rwx------ 512 12:05:24 11/18/2009 rsrc
root sys 2 dir rwx------ 512 09:24:38 06/24/2008 xprt
There are 5 items and 46.20MB (46,203,666 bytes) in /var/fm/fmd

# View fmd processes:
root@yourbox# ps -ef | grep fmd
root 9042 1 0 12:03:30 ? 2:25 /usr/lib/fm/fmd/fmd
root 25435 25261 0 12:54:51 pts/1 0:00 grep fmd

# Stop and start fmd:
svcadm disable svc:/system/fmd:default
svcadm enable svc:/system/fmd:default

Just a quick note about mounting ZFS resource in a non-global zone...

This is in response to a question that was posted in the SUN Solaris Experts group on LinkedIn:

I keep running into people who think that you have to reboot a non-global zone to add a ZFS mountpoint. Not true.

After you add the zfs resource to your zone.xml (use zonecfg, if you follow recomendation, heh) you perform the following on the Global Zone (not within the non-global zone). Be sure to define the type as "legacy":

root@global-zone# mount -F zfs your_zpool/your_filesystem_name /zones/non_global_zonename/root/your_mountpoint

Log into your zone and you should now see the new filesystem (DF or whatever).

Solaris 10: Enable SMCwebserver For Easy ZFS Management.

You know, sometimes a GUI is nice to have around. I'm not "really" a "GUI Fanboy" when it comes to system management and administration, but there are those times when it's just easier to see things, presented in way that's easy to access and not have to run a handful of commands and scroll through a ton of output, etc.

A lot of you are probably already aware of the SMCwebserver http interface and are still trying to remove the bad taste from your mouths, from the Oct 08 release of Sol 10 that totally fraked the whole thing up. I am happy to report that, thus far, it seems it's working again, in the May 09 release (5/09 s10s_u7wos_08 release). Now lets see if a subsequent cluster patch breaks it again, rofl.

I digress...

So, for those who are un-aware of how to enable the service to accept connections, remotely, here's a quick and dirty:

/usr/sbin/svccfg -s svc:/system/webconsole setprop options/tcp_listen = true

/usr/sbin/svcadm refresh svc:/system/webconsole

/usr/sbin/smcwebserver stop

/usr/sbin/smcwebserver start

/usr/sbin/svcadm enable svc:/system/webconsole

That should do it. Now make sure your port (6789) is listening to "All" (*):
/usr/bin/netstat -an|grep 6789

*.6789 *.* 0 0 49152 0 LISTEN

Now open your web browser on your desktop machine (laptop, whatever) and go to the server:6789

(http://your.server.address:6789)

Go through all of the security exception notifications and log in with the account with proper credentials (like root, for example, though I suggest you set up another account, instead).

Have fun with it and here's the smcwebserver manpage: http://docs.sun.com/app/docs/doc/816-5166/smcwebserver-1m?a=view

-W