Xenserver 6.2 cannot send alert using gmail smtp

alertgmailssmtpxenserver

I'm using Xenserver 6.2 and configured ssmtp.conf an mail_alert.conf in order to receive alerts through email. I followed the instructions on http://support.citrix.com/servlet/KbServlet/download/34969-102-706058/reference.pdf document. I'm using gmail smtp to send the emails. When i try:

[root@xen /]# ssmtp emailaddress@domain.com

from the command line and try to send the email, no problem. It is right on the way. But when i set some VM to generate alerts, alerts are generated. I see in XenCenter but emailing is not working. I see this in /var/log/maillog file:

May 27 16:17:09 xen sSMTP[30880]: Server didn't like our AUTH LOGIN (530 5.7.0 Must issue a STARTTLS command first. 18sm34990758wju.15 - gsmtp)

From command line every thing works fine. This is the log record for the above command line operation:

May 27 15:55:58 xen sSMTP[27763]: Creating SSL connection to host
May 27 15:56:01 xen sSMTP[27763]: SSL connection using RC4-SHA
May 27 15:56:04 xen sSMTP[27763]: Sent mail for emailaddress@gmail.com (221 2.0.0 closing connection ln3sm34863740wjc.8 - gsmtp) uid=0 username=root outbytes=495

Any ideas?

Best Answer

It would be useful that you post the contents of your /etc/ssmtp/ssmtp.conf and /etc/mail_alert.conf files.

Anyway, have you tried to include UseTLS=YES in /etc/mail_alert.conf?

Related Solutions

XenServer 6.2 – Changing MTU Settings

There's some discussion on the Xen wiki of how to do this: Xen wiki network performance page. In short:

Enabling Jumbo Frames

Suppose eth6 and xenbr6 are the device and the bridge corresponding to the 10 GiB/sec connection used.

Shut down user domains:

VMs=$(xe vm-list is-control-domain=false params=uuid --minimal | sed 's/,/ /g')
for uuid in $VMs; do xe vm-shutdown uuid=$uuid; done`

Set network MTU to 9000, and re-plug relevant PIFs:

net_uuid=`xe network-list bridge=xenbr6 params=uuid --minimal`
xe network-param-set uuid=$net_uuid MTU=9000
PIFs=$(xe pif-list network-uuid=$net_uuid --minimal | sed 's/,/ /g')
for uuid in $PIFs; do xe pif-unplug uuid=$uuid; xe pif-plug uuid=$uuid; done

Start user domains (you might want to make sure that VMs are started one after another to avoid potential VIF static allocation problems):

VMs=$(xe vm-list is-control-domain=false params=uuid --minimal | sed 's/,/ /g')
for uuid in $VMs; do xe vm-start uuid=$uuid; done

Set up the connections you will use inside the user domains to use MTU 9000. For Linux VMs, this is done with:

ETH=eth1   # the user domain connection you are concerned with
ifconfig $ETH mtu 9000 up

Verifying:

xe vif-list network-uuid=$net_uuid params=MTU --minimal

Creating a Xenserver 6.2 pool

So, what you do have now is a server running in Xenserver but with no pool configured.

Which of the servers are you setting up as master? I guess one of the new.

Setting the server you already have as a server wouldn't affect your vms. If you manage to join to the pool the other servers as slaves and then adding the new NAS to the pool you're done.

More information you can find in the Citrix XenServer ® 6.2.0 Administrator's Guide

http://support.citrix.com/servlet/KbServlet/download/34969-102-704897/reference.pdf

Related Topic