I noticed in the release log (http://mmonit.com/wiki/MMonit/Release2-1) Monit supports Jabber/GTalk messages but I can't find the proper syntax in any of the documentation. I'm trying to send out an alert via gTalk when a host goes down.
M/Monit (the Monit management server) can send XMPP messages. The monit daemon can only send email on its own.
Related
I would like to run one service process per MUC channel on an ejabberd server. Ideally I would like ejabberd to start / monitor that process.
That is, when a new MUC gets opened ejabberd should start the bot process and tell it the channel name through commandline options. The process will then connect to that MUC on its own and do its thing. in case it crashes, ejabberd should notice and try to restart it. In case the MUC gets closed, so should the bot process. Is such functionality available with ejabberd?
I am not aware of anything like that implemented.
I made a process using activiti-explorer and I deployed.I have a startevent,mail task,user task and endevent.When I started the process it says "Warning!Could not send e mail". What should I do?
Thanks
The Activiti engine sends e-mails trough an external mail server with SMTP capabilities. To actually send e-mails, the engine needs to know how to reach the mail server. Following properties can be set in the activiti.cfg.xml configuration file.
More info: http://www.activiti.org/userguide/#bpmnEmailTask
I want to send mail b Jboss server when server down , stop working or there is any unexpected crash in server
If jboss is down then it can't send email. Because it is down
So you need to monitor it with a different system.
Nagios is a widely open source monitoring system http://www.nagios.org It has a lot of plugins that can be configured to monitor jboss according to your exact business needs
I am using a PHP script for sending emails by IIS 5.1 SMTP.
The emails, go to outbound folder. really path is C:\Inetpub\mailroot\Queue.
after a seconds, it start to send emails properly, but after sending 5 or 6 emails, it stops to send the other ones. SMTP service is still start and it seems there is no problem to SMTP service.
but,If i restart the service, it sends 1 or 2 other emails and then, it stops again.
I mean sending emails stop but service is start.
by the way, emails are stucked in Queue folder.
Also i checked Badmail folder. it is empty
Thanks
are all the emails to the same network? I have seen behaviour like this when the recipient server bans you, yahoo's (xtra) used to do it sometimes to our server in particular. You can check the logs in event viewer for something from the smtp server, you'll find a message from the other server saying something to the effect that you have been temporarily banned, possibly with more detail about why. Trying to connect via telnet also gives you the same message.
When this happens windows will try and send them again later. Restarting the server starts to try sending again and if the ban condition has been lifted messages will flow for a while again until you are rebanned.
If I am using MSMQ over the web, what happens if the network connection is lost between client and server?
So can you still add messages to the Queue, and if so where are they stored? In the client app, or in the clients OS etc?
For instance if I have a windows service which is adding items to a queue in a different country. What if the network connection is lost, and the windows service is restarted. Do the messages get lost forever?
The other part of the question relates to the route that a message takes, is it sent directly to the receiving queue, or is it written into a queue on the client side? Does that require MSMQ to be installed on the sending server, and how about licensing for that?
Is there any good documentation to explain the required setup?
Update: Regarding your follow up question. Yes you have to install msmq on the sending server. There aren't any licensing cost, because MSMQ is part of windows and not a separate software (just like the IIS). Here is documentation on "Setting Up a Message Queue" on windwos 2003.
Before Update: Outgoing message are stored in the outgoing queue of the sending server. They are not lost if the sending service is restarted. They will wait in the outgoing queues ( which can be inspected with the msmq manager ) for I don't know how long.
if the msmq service or the sending server are restarted. Then "express" messages will be lost. express or recoverable are properties of non-transcriptional messages.