I am not sure (yet) if this is a bug: I have been doing numerous tweaks and running:
ee stack restart --nginx
and after a restart I receive the
Start : nginx [OK]
A few times I ran:
ee stack restart
and ee returnes:
Restart : nginx [OK] Restart : php5-fpm [OK] Restart : mysql [OK] Restart : postfix [OK]
What is interesting that I run SQL of of Google Cloud SQL so I had removed mySQL with:
ee stack remove --mysql
Terminal had shown that it was successfully removed. When I saw that ee was showing mysql was restarting, I ran:
The machine returned that mysql was not installed but why does ee still shows that it is and that it restarted - I also drilled thru the sever directories after running a purge and found nothing - just the client used to connect to Cloud SQL??
Now for the REAL problem:
I am running ee on Compute Engine, n1-highcpu-4 (4 vCPU, 3.6 GB memory, Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-31-generic x86_64) for development be for the BIG release of this project.
Thru-out the day, I stop the instance when I am not working on the project (Google doesn’t charge when the instance is off and I boot it up when I need it. During after hours (over-night), I shut down the instance and reboot in the morning but I find the ee server is not responding…? This has happened for the third day in a row now. What I discovered is if I run:
ee stack restart --nginx or ee stack start --nginx or ee stack stop and ee stack start
I get a return from ee that everything is O.K. I try to access the site and still no response from the server. Back in terminal I run:
and that returns NGINX is not running! So what is REALLY going on here? I have tried every way imaginable to start NGINX the traditional way or the ee way and it doesn’t start even-though ee says it is…
The only way around this is for me to start a new instance with a snapshot. I am starting to find that ee may not be reliable because I was experiencing the same thing a few months ago on a Digital Ocean image but I blew it off as a flewk.
Please, any help here would be greatly appreciated and I don’t wan’t to give up on ee just yet - It does make set up much easier.
PS: I also can’t access the logs using ‘ee log’ because ee isn’t really running in this situation - it just locks up terminal -weird.
This seams to be an ee cache issue(?) At the end of the day I work on some security settings for the server. When I close and save the config files, I see the “Restart : nginx [OK]” and assume all is well. Then I shut down the instance and the next morning, all is not well.
Today I discovered when I opened back up a config, added a space between a line, closed and saved, I got a Reload : nginx [Failed]. I manually looked into the logs and discovered I had a typo from an edit the day before. This tells me that when a edit is done on a config, ee is checking against the cache and is returning what it sees there. Maybe rtCamp can modify the script to purge the cache when a config file is saved??
Like I had said, I was ASSUMING because ee was outputting "Reload : nginx [OK]’ after a save - This is misleading that it is purging everything with a restart. Even after running “ee stack restart” a all is OK was returned because its checking the cache not the changes - I don’t get any errors from ee until the instance has been turned off. Even when I run “ee stack restart” in the morning. I only see errors after editing a config - I am I right on this?? Thnx -j