robert@robert-Lenovo-B590:~$ openemr-cmd
Usage: openemr-cmd COMMAND [ARGS]
Usage: openemr-cmd -d <docker name> COMMAND [ARGS]
Options:
-h, --help Show the commands usage
-v, --version Show the openemr-cmd command version
-d Specify the docker id or name to execute commands
Commands:
docker-management:
up Execute: docker-compose up -d
down Execute: docker-compose down -v
start Execute: docker-compose start
stop Execute: docker-compose stop
s, shell Open a docker shell quickly
e, exec Execute commands outside docker
dl, docker-log To check docker log
dn, docker-names To check docker the running docker names
php-management:
bt, build-themes Make changes to any files on your local file system
pl, php-log To check PHP error logs
pr, psr12-report To create a report of PSR12 code styling issues
pf, psr12-fix To fix PSR12 code styling issues
ltr, lint-themes-report To create a report of theme styling issues
ltf, lint-themes-fix To fix theme styling issues
pp, php-parserror To check PHP parsing errors
xl, xdebug-log To check xdebug log
lxp, list-xdebug-profiles To list xdebug profiles
test-management:
ut, unit-test To run unit testing
at, api-test To run api testing
et, e2e-test To run e2e testing
st, services-test To run services testing
ft, fixtures-test To run fixtures testing
vt, validators-test To run validators testing
ct, controllers-test To run controllers testing
ctt, common-test To run common testing
sweep-management:
cs, clean-sweep To run the entire dev tool suite
cst, clean-sweep-tests To run only all the automated tests
reset-mamagement:
dr, dev-reset To reset OpenEMR only
di, dev-install To install OpenEMR (reset needs to be run prior)
dri, dev-reset-install To reset and reinstall OpenEMR
drid, dev-reset-install-demodata To reset and reinstall OpenEMR with demo data
backup-management:
bs, backup-snapshot Create a backup snapshot
rs, restore-snapshot Restore from a snapshot
ls, list-snapshots To list the snapshots
lc, list-capsules List the capsules
gc, get-capsule Copy the capsule from the docker to your host directory
pc, put-capsule Copy the capsule into the docker
ssl-management:
fh, force-https Force https
ufh, un-force-https Removing forcing of https
ossc, on-self-signed-cert Toggle on self signed certificates (on by default)
scc, setup-client-cert Turn on client based cert with designated package
lcc, list-client-certs To list the certificate packages
pcc, put-client-cert To copy certificate package into the docker
ss, sql-ssl Use testing sql ssl CA cert
sso, sql-ssl-off Remove testing sql ssl CA cert
ssc, sql-ssl-client Use testing sql ssl client certs
ssco, sql-ssl-client-off Remove testing sql ssl client certs
css, couchdb-ssl Use testing couchdb ssl CA cert
cso, couchdb-ssl-off Remove testing couchdb ssl CA cert
csc, couchdb-ssl-client Use testing couchdb ssl client certs
csco, couchdb-ssl-client-off Remove testing couchdb ssl client certs
lss, ldap-ssl Use testing ldap ssl CA cert
lso, ldap-ssl-off Remove testing ldap ssl CA cert
lsc, ldap-ssl-client Use testing ldap ssl client certs
lsco, ldap-ssl-client-off Remove testing ldap ssl client certs
multisite-management:
lm, list-multisites List multisites
swtm, set-swagger-to-multisite Direct swagger api testing suite to use a multisite <multisite>
gmb, generate-multisite-bank Create bank of multisites cloned from default <number sites>
em, enable-multisite Turn on support for multisite in setup.php
dm, disable-multisite Turn off support for multisite in setup.php
api-management:
bad, build-api-docs Build and place api documentation/configuration for swagger
roc, register-oauth2-client Register oauth2 client (returns client id/secret)
rocd, register-oauth2-client-demo Register oauth2 client (returns client id/secret) on online demo
swtm, set-swagger-to-multisite Direct swagger api testing suite to use a multisite <multisite>
computational-health-informatics:
irp, import-random-patients Create and import random patients <number patients>
gmb, generate-multisite-bank Create bank of multisites cloned from default <number sites>
webroot-management:
cwb, change-webroot-blank Change webroot to be blank (this is default setting of environment)
cwo, change-webroot-openemr Change webroot to be openemr
others:
ev, ensure-version Upgrade OpenEMR from specified old version to current version
el, enable-ldap Turn on support for LDAP - login credentials are admin:admin
dld, disable-ldap Turn off support for LDAP - standard login credentials
ec, encoding-collation Change the database character set and collation
robert@robert-Lenovo-B590:~$
Try to load OpenEMR and then run openemr-cmd pl
in the terminal to see any errors listed by the docker.
robert@robert-Lenovo-B590:~$ openemr-cmd pl
sh: /root/devtools: not found
sorry, forgot this doesn’t have devtools, try this command instead:
docker exec -it $(docker ps | grep _openemr | cut -f 1 -d " ") tail /var/log/apache2/error.log
robert@robert-Lenovo-B590:~$ docker exec -it $(docker ps | grep _openemr | cut -f 1 -d " ") tail /var/log/apache2/error.log
[Thu Aug 25 14:35:45.588748 2022] [core:notice] [pid 12] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.18.0.2. Set the 'ServerName' directive globally to suppress this message
[Fri Aug 26 06:44:38.688715 2022] [core:warn] [pid 11] AH00098: pid file /run/apache2/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Fri Aug 26 06:44:38.746524 2022] [mpm_prefork:notice] [pid 11] AH00163: Apache/2.4.54 (Unix) OpenSSL/1.1.1q configured -- resuming normal operations
[Fri Aug 26 06:44:38.746610 2022] [core:notice] [pid 11] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.18.0.2. Set the 'ServerName' directive globally to suppress this message
[Fri Aug 26 13:37:51.447515 2022] [mpm_prefork:notice] [pid 12] AH00163: Apache/2.4.54 (Unix) OpenSSL/1.1.1q configured -- resuming normal operations
[Fri Aug 26 13:37:51.447658 2022] [core:notice] [pid 12] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Aug 26 13:40:49.497349 2022] [php:notice] [pid 23] [client 172.18.0.1:46062] OpenEMR Error : Decryption failed authentication.
[Fri Aug 26 13:40:49.497467 2022] [php:notice] [pid 23] [client 172.18.0.1:46062] OpenEMR Error : Key in drive is not compatible (ie. can not be decrypted) with key in database - Exiting.
robert@robert-Lenovo-B590:~$
did you bring in your documents? that’s where the keys are, Blank screen on first start of OpenEMR 5.0.2 - #62 by stephenwaite
Yes, I did bring them in.
either your db wasn’t imported or the keys weren’t copied in or both, or there’s a permission issue
What do you suggest I do?
in your extracted documents find the name of the keys which are most likely under sites/default/documents/logs_and_misc/methods
This contains only a file called README.md containing only the following sentence:
“This holds pieces needed for different versions of encryption.”
I’ll look through the other folders.
The only thing referring to keys that I can find is in the README file in /sites/default/documents/certificates but it pertains to creating certificates and keys. It does not specify any names.
Incidentally, I do not know what a key is in this context or what one looks like. What kind of file should I be looking for?
you should have something like sixa and sixb in the above folder, sites/default/documents/logs_and_misc/methods
, of your extracted backup documents if you were running v6
Actually this is a backup from v7. I recently changed my OS from Lubuntu to LM. I had installed v7 on my old OS (Lubuntu) in order to make the backup, believing that this would be less potentially problematic than a backup from a previous version. Then I installed LM over Lubuntu, installed docker openemr v7 on that (as you know) and then followed the restore procedure as described in the other thread.
There is nothing in the methods folder apart from the readme file and nothing in any other folder that looks like sixa or sixb (or even sevena, sevenb).
are you upgrading an OpenEMR install?
No. I did that before, on my old OS, from 6 to 7. But this is a fresh install of 7 on a fresh install of LM. The back up is made from 7 on my old OS.
what version are you running in production?
In production? Sorry, what do you mean?
which version are you running currently that you’re able to log into and use?
I have version 7 on my home computer, which I am able to log into and use.