Implement an oracle policy for the switching bandit problem, to have a strong baseline

Given an efficient bandit policy designed for the stationary bandit problem, an oracle that knows the location of the breakpoints can restart the policy at each breakpoint.
It is simple to implement (using BaseWrapperPolicy) and can act as an efficient baseline for experiments comparing several policies on switching bandit problems!

See the documentation for class Policies.OracleSequentiallyRestartPolicy.
Example:

It works quite fine, but it has no reason to be optimal.


Better Media Sections

It would be nice to make selecting media sections a bit easier:
Being able to paste in time.
Use the scrollwheel/arrow keys to quickly add/subtract time.
Related to above, an option to separate hours, minutes and seconds for easier editting; not needing to add ":" or erasing it by mistake.
An option to add the "- section x to y" in the title even with only one section.

I've added the copy/paste functionality in v2.13 (took me 8 months for some reason, sorry about that). The other suggestions are too much of a headache to implement, I'm afraid. I might revisit the issue at some point, but I'll be focusing on other priorities for now.


Google reCAPTCHA (v3) token expires after 2 minutes, but not renewed in plugin

According to the following page:
https://developers.google.com/recaptcha/docs/v3
the token expires after two minutes, but I don't find anything in the plugin that takes this into account. As far as I understand the token is created on page load and verified along with the form submission. This results in all submissions being flagged as spam if a user is active on a page for longer than 2 minutes before submitting a form.
This was the case on one of my pages with an extensive form (job application), where all submissions were being flagged as spam even with a sensitivity of 0 (lowest). The form is submitted via an AJAX-call, I'm not sure whether that makes a difference.
I've solved this by refreshing the token via Javascript on submission of the form, but it would be better if the plugin takes this expiration time into account.

@MetaDevelopment Have you tried updating the 'recaptchaTimeout'        => 5, value in your configi/contact-form-extensions.php file?
These are all of the options that you can override in that config file:
<?php
use craft\helpers\App;

return [
	'enableDatabase'          => true,
	'enableConfirmationEmail' => true,
	'enableTemplateOverwrite' => true,
	'notificationTemplate'    => '_emails/contact/notification',
	'confirmationTemplate'    => '_emails/contact/confirmation',
	'confirmationSubject'     => 'Thank you for your contact!',
	'recaptcha'               => (bool)App::env('RECAPTCHA') ?: true,
	'recaptchaVersion'        => '3',
	'recaptchaSiteKey'        => App::env('RECAPTCHA_SITE_KEY'),
	'recaptchaSecretKey'      => App::env('RECAPTCHA_SECRET_KEY'),
	'recaptchaHideBadge'      => true,
	'recaptchaDataBadge'      => 'bottomright',
	'recaptchaTimeout'        => 5,
	'recaptchaDebug'          => (bool)App::env('RECAPTCHA_DEBUG') ?: true,
	'recaptchaThreshold'      => .5,
];

There's currently no way of changing that value based on the form itself, but hopefully that helps 👍

@DynamiteGoesBoom Thanks for the reply and suggestion!
The 'recaptchaTimeout' value can also be set via the plugin's settings in the control panel. I thought that this setting applies to the amount of seconds after which the plugin will no longer wait for a response from Google, for example when the Google services are down. But I don't find any documentation about it, so I might be wrong.
However, in my use-case this is set to the default of 5 and the tests I did proved that the actual "token expiration time" nevertheless was 2 minutes, because I tested submitting some forms after waiting a bit longer than 2 minutes, but certainly not 5.
I'm quite certain that this "token expiration time" can not be adjusted, a quick search on "reCaptcha token expiration" shows that many people struggle with this and most of the time someone suggests to add a function which refreshes the token each 90 seconds or so. But it is advised by Google not to do that (as also said in an answer on one of the stack overflow questions) but rather to only call execute when the user takes the action instead of on page load. This can be found in their first note in the blue bar on the linked page (https://developers.google.com/recaptcha/docs/v3):

"Note: reCAPTCHA tokens expire after two minutes. If you're protecting an action with reCAPTCHA, make sure to call execute when the user takes the action rather than on page load."

Regarding the tags on this issue, I believe "bug" is more appropriate than "feature request" since this isn't an enhancement, but rather something to make sure this existing feature of the plugin actually works properly.

@MetaDevelopment let me look into this to see what it will take. Any suggestions or pull requests are welcome. Thanks!

@rosskenney I really don't know much about PHP-development, so I can't help there or with an actual pull request. However, as I understand from that Google page as well as the following guide:
https://code.tutsplus.com/tutorials/example-of-how-to-add-google-recaptcha-v3-to-a-php-form--cms-33752
The token needs to be generated via Javascript upon submission of the form. That's also how I fixed it in my use case. The link to the Google page again:
https://developers.google.com/recaptcha/docs/v3
The part under "Programmatically invoke the challenge" is essentially what needs to happen: (re-)request the token and send that along with the form.
Or just include instructions in the documentation to include this JS-code in the JS of your site, and that it should be linked to the correct form(s).
It's probably easier to then submit the form via an AJAX-submission - this is the code I use (with jQuery, and all the forms have the "form" class):
$('.form').submit(function(e) {
    e.preventDefault();

    let $form = $(this);
    if ($form.hasClass('is-submitting')) return false;

    grecaptcha.ready(function() {
        grecaptcha.execute('[reCAPTCHA_site_key]', {action: 'submit'}).then(function(token) {
            $('#g-recaptcha-response').val(token);

            $form.addClass('is-submitting').removeClass('is-error');

            // Send it to the server
            $.ajax({
                url: $form.attr('action'),
                type: $form.attr('method'),
                data: new FormData($form.get(0)),
                dataType: 'json',
                cache: false,
                contentType: false,
                processData: false,
                complete: function() {
                    $form.removeClass('is-submitting');
                },
                success: function(data) {
                    $form.addClass(data.success == true ? 'is-success' : 'is-error' );
                    $form.addClass('submitted');
                },
                error: function() {
                    alert('Something went wrong, please try again later');
                }
            });
        });
    });
});

No worries on the php/plugin side. Thanks for those links. I'll have a look to see if we can refresh the token after the form is submitted to the plugin via AJAX.

@DynamiteGoesBoom does this not get satisfied by the PR we received?

@rosskenney Oh yep, just didn't close it. I'll do that now and thanks for checking!


Consider revisiting identifiers storage

Consider revisiting metadata storage of identifiers from dict to an array in the backend?
- would greatly simplify serialization, deserialization and error handling on the frontend

Here's a use cases which requires that we implement this method.
In the deposit form, we need to be able to send identifiers without necessarily providing a scheme. For instance something like:
{
   "identifiers": [{"scheme": "", "value": "0000-0001-8135-3489"}]
}

This way the backend, can automatically determine the scheme of the identifier. If we use the dictionary structure:
{
   "identifiers": {
       "<scheme>": "<identifier>",
       "<scheme>": "<identifier>",
   }
}

Then, we cannot send multiple identifiers.

Here's a use cases which requires that we implement this method.
In the deposit form, we need to be able to send identifiers without necessarily providing a scheme. For instance something like:
{
   "identifiers": [{"scheme": "", "value": "0000-0001-8135-3489"}]
}

This way the backend, can automatically determine the scheme of the identifier. If we use the dictionary structure:
{
   "identifiers": {
       "<scheme>": "<identifier>",
       "<scheme>": "<identifier>",
   }
}

Then, we cannot send multiple identifiers.


[After #182][ml-service] Add service APIs using pipeline d-bus interface

Implement some service APIs using pipeline d-bus interface
Add gtest and GTestDBus based unittest for ml-service-agent-client. It use session mode d-bus to test the features.

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #185. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @anyj0527, tests/capi/unittest_capi_service_agent_client.cc does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @anyj0527, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/185-202207261053200.67186689376831-a38a3ad457016ae2b2449bd86b1028c6588388cd/.

:octocat: cibot: @anyj0527, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/185-202207261114390.22790503501892-0ccab1defac97b6821a15afb32a177fdb8e9a07a/.

The failed test would be fixed after the recent changes in nnstreamer/nnstreamer-edge are merged into the latest tizen snapshot

:octocat: cibot: @anyj0527, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/185-202207291114200.17487001419067-34e4c47fec03a1c1469e3b2b9879f7aedee8052a/.

:octocat: cibot: @anyj0527, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/185-202208042027290.49794602394104-a5eb8b98dd8d92cdd005a1ba7e1399bade8c3b46/.

:octocat: cibot: @anyj0527, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/185-202208050903240.64104104042053-a34d6cffb623fd18c961acdeadca63b3fdbbf6e7/.

:octocat: cibot: @anyj0527, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/185-202208121652310.78950309753418-1791cbf6863287b97a7c3cd33460126894140da8/.


Decide how to deal with global flag names in kubectl-gs

kubectl provides some flags that are used with many commands. Examples:

--cluster: The name of the kubeconfig cluster to use
--context: The name of the kubeconfig context to use
-n, --namespace: If present, the namespace scope for this CLI request

See kubectl options for more.
We are already using flags with the same name in some of our commands and wonder what the consequence of this is. Specifically:

If we use a flag (e. g. --namespace) for a specific purpose in a plug-in command, will it prevent us from using the flag in the sense of the common options?
Does the position/order of flags have an impact on the command execution? Ideally it should not.

Example: kubectl gs template app

Template App CR.

Usage:
  kubectl gs template app [flags]

Flags:
      --app-name string                 Optionally set a different name for the App CR.
      --catalog string                  Catalog name where app is stored.
      --cluster string                  Name of the cluster the app will be deployed to.
      --defaulting-enabled              Don't template fields that will be defaulted. (default true)
  -h, --help                            help for app
      --name string                     Name of the app in the Catalog.
      --namespace string                Namespace where the app will be deployed.
      --namespace-annotations strings   Namespace configuration annotations in form key=value.
      --namespace-labels strings        Namespace configuration labels in form key=value.
      --user-configmap string           Path to the user values configmap YAML file.
      --user-secret string              Path to the user secrets YAML file.
      --version string                  App version to be installed.

Global Flags:
      --debug   Toggle debug mode, for seeing full error output.

Here, the flags --cluster and --namespace clash with the purpose specified by common options.
Example: kubectl gs update app

Update App CR.

Updates given app with the provided values.

Options:
  --name <name>              App CR name to update.
  --namespace <cluster>      Cluster to update the app on.
  --version <version>        New version to update the app to.

Usage:
  kubectl gs update app --name <app-name> --namespace <cluster-namespace> --version <updated-app-version> [flags]

Examples:
  # Display this help
kubectl gs update app --help

# Update app version
kubectl gs update app --name hello-world-app --namespace ab01c --version 0.2.0

Flags:
      --allow-missing-template-keys    If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
      --as string                      Username to impersonate for the operation
      --as-group stringArray           Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
      --cache-dir string               Default HTTP cache directory (default "/Users/marian/.kube/http-cache")
      --certificate-authority string   Path to a cert file for the certificate authority
      --client-certificate string      Path to a client certificate file for TLS
      --client-key string              Path to a client key file for TLS
      --cluster string                 The name of the kubeconfig cluster to use
      --context string                 The name of the kubeconfig context to use
  -h, --help                           help for app
      --insecure-skip-tls-verify       If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
      --kubeconfig string              Path to the kubeconfig file to use for CLI requests.
  -n, --namespace string               If present, the namespace scope for this CLI request
  -o, --output string                  Output format. One of: json|yaml|name|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-file.
      --request-timeout string         The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests. (default "0")
  -s, --server string                  The address and port of the Kubernetes API server
      --template string                Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
      --tls-server-name string         Server name to use for server certificate validation. If it is not provided, the hostname used to contact the server is used
      --token string                   Bearer token for authentication to the API server
      --user string                    The name of the kubeconfig user to use

Global Flags:
      --debug   Toggle debug mode, for seeing full error output.

Here the --namespace flag is defined both for the command and as a common flag.
Tasks

[ ] Change the existing conflicting local flag names and update command documentation
[ ] Document global flags
[ ] Investigate whether there is a way to automate and enforce this (e.g. in CI)

As of the latest kubectl-gs release (https://github.com/giantswarm/kubectl-gs/releases/tag/v2.19.0), we don't observe the local --namespace flag anymore (e.g. in the template app command). Has this been overwritten, or has functionality been accidentally removed?

The template app command has several local flags which are in conflict with the global flags. It seems however that local overrides global.
This command
kubectl gs template app --catalog=catalog --name=name --namespace=namespace --cluster=cluster --version=1.2.3

produces this output:
---
apiVersion: application.giantswarm.io/v1alpha1
kind: App
metadata:
  name: name
  namespace: cluster
spec:
  catalog: catalog
  kubeConfig:
    inCluster: false
  name: name
  namespace: namespace
  version: 1.2.3

So the --cluster and --namespace flags are interpreted as local, making it impossible to use the global flags with the same name.
Positioning does not change this. The following command produces the same result as the one above:
kubectl gs --cluster=cluster template app --catalog=catalog --name=name --namespace=namespace --version=1.2.3

Refinement August 19th 2022
Ideas:

Rename local flags that duplicate global flags (we don't have control over the global/upstream flags, but we can change the local ones)
We need a way to prevent kubectl-gs developers from introducing conflicting flags without relying on Team Rainbow review on every PR

Overriding a persistent flag with a flag is allowed in cobra

Actions:

[ ] Change the existing conflicting local flag names and update command documentation
[ ] Document global flags
[ ] Investigate whether there is a way to automate and enforce this (e.g. in CI)

Notes from refinement

Rename --namespace to --target-namespace
Rename --cluster to --cluster-name
Update usage and documentation
Warn users in case they use --cluster and --namespace that hey are deprecated and will be removed in the new major version
Investigate if it's possible to remove --cluster and --namespace from the global flags and mark them as deprecated in the local flags
Investigate which flags are available in the kubectl-gs update app command and align the Usage output


[docs]: Update README.md Description

Detailed description
Review and update the project's README.md file as mentioned in template issue no 1
Context
this will help to better understandinga
Possible implementation
No response
Additional information
I would like to work on it under gssoc23
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@suzy-g38 Thanks for creating the issue.
Do you want to work on this issue?


Cannot pass a Map instance as a property

When I pass an object as a property it works like I would expect.
If however i pass a Map instance as a property, the tonic component gets "[object Map]" instead of the actual map instance, it looks like the html method only understands object literals and not different builtin types.
It would be nice to support Map / Set / WeakMap and have them behave the same object literals.

I recently noticed this with a Set recently, i looked the other way by doing [...set] but this would be good, it should be easy to implement too.

i looked the other way by effectively doing object=${{ map: map }} ...


Feature Request - Receive and emit messages from the UI

Hi
Currently the admin-ui let us gather useful information about connected sockets, rooms for a targeted server…
What do you envision as the next steps?
I think this would be very useful if it we could display all messages received in a room and also offer the possibility to emit messages to it. This way it would allow to gather even more clues about what's happening during a debug session and test various behaviors.
Thanks a lot for this tool

Thanks a lot for the feedback :heart:

I think this would be very useful if it we could display all messages received in a room

That's a great idea! I don't think we currently have the ability to track it at the room level though.
Here's a few additional features that I had in mind:

an histogram of all events sent/received by the server in the last X minutes
an histogram of all connections/disconnections/connection errors
the ability to emit a message a given socket/room
a production mode, which tracks a little less details (in order to solve https://github.com/socketio/socket.io-admin-ui/issues/22)

Update: the receive part is now implemented: https://github.com/socketio/socket.io-admin-ui/commit/8542601b55022f6ca00b677b7d7c7664a326526f

@darrachequesne how about this task, especially:

the ability to emit a message a given socket/room

is it possible that it will be introduced in upcoming months? or you won't work on this project anymore?

Yep, it's on my to-do list!
No specific ETA, but if there is enough demand for this feature it could be prioritized.


pulley: Fill out bnot lowering

Gets some embenchen_*.wast tests passing.
cc https://github.com/bytecodealliance/wasmtime/issues/9783

Note this is based on https://github.com/bytecodealliance/wasmtime/pull/9815 which is in turn based on https://github.com/bytecodealliance/wasmtime/pull/9814


Upgrade to boot 3.0

Hi,
This is an experiment running an automatic upgrade to adopt Spring Boot 3.0 using Tanzu Spring Application Advisor. It is still work in progress. Some of the learnings we are accumulating for this example are:

This project can't be upgraded to boot 3.0 until spring-security-saml-extensions are not migrated to Spring security. https://spring.io/blog/2020/09/22/spring-security-saml-extensions-1-x-eol-on-october-6-2021 .

On the other hand, looks like you are using spring-security-saml 1.0.x instead of 2.0.x, which uses Spring security 5.2.x. This means, that in our end, the application requires the following upgrade plan for upgrading until boot 3.0.

Step 1:
*  Upgrade spring-security-saml 1.0.x to 2.0.x
Step 2:
* Replace spring-security-saml 2.0.x for spring-security 5.8.x
Step 3:
* Upgrade spring-framework from 5.3.x to 6.0.x
* Upgrade spring-security from 5.8.x to 6.0.x
* Upgrade spring-ldap from 2.4.x to 3.0.x
* Upgrade spring-boot from 2.7.x to 3.0.x
* Upgrade spring-retry from 1.3.x to 2.0.x

The dependency versions can't be upgraded in the way they are defined, but looks like the main reason is to overwrite the dependency resolution. This means that dependency versions should be changed manually.

FYI: https://github.com/cloudfoundry/uaa/issues/2561 , https://github.com/cloudfoundry/uaa/issues/2115

@rpau we will do the upgrade soon, now all legacy parts are removed

I am sending a PR at this moment.

https://github.com/cloudfoundry/uaa/pull/3171


docs(whitepaper): tiered storage plugins design

Description
We need to design storage with tiers instead of focusing on the type of schema the data has (which is also a valid concern, but the tiers are much more important/significant).
Examples of tiers would be:

Storage for data relevant/accessible to the API server
Storage for data relevant/accessible to the Node (e.g. cluster of API servers)
Storage for data relevant/accessible to the Consortium (needs consortium since here the data is shared/accessed among different consortium members who don't necessarily trust each other implicitly.

Context:
There is an initial proposal in the whitepaper that talks about having different packages with plugins for relational data/documents/key value storage so that plugin developers can optimize their code by using the most fitting storage engines. This is cool, but what's much more important is that we give plugins the flexibility to store private data of a consortium member "locally" (in the sense that other members may not need to have access to this data nor it may be relevant to them at all).
In a way a consortium can also be thought of as a large system comprised of micro-services where each member can have their own micro-service with the data held internally to the service and of course some data needed/being available on a global scale for all.
Acceptance Criteria

Whitepaper is updated with a proposed future design of the storage tiers and what they should be storing
Example implementations are mentioned as well such as having a global storage plugin powered by a permissionless with multi-sig wallets ledger or a permissioned ledger that is co-operated by the members making up the consortium (albeit separately from the Cactus nodes themselves)

cc: @jonathan-m-hamilton @takeutak @sfuji822

@RafaelAPB All agreed and all help is welcome so thank you very much in advance for this one as well! :-) Added this to the v1.0.0 milestone.

Happy to discuss this on the meetings!


Extend existing dataset of any report

Is your feature request related to a problem? Please describe.
At this moment there is now way to add new field inside the existing report.
Describe the solution you'd like
As a Business Central dev I would like:

Extend existing dataset of any report (standard and own maded) as we do with pages and tables.

I would recommend split AL report object to dataset object and layout object
Eg: dataset Id MyExtension extends MyTargeDataset
{
fields
{
// Add changes to datasset fields here
}
var
myInt: Integer;
}

After extending the dataset I would like to add new custom field to report layout with DEV tools or with business central report layout designer

Describe alternatives you've considered
As a business Central dev I would like to set up dataset extensions:

I would like to use Business Central and extend or add new datasets inside applications without any coding. More like the click and point.
I would like to make those datasets also available to AL developer.
After defining the dataset inside Business central I would like to add new custom field to report layout with DEV tools or with business central report layout designer

Additional context
Sorry if it sounds like a dublicate!

see Report extendibility #1452

Thanks @gudrunleos, I'll close this as a duplicate of #1452.


Webpack and Babel

I have zero experience in setting up Webpack and Babel but apparently that's going to be needed to ESMify this package and remove a lot of the old-school JS stuff in here.
Modernizing and deleting things to simplify life sounds good, and made #288 seem appealing, but it's turned into a bit of a mess as it now seems like we'll need to make everything completely ESM and then convert to CommonJS format with Babel?
If anyone can do this I will pay them money, and if anyone wants this but doesn't know how please sponsor the package so that I have money to pay whoever does it.

Or do we use SWC as its quicker or something. https://blog.logrocket.com/why-you-should-use-swc/

I recently wrapped this library to inline a bunch of things, and introduced babel, if someone picks this issue up the changes might provide some good inspiration: https://github.com/Rhosys/openapi-resolver.js

I don't think Webpack or Babel are needed for this.  If we want the codebase to be ESM, we can set type to module in package.json and have conditional exports that look like:
{
  "exports": {
    "import": "lib/index.js",
    "require": "lib/index.cjs"
  }
}

Then index.cjs can re-export what's in index.js but for CommonJS.  This should work for Node versions all the way back to 12.6.x.

@kevinswiber oh if that works then brilliant! I had a quick go and again clearly don't know what I'm doing because my wild stabs are giving more errors.


Theming/Branding Options

This YUIDoc theme is amazing! Was wondering if you would be open to adding just a few theme options. Very simple stuff, mainly being able to specify a custom logo to replace the Ember logo, and maybe a small color palette for the accent colors. I can work on it if your open to it, if not no worries!

@pzuraq yeah that sounds good to me. PRs are always welcome 😸


readme update!!

Fix configuration to build.gradle.

I have merched this into my branch, along with all the other pending pull-requests:
https://github.com/arberg/SingleDateAndTimePicker

Obsolete if #267 gets merged.


[Fix-8398] Rectify this issue with failing to initialize the database under the postgresql database.

Purpose of the pull request
This PR will close #8398 .

Brief change log

Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

Codecov Report

Merging #8399 (f1dd909) into dev (ca086c0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #8399   +/-   ##
=========================================
  Coverage     45.36%   45.36%
  Complexity     4028     4028
=========================================
  Files           686      686
  Lines         26700    26700
  Branches       2866     2866
=========================================
  Hits          12112    12112
  Misses        13446    13446
  Partials       1142     1142

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ca086c0...f1dd909. Read the comment docs.


Add nixpkgs documentation about how to create a derivation with Vim plugins

Any progress here? I think we can merge this as-is, can't we?

Looks OK to me, after fixing the author :-)

Thanks @MarcWeber! (I somehow missed this half a year ago.)


 Also, map_mul can be stated for a BundledHom because coercions of BundledEmbeddings and BundledEquivs are unfolded to BundledHoms (with two and three arrows, resp.).
There are a few things I don't know how to do with this approach yet:

auto upgrade from MulEquiv to MonoidHom; maybe,

class HasProp {p : (A → B) → Prop} (f : BundledHom A B p) (q : (A → B) → Prop) : Prop where
  prop : q f

instead of WeakerPred?

FunLikes that have other data fields (e.g., Finsupp).
define a MulHom with nice where syntax instead of

def f : MulHom A B where
  toFun := f
  property := { map_mul := _ }

A similar redesign can be done with SetLike. Then we can have CanMap/CanComap classes (in Prop) that say something like p s → p (f '' s) with p in different universes.

From another Zulip thread:
I'm somewhat wary of the (p : (A → B) → Prop) predicates as parameters to the classes. These can have quite nontrivial equalities and equivalences that typeclasses cannot see through, or see through only very slowly. For example: if someone writes a monoid hom when an additive hom is expected, will Lean end up trying to unify * with +? This tends to get expensive quite quickly. Quite probably, we're okay as long as we stick to predicates of the form structure IsMonoidHom extends IsMulHom, IsOneHom (rather than IsMonoidHom := IsMulHom ∧ IsOneHom; we'd also avoid issues that would arise if someone writes the predicate as IsOneHom ∧ IsMulHom).

I tried rewriting Algebra.Hom.Group, replacing the bundled hom structures with abbrevs for BundledHom.
It was quite tedious to replace the nice where syntax with property := { map_mul := sorry, map_one := sorry }. Is there a way to define a "custom constructor" for an abbrev type, of the form MonoidHom.mk : ∀ (f : A → B) (map_one : f 1 = 1) (map_mul : ∀ x y, f (x * y) = f x * f y), BundledHom A B IsMonoidHom?
I kept the HomClasses around, which saved a lot of refactoring. Of course that meant that there wasn't much improvement in actual ease of use over the existing situation.
Some notes:

Defining ComposablePred instances for conjunctions of predicates (like IsMonoidHom from IsMulHom and IsOneHom) gets tedious very quickly. Can we automate this somehow?
I struggled in Lean 3 with choosing which params to make outParam in my attempts at ComposablePred and InvertiblePred, it seems even in basic files each parameter has to be inferred. In Lean 4 metavariables are allowed in instance search goals, so we could choose to use no outParams at all (as long as we keep the search space small enough).
Should we allow composition of a MulHom with a MonoidHom by adding an instance for ComposablePred p q r from ComposablePred p' q' r that takes in WeakerPred p p' and WeakerPred q q'? (Or maybe weaken p and q separately?)

It was quite tedious to replace the nice where syntax with property := { map_mul := sorry, map_one := sorry }. Is there a way to define a "custom constructor" for an abbrev type, of the form MonoidHom.mk : ∀ (f : A → B) (map_one : f 1 = 1) (map_mul : ∀ x y, f (x * y) = f x * f y), BundledHom A B IsMonoidHom?

If we want to do this, then we'll need an extended syntax. E.g., an ability to write something like
structure BundledHom α β (p : (α → β) → Prop) where
  toFun : α → β
  structure prop : p toFun -- or some other marker

structure IsMulHom [Mul α] [Mul β] (f : α → β) : Prop where
  map_mul : ∀ x y, f (x * y) = f x * f y

def f [Mul α] : BundledHom α α IsMulHom where
  toFun := id
  map_mul x y := rfl

* Defining `ComposablePred` instances for conjunctions of predicates (like `IsMonoidHom` from `IsMulHom` and `IsOneHom`) gets tedious very quickly. Can we automate this somehow?

We can put mk_iff on IsMonoidHom, then rw [isMonoidHom_iff]; infer_instance.

* I struggled in Lean 3 with choosing which params to make `outParam` in my attempts at `ComposablePred`

I thought that [ComposablePred p q r] should have r as an outParam, the same way we deal with ring_hom_triple. But I never did an experiment.

* Should we allow composition of a `MulHom` with a `MonoidHom` by adding an instance for `ComposablePred p q r` from `ComposablePred p' q' r` that takes in `WeakerPred p p'` and `WeakerPred q q'`? (Or maybe weaken `p` and `q` separately?)

IMHO, we should require explicit coercions, otherwise we'll have a huge search space (e.g., how Lean should decide which predicate to use for a composition of a ring homomorphism and a linear map?).


get_real_metric_path still does not properly handle some symlinks

What I attempted: /home/graphite-web/storage/whisper is a symbolic link pointing to /path/foo/whisper and /path/foo/whisper/collectd is a symbolic link pointing to /path/foo/collectd, which contains host metrics
Expected Result: all whisper files are found after looking up real metric path
Witnessed Result: no whisper files are found after looking up real metric path because the beginning of the real metric path gets truncated
System Details:

OS / Version: Ubuntu 16.04.2 LTS
Python Version: 2.7.12
Django Version: 1.8.7
graphite-web Version: 1.1.3

Related to #1738  and #2012

Still working on test case updates, but they have been a bit painful to run in my environment compared to the test harness I had for rapid prototyping of the fix.


where do you get the full list of fields of events to extract from the demo?

for example  parser.parse_event("player_hurt"), it didn't appear in the readme docs, so I searched the repo for player_hurt and because I couldn't find it I'm guessing it's contained in the demo file itself. I'd like to know where I can get these additional fields in the demo because they don't appear in the docs.

never mind, found it here

parser.list_game_events() gives you a list off all events in the demo.


chore(deps): update dependency @types/react-router to v4

This PR contains the following updates:

Package
Type
Update
Change
References

@types/react-router
devDependencies
major
2.0.54 -> 4.4.5
source

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 4.x releases. However, if you upgrade to 4.x manually then Renovate will then reenable updates for minor and patch updates automatically.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Add support for lttng

In order to support builds against lttng, lets add some packageconfig option.

this isn't enough, we also need to patch the native side of things, afaik via:
qtbase-native_git.bb:PACKAGECONFIG[lttng] = "-trace lttng,-no-trace,"
nativesdk-qtbase_git.bb:PACKAGECONFIG[lttng] = "-trace lttng,-no-trace,"

or not, based on: https://codereview.qt-project.org/c/qt/qtbase/+/276857 then tracegen will always be compiled

In zeus-next and master-next now.
Please add your Signed-off-by tag as well.


Update flytestdlib to 0.4.17

Signed-off-by: Haytham Abuelfutuh<EMAIL_ADDRESS>https://github.com/flyteorg/flyte/issues/2263

if you run make generate does this produce no other diff?


Demo Test failed

Hi,
I want to test kopano and made the default settings from your demo environment. But it is not working.
I followed your guide.
Error:
mail          | 2018-11-20 21:19:50,571 INFO spawned: 'saslauthd_ldap' with pid 959
mail          | 2018-11-20 21:19:50,572 INFO success: saslauthd_ldap entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | saslauthd_ldap: started
ldap          | 5bf46c66 conn=1015 fd=12 ACCEPT from IP=<IP_ADDRESS>:55462 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c66 conn=1015 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c66 conn=1015 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:50 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c66 conn=1015 op=1 UNBIND
ldap          | 5bf46c66 conn=1015 fd=12 closed
kopano_server | Tue Nov 20 21:19:50 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:50 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:50 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)

Full Log:
ldap          | *** CONTAINER_LOG_LEVEL = 4 (debug)
ldap          | *** Set environment for startup files
ldap          | *** ignore : LANG = en_US.UTF-8 (keep LANG = en_US.UTF-8 )
ldap          | *** ignore : LANGUAGE = en_US.UTF-8 (keep LANGUAGE = en_US:en )
ldap          | *** Environment files will be proccessed in this order :
ldap          | Caution: previously defined variables will not be overriden.
ldap          | /container/environment/99-default/default.yaml
ldap          |
ldap          | *** --- process file : /container/environment/99-default/default.yaml ---
ldap          | *** Run commands before startup...
ldap          | *** Running /container/run/startup/:ssl-tools...
ldap          | *** ------------ Environment dump ------------
ldap          | *** LANG = en_US.UTF-8
ldap          | *** LDAP_LOG_LEVEL = 256
ldap          | *** LC_ALL = en_US.UTF-8
ldap          | *** CONTAINER_SERVICE_DIR = /container/run/service
ldap          | *** LDAP_READONLY_USER_PASSWORD = kopano123
ldap          | *** LANGUAGE = en_US:en
ldap          | *** LDAP_ORGANISATION = "Kopano Demo"
ldap          | *** HOSTNAME = b7da7f51cd4f
ldap          | *** CONTAINER_STATE_DIR = /container/run/state
ldap          | *** LC_CTYPE = en_US.UTF-8
ldap          | *** LDAP_ADMIN_PASSWORD = kopano123
ldap          | *** LDAP_READONLY_USER = true
ldap          | *** INITRD = no
ldap          | *** CONTAINER_LOG_LEVEL = 4
ldap          | *** LDAP_DOMAIN = kopano.demo
ldap          | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap          | *** HOME = /root
ldap          | *** LDAP_BASE_DN = dc=kopano,dc=demo
ldap          | *** ------------------------------------------
kopano_ssl exited with code 0
ldap          | *** Running /container/run/startup/slapd...
ldap          | *** ------------ Environment dump ------------
ldap          | *** LANG = en_US.UTF-8
ldap          | *** LDAP_LOG_LEVEL = 256
ldap          | *** CONTAINER_SERVICE_DIR = /container/run/service
ldap          | *** LDAP_READONLY_USER_PASSWORD = kopano123
ldap          | *** LANGUAGE = en_US:en
ldap          | *** LDAP_ORGANISATION = "Kopano Demo"
ldap          | *** HOSTNAME = b7da7f51cd4f
ldap          | *** CONTAINER_STATE_DIR = /container/run/state
ldap          | *** LC_CTYPE = en_US.UTF-8
ldap          | *** LDAP_ADMIN_PASSWORD = kopano123
ldap          | *** LDAP_READONLY_USER = true
ldap          | *** INITRD = no
ldap          | *** CONTAINER_LOG_LEVEL = 4
ldap          | *** HOME = /root
ldap          | *** LC_ALL = en_US.UTF-8
ldap          | *** LDAP_DOMAIN = kopano.demo
ldap          | *** LDAP_BASE_DN = dc=kopano,dc=demo
ldap          | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap          | *** ------------------------------------------
kopano_db     | 2018-11-20 20:19:38 0 [Note] mysqld (mysqld 10.3.10-MariaDB-1:10.3.10+maria~bionic) starting as process 1 ...
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Using Linux native AIO
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Uses event mutexes
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Number of pools: 1
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Using SSE2 crc32 instructions
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
ldap          | 1048576
ldap          | *** Set environment for container process
ldap          | *** ignore : LANG = en_US.UTF-8 (keep LANG = en_US.UTF-8 )
ldap          | *** ignore : LANGUAGE = en_US.UTF-8 (keep LANGUAGE = en_US:en )
ldap          | *** Environment files will be proccessed in this order :
ldap          | Caution: previously defined variables will not be overriden.
ldap          | /container/environment/99-default/default.yaml
ldap          |
ldap          | *** --- process file : /container/environment/99-default/default.yaml ---
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Completed initialization of buffer pool
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Creating shared tablespace for temporary tables
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Waiting for purge to start
ldap          | *** Run commands before process...
ldap          | *** ------------ Environment dump ------------
ldap          | *** LANG = en_US.UTF-8
ldap          | *** LDAP_LOG_LEVEL = 256
ldap          | *** CONTAINER_SERVICE_DIR = /container/run/service
ldap          | *** LDAP_READONLY_USER_PASSWORD = kopano123
ldap          | *** LANGUAGE = en_US:en
ldap          | *** LDAP_ORGANISATION = "Kopano Demo"
ldap          | *** HOSTNAME = b7da7f51cd4f
ldap          | *** CONTAINER_STATE_DIR = /container/run/state
ldap          | *** LC_CTYPE = en_US.UTF-8
ldap          | *** LDAP_ADMIN_PASSWORD = kopano123
ldap          | *** LDAP_READONLY_USER = true
ldap          | *** INITRD = no
ldap          | *** CONTAINER_LOG_LEVEL = 4
ldap          | *** LC_ALL = en_US.UTF-8
ldap          | *** LDAP_DOMAIN = kopano.demo
ldap          | *** HOME = /root
ldap          | *** LDAP_BASE_DN = dc=kopano,dc=demo
ldap          | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap          | *** ------------------------------------------
ldap          | *** Running /container/run/process/slapd/run...
ldap          | *** /container/run/process/slapd/run started as PID 20
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: 10.3.10 started; log sequence number 1993374; transaction id 323
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
kopano_db     | 2018-11-20 20:19:38 0 [Note] Plugin 'FEEDBACK' is disabled.
kopano_db     | 2018-11-20 20:19:38 0 [Note] InnoDB: Buffer pool(s) load completed at 181120 20:19:38
kopano_db     | 2018-11-20 20:19:38 0 [Note] Server socket created on IP: '::'.
kopano_db     | 2018-11-20 20:19:38 0 [Warning] 'proxies_priv' entry '@% root@c9df8ad278f8' ignored in --skip-name-resolve mode.
kopano_db     | 2018-11-20 20:19:38 0 [Note] Reading of all Master_info entries succeded
kopano_db     | 2018-11-20 20:19:38 0 [Note] Added new Master_info '' to hash table
kopano_db     | 2018-11-20 20:19:38 0 [Note] mysqld: ready for connections.
kopano_db     | Version: '10.3.10-MariaDB-1:10.3.10+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
ldap          | 1048576
ldap          | 5bf46c59 @(#) $OpenLDAP: slapd  (May 23 2018 04:25:19) $
ldap          | 	Debian OpenLDAP Maintainers<EMAIL_ADDRESS>mail          | 2018-11-20 21:19:39,117 CRIT Supervisor running as root (no user in config file)
mail          | 2018-11-20 21:19:39,121 INFO Included extra file "/etc/supervisor/conf.d/saslauth.conf" during parsing
mail          | 2018-11-20 21:19:39,121 INFO Included extra file "/etc/supervisor/conf.d/supervisor-app.conf" during parsing
mail          | 2018-11-20 21:19:39,133 INFO RPC interface 'supervisor' initialized
mail          | 2018-11-20 21:19:39,133 CRIT Server 'unix_http_server' running without any HTTP authentication checking
mail          | 2018-11-20 21:19:39,133 INFO supervisord started with pid 6
mail          | 2018-11-20 21:19:40,146 INFO spawned: 'mailserver' with pid 9
ldap          | TLS: warning: ignoring dhfile
ldap          | 5bf46c5a slapd starting
ldap          | 5bf46c5f conn=1000 fd=12 ACCEPT from IP=<IP_ADDRESS>:55414 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c5f conn=1000 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c5f conn=1000 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c5f conn=1000 op=1 UNBIND
ldap          | 5bf46c5f conn=1000 fd=12 closed
mail          |
mail          | 2018-11-20 21:19:40,213 INFO success: mailserver entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | #
mail          | #
mail          | # docker-mailserver
mail          | #
mail          | #
mail          |
mail          | Initializing setup
mail          | Checking configuration
ldap          | 5bf46c5f conn=1001 fd=12 ACCEPT from IP=<IP_ADDRESS>:55420 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c5f conn=1001 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c5f conn=1001 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c5f conn=1001 op=1 UNBIND
ldap          | 5bf46c5f conn=1001 fd=12 closed
ldap          | 5bf46c60 conn=1002 fd=12 ACCEPT from IP=<IP_ADDRESS>:55424 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c60 conn=1002 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c60 conn=1002 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c60 conn=1002 op=1 UNBIND
ldap          | 5bf46c60 conn=1002 fd=12 closed
ldap          | 5bf46c60 conn=1003 fd=12 ACCEPT from IP=<IP_ADDRESS>:55426 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c60 conn=1003 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c60 conn=1003 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c60 conn=1003 op=1 UNBIND
ldap          | 5bf46c60 conn=1003 fd=12 closed
mail          | Configuring mail server
mail          |
ldap          | 5bf46c61 conn=1004 fd=12 ACCEPT from IP=<IP_ADDRESS>:55430 (IP=<IP_ADDRESS>:389)
mail          | Config'O'mat. Version 0.0.0
mail          | -------------------
ldap          | 5bf46c61 conn=1004 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
mail          | Got the ENV_PREFIX: LDAP_
mail          | Got the CONF_FILE:  /etc/postfix/ldap-users.cf
mail          | -------------------
mail          |
mail          | Starting to do overrides:
ldap          | 5bf46c61 conn=1004 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c61 conn=1004 op=1 UNBIND
ldap          | 5bf46c61 conn=1004 fd=12 closed
mail          |   >> /etc/postfix/ldap-users.cf: query_filter_group = (&(objectclass=kopano-group)(mail=%s))
ldap          | 5bf46c61 conn=1005 fd=12 ACCEPT from IP=<IP_ADDRESS>:55432 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c61 conn=1005 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c61 conn=1005 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c61 conn=1005 op=1 UNBIND
ldap          | 5bf46c61 conn=1005 fd=12 closed
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4 (debug)
ldap-admin    | *** Set environment for startup files
ldap-admin    | *** ignore : LANG = en_US.UTF-8 (keep LANG = en_US.UTF-8 )
ldap-admin    | *** ignore : LANGUAGE = en_US.UTF-8 (keep LANGUAGE = en_US:en )
ldap-admin    | *** Environment files will be proccessed in this order :
ldap-admin    | Caution: previously defined variables will not be overriden.
ldap-admin    | /container/environment/99-default/default.yaml
ldap-admin    |
ldap-admin    | *** --- process file : /container/environment/99-default/default.yaml ---
ldap-admin    | *** ignore : PHPLDAPADMIN_HTTPS = True (keep PHPLDAPADMIN_HTTPS = false )
ldap-admin    | *** Run commands before startup...
ldap-admin    | *** Running /container/run/startup/:apache2...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running /container/run/startup/:cron...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running /container/run/startup/:logrotate...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
mail          |   >> /etc/postfix/ldap-users.cf: saslauthd_ldap_server = ldap://ldap:389
ldap          | 5bf46c62 conn=1006 fd=12 ACCEPT from IP=<IP_ADDRESS>:55434 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c62 conn=1006 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c62 conn=1006 op=0 RESULT tag=97 err=49 text=
ldap          | 5bf46c62 conn=1006 op=1 UNBIND
ldap          | 5bf46c62 conn=1006 fd=12 closed
mail          |   >> /etc/postfix/ldap-users.cf: search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-users.cf: saslauthd_ldap_bind_dn = CN=readonly,DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-users.cf: saslauthd_ldap_filter = (&(kopanoAccount=1)(uid=%s))
mail          |   >> /etc/postfix/ldap-users.cf: saslauthd_ldap_password = kopano123
mail          |   >> /etc/postfix/ldap-users.cf: server_host = ldap://ldap:389
mail          |   >> /etc/postfix/ldap-users.cf: query_filter = (&(kopanoAccount=1)(mail=%s))
mail          |   >> /etc/postfix/ldap-users.cf: query_filter_user = (&(kopanoAccount=1)(mail=%s))
mail          |   >> /etc/postfix/ldap-users.cf: query_filter_alias = (&(kopanoAccount=1)(kopanoAliases=%s))
mail          |   >> /etc/postfix/ldap-users.cf: saslauthd_ldap_search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-users.cf: bind_pw = kopano123
mail          |   >> /etc/postfix/ldap-users.cf: query_filter_domain = (&(|(mail=*@%s)(kopanoAliases=%s=*@%s)))
mail          |   >> /etc/postfix/ldap-users.cf: bind_dn = CN=readonly,DC=kopano,DC=demo
mail          |
mail          | Config'O'mat. Version 0.0.0
mail          | -------------------
mail          | Got the ENV_PREFIX: LDAP_
mail          | Got the CONF_FILE:  /etc/postfix/ldap-groups.cf
mail          | -------------------
mail          |
mail          | Starting to do overrides:
mail          |   >> /etc/postfix/ldap-groups.cf: query_filter_group = (&(objectclass=kopano-group)(mail=%s))
mail          |   >> /etc/postfix/ldap-groups.cf: saslauthd_ldap_server = ldap://ldap:389
mail          |   >> /etc/postfix/ldap-groups.cf: search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-groups.cf: saslauthd_ldap_bind_dn = CN=readonly,DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-groups.cf: saslauthd_ldap_filter = (&(kopanoAccount=1)(uid=%s))
mail          |   >> /etc/postfix/ldap-groups.cf: saslauthd_ldap_password = kopano123
mail          |   >> /etc/postfix/ldap-groups.cf: server_host = ldap://ldap:389
kopano_server | Nov 20 21:19:39 Configure core service 'server'
mail          |   >> /etc/postfix/ldap-groups.cf: query_filter = (&(objectclass=kopano-group)(mail=%s))
kopano_server | Nov 20 21:19:40 Set ownership
kopano_server | 2018/11/20 21:19:40 Waiting for: file:///kopano/ssl/ca.pem
kopano_server | 2018/11/20 21:19:40 Waiting for: file:///kopano/ssl/kserver.pem
kopano_server | 2018/11/20 21:19:40 Waiting for: tcp://db:3306
mail          |   >> /etc/postfix/ldap-groups.cf: query_filter_user = (&(kopanoAccount=1)(mail=%s))
mail          |   >> /etc/postfix/ldap-groups.cf: query_filter_alias = (&(kopanoAccount=1)(kopanoAliases=%s))
kopano_server | 2018/11/20 21:19:40 Connected to tcp://db:3306
mail          |   >> /etc/postfix/ldap-groups.cf: saslauthd_ldap_search_base = DC=kopano,DC=demo
kopano_server | 2018/11/20 21:19:40 Waiting for: tcp://localhost:236
kopano_server | 2018/11/20 21:19:40 Problem with dial: dial tcp <IP_ADDRESS>:236: connect: connection refused. Sleeping 1s
kopano_server | 2018/11/20 21:19:40 Waiting for: tcp://localhost:236
kopano_server | 2018/11/20 21:19:40 Problem with dial: dial tcp <IP_ADDRESS>:236: connect: connection refused. Sleeping 1s
kopano_server | 2018/11/20 21:19:41 File file:///kopano/ssl/kserver.pem had been generated
kopano_server | 2018/11/20 21:19:41 File file:///kopano/ssl/ca.pem had been generated
mail          |   >> /etc/postfix/ldap-groups.cf: bind_pw = kopano123
mail          |   >> /etc/postfix/ldap-groups.cf: query_filter_domain = (&(|(mail=*@%s)(kopanoAliases=%s=*@%s)))
mail          |   >> /etc/postfix/ldap-groups.cf: bind_dn = CN=readonly,DC=kopano,DC=demo
kopano_server | 2018/11/20 21:19:41 Problem with dial: dial tcp <IP_ADDRESS>:236: connect: connection refused. Sleeping 1s
kopano_server | 2018/11/20 21:19:41 Problem with dial: dial tcp <IP_ADDRESS>:236: connect: connection refused. Sleeping 1s
mail          |
mail          | Config'O'mat. Version 0.0.0
kopano_server | Tue Nov 20 21:19:41 2018: [=======] Starting kopano-server version 8.7.80 (pid 30 uid 0)
mail          | -------------------
mail          | Got the ENV_PREFIX: LDAP_
mail          | Got the CONF_FILE:  /etc/postfix/ldap-aliases.cf
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for TCP connections on port 236
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for SSL connections on port 237
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Coredumps are disabled via configuration file.
mail          | -------------------
mail          |
mail          | Starting to do overrides:
kopano_server | Tue Nov 20 21:19:41 2018: [=======] Starting kopano-server version 8.7.80 (pid 30 uid 999)
mail          |   >> /etc/postfix/ldap-aliases.cf: query_filter_group = (&(objectclass=kopano-group)(mail=%s))
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for TCP connections on port 236
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for SSL connections on port 237
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Listening for pipe connections on /var/run/kopano/server.sock
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Coredumps are disabled via configuration file.
mail          |   >> /etc/postfix/ldap-aliases.cf: saslauthd_ldap_server = ldap://ldap:389
mail          |   >> /etc/postfix/ldap-aliases.cf: search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-aliases.cf: saslauthd_ldap_bind_dn = CN=readonly,DC=kopano,DC=demo
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Connection to database 'kopano' succeeded
kopano_server | Tue Nov 20 21:19:41 2018: [crit   ] Warning: Process /usr/sbin/kopano-server is probably already running.
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Querying database for searchfolders. This may take a while.
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Loading search folders.
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Done loading search folders.
kopano_server | Tue Nov 20 21:19:41 2018: [notice ] Startup succeeded on pid 30
kopano_server | 2018/11/20 21:19:42 Connected to tcp://localhost:236
kopano_server | 2018/11/20 21:19:42 Connected to tcp://localhost:236
kopano_server | Tue Nov 20 21:19:42 2018: [error  ] createStore(): already exists
kopano_server | Tue Nov 20 21:19:42 2018: [error  ] Failed to create store (id=1): collision (80000008)
kopano_server | [error  ] Public store already exists: collision (80040604)
kopano_server | 2018/11/20 21:19:42 Command exited with error: exit status 1
kopano_server | Tue Nov 20 21:19:43 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:43 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:43 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:43 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_server | Tue Nov 20 21:19:43 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:43 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:43 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:43 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_server | Tue Nov 20 21:19:44 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:44 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:44 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:44 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_server | Tue Nov 20 21:19:44 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:44 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:44 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:44 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_server | Tue Nov 20 21:19:45 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:45 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:45 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:45 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_server | Tue Nov 20 21:19:45 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:45 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:45 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:45 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_server | Tue Nov 20 21:19:46 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
kopano_server | Tue Nov 20 21:19:46 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:46 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:46 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
mail          |   >> /etc/postfix/ldap-aliases.cf: saslauthd_ldap_filter = (&(kopanoAccount=1)(uid=%s))
mail          |   >> /etc/postfix/ldap-aliases.cf: saslauthd_ldap_password = kopano123
mail          |   >> /etc/postfix/ldap-aliases.cf: server_host = ldap://ldap:389
mail          |   >> /etc/postfix/ldap-aliases.cf: query_filter = (&(kopanoAccount=1)(kopanoAliases=%s))
mail          |   >> /etc/postfix/ldap-aliases.cf: query_filter_user = (&(kopanoAccount=1)(mail=%s))
mail          |   >> /etc/postfix/ldap-aliases.cf: query_filter_alias = (&(kopanoAccount=1)(kopanoAliases=%s))
mail          |   >> /etc/postfix/ldap-aliases.cf: saslauthd_ldap_search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-aliases.cf: bind_pw = kopano123
mail          |   >> /etc/postfix/ldap-aliases.cf: query_filter_domain = (&(|(mail=*@%s)(kopanoAliases=%s=*@%s)))
mail          |   >> /etc/postfix/ldap-aliases.cf: bind_dn = CN=readonly,DC=kopano,DC=demo
mail          |
mail          | Config'O'mat. Version 0.0.0
mail          | -------------------
mail          | Got the ENV_PREFIX: LDAP_
mail          | Got the CONF_FILE:  /etc/postfix/ldap-domains.cf
mail          | -------------------
mail          |
mail          | Starting to do overrides:
mail          |   >> /etc/postfix/ldap-domains.cf: query_filter_group = (&(objectclass=kopano-group)(mail=%s))
mail          |   >> /etc/postfix/ldap-domains.cf: saslauthd_ldap_server = ldap://ldap:389
mail          |   >> /etc/postfix/ldap-domains.cf: search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-domains.cf: saslauthd_ldap_bind_dn = CN=readonly,DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-domains.cf: saslauthd_ldap_filter = (&(kopanoAccount=1)(uid=%s))
mail          |   >> /etc/postfix/ldap-domains.cf: saslauthd_ldap_password = kopano123
mail          |   >> /etc/postfix/ldap-domains.cf: server_host = ldap://ldap:389
mail          |   >> /etc/postfix/ldap-domains.cf: query_filter = (&(|(mail=*@%s)(kopanoAliases=%s=*@%s)))
mail          |   >> /etc/postfix/ldap-domains.cf: query_filter_user = (&(kopanoAccount=1)(mail=%s))
mail          |   >> /etc/postfix/ldap-domains.cf: query_filter_alias = (&(kopanoAccount=1)(kopanoAliases=%s))
mail          |   >> /etc/postfix/ldap-domains.cf: saslauthd_ldap_search_base = DC=kopano,DC=demo
mail          |   >> /etc/postfix/ldap-domains.cf: bind_pw = kopano123
mail          |   >> /etc/postfix/ldap-domains.cf: query_filter_domain = (&(|(mail=*@%s)(kopanoAliases=%s=*@%s)))
mail          |   >> /etc/postfix/ldap-domains.cf: bind_dn = CN=readonly,DC=kopano,DC=demo
mail          |
mail          | Config'O'mat. Version 0.0.0
mail          | The file could not be found: /etc/postfix/maps/sender_login_maps.ldap. Exiting ...
mail          |
mail          | Config'O'mat. Version 0.0.0
mail          | -------------------
mail          | Got the ENV_PREFIX: DOVECOT_
mail          | Got the CONF_FILE:  /etc/dovecot/dovecot-ldap.conf.ext
mail          | -------------------
mail          |
mail          | Starting to do overrides:
mail          |   >> /etc/dovecot/dovecot-ldap.conf.ext: hosts = ldap://ldap:389
mail          |   >> /etc/dovecot/dovecot-ldap.conf.ext: dn = CN=readonly,DC=kopano,DC=demo
mail          |   >> /etc/dovecot/dovecot-ldap.conf.ext: dnpass = kopano123
mail          |   >> /etc/dovecot/dovecot-ldap.conf.ext: base = DC=kopano,DC=demo
mail          | Adding user postfix to group sasl
mail          |   * No DKIM key provided. Check the documentation to find how to get your keys.
mail          | Starting Misc
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running /container/run/startup/:php7.0-fpm...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | Conf php7.0-fpm already enabled
ldap-admin    | *** Running /container/run/startup/:ssl-tools...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running /container/run/startup/:syslog-ng-core...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running /container/run/startup/ldap-client...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
kopano_gateway | Nov 20 21:19:43 Configure core service 'gateway'
kopano_gateway | Nov 20 21:19:43 Set ownership
kopano_gateway | 2018/11/20 21:19:43 Waiting for: tcp://kserver:236
kopano_gateway | 2018/11/20 21:19:43 Connected to tcp://kserver:236
kopano_gateway | Tue Nov 20 21:19:43 2018: [kopano-gateway|T18] [=======] Starting kopano-gateway version 8.7.80 (pid 18 uid 0)
kopano_gateway | Tue Nov 20 21:19:43 2018: [kopano-gateway|T18] [error  ] ECChannel::HrSetCtx(): cannot open key file
kopano_gateway | Tue Nov 20 21:19:43 2018: [kopano-gateway|T18] [error  ] Error loading SSL context, POP3S and IMAPS will be disabled
kopano_gateway | Tue Nov 20 21:19:43 2018: [kopano-gateway|T18] [crit   ] POP3, POP3S, IMAP and IMAPS are all four disabled
kopano_gateway | /usr/sbin/kopano-gateway: Startup failed: call failed (80004005). Please check the logfile (-) for details.
kopano_gateway | 2018/11/20 21:19:43 Command exited with error: exit status 1
kopano_gateway exited with code 1
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running /container/run/startup/phpldapadmin...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** HOME = /root
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
kopano_monitor | Nov 20 21:19:43 Configure core service 'monitor'
kopano_monitor | Nov 20 21:19:43 Set ownership
kopano_monitor | 2018/11/20 21:19:43 Waiting for: file://var/run/kopano/server.sock
kopano_monitor | 2018/11/20 21:19:44 File file://var/run/kopano/server.sock had been generated
kopano_monitor | Tue Nov 20 21:19:44 2018: [=======] Starting kopano-monitor version 8.7.80 (pid 18 uid 0)
kopano_monitor | Tue Nov 20 21:19:44 2018: [=======] Starting kopano-monitor version 8.7.80 (pid 18 uid 999)
kopano_monitor | Tue Nov 20 21:19:44 2018: [crit   ] Warning: Process /usr/sbin/kopano-monitor is probably already running.
kopano_monitor | Tue Nov 20 21:19:44 2018: [crit   ] If you are sure the process is stopped, please remove pidfile /var/run/kopano/monitor.pid
kopano_monitor | 2018/11/20 21:19:44 Command exited with error: exit status 1
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
kopano_dagent | Nov 20 21:19:44 Configure core service 'dagent'
ldap-admin    | Set apache2 http config...
kopano_dagent | Nov 20 21:19:44 Set ownership
ldap-admin    | Site phpldapadmin already enabled
kopano_dagent | 2018/11/20 21:19:44 Waiting for: file://var/run/kopano/server.sock
ldap-admin    | *** Set environment for container process
ldap-admin    | *** ignore : LANG = en_US.UTF-8 (keep LANG = en_US.UTF-8 )
ldap-admin    | *** ignore : LANGUAGE = en_US.UTF-8 (keep LANGUAGE = en_US:en )
ldap-admin    | *** Environment files will be proccessed in this order :
ldap-admin    | Caution: previously defined variables will not be overriden.
ldap-admin    | /container/environment/99-default/default.yaml
ldap-admin    |
ldap-admin    | *** --- process file : /container/environment/99-default/default.yaml ---
kopano_dagent | 2018/11/20 21:19:45 File file://var/run/kopano/server.sock had been generated
kopano_dagent | Tue Nov 20 21:19:46 2018: [info   ] Coredump status left at system default.
ldap-admin    | *** ignore : PHPLDAPADMIN_HTTPS = True (keep PHPLDAPADMIN_HTTPS = false )
kopano_dagent | Tue Nov 20 21:19:46 2018: [=======] Starting kopano-dagent version 8.7.80 (pid 18 uid 0) (LMTP mode)
kopano_dagent | Tue Nov 20 21:19:46 2018: [info   ] Listening on *:2003 for LMTP
kopano_dagent | Tue Nov 20 21:19:46 2018: [debug  ] Reexecing /usr/sbin/kopano-dagent
ldap-admin    | *** Run commands before process...
ldap-admin    | *** ------------ Environment dump ------------
ldap-admin    | *** PHPLDAPADMIN_HTTPS = false
ldap-admin    | *** LC_CTYPE = en_US.UTF-8
ldap-admin    | *** PHPLDAPADMIN_SSL_HELPER_PREFIX = phpldapadmin
ldap-admin    | *** INITRD = no
ldap-admin    | *** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
ldap-admin    | *** HOME = /root
ldap-admin    | *** PHPLDAPADMIN_HTTPS_KEY_FILENAME = phpldapadmin.key
ldap-admin    | *** LANG = en_US.UTF-8
ldap-admin    | *** affinity:container = =5b1a3af820f0f5ad532ce9c0311b766088279b916950814c25a345d8fb258b00
ldap-admin    | *** PHPLDAPADMIN_SERVER_ADMIN =<EMAIL_ADDRESS>ldap-admin    | *** CONTAINER_SERVICE_DIR = /container/service
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CA_CRT_FILENAME = ca.crt
ldap-admin    | *** LANGUAGE = en_US:en
ldap-admin    | *** CADDY_HOST = ldap.kopano.demo
ldap-admin    | *** CADDY_PORT = 80
ldap-admin    | *** CADDY_PROXY_PARAMS = transparent
ldap-admin    | *** PHPLDAPADMIN_HTTPS_CRT_FILENAME = phpldapadmin.crt
ldap-admin    | *** PHPLDAPADMIN_TRUST_PROXY_SSL = False
ldap-admin    | *** PHPLDAPADMIN_LDAP_HOSTS = ldap
ldap-admin    | *** CONTAINER_LOG_LEVEL = 4
ldap-admin    | *** LC_ALL = en_US.UTF-8
ldap-admin    | *** HOSTNAME = 1ed06f8b12a1
ldap-admin    | *** CONTAINER_STATE_DIR = /container/run/state
ldap-admin    | *** PHPLDAPADMIN_SERVER_PATH = /phpldapadmin
ldap-admin    | *** ------------------------------------------
ldap-admin    | *** Running runit daemon...
ldap-admin    | *** runit daemon started as PID 1432
kopano_dagent | Tue Nov 20 21:19:46 2018: [info   ] Coredump status left at system default.
kopano_dagent | Tue Nov 20 21:19:46 2018: [=======] Starting kopano-dagent version 8.7.80 (pid 18 uid 999) (LMTP mode)
kopano_dagent | Tue Nov 20 21:19:46 2018: [info   ] Listening on *:2003 for LMTP
kopano_dagent | Tue Nov 20 21:19:46 2018: [crit   ] Warning: Process /usr/sbin/kopano-dagent is probably already running.
kopano_dagent | Tue Nov 20 21:19:46 2018: [info   ] Logger process started on pid 22
kopano_dagent | Tue Nov 20 21:19:46 2018: [info   ] Maximum LMTP threads set to 20
kopano_ical   | Nov 20 21:19:44 Configure core service 'ical'
kopano_monitor exited with code 1
ldap-admin    | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
kopano_ical   | Nov 20 21:19:44 Set ownership
ldap-admin    | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
kopano_ical   | 2018/11/20 21:19:45 Waiting for: tcp://kserver:236
ldap-admin    | [20-Nov-2018 20:19:41] NOTICE: fpm is running, pid 1443
ldap-admin    | [20-Nov-2018 20:19:41] NOTICE: ready to handle connections
ldap-admin    | [20-Nov-2018 20:19:41] NOTICE: systemd monitor interval set to 10000ms
ldap-admin    | [Tue Nov 20 20:19:41.879933 2018] [core:warn] [pid 1452:tid<PHONE_NUMBER>74400] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?
kopano_ical   | 2018/11/20 21:19:45 Connected to tcp://kserver:236
kopano_ical   | Tue Nov 20 21:19:45 2018: [kopano-ical|T18] [=======] Starting kopano-ical version 8.7.80 (pid 18 uid 0)
ldap-admin    | [Tue Nov 20 20:19:41.888460 2018] [mpm_event:notice] [pid 1452:tid<PHONE_NUMBER>74400] AH00489: Apache/2.4.25 (Debian) OpenSSL/1.0.2l configured -- resuming normal operations
ldap-admin    | [Tue Nov 20 20:19:41.888480 2018] [core:notice] [pid 1452:tid<PHONE_NUMBER>74400] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
kopano_ical   | Tue Nov 20 21:19:45 2018: [kopano-ical|T18] [=======] Starting kopano-ical version 8.7.80 (pid 18 uid 999)
ldap-admin    | Nov 20 20:19:41 1ed06f8b12a1 syslog-ng[1438]: syslog-ng starting up; version='3.8.1'
kopano_ical   | Tue Nov 20 21:19:45 2018: [kopano-ical|T18] [crit   ] Warning: Process /usr/sbin/kopano-ical is probably already running.
kopano_webapp | Ensure directories
kopano_webapp | Kopano WebApp is using the default: connection
kopano_webapp | Configuring Kopano WebApp for use behind a reverse proxy
kopano_webapp | Ensure config ownership
kopano_webapp | Starting Apache
kopano_webapp | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
kopano_webapp | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
kopano_webapp | [Tue Nov 20 21:19:45.940834 2018] [mpm_prefork:notice] [pid 6] AH00163: Apache/2.4.25 (Debian) configured -- resuming normal operations
kopano_webapp | [Tue Nov 20 21:19:45.941319 2018] [core:notice] [pid 6] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
kopano_zpush  | Ensure directories
kopano_zpush  | Z-Push is using the default: connection
kopano_zpush  | Configuring Z-Push for use behind a reverse proxy
kopano_zpush  | Ensure config ownership
kopano_zpush  | Activate z-push log rerouting
kopano_zpush  | Starting Apache
kopano_zpush  | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
kopano_zpush  | AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <IP_ADDRESS>. Set the 'ServerName' directive globally to suppress this message
kopano_zpush  | [Tue Nov 20 21:19:46.211501 2018] [mpm_prefork:notice] [pid 6] AH00163: Apache/2.4.25 (Debian) configured -- resuming normal operations
kopano_zpush  | [Tue Nov 20 21:19:46.219853 2018] [core:notice] [pid 6] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
web           | 2018/11/20 20:19:46 [WARNING] No files matching import glob pattern: /etc/caddy/*.caddyfile
web           | Activating privacy features... done.
web           | http://localhost:2015
web           | 2018/11/20 20:19:46 http://localhost:2015
web           | https://webapp.kopano.demo
web           | 2018/11/20 20:19:46 https://webapp.kopano.demo
web           | https://zpush.kopano.demo
web           | 2018/11/20 20:19:46 https://zpush.kopano.demo
web           | https://ldap.kopano.demo
web           | 2018/11/20 20:19:46 https://ldap.kopano.demo
web           | 2018/11/20 20:19:46 [INFO] Nonblocking Command "docker-gen.sh " with ID 50d50d4d-fd2f-42c5-b6ba-260789f3aec0
web           | 2018/11/20 20:19:46 Contents of /etc/Caddyfile did not change. Skipping notification 'pkill -USR1 caddy'
web           | 2018/11/20 20:19:46 Watching docker events
kopano_search | Nov 20 21:19:46 Configure core service 'search'
kopano_spooler | Nov 20 21:19:46 Configure core service 'spooler'
web           | 2018/11/20 20:19:47 Contents of /etc/Caddyfile did not change. Skipping notification 'pkill -USR1 caddy'
kopano_search | Nov 20 21:19:47 Set ownership
mail          | Starting mail server
kopano_search | 2018/11/20 21:19:47 Waiting for: file://var/run/kopano/server.sock
kopano_spooler | Nov 20 21:19:47 Set ownership
kopano_spooler | 2018/11/20 21:19:47 Waiting for: file://var/run/kopano/server.sock
kopano_spooler | 2018/11/20 21:19:47 Waiting for: tcp://mail:25
kopano_spooler | 2018/11/20 21:19:47 Problem with dial: dial tcp <IP_ADDRESS>:25: connect: connection refused. Sleeping 1s
ldap          | 5bf46c63 conn=1007 fd=12 ACCEPT from IP=<IP_ADDRESS>:55440 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c63 conn=1007 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c63 conn=1007 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:47 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c63 conn=1007 op=1 UNBIND
ldap          | 5bf46c63 conn=1007 fd=12 closed
kopano_server | Tue Nov 20 21:19:47 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:47 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:47 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
mail          | 2018-11-20 21:19:47,547 INFO spawned: 'cron' with pid 874
mail          | 2018-11-20 21:19:47,548 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
web           | 2018/11/20 20:19:47 [WARNING] Sending telemetry (attempt 1): telemetry server replied with unknown content-type: 'text/plain; charset=utf-8' and HTTP 502 Bad Gateway - backing off and retrying
mail          | cron: started
ldap          | 5bf46c63 conn=1008 fd=12 ACCEPT from IP=<IP_ADDRESS>:55442 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c63 conn=1008 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c63 conn=1008 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:47 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c63 conn=1008 op=1 UNBIND
ldap          | 5bf46c63 conn=1008 fd=12 closed
kopano_server | Tue Nov 20 21:19:47 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:47 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:47 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
mail          | 2018-11-20 21:19:47,905 INFO spawned: 'rsyslog' with pid 876
mail          | 2018-11-20 21:19:47,905 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | rsyslog: started
ldap          | 5bf46c64 conn=1009 fd=12 ACCEPT from IP=<IP_ADDRESS>:55444 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c64 conn=1009 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c64 conn=1009 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:48 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c64 conn=1009 op=1 UNBIND
ldap          | 5bf46c64 conn=1009 fd=12 closed
kopano_server | Tue Nov 20 21:19:48 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:48 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:48 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_search | 2018/11/20 21:19:48 File file://var/run/kopano/server.sock had been generated
kopano_search | 2018/11/20 21:19:48 Error starting command: `/usr/bin/python` - fork/exec /usr/bin/python: no such file or directory
kopano_spooler | 2018/11/20 21:19:48 File file://var/run/kopano/server.sock had been generated
kopano_spooler | 2018/11/20 21:19:48 Problem with dial: dial tcp <IP_ADDRESS>:25: connect: connection refused. Sleeping 1s
web           | 2018/11/20 20:19:48 Received event die for container 7b3fe03d3054
mail          | 2018-11-20 21:19:48,411 INFO spawned: 'opendkim' with pid 880
mail          | 2018-11-20 21:19:48,422 INFO success: opendkim entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | opendkim: started
kopano_search exited with code 1
web           | 2018/11/20 20:19:48 Contents of /etc/Caddyfile did not change. Skipping notification 'pkill -USR1 caddy'
ldap          | 5bf46c64 conn=1010 fd=12 ACCEPT from IP=<IP_ADDRESS>:55448 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c64 conn=1010 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c64 conn=1010 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:48 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c64 conn=1010 op=1 UNBIND
ldap          | 5bf46c64 conn=1010 fd=12 closed
kopano_server | Tue Nov 20 21:19:48 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:48 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:48 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
mail          | 2018-11-20 21:19:48,960 INFO spawned: 'opendmarc' with pid 888
mail          | 2018-11-20 21:19:48,964 INFO success: opendmarc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | opendmarc: started
ldap          | 5bf46c65 conn=1011 fd=12 ACCEPT from IP=<IP_ADDRESS>:55450 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c65 conn=1011 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c65 conn=1011 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:49 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c65 conn=1011 op=1 UNBIND
ldap          | 5bf46c65 conn=1011 fd=12 closed
kopano_server | Tue Nov 20 21:19:49 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:49 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:49 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_spooler | 2018/11/20 21:19:49 Problem with dial: dial tcp <IP_ADDRESS>:25: connect: connection refused. Sleeping 1s
mail          | 2018-11-20 21:19:49,375 INFO spawned: 'postgrey' with pid 896
mail          | 2018-11-20 21:19:49,375 INFO success: postgrey entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | postgrey: started
ldap          | 5bf46c65 conn=1012 fd=12 ACCEPT from IP=<IP_ADDRESS>:55454 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c65 conn=1012 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c65 conn=1012 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:49 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c65 conn=1012 op=1 UNBIND
ldap          | 5bf46c65 conn=1012 fd=12 closed
kopano_server | Tue Nov 20 21:19:49 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:49 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:49 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
mail          | 2018-11-20 21:19:49,959 INFO spawned: 'postfix' with pid 898
mail          | 2018-11-20 21:19:49,960 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | postfix: started
ldap          | 5bf46c65 conn=1013 fd=12 ACCEPT from IP=<IP_ADDRESS>:55456 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c65 conn=1013 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c65 conn=1013 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:49 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c65 conn=1013 op=1 UNBIND
ldap          | 5bf46c65 conn=1013 fd=12 closed
kopano_server | Tue Nov 20 21:19:49 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:49 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:49 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
kopano_spooler | 2018/11/20 21:19:50 Problem with dial: dial tcp <IP_ADDRESS>:25: connect: connection refused. Sleeping 1s
ldap          | 5bf46c66 conn=1014 fd=12 ACCEPT from IP=<IP_ADDRESS>:55460 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c66 conn=1014 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c66 conn=1014 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:50 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c66 conn=1014 op=1 UNBIND
ldap          | 5bf46c66 conn=1014 fd=12 closed
kopano_server | Tue Nov 20 21:19:50 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:50 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:50 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)
mail          | 2018-11-20 21:19:50,571 INFO spawned: 'saslauthd_ldap' with pid 959
mail          | 2018-11-20 21:19:50,572 INFO success: saslauthd_ldap entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail          | saslauthd_ldap: started
ldap          | 5bf46c66 conn=1015 fd=12 ACCEPT from IP=<IP_ADDRESS>:55462 (IP=<IP_ADDRESS>:389)
ldap          | 5bf46c66 conn=1015 op=0 BIND dn="cn=readonly,dc=kopano,dc=demo" method=128
ldap          | 5bf46c66 conn=1015 op=0 RESULT tag=97 err=49 text=
kopano_server | Tue Nov 20 21:19:50 2018: [warning] LDAP (simple) bind on CN=readonly,DC=kopano,DC=demo failed: Invalid credentials
ldap          | 5bf46c66 conn=1015 op=1 UNBIND
ldap          | 5bf46c66 conn=1015 fd=12 closed
kopano_server | Tue Nov 20 21:19:50 2018: [crit   ] Cannot instantiate user plugin: Failure connecting any of the LDAP servers
kopano_server | Tue Nov 20 21:19:50 2018: [crit   ] Unable to instantiate user plugin
kopano_server | Tue Nov 20 21:19:50 2018: [error  ] Error synchronizing company list: not found (80000002)
kopano_server | MAPI error 8004010F (MAPI_E_NOT_FOUND)

hi @8ear,
that sounds strange. Did you do any further modifications to the .env file? What os and which version of Docker are you using?
I just nuked my test environment, deleted the data folder. reran setup.sh and ran docker-compose. kopano-server was afterwards able to log into ldap.

I have exactly the same problem.
No modification. Just clone, run setup and docker-compose. Docker run on a MacBook

@8ear are you also running on a mac?
Looking at the issue tracer of https://github.com/osixia/docker-openldap/issues?utf8=✓&q=mac I do see two issues where people were reporting issues when running the image on a mac, which were not reproducible on another os.
@r00tc0d3 Can you try on e.g. Ubuntu?

I tried it on an Arch linux machine. On this machine I do not have this problem.

@r00tc0d3 thanks for the confirmation. I've added a note to the readme to avoid MacOS if you want to use the bundled ldap.