text:
Encountered a problem when interactive drawing polygon when terrain is added

When terrain is added, If I dynamicly draw polygon and set the polygons hierarchy to a callbackproperty which returns an array containing the polygons vertex cartesain3. A point is added to the callbackproperty when leftclick event is fired. A point is first poped then added when mousemove event is fired. But if i click on the same location or move very slowly after I left click on map, error occurs when dynamicly drawing.
When I dont add terrain,the code works fine.
Do you know why?

Hi @medusaless, sorry I'm not exactly sure what the error is.
Can you please post on the forum? https://groups.google.com/forum/?hl=en#!forum/cesium-dev
Someone will be able to help you there.  We use GitHub exclusively for tracking bugs and planning new features.
When you post on the forum, please include a Sandcaslte Example that reproduces the problem.  That'll make it easier for people to help you debug the problem.
Thanks!

Thank you for your help. Can you give me your email or something like that? I want to ask you more questions about cesium.

@medusaless The Cesium team monitors the forum so that's the best place to ask questions about Cesium

I have some problems creating new google account, because I am in China.
I have already pasted my code link below.

I have some problems creating new account in Google right now.
I have already pasted my code below.
Please have a look.
https://cesiumjs.org/Cesium/Apps/Sandcastle/index.html#c=xVdtc+I2EP4raj5czA1j2n7pDIRMMxy9Y0oumYTmPpTOnbAXrEFIHkmG0h7/vSvZBvkFmrl+aN4meHef3X32RfJc9N7OxVtCZgkoIBR/zU6SjYxBEyNJRHmUcWrwcQKEw9KQiLNoTVZKZiImqWTCEIewgIhmGhVBKcoEYWLJMxCRBULbXLPEY1KE1spZTpbOIWGaXM/GT093k4/XXYIwUhEZRZnSwUQgCMo1M5mzRktCHPCWwQ7UF106flRyy2JQRCcy4zHGRUagWbYJIwXUfJKKx7NcNeh0Qodz+uPHMp5OH58fJu8wGGbITqq1JksmoBlN19nugMQSk6RxXAbTcVkWaTrpF0PWQu7ILtkXKVLFNJK0S0CcyNMWBWJrjj+9ubDfW6qKdMmQCNiVib24Z8F15D6O0AtigLruDEqrR8n3KylmoA2aLjMRORKDHK3rcu6Qv10aLrfw6Cf/Z+CJHEHDnKevX081c96OWrGiOyZWL6AM/In5Dcnvfwya8iKysTDM7FEJuwosyXGh61kw/S63GWPnYRaUaziPOLLVhrqip469yBc0WmPDpBhk3bmnuWAiHm9BmMAyesiL4VEapkoaafappaUgMZJCG5VFRqq+T3/eKsSDLC2O7qSY4qCN7Jx9oCLmrgxnJC62wAo7gwbME1slZ3AaootA9xIn+15uoYFTl1RhakBgEz5BeB38jLMJ4jmlEYw9pcBrRawXtnIzOh801GAmIs3Mnevv4Axp3XNuZ1jCcDr+ZfZ5NJ2Mfv0WXw1iLzt7mrz/8B+81em/7Oz+4bfn8ef7h5dx6etQtGOTo8B5rzSnXST5Gi/KvwLz3p0Dj/ZpbhGmEtei3YmnZdHIrLYbwjTTSeCgfVW2JEGrOgexMgkZDsmP5M0b8t356a/Ef2nyvV4c1aTBaV024OyXApMp0ZrYoKp98Kajm6+l6pQcI8TlXyQStEbcabE5t/5wC4EXyKFaec9TWblG0aFczh5L+cIOanykOVS/jaeEgaIqSvZ9cuyRppbMDMcN3Hdht8g3mJVilPcrJZNcqvtCcqybLww/fZjMxuGOmeSOpwkNvg9/6nRq+AePpXM9Wz+vcm5qusXGcjIGrpxBrugPXjl6jZXxf83exYzbz9Nzh7PXdKcdU99WLXmyZdCA61SbKZ+3ZkefjvfXEwb240XOXrOE2rfM65bcgQCy+a9ubl/tRaZBZ/Dt4VRrViPt1F+VC2Odb5Fx7mFqnLooIUHDxt2TKGZ/vEL2mwNvgRXdl2U8XgY2uE1sUR9xbp7o/rS9Bk2MSiMUCDoCAeGKywWEKWIE6KTb1GiDW+AorAdteeArwyR/Z+i/LooiDxvAmHOWasnii6nUfXvNXxxEzo03e6hhV6V3By2u/TjvV92rG232HG5z/Z/ZJpXKkEzxIAx7BjapffvTvUUWrcGEkXYXsJteaXQTsy1h8XB+VXv5mF/hmyLVGiVLbIdn9hfMr25veqhfMeOSxtiWD1tQnO6tSvLD7TR/GIbhTQ8/Nq2MlHgeKg/xHw

@medusaless sorry you can't access the forum.  I don't have time to debug your application, but from a breif look I noticed two things:

There might be a problem with how you're adding and removing points from the polygon on mouse move.
Sometimes pick and pickEllipsoid return undefined.  You should be checking if the result is defined before adding it to your polygon positions

authors: hpinkos medusaless


text:
Pointcloud performance issues.

Browser: Chrome
Operating System: Ubuntu
Code sample:
var url = <INSERT URL>;
var viewer = new Cesium.Viewer('cesiumContainer', {});
var tileset = viewer.scene.primitives.add(new Cesium.Cesium3DTileset({
    url: url
}));
tileset.style = new Cesium.Cesium3DTileStyle({
    pointSize:2
});

tileset.readyPromise.then(function() {
    var bounding = tileset._root._boundingVolume;
    var center = bounding.boundingSphere.center;
    var cart = Cesium.Ellipsoid.WGS84.cartesianToCartographic(center);

    var dest = Cesium.Cartesian3.fromDegrees(
            cart.longitude * (180 / Math.PI),
            cart.latitude * (180 / Math.PI),
            bounding._boundingSphere.radius * 1.0);

    viewer.camera.setView({ destination: dest });
});

viewer.scene.debugShowFramesPerSecond = true;

The Cesium version I discovered the issue in is 1.57. I tested in an earlier version of Cesium (1.47) and there are no performance issues. In 1.57, the FPS is constantly < 10, often < 5. In 1.47 the FPS is constantly > 15, which is I assume is just due to tileset size.
Unfortunately I can't share the tileset I've been testing on. "http://cesium.entwine.io/data/half-dome/cesium/tileset.json" is the closest thing to public I could find for you, but there are some CORS issues occasionally.
For context, the tileset I'm using was generated with Entwine from a las file originally. It seems like tilesets in the sandcastle don't have the same issue, maybe because they were generated in Cesium Ion? I couldn't test these tilesets properly since I can't import them into my application.

To help narrow down where the issue is, are you able to tile your LAS file using Cesium ion and see if it still performs better in 1.47 compared to 1.57?

It seems like tilesets in the sandcastle don't have the same issue, maybe because they were generated in Cesium Ion? I couldn't test these tilesets properly since I can't import them into my application.

Your application is a CesiumJS based app, right? Why couldn't you import those tilesets?
Another thing that might help here is that we host Sandcastles for all previous versions of CesiumJS. So for example you can get a hosted version 1.47 with this link:
https://cesiumjs.org/releases/1.47/Apps/Sandcastle/index.html?src=Offline.html
Which might make it easier to quickly test versions and share comparison links.

Thanks for your comment Omar, I hadn't been using Cesium Ion up until this point. I tiled my dataset with Cesium Ion and the performance improved massively, so I suppose this is an issue with Entwine. I'll report an issue on their Github and see if it can be fixed.

@ThornM9 are you able to share the tileset with someone on the Cesium team? You can send it to support@cesium.com and we can figure out when the performance regression was introduced.
Or if you are comfortable with using git bisect you can find out which commit introduced the slowness.

@lilleyse Thanks for the response, I thought that the issue would be solved by Entwine, but they never ended up responding to my issue.
I used git bisect to find the commit responsible for the performance issues for entwine point clouds, the first bad commit hash is: 06f133bf55c800272a38c3908ae6404ff2168bf6

@ThornM9 I appreciate you debugging this further and finding the first commit that causes this issue. Did you send the tileset you're testing with to support@cesium.com ? Otherwise we can't verify/merge a fix without having a reproducible test case.

@OmarShehata Just sent it in

source: gharchive/issue

authors: OmarShehata ThornM9 lilleyse

repo: AnalyticalGraphicsInc/cesium

license_type: permissive

license_source: github-api


text:
Fix style colors interfering across tilesets

In this Sandcastle, there are two tilesets, each has a different color style. But if you zoom out so both are in view, they will be colored the same.
If you zoom in to one or the other, they will each have the right color. This is happening because a scratch variable is being re-used across all b3dm's:
https://github.com/AnalyticalGraphicsInc/cesium/blob/54acd32f50c332605615a7b37b774c04690ef55c/Source/Scene/Batched3DModel3DTileContent.js#L458
This only happens for tilesets that have 0 features.
I'm not sure if a more elaborate fix is needed here - should model.color have a setter, and use the underlying ._color to keep track of when it changes etc? I noticed there was a model._color that wasn't being used for anything, which I've removed in this commit.
This came up in this forum thread.
Todo:

[x] Update CHANGES
[ ] Add some color tests?

Thanks for the pull request @OmarShehata!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

Thanks @OmarShehata!  This fix looks good.  I'll merge this as soon as CI passes

Thanks for pushing this over the finish line @hpinkos !

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/d/msg/cesium-dev/jLoxC7jcbFY/IZeGDv6EBwAJ
If this issue affects any of these threads, please post a comment like the following:

The issue at https://github.com/AnalyticalGraphicsInc/cesium/pull/8051 has just been closed and may resolve your issue. Look for the change in the next stable release of Cesium or get it now in the master branch on GitHub https://github.com/AnalyticalGraphicsInc/cesium.

source: gharchive/pull-request

authors: OmarShehata cesium-concierge hpinkos


text:
Formatting

Fixes formatting on code and prettifies generated code.

Codecov Report

Merging #57 (f7fc9c0) into 0.6.0 (0cf2813) will not change coverage.
The diff coverage is 25.00%.

:exclamation: Current head f7fc9c0 differs from pull request most recent head 41c3843. Consider uploading reports for the commit 41c3843 to get more accurate results

@@           Coverage Diff           @@
##            0.6.0      #57   +/-   ##
=======================================
  Coverage   86.09%   86.09%
=======================================
  Files           9        9
  Lines         683      683
=======================================
  Hits          588      588
  Misses         95       95

Impacted Files
Coverage Δ

word_filter_codegen/src/lib.rs
82.60% <ø> (ø)

word_filter_codegen/src/pda.rs
88.13% <0.00%> (ø)

word_filter_codegen/src/state.rs
70.00% <33.33%> (ø)

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 0cf2813...41c3843. Read the comment docs.


text:
Opportunities Feature Implementation

Pages Added:

Create/edit Opportunity Post
Opportunity Details Page
Opportunities Search

Notes:

Left the Pay field as string field for now.

#94

Still need to add better dummy information for opportunities.
Added CKeditor 5 for rich-text editing. Put a setup guide in the Readme if you guys want to use it.

I took a look, ran it, and looks cool!

repo: AndrewHocking/DanceConnect

license: MIT


text:
🛑 VaultWarden is down

In e240cba, VaultWarden (https://vault.androz2091.fr) was down:

HTTP code: 502
Response time: 427 ms

Resolved: VaultWarden is back up in 548b78d.


text:
🛑 DDPE is down

In 01195fb, DDPE (https://ddpe.androz2091.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DDPE is back up in 7b18c14 after 2 hours, 46 minutes.


text:
stopwords for Tamil

 Issue by vjyanand
Tue May 21 01:44:06 2019
Originally opened as https://github.com/codelucas/newspaper/pull/701

vjyanand included the following code: https://github.com/codelucas/newspaper/pull/701/commits

added 0.9.3


text:
fix: trailling styleguide mistakes

Hey guys!
I made a little correction on the temp.spec.js.
I use your project as a boilerplate and the component scaffolding quite often. Then I've set up eslint on webpack and a CI that runs eslint . at the root of the project.
Thing is... the *.spec.js files were getting the same style error: Missing semicollon and Space after comma.
All these components were generated by the scaffolding. So I just fixed this little detail left behind.
Cheers.

Thank!

authors: bernardocs fesor

license_source: bigquery


text:
IF|ELSE Event node causes major lag when carried around with it having any events

IF|ELSE nodes are very expensive to drag around, causing major lag to the program - maybe drag&drop should be remade to only have a reference to the dragged event and not physically deleting it? (so the Drag&Drop data dictionary doesn't carry any information besides node index)
https://user-images.githubusercontent.com/3470436/131583320-ec382515-c79f-431e-875f-d0dda9d12497.mp4

https://github.com/AnidemDex/Godot-DialogPlugin/issues/28

Future note: Change the drag_data() behaviour to avoid this in all events

authors: AnidemDex Crystalwarrior

repo: AnidemDex/Godot-DialogPlugin


text:
Add yourself as contributors

Add yourself as contributors in README.md

Add your name
Add github username
Add Linkedin Profile URL

i  would like to contribute for the issue

i would like to work with u

I  would like to work with you

Thanks @Prats2017 and @GunjanGiri  for #14  and #13

authors: Abhilashsipu GunjanGiri Prats207


text:
🐞[Bug]: Page Not found error in the footbar

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Page Not found error when we click on phone icon and mail icon in the footbar
Expected behavior
When we click on phone icon it should redirect to call and when we click on mail it should redirect to mail app
Add ScreenShots

What browsers are you seeing the problem on?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Anishkagupta04 Please assign me this issue

/assign


text:
🛑 AnnAngela.cn is down

In 3d50bdd, AnnAngela.cn (https://ping.annangela.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AnnAngela.cn is back up in 013c22e.


text:
🛑 AnnAngela.cn is down

In facfd2a, AnnAngela.cn (https://ping.annangela.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AnnAngela.cn is back up in 8a3cd63.


text:
🛑 AnnAngela.cn is down

In 66aa5dc, AnnAngela.cn (https://ping.annangela.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AnnAngela.cn is back up in 4860eef.


text:
🛑 AnnAngela.cn is down

In b66a2f0, AnnAngela.cn (https://ping.annangela.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AnnAngela.cn is back up in bb7bd20.


text:
Add moveOnPath method

Add a method that allows passing a path for the character to move along.

this would be very useful for what im building, could it be viable to add a loop property? to make it auto restart the path move when finished

Regarding the loop functionality. Do you have something like this in mind:
If you have a path consisting of adjacent tile positions like: [pos1, pos2, ... posN] and the char arrives at posN. Should he then walk back again (walk the path in reverse order)?

this gif describes what i mean quite nicely, (its just me running around a house) but a npc with the 4 corners of the house being its path, once it gets to the end of the path, it just starts again and runs to pos1 if its not already

When implemented you will have an observable that notifies you when the character has reached the target. Then you can simply restart the movement. So this kind of looping should not be a problem.

Closing this, because it can be achieved using isPositionAllowedFn. Also see this example: https://annoraaq.github.io/grid-engine/examples/pathfinding-restriction.html

authors: Annoraaq xLink

repo: Annoraaq/grid-engine


text:
refactor: backend refactoring

[x] use springboot
[ ] use mysql save data
[x] switch poi
[x] implement a minimum demo

make design doc

repo: AnnularLabs/auto-words


text:
To Do

Upcoming Simple Applications
Regression

Polynomial Regression (Non-Linear)
Perceptrons
Naive Bayes
Support Vector Regressors
Decision Tree Regressors
Random Forest Regressors
CatBoost Regressors
XGBoost Regressors
LightGBMs

Classification

Linear Discriminant Analysis
Multi Layered Perceptrons
Naive Bayes Classification
K-Nearest Neighbour
Support Vector Classifiers
Decision Tree Classifiers
Random Forest Classifiers
CatBoost Classification
XGBoost Classification
LightGBMs

Implementations

Wealth Index
Trailblazers

Always Looking For More Suggestions!

Hello!
Need some help?

Hey @BusyDoingNothing
I would love to collaborate on this repository development and maintenance, if you're down, send me your Discord

Sent a Discord request!


text:
CRUD Example

Is it possible to please give me a complete CRUD example of using database i.e. Add/Edit/Delete/Next/Previous options in table rows by having Checkbox, Combo Box, Textbox, Option Button, Toggle Button, Command Button etc. and almost all most used controls with Comments and clarifications, so that it may increase its usages.

hi  i want to work on this issue

Actually we've got one from @rohitmidha23 now! I'm just trying to convince him to pop it in a repo and give it a readme :D

repo: AnswerDotAI/fasthtml


text:
Unclear instructions.

The instructions on installing this is pretty vague. I've tried copying everything to C:\Users\user\AppData\Local\ActiveWorlds 3D\Help and running the install file, but PowerShell pops up for a millisecond then exits. I enter AW and the guide isn't there. If there was a video or more clear/thorough instructions that would be immensely helpful. Thanks!

@GilgameshAlpha
Copying everything in this repo to the Help directory directly would fail to install the user guide because it isn't at the project root.
To troubleshoot the install.ps1, you can first open a Windows PowerShell terminal by opening your start menu and typing 'PowerShell', navigating to the install directory, and running as described in the readme.  Any errors will print to that terminal and persist after the script is complete.
If you just want to get up and running manually quickly:

Go to: https://raw.githubusercontent.com/AnthonyNeace/ultimate-aw-user-guide/main/user-guides/ultimateawuserguide.awh
Save As > default.awh in the AW User Guide directory on your local machine.  This is usually at C:\Users\<your_windows_user>\AppData\Local\ActiveWorlds 3D\Help

This is all the install script does.

@GilgameshAlpha I've incorporated the steps above into the readme.  Please let me know if you have any further issue.

Resolving issue; thanks and feel free to post another one if you need any more help!

authors: AnthonyNeace GilgameshAlpha

repo: AnthonyNeace/ultimate-aw-user-guide


text:
Crash when restarting nodes

Steps to reproduce:

Run a 2 DC system with 2 nodes each (e.g. using https://github.com/dajenet/antidote/blob/e1daa9df148ea414a598c1feab5e4d8737b8b78c/monitoring/network/dc2n2/docker-compose.yml)
Start the system (docker-compose up)
Wait until the system has started (output link_1        | Connection setup!)
Stop the system (Ctrl+c)
Restart the system (docker-compose up)

The system crashes with the following error message:
antidote2_1   | 2019-11-05 13:33:46.636 [error] <0.1073.0>
 @inter_dc_manager:-check_node_restart/0-lc$^2/1-0-:199
 CRASH REPORT Process <0.1073.0> with 0 neighbours exited with reason:
  no match of right hand value ok
    in inter_dc_manager:'-check_node_restart/0-lc$^2/1-0-'/1 line 199
    in application_master:init/4 line 138

Full output:
Starting dc2n2_antidote1_1 ... done
Starting dc2n2_antidote2_1 ... done
Starting dc2n2_antidote3_1 ... done
Starting dc2n2_cadvisor_1  ... done
Starting dc2n2_antidote4_1 ... done
Starting dc2n2_link_1      ... done
Starting dc2n2_prometheus_1 ... done
Starting dc2n2_grafana_1    ... done
Attaching to dc2n2_antidote1_1, dc2n2_antidote3_1, dc2n2_cadvisor_1, dc2n2_antidote4_1, dc2n2_antidote2_1, dc2n2_link_1, dc2n2_prometheus_1, dc2n2_grafana_1
antidote3_1   | Waiting for Antidote logger...✔
antidote1_1   | Waiting for Antidote logger...✔
antidote1_1   | 2019-11-05 13:30:59.703 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,bucket_types} = true
antidote1_1   | 2019-11-05 13:30:59.720 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote1_1   | 2019-11-05 13:31:00.000 [warning] <0.900.0> lager_error_logger_h dropped 178 messages in the last second that exceeded the limit of 50 messages/sec
antidote1_1   | 2019-11-05 13:31:01.035 [warning] <0.900.0> lager_error_logger_h dropped 357 messages in the last second that exceeded the limit of 50 messages/sec
antidote1_1   | 2019-11-05 13:31:02.799 [info] <0.821.0> Application antidote started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:31:09.805 [info] <0.982.0>@riak_core_gossip:log_node_added:354 'antidote@antidote2' joined cluster with status 'joining'
antidote1_1   | 2019-11-05 13:32:28.174 [info] <0.967.0>@riak_core_app:stop:47 Stopped  application riak_core.
antidote1_1   | 2019-11-05 13:32:28.186 [info] <0.914.0> alarm_handler: {clear,system_memory_high_watermark}
antidote1_1   | 2019-11-05 13:32:28.187 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/etc/hosts"}}
antidote1_1   | 2019-11-05 13:32:28.187 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/"}}
antidote1_1   | IP address not set; defaulting to 127.0.0.1.
antidote1_1   | NODE_NAME: antidote@antidote1
antidote1_1   | COOKIE: antidote
antidote1_1   | IP: 127.0.0.1
antidote1_1   | HOSTNAME: 1f7b8bcc163e
antidote1_1   | 2019-11-05 13:32:45.662 [info] <0.821.0> Application lager started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.666 [info] <0.821.0> Application sasl started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.667 [info] <0.821.0> Application crypto started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.669 [info] <0.821.0> Application riak_sysmon started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.670 [info] <0.821.0> Application os_mon started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.670 [info] <0.821.0> Application basho_stats started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.671 [info] <0.821.0> Application eleveldb started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.671 [info] <0.821.0> Application pbkdf2 started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.671 [info] <0.821.0> Application poolboy started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.672 [info] <0.942.0> Setup running ...
antidote1_1   | 2019-11-05 13:32:45.676 [info] <0.914.0> alarm_handler: {set,{{disk_almost_full,"/"},[]}}
antidote1_1   | 2019-11-05 13:32:45.676 [info] <0.914.0> alarm_handler: {set,{{disk_almost_full,"/etc/hosts"},[]}}
antidote1_1   | 2019-11-05 13:32:45.676 [info] <0.942.0> Directories verified. Res = ok
antidote1_1   | 2019-11-05 13:32:45.676 [info] <0.942.0> Setup finished processing hooks (Mode=normal)...
antidote1_1   | 2019-11-05 13:32:45.677 [info] <0.821.0> Application setup started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.678 [info] <0.949.0>@exometer_report:do_start_reporters:613 Starting reporters with []
antidote1_1   | 2019-11-05 13:32:45.678 [info] <0.821.0> Application exometer_core started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.710 [info] <0.914.0> alarm_handler: {set,{system_memory_high_watermark,[]}}
antidote1_1   | 2019-11-05 13:32:45.713 [info] <0.821.0> Application clique started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.714 [info] <0.821.0> Application bear started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.715 [info] <0.821.0> Application folsom started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:45.816 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,vnode_routing} = proxy
antidote1_1   | 2019-11-05 13:32:45.824 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,staged_joins} = true
antidote1_1   | 2019-11-05 13:32:45.835 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,resizable_ring} = true
antidote1_1   | 2019-11-05 13:32:45.853 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,fold_req_version} = v2
antidote1_1   | 2019-11-05 13:32:45.867 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,security} = true
antidote1_1   | 2019-11-05 13:32:45.873 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,bucket_types} = true
antidote1_1   | 2019-11-05 13:32:45.884 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote1_1   | 2019-11-05 13:32:45.984 [info] <0.923.0>@riak_core_sysmon_handler:handle_event:92 monitor long_schedule <0.864.0> [{name,logger_std_h_default},{initial_call,{logger_olp,init,1}},{almost_current_function,{gen_server,loop,7}},{message_queue_len,0}] [{timeout,60},{in,{gen_server,loop,7}},{out,{gen_server,loop,7}}]
antidote1_1   | 2019-11-05 13:32:46.026 [warning] <0.900.0> lager_error_logger_h dropped 26 messages in the last second that exceeded the limit of 50 messages/sec
antidote1_1   | 2019-11-05 13:32:46.026 [info] <0.821.0> Application riak_core started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.027 [info] <0.821.0> Application cuttlefish started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.027 [info] <0.821.0> Application erlzmq started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.028 [info] <0.821.0> Application runtime_tools started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.028 [info] <0.821.0> Application tools started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.033 [info] <0.821.0> Application prometheus started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.049 [info] <0.821.0> Application elli started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.049 [info] <0.821.0> Application accept started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.049 [info] <0.821.0> Application elli_prometheus started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.049 [info] <0.821.0> Application prometheus_process_collector started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.050 [info] <0.821.0> Application antidote_stats started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.050 [info] <0.821.0> Application asn1 started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.050 [info] <0.821.0> Application public_key started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:46.060 [info] <0.821.0> Application ssl started on node antidote@antidote1
antidote1_1   | 2019-11-05 13:32:47.117 [warning] <0.900.0> lager_error_logger_h dropped 509 messages in the last second that exceeded the limit of 50 messages/sec
antidote3_1   | 2019-11-05 13:30:59.795 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote3_1   | 2019-11-05 13:31:00.001 [warning] <0.900.0> lager_error_logger_h dropped 226 messages in the last second that exceeded the limit of 50 messages/sec
antidote3_1   | 2019-11-05 13:31:01.044 [warning] <0.900.0> lager_error_logger_h dropped 309 messages in the last second that exceeded the limit of 50 messages/sec
antidote3_1   | 2019-11-05 13:31:01.477 [info] <0.923.0>@riak_core_sysmon_handler:handle_event:92 monitor long_schedule <0.1074.0> [{name,clocksi_vnode_master},{initial_call,{riak_core_vnode_master,init,1}},{almost_current_function,{gen_server,loop,7}},{message_queue_len,0}] [{timeout,55},{in,{gen_server,loop,7}},{out,{gen_server,loop,7}}]
antidote3_1   | 2019-11-05 13:31:02.938 [info] <0.821.0> Application antidote started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:31:30.673 [info] <0.982.0>@riak_core_gossip:log_node_added:354 'antidote@antidote4' joined cluster with status 'joining'
antidote3_1   | 2019-11-05 13:32:28.332 [info] <0.967.0>@riak_core_app:stop:47 Stopped  application riak_core.
antidote3_1   | 2019-11-05 13:32:28.338 [info] <0.914.0> alarm_handler: {clear,system_memory_high_watermark}
antidote3_1   | 2019-11-05 13:32:28.338 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/"}}
antidote3_1   | 2019-11-05 13:32:28.338 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/etc/hosts"}}
antidote3_1   | IP address not set; defaulting to 127.0.0.1.
antidote3_1   | NODE_NAME: antidote@antidote3
antidote3_1   | COOKIE: antidote
antidote3_1   | IP: 127.0.0.1
antidote3_1   | HOSTNAME: 01f2303713b3
cadvisor_1    | W1105 13:32:44.005508       1 manager.go:349] Could not configure a source for OOM detection, disabling OOM events: open /dev/kmsg: no such file or directory
antidote3_1   | 2019-11-05 13:32:46.780 [info] <0.821.0> Application lager started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.784 [info] <0.821.0> Application sasl started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.784 [info] <0.821.0> Application crypto started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.785 [info] <0.821.0> Application riak_sysmon started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.787 [info] <0.821.0> Application os_mon started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.787 [info] <0.821.0> Application basho_stats started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.788 [info] <0.821.0> Application eleveldb started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.788 [info] <0.821.0> Application pbkdf2 started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.788 [info] <0.821.0> Application poolboy started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.789 [info] <0.942.0> Setup running ...
antidote3_1   | 2019-11-05 13:32:46.791 [info] <0.914.0> alarm_handler: {set,{{disk_almost_full,"/"},[]}}
antidote3_1   | 2019-11-05 13:32:46.791 [info] <0.914.0> alarm_handler: {set,{{disk_almost_full,"/etc/hosts"},[]}}
antidote3_1   | 2019-11-05 13:32:46.791 [info] <0.914.0> alarm_handler: {set,{system_memory_high_watermark,[]}}
antidote3_1   | 2019-11-05 13:32:46.800 [info] <0.942.0> Directories verified. Res = ok
antidote3_1   | 2019-11-05 13:32:46.801 [info] <0.942.0> Setup finished processing hooks (Mode=normal)...
antidote3_1   | 2019-11-05 13:32:46.801 [info] <0.821.0> Application setup started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.804 [info] <0.949.0>@exometer_report:do_start_reporters:613 Starting reporters with []
antidote3_1   | 2019-11-05 13:32:46.808 [info] <0.821.0> Application exometer_core started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.842 [info] <0.821.0> Application clique started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.842 [info] <0.821.0> Application bear started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.843 [info] <0.821.0> Application folsom started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:46.941 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,vnode_routing} = proxy
antidote3_1   | 2019-11-05 13:32:46.953 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,staged_joins} = true
antidote3_1   | 2019-11-05 13:32:46.959 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,resizable_ring} = true
antidote3_1   | 2019-11-05 13:32:46.970 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,fold_req_version} = v2
antidote3_1   | 2019-11-05 13:32:46.978 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,security} = true
antidote3_1   | 2019-11-05 13:32:46.993 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,bucket_types} = true
antidote3_1   | 2019-11-05 13:32:47.001 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote3_1   | 2019-11-05 13:32:47.056 [warning] <0.900.0> lager_error_logger_h dropped 26 messages in the last second that exceeded the limit of 50 messages/sec
antidote3_1   | 2019-11-05 13:32:47.056 [info] <0.821.0> Application riak_core started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.056 [info] <0.821.0> Application cuttlefish started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.056 [info] <0.821.0> Application erlzmq started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.057 [info] <0.821.0> Application runtime_tools started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.057 [info] <0.821.0> Application tools started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.061 [info] <0.821.0> Application prometheus started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.062 [info] <0.821.0> Application elli started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.062 [info] <0.821.0> Application accept started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.062 [info] <0.821.0> Application elli_prometheus started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.062 [info] <0.821.0> Application prometheus_process_collector started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.066 [info] <0.821.0> Application antidote_stats started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.066 [info] <0.821.0> Application asn1 started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.066 [info] <0.821.0> Application public_key started on node antidote@antidote3
antidote3_1   | 2019-11-05 13:32:47.067 [info] <0.821.0> Application ssl started on node antidote@antidote3
antidote4_1   | Waiting for Antidote logger...✔
antidote4_1   | 2019-11-05 13:31:01.248 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,security} = true
antidote4_1   | 2019-11-05 13:31:01.254 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,bucket_types} = true
antidote4_1   | 2019-11-05 13:31:01.296 [info] <0.998.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote4_1   | 2019-11-05 13:31:02.202 [warning] <0.900.0> lager_error_logger_h dropped 568 messages in the last second that exceeded the limit of 50 messages/sec
antidote4_1   | 2019-11-05 13:31:03.535 [info] <0.821.0> Application antidote started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:31:32.201 [info] <0.982.0>@riak_core_gossip:log_node_changed:351 'antidote@antidote4' changed from 'joining' to 'valid'
antidote4_1   | 2019-11-05 13:32:28.348 [info] <0.967.0>@riak_core_app:stop:47 Stopped  application riak_core.
antidote4_1   | 2019-11-05 13:32:28.357 [info] <0.914.0> alarm_handler: {clear,system_memory_high_watermark}
antidote4_1   | 2019-11-05 13:32:28.357 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/etc/hosts"}}
antidote4_1   | 2019-11-05 13:32:28.357 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/"}}
antidote4_1   | IP address not set; defaulting to 127.0.0.1.
antidote4_1   | NODE_NAME: antidote@antidote4
antidote4_1   | COOKIE: antidote
antidote4_1   | IP: 127.0.0.1
antidote4_1   | HOSTNAME: d3c4a8beb7b1
prometheus_1  | level=info ts=2019-11-05T13:32:48.692Z caller=main.go:293 msg="no time or size retention was set so using the default time retention" duration=15d
prometheus_1  | level=info ts=2019-11-05T13:32:48.692Z caller=main.go:329 msg="Starting Prometheus" version="(version=2.12.0, branch=HEAD, revision=43acd0e2e93f9f70c49b2267efa0124f1e759e86)"
prometheus_1  | level=info ts=2019-11-05T13:32:48.692Z caller=main.go:330 build_context="(go=go1.12.8, user=root@7a9dbdbe0cc7, date=20190818-13:53:16)"
prometheus_1  | level=info ts=2019-11-05T13:32:48.692Z caller=main.go:331 host_details="(Linux 4.18.0-25-generic #26-Ubuntu SMP Mon Jun 24 09:32:08 UTC 2019 x86_64 3d37a9c871d3 (none))"
prometheus_1  | level=info ts=2019-11-05T13:32:48.692Z caller=main.go:332 fd_limits="(soft=1048576, hard=1048576)"
prometheus_1  | level=info ts=2019-11-05T13:32:48.693Z caller=main.go:333 vm_limits="(soft=unlimited, hard=unlimited)"
prometheus_1  | level=info ts=2019-11-05T13:32:48.704Z caller=main.go:654 msg="Starting TSDB ..."
prometheus_1  | level=info ts=2019-11-05T13:32:48.706Z caller=web.go:448 component=web msg="Start listening for connections" address=0.0.0.0:9090
prometheus_1  | level=info ts=2019-11-05T13:32:48.718Z caller=head.go:509 component=tsdb msg="replaying WAL, this may take awhile"
prometheus_1  | level=info ts=2019-11-05T13:32:48.898Z caller=head.go:557 component=tsdb msg="WAL segment loaded" segment=0 maxSegment=1
prometheus_1  | level=info ts=2019-11-05T13:32:48.898Z caller=head.go:557 component=tsdb msg="WAL segment loaded" segment=1 maxSegment=1
prometheus_1  | level=info ts=2019-11-05T13:32:48.910Z caller=main.go:669 fs_type=EXT4_SUPER_MAGIC
prometheus_1  | level=info ts=2019-11-05T13:32:48.910Z caller=main.go:670 msg="TSDB started"
prometheus_1  | level=info ts=2019-11-05T13:32:48.910Z caller=main.go:740 msg="Loading configuration file" filename=/data/prometheus.yml
prometheus_1  | level=info ts=2019-11-05T13:32:48.911Z caller=main.go:768 msg="Completed loading of configuration file" filename=/data/prometheus.yml
prometheus_1  | level=info ts=2019-11-05T13:32:48.911Z caller=main.go:623 msg="Server is ready to receive web requests."
antidote2_1   | Waiting for Antidote logger...✔
antidote2_1   | 2019-11-05 13:32:27.857 [error] <0.1726.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1726.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:32:27.858 [error] <0.1636.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1636.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:32:27.859 [error] <0.1638.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:32:27.871 [error] <0.1638.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1638.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:32:28.011 [warning] <0.900.0> lager_error_logger_h dropped 43 messages in the last second that exceeded the limit of 50 messages/sec
antidote2_1   | 2019-11-05 13:32:28.011 [info] <0.967.0>@riak_core_app:stop:47 Stopped  application riak_core.
antidote2_1   | 2019-11-05 13:32:28.627 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with riak_core_vnode:start_link() at undefined exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context shutdown_error
antidote2_1   | 2019-11-05 13:32:28.631 [info] <0.914.0> alarm_handler: {clear,system_memory_high_watermark}
antidote2_1   | 2019-11-05 13:32:28.631 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/etc/hosts"}}
antidote2_1   | 2019-11-05 13:32:28.631 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/"}}
antidote2_1   | IP address not set; defaulting to 127.0.0.1.
antidote2_1   | NODE_NAME: antidote@antidote2
antidote2_1   | COOKIE: antidote
antidote2_1   | IP: 127.0.0.1
antidote2_1   | HOSTNAME: 401ae01d8433
dc2n2_link_1 exited with code 0
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Starting Grafana" logger=server version=6.3.6 commit=fdd2117 branch=HEAD compiled=2019-09-23T08:14:34+0000
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_DATA=/var/lib/grafana"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_LOGS=/var/log/grafana"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PLUGINS=/var/lib/grafana/plugins"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PROVISIONING=/etc/grafana/provisioning"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="App mode production" logger=settings
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing SqlStore" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Connecting to DB" logger=sqlstore dbtype=sqlite3
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Starting DB migration" logger=migrator
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing HTTPServer" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing InternalMetricsService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing RemoteCache" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing QuotaService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing PluginManager" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Starting plugin search" logger=plugins
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing RenderingService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing AlertEngine" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing DatasourceCacheService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing HooksService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing LoginService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing SearchService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing ServerLockService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing TracingService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing UsageStatsService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing UserAuthTokenService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing CleanUpService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing NotificationService" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing provisioningServiceImpl" logger=server
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=warn msg="[Deprecated] the datasource provisioning config is outdated. please upgrade" logger=provisioning.datasources filename=/etc/grafana/provisioning/datasources/all.yml
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=eror msg="Can't read alert notification provisioning files from directory" logger=provisioning.notifiers path=/etc/grafana/provisioning/notifiers error="open /etc/grafana/provisioning/notifiers: no such file or directory"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=warn msg="[Deprecated] the dashboard provisioning config is outdated. please upgrade" logger=provisioning.dashboard filename=/etc/grafana/provisioning/dashboards/all.yml
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=warn msg="[Deprecated] The folder property is deprecated. Please use path instead." logger=provisioning.dashboard type=file name=default
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="Initializing Stream Manager"
grafana_1     | t=2019-11-05T13:32:49+0000 lvl=info msg="HTTP Server Listen" logger=http.server address=0.0.0.0:3000 protocol=http subUrl= socket=
antidote3_1   | 2019-11-05 13:32:48.037 [warning] <0.900.0> lager_error_logger_h dropped 509 messages in the last second that exceeded the limit of 50 messages/sec
antidote4_1   | 2019-11-05 13:32:48.291 [info] <0.821.0> Application lager started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.308 [info] <0.821.0> Application sasl started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.308 [info] <0.821.0> Application crypto started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.309 [info] <0.821.0> Application riak_sysmon started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.310 [info] <0.821.0> Application os_mon started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.311 [info] <0.821.0> Application basho_stats started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.311 [info] <0.821.0> Application eleveldb started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.311 [info] <0.821.0> Application pbkdf2 started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.312 [info] <0.821.0> Application poolboy started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.313 [info] <0.942.0> Setup running ...
antidote4_1   | 2019-11-05 13:32:48.313 [info] <0.942.0> Directories verified. Res = ok
antidote4_1   | 2019-11-05 13:32:48.314 [info] <0.942.0> Setup finished processing hooks (Mode=normal)...
antidote4_1   | 2019-11-05 13:32:48.315 [info] <0.821.0> Application setup started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.317 [info] <0.949.0>@exometer_report:do_start_reporters:613 Starting reporters with []
antidote4_1   | 2019-11-05 13:32:48.318 [info] <0.914.0> alarm_handler: {set,{{disk_almost_full,"/"},[]}}
antidote4_1   | 2019-11-05 13:32:48.318 [info] <0.914.0> alarm_handler: {set,{{disk_almost_full,"/etc/hosts"},[]}}
antidote4_1   | 2019-11-05 13:32:48.318 [info] <0.821.0> Application exometer_core started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.322 [info] <0.914.0> alarm_handler: {set,{system_memory_high_watermark,[]}}
antidote4_1   | 2019-11-05 13:32:48.322 [info] <0.821.0> Application clique started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.323 [info] <0.821.0> Application bear started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.324 [info] <0.821.0> Application folsom started on node antidote@antidote4
antidote4_1   | 2019-11-05 13:32:48.385 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,vnode_routing} = proxy
antidote4_1   | 2019-11-05 13:32:48.393 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,staged_joins} = true
antidote4_1   | 2019-11-05 13:32:48.409 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,resizable_ring} = true
antidote4_1   | 2019-11-05 13:32:48.423 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,fold_req_version} = v2
antidote4_1   | 2019-11-05 13:32:48.471 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,security} = true
antidote4_1   | 2019-11-05 13:32:48.481 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,bucket_types} = true
antidote4_1   | 2019-11-05 13:32:48.492 [info] <0.1000.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote4_1   | 2019-11-05 13:32:49.054 [warning] <0.900.0> lager_error_logger_h dropped 586 messages in the last second that exceeded the limit of 50 messages/sec
antidote2_1   | 2019-11-05 13:32:49.005 [info] <0.821.0> Application lager started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.007 [info] <0.821.0> Application sasl started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.007 [info] <0.821.0> Application crypto started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.008 [info] <0.821.0> Application riak_sysmon started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.009 [info] <0.821.0> Application os_mon started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.010 [info] <0.821.0> Application basho_stats started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.010 [info] <0.821.0> Application eleveldb started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.010 [info] <0.821.0> Application pbkdf2 started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.010 [info] <0.821.0> Application poolboy started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.011 [info] <0.945.0> Setup running ...
antidote2_1   | 2019-11-05 13:32:49.016 [info] <0.916.0> alarm_handler: {set,{system_memory_high_watermark,[]}}
antidote2_1   | 2019-11-05 13:32:49.017 [info] <0.945.0> Directories verified. Res = ok
antidote2_1   | 2019-11-05 13:32:49.017 [info] <0.945.0> Setup finished processing hooks (Mode=normal)...
antidote2_1   | 2019-11-05 13:32:49.018 [info] <0.821.0> Application setup started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.021 [info] <0.952.0>@exometer_report:do_start_reporters:613 Starting reporters with []
antidote2_1   | 2019-11-05 13:32:49.021 [info] <0.821.0> Application exometer_core started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.025 [info] <0.821.0> Application clique started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.025 [info] <0.821.0> Application bear started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.025 [info] <0.821.0> Application folsom started on node antidote@antidote2
antidote2_1   | 2019-11-05 13:32:49.025 [info] <0.916.0> alarm_handler: {set,{{disk_almost_full,"/"},[]}}
antidote2_1   | 2019-11-05 13:32:49.026 [info] <0.916.0> alarm_handler: {set,{{disk_almost_full,"/etc/hosts"},[]}}
antidote2_1   | 2019-11-05 13:32:49.090 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,vnode_routing} = proxy
antidote2_1   | 2019-11-05 13:32:49.096 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,staged_joins} = true
antidote2_1   | 2019-11-05 13:32:49.106 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,resizable_ring} = true
antidote2_1   | 2019-11-05 13:32:49.113 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,fold_req_version} = v2
antidote2_1   | 2019-11-05 13:32:49.121 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,security} = true
antidote2_1   | 2019-11-05 13:32:49.131 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,bucket_types} = true
antidote2_1   | 2019-11-05 13:32:49.142 [info] <0.1001.0>@riak_core_capability:process_capability_changes:568 New capability: {riak_core,net_ticktime} = true
antidote2_1   | 2019-11-05 13:32:50.029 [warning] <0.902.0> lager_error_logger_h dropped 582 messages in the last second that exceeded the limit of 50 messages/sec
antidote3_1   | 2019-11-05 13:32:54.776 [info] <0.821.0> Application antidote started on node antidote@antidote3
antidote1_1   | 2019-11-05 13:32:55.792 [info] <0.2680.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote1_1   | 2019-11-05 13:32:55.792 [info] <0.2681.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote1_1   | 2019-11-05 13:32:55.792 [info] <0.2682.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote1_1   | 2019-11-05 13:32:55.793 [info] <0.2683.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote1_1   | 2019-11-05 13:32:55.793 [info] <0.2684.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote1_1   | 2019-11-05 13:32:55.793 [info] <0.2685.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote4_1   | 2019-11-05 13:32:56.780 [info] <0.821.0> Application antidote started on node antidote@antidote4
antidote2_1   | 2019-11-05 13:32:59.087 [info] <0.2651.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote2_1   | 2019-11-05 13:32:59.087 [info] <0.2652.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote2_1   | 2019-11-05 13:32:59.087 [info] <0.2653.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote2_1   | 2019-11-05 13:32:59.087 [info] <0.2654.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote2_1   | 2019-11-05 13:32:59.087 [info] <0.2655.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote2_1   | 2019-11-05 13:32:59.087 [info] <0.2656.0>@riak_core:wait_for_application:413 Waiting for application antidote to start (0 seconds).
antidote2_1   | 2019-11-05 13:33:46.636 [error] <0.1073.0>@inter_dc_manager:-check_node_restart/0-lc$^2/1-0-:199 CRASH REPORT Process <0.1073.0> with 0 neighbours exited with reason: no match of right hand value ok in inter_dc_manager:'-check_node_restart/0-lc$^2/1-0-'/1 line 199 in application_master:init/4 line 138
antidote2_1   | 2019-11-05 13:33:46.638 [info] <0.821.0>@inter_dc_manager:-check_node_restart/0-lc$^2/1-0-:199 Application antidote exited with reason: no match of right hand value ok in inter_dc_manager:'-check_node_restart/0-lc$^2/1-0-'/1 line 199
antidote2_1   | 2019-11-05 13:33:46.644 [error] <0.1653.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.647 [error] <0.1653.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1653.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.648 [error] <0.1653.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1653.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.653 [error] <0.1655.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.653 [error] <0.1675.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.653 [error] <0.1665.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.654 [error] <0.1663.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.654 [error] <0.1651.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.655 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1653.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.655 [error] <0.1655.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1655.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.656 [error] <0.1665.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1665.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.656 [error] <0.1663.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1663.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.656 [error] <0.1651.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1651.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.657 [error] <0.1675.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1675.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.660 [error] <0.1651.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1651.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.661 [error] <0.1675.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1675.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.662 [error] <0.1669.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.663 [error] <0.1669.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1669.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.667 [error] <0.1673.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.667 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1675.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.667 [error] <0.1673.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1673.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.671 [error] <0.1661.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.671 [error] <0.1667.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote2_1   | 2019-11-05 13:33:46.673 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1651.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.674 [error] <0.1665.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1665.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.676 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1665.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.635 [error] <0.1088.0>@inter_dc_manager:-check_node_restart/0-lc$^2/1-0-:199 CRASH REPORT Process <0.1088.0> with 0 neighbours exited with reason: no match of right hand value ok in inter_dc_manager:'-check_node_restart/0-lc$^2/1-0-'/1 line 199 in application_master:init/4 line 138
antidote1_1   | 2019-11-05 13:33:46.637 [info] <0.821.0>@inter_dc_manager:-check_node_restart/0-lc$^2/1-0-:199 Application antidote exited with reason: no match of right hand value ok in inter_dc_manager:'-check_node_restart/0-lc$^2/1-0-'/1 line 199
antidote1_1   | 2019-11-05 13:33:46.646 [error] <0.1684.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.648 [error] <0.1672.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.651 [error] <0.1690.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.651 [error] <0.1682.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.652 [error] <0.1672.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1672.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.652 [error] <0.1684.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1684.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.652 [error] <0.1690.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1690.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.652 [error] <0.1682.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1682.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.652 [error] <0.1670.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.653 [error] <0.1670.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1670.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.657 [error] <0.1672.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1672.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.658 [error] <0.1692.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.659 [error] <0.1674.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.659 [error] <0.1684.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1684.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.661 [error] <0.1692.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1692.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.661 [error] <0.1674.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1674.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.661 [error] <0.1670.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1670.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.667 [error] <0.1648.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.667 [error] <0.1694.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.667 [error] <0.1682.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1682.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.668 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1682.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.668 [error] <0.1692.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1692.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.668 [error] <0.1674.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1674.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.668 [error] <0.1648.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1648.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.668 [error] <0.1694.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1694.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.669 [error] <0.1680.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.670 [error] <0.1696.0>@riak_core_vnode:vnode_command:377 inter_dc_log_sender_vnode command failed {badarg,[{ets,lookup,[a_stable_meta_data_table,my_dc],[]},{stable_meta_data_server,read_meta_data,1,[{file,"/usr/src/antidote/src/stable_meta_data_server.erl"},{line,85}]},{dc_meta_data_utilities,get_my_dc_id,0,[{file,"/usr/src/antidote/src/dc_meta_data_utilities.erl"},{line,139}]},{inter_dc_txn,ping,3,[{file,"/usr/src/antidote/src/inter_dc_txn.erl"},{line,65}]},{inter_dc_log_sender_vnode,handle_command,3,[{file,"/usr/src/antidote/src/inter_dc_log_sender_vnode.erl"},{line,135}]},{riak_core_vnode,vnode_command,3,[{file,"/usr/src/antidote/_build/default/lib/riak_core/src/riak_core_vnode.erl"},{line,374}]},{gen_fsm_compat,handle_msg,8,[{file,"/usr/src/antidote/_build/default/lib/gen_fsm_compat/src/gen_fsm_compat.erl"},{line,464}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,249}]}]}
antidote1_1   | 2019-11-05 13:33:46.671 [error] <0.1680.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1680.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.671 [error] <0.1696.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1696.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.676 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1672.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.726 [info] <0.967.0>@riak_core_app:stop:47 Stopped  application riak_core.
antidote1_1   | 2019-11-05 13:33:46.950 [error] <0.1690.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1690.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.951 [error] <0.1648.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1648.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.951 [error] <0.1694.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1694.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.951 [error] <0.1696.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1696.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.951 [error] <0.1680.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1680.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote1_1   | 2019-11-05 13:33:46.952 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1692.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.952 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1684.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.952 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1670.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.952 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1674.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.952 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1694.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.952 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1648.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.953 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1690.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.953 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1696.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.953 [error] <0.971.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1680.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote1_1   | 2019-11-05 13:33:46.959 [info] <0.914.0> alarm_handler: {clear,system_memory_high_watermark}
antidote1_1   | 2019-11-05 13:33:46.959 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/etc/hosts"}}
antidote1_1   | 2019-11-05 13:33:46.960 [info] <0.914.0> alarm_handler: {clear,{disk_almost_full,"/"}}
antidote2_1   | 2019-11-05 13:33:46.677 [error] <0.1669.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1669.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.679 [error] <0.1673.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1673.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.683 [error] <0.1663.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1663.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.685 [error] <0.1655.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1655.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.687 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1669.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.688 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1673.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.689 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1663.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.689 [error] <0.1661.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1661.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.691 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1655.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.692 [error] <0.1661.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1661.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.692 [error] <0.1667.0>@stable_meta_data_server:read_meta_data:85 gen_fsm <0.1667.0> in state active terminated with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.693 [error] <0.1667.0>@stable_meta_data_server:read_meta_data:85 CRASH REPORT Process <0.1667.0> with 0 neighbours exited with reason: bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85
antidote2_1   | 2019-11-05 13:33:46.699 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1667.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated
antidote2_1   | 2019-11-05 13:33:46.723 [info] <0.970.0>@riak_core_app:stop:47 Stopped  application riak_core.
antidote2_1   | 2019-11-05 13:33:46.995 [error] <0.974.0>@stable_meta_data_server:read_meta_data:85 Supervisor riak_core_vnode_sup had child undefined started with {riak_core_vnode,start_link,undefined} at <0.1661.0> exit with reason bad argument in call to ets:lookup(a_stable_meta_data_table, my_dc) in stable_meta_data_server:read_meta_data/1 line 85 in context child_terminated

errors.log
console.log
crash.log
error.log

Is it important that the DCs have 2 nodes each?

I guess it is not important, you can try with one node per DC.

I thought so, too. But it works for me with one node per DC, and 2 nodes in only 1 DC.

authors: albsch peterzeller

repo: AntidoteDB/antidote


text:
Add support for HR tag via Markdown

By having a line solely as --- you will be able to add an <hr> tag in the html

Closed by https://github.com/Antonio-Bennett/rssg/commit/8b70bf0f

repo: Antonio-Bennett/rssg


text:
adding the paths options

I wanted to have the option to specify a paths array. If the asset is not in one of the paths specified, then I don't want to have it removed (despite it's size). Let me know if this works for you. I appreciate your feedback.

This is a great addition, thanks for contributing!

Thank you @AnujRNair! When you get a chance, can you publish an updated version to NPM. I'm currently using this plugin for one of my projects.

I just did! https://github.com/AnujRNair/webpack-extraneous-file-cleanup-plugin/releases/tag/v1.0.4

Awesome. Thank you so much for the quick response!

license: mit


text:
Option to load accounts using private key

Overview
Something like this to load accounts from a private key. This is not encouraged but some times comes in handy. May be add a warning to force users to use ape accounts import instead of loading the private key.
Specification
from ape import accounts

acc = accounts.from_key("0x00dead")

Dependencies
N/A

Can move some of the logic here: https://github.com/ApeWorX/ape/blob/main/src/ape_accounts/_cli.py#L129
into classmethods KeyfileAccount.from_mnemonic or KeyfileAccount.from_private_key

Actually, noticed that https://github.com/ApeWorX/ape/blob/main/src/ape_accounts/_cli.py#L103-L112 and https://github.com/ApeWorX/ape/blob/main/src/ape_accounts/_cli.py#L146-L154 are quite similar code

Added import_account_from_mnemonic() and import_account_from_private_key() to the eth_accounts core plugin.  They'll be documented in the accounts user guide after release.

authors: Aviksaikat fubuloubu mikeshultz

repo: ApeWorX/ape