As long as you've actually setup a valid process setup somewhere under /Processes (from the left menu) you should see the process listed in the OS tab after the next remodel of that device, as a base install (pretty much) only has mysqld and httpd setup by default that's all you'll see.
However, there is/was a problem with Zenoss not realising when a down process is back up caused by the length of the component field in the events database. I thought this was fixed in fresh installs of (not upgrades to) 2.2.3, although I did a fresh 2.2.3 install the other day and it wasn't. You can fix that problem by doing the below (and find more about this elsewhere in the forum): NOTE: Make sure you have plenty of disk space if you have a big events database before doing the below!! Also be aware this can take a LONG time: Code: [EMAIL PROTECTED] ~]$ mysql -u zenoss -p Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 136335 to server version: 5.0.24a-standard Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> use events; Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> alter table status modify component varchar(255); Query OK, 10 rows affected (0.33 sec) Records: 10 Duplicates: 0 Warnings: 0 mysql> alter table history modify component varchar(255); Query OK, 473 rows affected (0.27 sec) Records: 473 Duplicates: 0 Warnings: 0 mysql> mysql> Bye [EMAIL PROTECTED] ~]$ NOTE: Move all OSProcess events to history once this is done to complete the fix. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=25701#25701 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
