I am using Ambari 2.0 and trying to configure email alerts. In the Ambari server logs I can see the following message:
There are 5 alert notices waiting to be dispatched.
But I am not receiving any emails. Using Gmail SMTP configuration
smtp.gmail.com port 465. Is this a problem in the latest Ambari version?
Looks like you are hitting known bug...
Check BUG-30278 in the Ambari 2.0.0 Release notes http://docs.hortonworks.com/HDPDocuments/Ambari-2.0.0.0/bk_releasenotes_ambari_2.0.0/content/ambari_relnotes-2.0.0.0-known-issues.html
Workaround is to restart ambari-server.
Related
I am using Apache Ambari 2.7.3V. I am trying to configure Email Alerts. I have Followed the Below Link. But I am not getting any alerts To my Gmail. Below are my configurations
https://docs.cloudera.com/HDPDocuments/Ambari-2.7.4.0/managing-and-monitoring-ambari/content/amb_create_an_alert_notification.html
In Manage Alert Notifications I have configured All required configurations. like below.
Name: amabri Alerts
groups: All
Severity: WARNING, CRITICAL
Description : xxxxxxxx
METHOD: EMAIL
SMTP SERVER: smtp-relay.gmail.com
SMTP PORT : 587
I am not sure whether your issue has been resolved. But posting for other users' reference.
You need to set the app password to use Gmail SMTP. You have to enable two-step verification to enable the app password as below. In addition to that, the SMTP server for Gmail would be-smtp.gmail.com
.
If still, you are not getting emails then you can test the python script(from head node) here
and test the below:
Ssh to head node
Then edit the file -Sudo vi /etc/ambari-server/conf/log4j.properties
Modify - log4j.logger.alerts=INFO,alerts to log4j.logger.alerts=DEBUG,alerts
Add below line to Alerts section -
log4j.logger.org.apache.ambari.server.notifications.dispatchers=DEBUG,alerts
Save the file and restart ambari server service using usr/lib/hdinsight-common/scripts/restart_ambari_server.sh
Try to stop zookeeper on any one of the node and check for the ambari-server.log and amabri-alerts.log.
In /var/log/ambari-server, check ambari-alerts.log and ambari-server.log after an alert was fired.
I am testing a deployment of MQ 9.0.1 using Docker, and trying to administer this instance using the Web console. However I am receiving a warning when attaching widgets stating the "Queue manager unavailable".
Warning messages
In the console I can see my Queues are running and have created local queues and can run commands against them.
Also if I try to modify the Queue security records I get another error:
Failed to get authority recordsWMQWB0003E: The request could not be completed due to an internal web application server error.
Any thoughts or suggestions around this issue?
There is no definitive fix for MQ9.0.1 but upgrading to use MQ9.0.2 will resolve issues with hosting MQ Console on linux.
I'm trying to track down an issue where email alerts are being sent from Cloudera Manager to an incorrect email address. We've corrected the email address in the Cloudera UI under "Alerts: Mail Message Recipients" and restarted the entire cluster a few times, but the messages are still being sent to the old incorrect addresses. Could someone detail the chain through which these alerts are passed?
(Moving from comment.) It's stored in a database like MySQL or postgresql by default. You can configure it to use a different DB but otherwise it runs one locally.
I setup Xcode Bots, which is working successfully. However, despite setting email addresses to get notified when a build is successful or it fails, I do not receive any emails. Is there any additional SMTP setup I need to do hidden somewhere?
You probably need to configure the Mac OSX Server for sending e-mail.
The local server is located in the Server application under "Mail" in the left sidebar.
I recently changed to using Amazon SES and had to edit the Postfix SASL configuration manually. Edit SASL password file, run postmap, enable SASL/TLS in main.cf configuration file and finally restart Postfix.
This detailed description by Rojas helped me:
http://benjaminrojas.net/configuring-postfix-to-send-mail-from-mac-os-x-mountain-lion/
I recently was tasked with doing the same thing, setting up OSX Server for sending e-mail. What worked for me was setting up the postfix configuration manually as well but the link in the previous answer wasn't effective for me. what was effective was following this tutorial
http://blog.anupamsg.me/2012/02/14/enabling-postfix-for-outbound-relay-via-gmail-on-os-x-lion-11/
and there's also a follow up that shows details to what needs to change to get it to work on Mavericks and newer http://blog.anupamsg.me/2013/12/22/enabling-postfix-on-osx-as-a-relay-revisited/
Without any changes, email notifications stopped being sent from our continuous integration server which is a Teamcity 7.1 server. Up to now I've just used the default teamcity email configuration, which was this:
SMTP host: mail
SMTP port: 25
Send email messages from: Teamcity
SMTP login: <blank>
SMTP password: <blank>
Secure connection: none
Worked fine for last year or so. Now I'm trying to diagnose what is wrong, but I don't really know what the above configuration is doing... Is it pointing to a built-in mail server that is bundled with Teamcity? Is it pointing to the company's exchange server? Something else?
Teamcity does not have any bundled mail servers. This configuration point to your company's SMTP server. By occasion, SMTP server's name is 'mail'. So TC tries to connect to mail:25 and send messages 'from' 'Teamcity'
Please check if SMTP server's authentication settings were modified (e.g., anonymous access is now forbidden). Also please check 'teamcity-server.log' for error messages related to sending notifications.