I found a work around, instead of Apache I use NGINX and that works.
Little did I know that sending mail from an EC2 instance is problematic to
say the least.
Thanks all for your help.
On Tue, Feb 21, 2017 at 2:11 PM, François Meehan wrote:
> Hi,
>
> I have restored a production instance of RT
On Feb 22, 2017, at 4:09 AM, Peter Nikolaidis
mailto:pet...@paradigmcc.com>> wrote:
Sorry- too quick with the send button. I did have to add a separate swap
partition because my instance was indeed running out of memory. I also was not
able to quickly get fcgi working, so I just moved on with s
Sorry- too quick with the send button. I did have to add a separate swap
partition because my instance was indeed running out of memory. I also was not
able to quickly get fcgi working, so I just moved on with standard Apache2. I
am using the Amazon Ubuntu AMI.
Peter
--
Peter Nikolaidis, CISSP,
Hi François,
I just recently moved back to RT after three years of coping with ConnectWise
and Autotask. I am presently running RT/Apache on a t2 nano and Postgres on
another t2 nano instance. I have not noticed the behavior you reported, but
have noticed that, sometime in the last week or so, a
I had this issue the other day using Amazon Linux AMI. Stand alone server
would run, but httpd would spike to 100+% cpu, no error, no logs, no output..
eventually I gave up and used the Centos7 AMI, worked like a dream first time.
I now run rt4 in aws.
Andrew Huddleston
On 22 Feb 2017, at 6:1