nice, would dbl check the home computer
1 Like
Way to hang in there!
I checked my home computer again:
robert@robert-ideacentre-AIO-520-22IKU:~$ docker exec -it $(docker ps | grep _openemr | cut -f 1 -d " ") ls -lrt sites/default/documents/logs_and_misc/methods
total 4
-rwx------ 1 apache 1000 63 Sep 30 2018 README.md
robert@robert-ideacentre-AIO-520-22IKU:~$
I then used the new back up (with keys present) to restore openemr to my home computer. Same result. So evidently something is going wrong either with the restore or when openemr starts up. I had understood from you that if the keys were not present openemr would recreate them on loading, which appears not to be happening.
And yet I am able to log in and use it.
Half way along this trail I had a choice: throw in the towel or be more Zen. I chose the latter. Stephen has been a great help.
why are you running 2 instances of openemr?
In order to be able to access my patient records while I am at home as well as at work.
one instance is all that’s needed since it’s a web server so you could connect to it from anywhere but you’d need to do additional configuration
Then I’d need to leave the computer permanently turned on.
But my questions are: (1) Why should it be that the instance of openemr on my home computer appears to have no keys even though it was restored from a backup with keys present and correct? (2) Is this going to be a problem for me?
Thank you.
You’re logging into another instance than that docker you’re listing.
I see. OK, let’s forget about my home computer. But I’ve run into another, hopefully minor problem, with the instance on my work computer, which had been working nicely until today. Are you still up for this?
False alarm - it is working.
I replied, “I see”, but on reflection, I don’t see! Say for example my work computer dies but I have an openemr backup made from it. I buy a new computer, install an OS and openemr in docker, and use my backup to restore my database. That too would be another instance of docker. Is that not an analogous scenario? Presumably what is supposed to happen is that the keys should be imported from the backup. Would or would not that be the case?
I think the issue is determining where openemr is running on your home computer since the keys will be there if you can login.
I can indeed log in.
do you have apache running?
Yes, I have Apache running.
maybe that’s where openemr lives instead of the docker?
I have now uninstalled apache.
I can still log in to openemr.
And
robert@robert-ideacentre-AIO-520-22IKU:~$ docker exec -it $(docker ps | grep _openemr | cut -f 1 -d " ") ls -lrt sites/default/documents/logs_and_misc/methods
total 4
-rwx------ 1 apache 1000 63 Sep 30 2018 README.md
robert@robert-ideacentre-AIO-520-22IKU:~$
I am particularly interested in this now because I am thinking that a good solution for me would be to have, as you suggested, a single instance of openemr running as a server, but on my home computer, which I could log into from my work computer. I think it would probably be better to start a separate thread for that set up, but first I need to make sure that the instance running on my home computer is free of problems.
I believe @stephenwaite is suggesting that there is a different OpenEMR instance running on your home computer than the one without keys. You can run that port listening command to know for sure:
sudo ss -ltpn
I used this command once without openemr loaded and once with openemr loaded. The output was the exactly the same:
robert@robert-ideacentre-AIO-520-22IKU:~$ sudo ss -ltpn
[sudo] password for robert:
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 127.0.0.1:33383 0.0.0.0:* users:(("containerd",pid=1010,fd=12))
LISTEN 0 50 0.0.0.0:139 0.0.0.0:* users:(("smbd",pid=1897,fd=35))
LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:(("docker-proxy",pid=2712,fd=4))
LISTEN 0 10 192.168.1.48:53 0.0.0.0:* users:(("named",pid=1001,fd=28))
LISTEN 0 10 172.17.0.1:53 0.0.0.0:* users:(("named",pid=1001,fd=27))
LISTEN 0 10 172.18.0.1:53 0.0.0.0:* users:(("named",pid=1001,fd=26))
LISTEN 0 10 192.168.1.49:53 0.0.0.0:* users:(("named",pid=1001,fd=25))
LISTEN 0 10 127.0.0.1:53 0.0.0.0:* users:(("named",pid=1001,fd=22))
LISTEN 0 128 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=673,fd=13))
LISTEN 0 5 127.0.0.1:631 0.0.0.0:* users:(("cupsd",pid=747,fd=8))
LISTEN 0 128 127.0.0.1:953 0.0.0.0:* users:(("named",pid=1001,fd=23))
LISTEN 0 128 0.0.0.0:443 0.0.0.0:* users:(("docker-proxy",pid=2691,fd=4))
LISTEN 0 50 0.0.0.0:445 0.0.0.0:* users:(("smbd",pid=1897,fd=34))
LISTEN 0 50 [::]:139 [::]:* users:(("smbd",pid=1897,fd=33))
LISTEN 0 128 [::]:80 [::]:* users:(("docker-proxy",pid=2718,fd=4))
LISTEN 0 32 *:21 *:* users:(("proftpd",pid=1944,fd=0))
LISTEN 0 10 [::]:53 [::]:* users:(("named",pid=1001,fd=21))
LISTEN 0 5 [::1]:631 [::]:* users:(("cupsd",pid=747,fd=7))
LISTEN 0 128 [::1]:953 [::]:* users:(("named",pid=1001,fd=24))
LISTEN 0 128 [::]:443 [::]:* users:(("docker-proxy",pid=2698,fd=4))
LISTEN 0 50 [::]:445 [::]:* users:(("smbd",pid=1897,fd=32))
robert@robert-ideacentre-AIO-520-22IKU:~$