BB Unix Network Monitor - Message
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: {bb} No Notifications from BB after upgrading to bb1.9f-btf and RHEL 4
- To: bb@bb4.com
- Subject: Re: {bb} No Notifications from BB after upgrading to bb1.9f-btf and RHEL 4
- From: "David" <david@lolling.org>
- Date: Thu, 21 Jul 2005 14:13:07 -0000
- Content-transfer-encoding: 8bit
- Content-type: text/plain; charset="iso-8859-1";
- Importance: Medium
- Reply-to: bb@bb4.com
- Sender: owner-bb@bb4.com
Thanks for the confirmation. I saw that in the Changes for 1.9g
but it did not state that it was broken for all conditions so I
was going to try that next.
Did you have any problems with sending email as your bbuser
using mail/mailx?
thanks,
Dave
--------- Original Message --------
From: bb@bb4.com
To: bb@bb4.com <bb@bb4.com>
Subject: Re: {bb} No Notifications from BB after upgrading to bb1.9f-btf and
RHEL 4
Date: 21/07/05 13:40
>
>
> I ran into the same issue.
>
> someone else posted here that 1.9f notification is broken. I went to
> 1.9h and then it worked.
>
> Hope this helps.
>
> Paul
>
> At 07:57 AM 7/21/2005, you wrote:
> >Hello,
> >
> >A former employer has asked me to upgrade 4 BB servers I deployed
several
> >years ago from:
> >Red Hat 8 / bb1.8b
> >Red Hat 9 / bb1.8b
> >Red Hat WS 2.1 / bb1.8b
> >
> >to:
> >Red Hat Enterprise Linux ES release 4 (Nahant Update 1) / bb1.9f-btf
> >
> >
> >After installing the OS, the new version of BB, migrating the config
> >files and working through most of the issues, I have found that I am
> >no longer getting email notifications.
> >
> >At first I blamed it on selinux, so I set selinux to permissive mode
> >which did not solve this particular problem.
> >
> >My bbuser is george:orwell.
> >
> >I found under RHEL 4 that the user george cannot send mail from
> >the command line, nor can the user goerge send email from the command
> >line when su'd from root but the root user can send email from the
> >command line.
> >
> >For the time being, I am using MUTT as the email client as it can
> >send email as george, su - goerge and root.
> >
> >I have recompliled bbpage.c to include debugging information and
switched
> >to a very minimal bbwarnrules.cfg and bbwarnsetup.cfg for testing
purposes.
> >While tailing BBOUT, I can see where bbd is trying to process
notifications
> >but never seems to find a match and gives up.
> >
> >For example when I try to send a page using bb-ack.html/bb-ack.sh we I
see:
> >
> >argmsg: notify-admin.pagehelp 8675309 User has requested your help.
Call
> >8675309
> >msg: 8675309 User has requested your help. Call 8675309
> >hostsvc: notify-admin.pagehelp
> >2nd word in message is: <8675309>
> >We have a "notify-admin" request
> >bbwarn: TRUE
> >The pagelevels is set to <red purple>
> >pagedelay: 1
> >cfgdelim: ;
> >svcerrlist: disk:100 cpu:200 procs:300 msgs:400 conn:500 http:600
dns:800
> >ERR:999
> >pagehelpcode: 911
> >hostinfo: (hostsvc:notify-admin.pagehelp)
(bbhostsvc:notify-admin.pagehelp)
> >(redhost:notify-admin) (redsvc:pagehelp)
> >ignforall:
> >machip: 8675309 - svcerr: 911
> >rule line: *;;*;;*;*;lollidp@cat.com
> >rule line: notify-admin;;pagehelp;;*;*;lollidp@cat.com
> >Column 1: notify-admin
> >Column 2:
> >Column 3: pagehelp
> >Column 4:
> >Column 5: *
> >Column 6: *
> >Column 7: lollidp@cat.com
> >Substituting hg- tags in the rule line
> >Original column 1: notify-admin
> >Checking host definition: notify-admin
> >Included hosts are: <notify-admin>
> >Column 1 converted to a regex: <notify-admin>
> >Original column 2:
> >Excluded hosts are: <>
> >Trying to match host <notify-admin> with hosts regex:
notify-admin
> >Host <notify-admin> matched this regex: notify-admin
> >Trying to match service <pagehelp> with svcs regex:
> >Day definition in rule line matched all (*)
> >Time definition in rule line matched all (*)
> >Recipients column: <lollidp@cat.com>
> >Validate recipient: <lollidp@cat.com>
> >The list of recipients to notify is now: <8H~>
> >The list of recipients to ignore is now: <>
> >The final list of recipients is: <8H~>
> >rule line: unmatched-*;;*;;*;*;lollidp@cat.com
> >Preliminary recipients list <8H~>
> >Keep only one recipient definition per recipient
> >Our recipients list is <8H~ >
> >Working on recipient <8H~>
> >getdelay(): PAGE_BASIC:DEFAULT - initdelay = 0, delay = 1
> >Adding recipient <8H~> to recipient list
> >Final recipients list <8H~>
> >
> >other notifications look like:
> >rule line: unmatched-*;;*;;*;*;lollidp@cat.com
> >Column 1: unmatched-*
> >Column 2:
> >Column 3: *
> >Column 4:
> >Column 5: *
> >Column 6: *
> >Column 7: lollidp@cat.com
> >Substituting hg- tags in the rule line
> >Original column 1: unmatched-*
> >Checking host definition: unmatched-*
> >Included hosts are: <unmatched-*>
> >Column 1 converted to a regex: <unmatched-*>
> >Original column 2:
> >Excluded hosts are: <>
> >Trying to match host <dqhpsp.cnc.cat.com> with hosts regex:
unmatched-*
> >Ignore this rule as host <dqhpsp.cnc.cat.com> did not match this
regex:
> >unmatched-*
> >Oh well, no recipients were determined, we're done
> >
> >
> >Notifications did work on the old servers, so I am assuming the old
config
> >files
> >are still valid.
> >
> >I have racked my brain on this one, so any help or guidance would be
> >appreciated.
> >
> >Thanks,
> >
> >David
> >
> >--
> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> >To unsubscribe from this list, or to subscribe to the bb-digest list
> >send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> >subscribe bb-digest in the BODY of the message.
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
> subscribe bb-digest in the BODY of the message.
>
>
>
>
>
>
>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.
Home |
Main Index |
Thread Index