Hello There, Guest! Login Register
 Previous 1 2 3 4 5 7 Next   
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

sendemail ERROR => You must specify a 'from' field! Try --help.

#21
Something must have gone wrong the first time... Now I have received confirmation from WeTransfer...

nems-mailtest runs fine.

As far as the notifications are concerned: nothing in my spam folder...

BR
 Reply
#22
K let's not mix forum notifications here since it could get confusing for future readers. Maybe a new thread specifically for the forum?

I received the file just now, thanks.

However, this file does not reflect the changes I made... did nems-quickfix work okay?

Maybe try making a couple changes to your NEMS SST and then save, then change it back to your normal settings and save again.

Thanks! I'll also test NEMS SST at home tonight to make sure my changes stuck. Smile

Robbie
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#23
So I made some changes to NEMS SST, saved them and then reverted them and saved again. Still the same error.

nems-quickfix ran without complaining, asking to be patient... and then finished...

BR
 Reply
#24
Thanks baggins - so now that you've done that with NEMS SST can you please re-send me your backup.nems file? :p
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#25
Got the new file, thanks baggins. This shows that the update I pushed out did not take. I'll have to dig into this on the weekend as it will take some local testing to see why this is.

Do you by any chance get any errors when you run sudo nems-update ? Just to rule that out.
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#26
Hi Robbie,

nems-update fails:
Code:
PING google.com(ams15s21-in-x0e.1e100.net (2a00:1450:400e:800::200e)) 56 data bytes
64 bytes from ams15s21-in-x0e.1e100.net (2a00:1450:400e:800::200e): icmp_seq=1 ttl=53 time=54.3 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 54.395/54.395/54.395/0.000 ms
Updating nems-migrator... fatal: unable to access 'https://github.com/Cat5TV/nems-migrator/': Couldn't connect to server
Done.                                                                                                                                                                                                        
Updating nems-www... fatal: unable to access 'https://github.com/Cat5TV/nems-www/': Couldn't connect to server                                                                                              
Done.
Updating nems-admin... fatal: unable to access 'https://github.com/Cat5TV/nems-admin/': Couldn't connect to server
Done.
Updating nems-conf... fatal: unable to access 'https://github.com/Cat5TV/nconf/': Couldn't connect to server
Done.
Updating nems-scripts... fatal: unable to access 'https://github.com/Cat5TV/nems-scripts/': Couldn't connect to server
Done.
Running updates and fixes... grep: /etc/cgi.cfg: map does not exist
Genegeerd:1 http://giteduberger.fr rpimonitor/ InRelease
Fout:2 http://giteduberger.fr rpimonitor/ Release                                                            
  Kan de verbinding met giteduberger.fr:80 (213.186.33.17) niet aangaan. - connect (101: Netwerk is onbereikbaar)
Ophalen:3 http://ftp.debian.org/debian stretch-backports InRelease [91,8 kB]                                 
Geraakt:4 http://archive.raspberrypi.org/debian stretch InRelease                                            
Geraakt:5 http://mirrordirector.raspbian.org/raspbian stretch InRelease                                      
Geraakt:6 http://archive.raspbian.org/raspbian stretch InRelease                                             
Genegeerd:7 http://download.webmin.com/download/repository sarge InRelease                                   
Fout:8 http://download.webmin.com/download/repository sarge Release                
  Kan de verbinding met download.webmin.com:80 (108.60.199.109) niet aangaan. - connect (101: Netwerk is onbereikbaar)
Pakketlijsten worden ingelezen... Klaar
E: De pakketbron 'http://giteduberger.fr rpimonitor/ Release' heeft niet langer een Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant.
E: De pakketbron 'http://download.webmin.com/download/repository sarge Release' heeft niet langer een Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant.


Halfway the error messages switch from English to Dutch. No idea why...
BR
 Reply
#27
Well, at least this explains why you're having trouble - your system can't connect to Github, which is where the updates come from.

Everyone else - do you get errors as well? Wondering if that is related to this issue or just a fluke.

baggins, what is the output of this command?

Code:
cat /etc/resolv.conf

Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#28
Whats in the new nems fix? I can try and see if it resolves the issue... Thanks.
 Reply
#29
alerty please see the changelog. https://docs.nemslinux.com/changelogs/nems_1.3
  • January 19, 2018 - Some minor bugfixes on NEMS SST that load previously saved settings more correctly.
  • January 22, 2018 - NEMS-SST now saves null fields to resource.cfg. Resolves issue where Nagios can't read user macros beyond a missing incremental number.

To update and test:

Code:
sudo nems-quickfix



Then open NEMS SST and press "Save".

Then, let me know if the "You must specify a 'from' field error is fixed or not. I still do not have confirmation whether this is the cause or not as I have not been able to replicate the issue.

Also, if you could let me know if you get any errors when running this command, as we are trying to see if it is related (it certainly is why baggins didn't get the update):

Code:
sudo nems-update


Thanks!
Robbie Ferguson // The Bald Nerd

Did I help you out? Appreciate what I do? Please consider saying thanks:
 Reply
#30
Ok so did the quickfix and nems update, same config in SST but still have the issue. Same message yet a nems test email works fine.

Thanks
 Reply
 Previous 1 2 3 4 5 7 Next   
 
 
Forum Jump:

Users browsing this thread: 1 Guest(s)