E-mail troubleshoot
hudene opened this issue · 13 comments
I'm running everything through Raspberry Pi Debian Linux terminal, I am very new to all of this.
- My first question is about the e-mail feature. I have set e-mail alerts to ON and the e-mail timer to OFF through the config file, but have not received any e-mails in my spam folder or my inbox.
There is a commented line above the e-mail alerts about " # CURRENT SUPPORT IS FOR SMTP, ENTER YOUR USERNAME AND PASSWORD HERE. LEAVE BLANK FOR OPEN RELAY
USERNAME="" "
ENTER THE SMTP PASSWORD HERE. LEAVE BLANK FOR OPEN RELAY
PASSWORD=""
Do I need to fill out my username and password in those lines in order to receive an e-mail alert?
When I go into the sys log, it says "raspberrypi [!] Error, Artillery was unable to log into the mail server"
Why might the e-mail function not work?
- Side Question: I'm starting to wonder if I installed Artillery correct.
I used git clone https://github.com/trustedsec/artillery artillery/
When I set it up, it asks if I'd like to install, and I put yes. But when it asks if I'd like to keep it updated, I have to put No or I can't run artillery. Is this normal?
It talks about how it can't getcwd() if I say Yes to updating it.
- when you launch python, and type into interpreter
import os
print os.name
what will you get ?
getcwd() is only used here https://github.com/trustedsec/artillery/blob/master/setup.py#L81
I actually cannot run that command. I have python running through my raspberry pi terminal.
root@raspberrypi:/# import os
-bash: import: command not found
root@raspberrypi:/# print os.name
Warning: unknown mime-type for "os.name" -- using "application/octet-stream"
Error: no such file "os.name"
Type python[enter] and then issue those commands.
For the email server, you need to specify either an open relay server or something that you have a username and password for in order to receive email alerts. Specifying "no" on keeping Artillery up-to-date simply doesn't go and pull the latest version and set incremental updates. Closing this one as it does not appear to be an Artillery issue.
I think this is an error with Artillery. I've tried installing Artillery on different OS as well. I cannot properly install Artillery. When I say "yes" to updating artillery upon using the ./setup.py command, it fails to install properly on both Debian and Ubuntu.
I was able to successfully install it on three different Ubuntu systems just this week. The installer works perfectly.
I keep getting errors "shell-init: error retrieving current directory: getcwd: cannot access parent directories..."
I've gotten this on Ubuntu and Debian. I tried again 5 minutes ago.
I suggest trying the tips at http://shriikant.blogspot.com/2010/04/shell-init-error-retrieving-current.html
That doesn't help. By the way, thank you for trying to still help me, much appreciated!
So, right now I'm running Ubuntu 4.4.3
I've installed Artillery into my /var directory using git clone
./setup.py
it asks if I want to install --> y
That works fine.
Then it asks me if I want to keep Artillery updated --> y
Then the shell-init error pops up.
Then it asks would you like to start Artillery --> y
Then the shell-init error pops up again. and chdir: error retrieving current directory.
After this, I use ps -Al to see if Artillery is running, and it is not.
When I 'ls' into my artillery directory, it is completely empty for some reason.
Now when I try to install and say N when it asks if I'd like to keep Artillery updated, my installation works fine.
I suggest you try running it with sudo
I'm already in root, should I log in as a regular user and use sudo?
I've tried that on Debian and it did not work either.
I just reread your previous email and I think I see the issue.
Try completely removing /var/artillery
Use git to download the folder to either /opt or /tmp, then try running the installer. The installer copied the entire directory structure to /var for me, so I think it's confused as it's trying to write to /var/artillery but that's where you're running it from.
it worked! thank you so much!