Help with "Check that you can ping the server mysql"


(Susmita) #21

ah, thanks for trouble shooting that, any additional help would be greatly appreciated!


(Asher Densmore-Lynn) #22

First thing I’d try is connecting to the OpenEMR docker and seeing if there’s an issue with your Apache logfiles – there might be a lot of them, if there’s no rotation.

Failing this, you can increase the size of the EBS volume attached to the EC2 instance, and then extend the file system to make use of the additional space. See the Amazon documentation (or the support forums) for more information about this process.


(Stephen Waite) #23

so @susmitahunter, reconnect to the openemr docker and run the below to see the size of the files

/var/www/localhost/htdocs/openemr # ls -lrt /var/log/apache2/

(Susmita) #24
/var/www/localhost/htdocs/openemr # ls -lrt /var/log/apache2/
total 359932
-rw-r--r--    1 root     wheel            0 Apr 28  2018 ssl_request.log
-rw-r--r--    1 root     wheel            0 Apr 28  2018 ssl_access.log
-rw-r--r--    1 root     wheel         6908 Sep 18 13:38 ssl_error.log
-rw-r--r--    1 root     wheel     88104960 Sep 20 12:43 error.log
-rw-r--r--    1 root     wheel    280445360 Sep 20 13:58 access.log

(Stephen Waite) #25

try this

/var/www/localhost/htdocs/openemr # : > /var/log/apache2/access.log

the command includes the :
: > /var/log/apache2/access.log


(Susmita) #26

I put in the command as you have it, no errors, but it didn’t output anything


(Stephen Waite) #27

rerun the long list,


(Susmita) #28
/var/www/localhost/htdocs/openemr # ls -lrt /var/log/apache2/
total 86052
-rw-r--r--    1 root     wheel            0 Apr 28  2018 ssl_request.log
-rw-r--r--    1 root     wheel            0 Apr 28  2018 ssl_access.log
-rw-r--r--    1 root     wheel         6908 Sep 18 13:38 ssl_error.log
-rw-r--r--    1 root     wheel     88104960 Sep 20 12:43 error.log
-rw-r--r--    1 root     wheel            0 Sep 20 14:31 access.log

(Stephen Waite) #29

do the same with the error_log
: > /var/log/apache2/error.log
and then exit back to the bash root shell and run
root@ip-10-0-1-118:~# docker restart d05167f16b1f
and you should be up and running again :slight_smile:

ps it might be docker start d05167f16b1f since it’s not running


(Susmita) #30

omg, it works. I cannot express how thankful I am, I could kiss you, this has been such a burden operating for the past week without it. Thank you so very much for practically holding my hands through this process.

I honestly have just been copying the commands through with only a vague idea of what/why I was doing it… but I take it the log file just got too large and that was why there was a space issue? I also had a problem doing the backup through openemr last wednesday, and I’m guessing that was related to this as well.

Again, thank you so much, you’re a life saver! I know it’s tedious to spell things out for me through this, so thank you again!


(Stephen Waite) #31

no prob, :blush:, it’s going to be helpful for others who encounter this issue since the logs aren’t rotating yet. Also, in the not too distant future we should help you to a larger ec2 instance since your database is healthy and growing