06:09:34.862 Changed loghwm of /opt/ejabberd/logs/ejabberd.log to 20000 Why its taking too much time on these steps and its not raising any error or warning 03:41:39.108 Application fs started on node ' 03:41:39.211 Failed to validate certificate from /opt/ejabberd-18.01/conf/server.pem: self-signed certificateĪccording to these logs it took around 2 minutes loading configuration and 1 minute on FQDN configuration. 03:40:10.836 Application mnesia started on node ' 03:40:10.997 Application os_mon started on node ' 03:40:10.998 FQDN used to check DIGEST-MD5 SASL authentication: ip-10-0-5-113.localdomain 03:38:34.450 Application elixir started on node ' 03:38:34.470 Loading configuration from /opt/ejabberd/conf/ejabberd.yml Secondly i am facing delay while starting ejabberd in my CentOS instance? Is this delay normal for graceful start and shutdown? Did you guys explicitly added warning in new version? We were using the same self signed server.pem bundled with the distribution (in conf dir) but it was not raising this warning before. On ejabberd server bootup or restart we see a warning for server.pem file that its self signed. Was the unexpected behavior? What was the expected result? 06:48:04.019 No certificate found matching 'xxxx-portal': strictly configured clients or server 06:48:03.996 Failed to validate certificate from /opt/ejabberd-18.01/conf/server.pem: self-signed certificate What did not work as expected? Are there error messages in the log? How did you install ejabberd (source, package, distribution)? What operating system (version) are you using?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |