psmon/asl -s -f inconsistencies?

jeremiah · Unread post by **jeremiah** » Fri Aug 29, 2008 9:28 am

Hi!

I just noticed that during the psmon scan/fix phase there is a difference on what gets [FIXED] between 2 servers.
One server says

Code: Select all

Checking System services monitored by psmon
  clamd: monitored                                         [FIXED]
  courier-imap: monitored                                  [FIXED]
  crond: monitored                                         [FIXED]
  ossec-hids: monitored                                    [FIXED]
  psa: monitored                                           [FIXED]
  sshd: monitored                                          [FIXED]
  xinetd: monitored                                        [FIXED]

2.6.25.4-4.art.x86_64
asl-2.0-2.el5.art
psmon-1.39-1.el5.art
[edit] - psa-spamassassin-8.3.0-cos5.build83071218.18

While the other says

Code: Select all

Checking System services monitored by psmon
  clamd: monitored                                         [FIXED]
  courier-imap: monitored                                  [FIXED]
  crond: monitored                                         [FIXED]
  ossec-hids: monitored                                    [FIXED]
  psa: monitored                                           [FIXED]
  psa-spamassassin: monitored                              [FIXED]
  sshd: monitored                                          [FIXED]
  xinetd: monitored                                        [FIXED]

2.6.25.4-4.art.x86_64
asl-2.0-2.el5.art
psmon-1.39-1.el5.art
[edit] - psa-spamassassin-8.4.0-cos5.build84080425.19

The diff is in psa-spamassassin.
Is this a config option I missed/forgot about in asl?

I edited /etc/psmon.conf and added psa-spamassassin, then ran asl -s -f again, with same results.

Couldn't really say if it just started, cuz umm, er well the words they wiz by so fast =P

Looking in /etc/psmon.conf after my edits and subsequently running asl -s -f my change is gone and psa-spamassassin wouldn't be monitored without re-editing psmon.conf

I bet I missed something but could use a tip please.

Unread post by **scott** » Fri Aug 29, 2008 9:49 am

It reads your sysv init configuration and monitors what the system has configured to start at boot time. I suspect you'll find that your one server doesn't start psa-spamassassin in runlevel 3.

jeremiah · Unread post by **jeremiah** » Fri Aug 29, 2008 10:48 am

fancy that

Not only was psa-spamassassin not configured to start on boot (although I haven't been starting it after reboots and it's still been running!?) BUT psa-spamassassin didn't show w/ chkconfig --list... so had to --add it first.

now all is happy and well. Thank you!