I basically want to run some specific functions in the module for various inputs and make sure the output is correct and I do need the server part running for this?Īny suggestions/pointers would be really appreciated. home/ec2-user/ejabberd/logs/raw.log 2>&1 failed with error: 1 and output:ĮRROR: ct failed while processing /home/ec2-user/ejabberd: rebar_abortĪlso, is there a recommended framework to write ejabberd/erlang unit tests? include /home/ec2-user/ejabberd/deps/xmpp/include > include /home/ec2-user/ejabberd/deps/fast_xml/include include /home/ec2-user/ejabberd/include -include /home/ec2-user/ejabberd/deps/p1_utils/include group mnesia -ct_hooks cth_surefire -include /home/ec2-user/ejabberd/tools cover /home/ec2-user/ejabberd/cover.spec -suite test/ejabberd_SUITE.erl "/home/ec2-user/ejabberd/logs" -env TEST_DIR "/home/ec2-user/ejabberd/test" "/usr/local/bin/rebar" "/home/ec2-user/ejabberd/." -include "/home/ec2-user/ejabberd/include" "/home/ec2-user/ejabberd/deps/lager/ebin" "/usr/local/bin/rebar/rebar/ebin" "/home/ec2-user/ejabberd/deps/uuid/ebin" "/home/ec2-user/ejabberd/deps/erlcloud/ebin" "/home/ec2-user/ejabberd/deps/xmpp/ebin" "/home/ec2-user/ejabberd/deps/cache_tab/ebin" "/home/ec2-user/ejabberd/deps/pkix/ebin" "/home/ec2-user/ejabberd/deps/p1_oauth2/ebin" "/home/ec2-user/ejabberd/deps/mqtree/ebin" "/home/ec2-user/ejabberd/deps/eimp/ebin" "/home/ec2-user/ejabberd/deps/p1_mysql/ebin" "/home/ec2-user/ejabberd/deps/p1_acme/ebin" "/home/ec2-user/ejabberd/deps/meck/ebin" "/home/ec2-user/ejabberd/deps/goldrush/ebin" "/home/ec2-user/ejabberd/deps/eini/ebin" "/home/ec2-user/ejabberd/deps/jsx/ebin" "/home/ec2-user/ejabberd/deps/lhttpc/ebin" "/home/ec2-user/ejabberd/deps/proper/ebin" "/home/ec2-user/ejabberd/deps/base16/ebin" "/home/ec2-user/ejabberd/deps/fast_xml/ebin" "/home/ec2-user/ejabberd/deps/unicode_util_compat/ebin" "/home/ec2-user/ejabberd/deps/ezlib/ebin" "/home/ec2-user/ejabberd/deps/fast_tls/ebin" "/home/ec2-user/ejabberd/deps/fast_yaml/ebin" "/home/ec2-user/ejabberd/deps/stringprep/ebin" "/home/ec2-user/ejabberd/deps/p1_utils/ebin" "/home/ec2-user/ejabberd/deps/base64url/ebin" "/home/ec2-user/ejabberd/deps/yconf/ebin" "/home/ec2-user/ejabberd/deps/jiffy/ebin" "/home/ec2-user/ejabberd/deps/jose/ebin" "/home/ec2-user/ejabberd/deps/idna/ebin" I installed rebar and made sure to have a running ejabberd server and followed the steps here to:īut I get the following error: ejabberd]$CT_BACKENDS=mnesia rebar ct suites=ejabberd groups=mnesiaĮRROR: ct_run -noshell -pa "/home/ec2-user/ejabberd/ebin" Now I have a ejabberd container that has the CA certs required permanently.How do I run ejabberd tests in the test folder? By changing image: to build: # image: ejabberd/ecs:latest FROM ejabberd/ecs:latestĬhange my docker-compose.yml from using an image to building the Dockerfile. This means I have to build my own container by creating my own build/ejabbed/Dockerfile. Then I have to make the change permanent. Now I can see the certificates load without error in the log. A quick proof of this by going into the container and add ca-certificates and restarting ejabberd: docker-compose exec -u root ejabberd sh These are Let’s Encrypt certs and I know they are trusted, so why the error? Turns out the image ejabberd/ecs:latest doesn’t come with any CA certificates. When I started the service it complains that the certificate is signed by an untrusted CA! ejabberd/conf/certs:/home/ejabberd/conf/certs:rw ejabberd/conf/ejabberd.yml:/home/ejabberd/conf/ejabberd.yml:rw ejabberd/upload:/home/ejabberd/upload:rw ejabberd/database:/home/ejabberd/database:rw Code Revisions 1 Download ZIP ejabberd config to make conversations client on android work perfectly Raw ejabberd.yml ejabberd configuration file The parameters used in this configuration file are explained in more detail in the ejabberd Installation and Operation Guide. Which are mounted using my docker-compose.yml ejabberd: home/ejabberd/conf/certs/fullchain.pem Then add in the location of the certs I’m using: certfiles: # "/.well-known/acme-challenge": ejabberd_acme Should be easy enough, all I have to do is comment out the acme: stanza and the request_handlers:, maybe just the request_handler: would do it. This meant I could switch to the staging ACME, which would mean untrusted CA certificate errors, or use a previously issued certificate set until my blockage was cleared. When running the ejabberd docker image in my container set I ran into a problem where I hit the rate limiter on Let’s Encrypt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |