I need this script to email the log it generates



  • I'm tired of dealing with shit for a while. So dumping it here. I'll do my own searching later if nothing gets posted.

    I just finished updating this script and the next step will be to have it email the results.
    https://github.com/sorvani/freepbx-helper-scripts/blob/master/InitialSetup/update.sh

    It is designed only for FreePBX systems, so you can assume the PBX already has valid email methods setup. By default, postfix should be working, because that is the FreePBX design.



  • Likely going to add an if check later also, if there was a kernel update during the yum upgrade to output that as a need to reboot.

    aa3ce112-5464-4a91-b205-ee345cacb19f-image.png



  • Found here: https://superuser.com/questions/1020680/how-to-mail-output-of-shell-script-as-a-cron-job because my memory is so rusty.

    Have to redirect the script output from stdout, so something like
    sudo ./update.sh 2>&1 | tee output.txt | mail -s "Subject FreePBX update" [email protected]



  • @travisdh1 I need the local output still, that why it’s creating a text log file. I want that log file emailed to me, not simply the output of the script piped to the mail command. I did assume that I would use the mail command, like I said I have not had the time to look it up yet (the syntax).

    Edited to de-Sirify the post.



  • @JaredBusch I'm not sure exactly what you're looking for except to email the textfile?

    Regardless I suggest putting some more information in the textfile such as hostname or otherthings that would identify what system it is.
    Also perhaps timestamp each output then you'll know how long something takes and you'll know what it was executed on the system.



  • @Pete-S said in I need this script to email the log it generates:

    Regardless I suggest putting some more information in the textfile such as hostname or otherthings that would identify what system it is.

    None of that needs to be in the log file. The subject line of the email, yes.



  • @Pete-S said in I need this script to email the log it generates:

    Also perhaps timestamp each output then you'll know how long something takes and you'll know what it was executed on the system.

    Not something that is needed to be known.



  • @Pete-S said in I need this script to email the log it generates:

    @JaredBusch I'm not sure exactly what you're looking for except to email the textfile?

    That is correct.



  • So, no time to deal with updating and testing the script, today.

    But since such a simple post, posted to hopefully generate a conversation, did not do anything helpful....

    The basic mail syntax to send an email and attachment is

    echo "Some Message Body Text" | mail -s "Some Subject Line" [email protected] -A file.txt
    


  • @JaredBusch said in I need this script to email the log it generates:

    So, no time to deal with updating and testing the script, today.

    But since such a simple post, posted to hopefully generate a conversation, did not do anything helpful....

    The basic mail syntax to send an email and attachment is

    echo "Some Message Body Text" | mail -s "Some Subject Line" [email protected] -A file.txt
    

    I found it interesting because it's what I was discussion in the other thread about notification emails.

    But I haven't researched it enough yet.
    For instance what is the difference between mail and mailx? What happens if the mail bounces? Is the mail cached for delivery if it can't be delivered?



  • @Pete-S said in I need this script to email the log it generates:

    I found it interesting because it's what I was discussion in the other thread about notification emails.

    I'm not after alerting. That is not the purpose of this email. It is for a historical record only.

    The way I handle this type of stuff is that it goes to a folder and is marked read by a rule.

    Then about once a year I purge anything older than a year.



  • @JaredBusch said in I need this script to email the log it generates:

    @Pete-S said in I need this script to email the log it generates:

    I found it interesting because it's what I was discussion in the other thread about notification emails.

    I'm not after alerting. That is not the purpose of this email. It is for a historical record only.

    The way I handle this type of stuff is that it goes to a folder and is marked read by a rule.

    Then about once a year I purge anything older than a year.

    Yeah, I understood - you just wanted to have the logs mailed to you.

    I'd call that a notification (not an alert). The script notifies you that it has been executed and what the results where. You don't intend to look at it, unless you have to, but it's still a notification nevertheless.



  • you could use mailgun. I just wrote this tiny app that will send the contents of a file.

    package main
    
    import (
    	"context"
    	"fmt"
    	"github.com/mailgun/mailgun-go/v3"
    	"io/ioutil"
    	"os"
    	"time"
    )
    
    func main() {
    	mg := mailgun.NewMailgun(os.Getenv("DOMAIN"), os.Getenv("API_KEY"))
    	to := os.Getenv("SEND_ADDRESS")
    	data, err := ioutil.ReadFile(os.Args[1])
    	if err != nil {
    		fmt.Println(err)
    	}
    	m := mg.NewMessage(
    		"[email protected]",
    		"Test Log",
    		string(data),
    		to)
    
    	ctx, cancel := context.WithTimeout(context.Background(), time.Second*10)
    	defer cancel()
    
    	_, id, err := mg.Send(ctx, m)
    	if err != nil {
    		fmt.Println(err)
    	}
    	fmt.Println(id)
    }
    

    I lazily take the first argument as the file with the contents you want to send. Just have env vars for the recipient address, your api key and domain (or hard code them). You could take flags and whatever, but this was free and I'm lazy.



  • @stacksofplates said in I need this script to email the log it generates:

    you could use mailgun. I just wrote this tiny app that will send the contents of a file.

    I lazily take the first argument as the file with the contents you want to send. Just have env vars for the recipient address, your api key and domain (or hard code them). You could take flags and whatever, but this was free and I'm lazy.

    There is one problem with the api approach I think.
    I believe tht if you use postfix to deliver the message over SMTP it will put the message in postfix' queue. So if for some reason the mail can't be delivered at that particular time, for instance because the firewall is being rebooted or there is a problem with the mailservice, it will try again later. Using the API you will just a timeout error and that was it.

    I'm not a mailgun user but I assume they have a SMTP relay as well?

    In any case since we like zoho, I intend to try the new Zoho TransMail service. They only send transactional mail, not marketing, and I think it was $2.5 or something like that per 10K emails. They have both api and SMTP.