Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 12 2021 09:28
    jejdouay opened #437
  • Jun 07 2021 12:01
    afck commented #401
  • Jun 01 2021 18:26
    whereistejas commented #401
  • Jun 01 2021 18:20
    whereistejas commented #401
  • Nov 29 2020 10:17
    afck commented #435
  • Nov 17 2020 05:15
    promptlyspeaking opened #435
  • Apr 01 2020 08:58
    DrPeterVanNostrand removed as member
  • Apr 01 2020 08:56
    vkomenda removed as member
  • Apr 01 2020 08:56
    VladimirNovgorodov removed as member
  • Apr 01 2020 08:56
    DemiMarie removed as member
  • Apr 01 2020 08:55
    symanovich-a removed as member
  • Apr 01 2020 08:54
    phahulin removed as member
  • Apr 01 2020 08:54
    natlg removed as member
  • Apr 01 2020 08:54
    pablofullana removed as member
  • Apr 01 2020 08:54
    mbr removed as member
  • Apr 01 2020 08:05
    c0gent removed as member
  • Apr 01 2020 08:04
    dforsten removed as member
  • Mar 31 2020 16:29
    afck edited as member
  • Mar 31 2020 16:28
    afck added as member
  • Mar 31 2020 09:35
    VladimirNovgorodov added as member
David Forstenlechner
@dforsten
Right now it is limited by the block timestamp having 1s granularity.
Meaning if you remove the 1s minimum block time you run into block verification errors pretty quickly.
Genysys
@Genysys
thats hwat i thought
if you make it 0.5 i reckon you would run into more
David Forstenlechner
@dforsten
Otherwise I see no problem with honeybadger going sub-second.
In Parity Unit tests the engine is configured differently, there the block timestamp has 1ms granularity.
With globally distributed nodes and larger node counts that 1s lower bound for block times will probably not be an obstacle for performance though. It would only make sense in highly centralized and high performance network environments.
Genysys
@Genysys
_status = Completed!

Parity Docker Image         = brave/honey-badger:latest
Number of Parity Nodes      = 4
ECS Task Revision           = 1
CloudWatch Log Group        = /ecs/parity/ubuntu-test

bastion_host_ip = 3.17.77.93
bucket_name = us-east-2-ecs-ubuntu-test-871448652392df6b
chain_id = 6309
ecs_cluster_name = parity-network-ubuntu-test
ethstats_host_url = http://3.17.77.93:3000
grafana_host_url = http://3.17.77.93:3001
grafana_password = Et6z39nbVC0ttyBN
grafana_username = admin
network_name = ubuntu-test
private_key_file = <sensitive>
Wrote summarry output to:  .m
I cant reproduce the error from an ubuntu machine
4 node cluster comes up in under 15 mins
David Forstenlechner
@dforsten
I will re-try in a different region, maybe there is still one resource I have missed which prevents terraform to complete successfully.
Which permissions did you give the AWS user running the scripts?
David Forstenlechner
@dforsten
Are you running the apply command in the mjolnir-cli Docker container or outside the Docker container?
I will try in a different region and on my Mac to make sure it is not a problem only occurring on my Ubuntu box.
Genysys
@Genysys
user has all the admin rights
for everything (probably not the most hygienic)
David Forstenlechner
@dforsten
I will try that as well - normally I should see errors if permissions are missing, but the first time I ran the script I got the furthest (and destroy worked too), and the first time I used a user with full admin rights as well.
David Forstenlechner
@dforsten
I ran into the same issue with hanging on remote exec on the bastion host on my Mac, running it in the Docker container (since I assume that is the most reproducible environment), used an AWS user with "admin" rights and left all settings in the values-local.yml file to defaults, except for AWS keys and region. I also used a different AWS region to rule out remnant AWS resources from previous run as cause of failure.
I will try it again tomorrow at the office to rule out issues with my local internet connection. Do you know any way how I could diagnose the issue further?
Genysys
@Genysys
Check cloud watch
Might give more insight
Check the log groups ; there is one ( I think it’s meta bootstrap ) that might show what’s gong on there
Happy to jump on a call if it helps
David Forstenlechner
@dforsten
In the parity logs on CloudWatch I see a lot of messages like these:
ERROR: ld.so: object '/node/lib/libfaketime.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Could that be a problem or would it run nonetheless?
All of the many parity log files in the CloudWatch Log Group show exclusively these error messages.
David Forstenlechner
@dforsten

In the ECS cluser task JSON file I see this:

        {
          "name": "LD_PRELOAD",
          "value": "/node/lib/libfaketime.so"
        }

Could it be that in the container it tries to run that library simply is not available, and for what purpose is this entry necessary at all?

Genysys
@Genysys
Will try to debug this but I doubt it’s the issue.
It usually shows that till the file is placed on the s3 bucket and copied but will have to double check
David Forstenlechner
@dforsten
This is the only information I could glean from the CloudWatch logs.
To debug further I will have to re-build the scripts from scratch step by step to see where they start to fail for me.
Which would not be the worst option, Terraform looks very powerful and worth getting to know at a deeper level, but if you have any other options I could try on my end it would be appreciated.
Genysys
@Genysys
can we please have a screen share session?
I am really struggling to understand what the issue is on your end as I am able to bring up hbbft multple times
David Forstenlechner
@dforsten
Sure, which time would be best for you?
Genysys
@Genysys
jsut seeing this
are you free in 30 mins? or from 3-430 CET today?
David Forstenlechner
@dforsten
Just came back from
the dentist, 3pm works for me!
W
Genysys
@Genysys
great will send an invite over email!
David Forstenlechner
@dforsten
Description:DescriptionLaunching a new EC2 instance. Status Reason: The subnet ID 'subnet-0be8a3666c358cf39' does not exist. Launching EC2 instance failed.
Cause:CauseAt 2019-12-10T11:37:03Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 5.
David Forstenlechner
@dforsten
Awesome, works now - thanks Samuel! :-)
Genysys
@Genysys
hey ! It was nice meeting @dforsten @afck the other week
in berlin
Andreas Fackler
@afck
Nice meeting you too! :slight_smile:
gauravagarwaltal
@gauravagarwaltal
@Genysys @dforsten @afck Hey, I want to integrate HBBFT in my blockchain framework. Please suggest a way for doing that.
Igor Barinov
@igorbarinov
@gauravagarwaltal what's your blockchain framework?
gauravagarwaltal
@gauravagarwaltal
@igorbarinov I need to add hbbft consensus in this framework.
David Forstenlechner
@dforsten
@gauravagarwaltal
An example how to integrate hbbft into a Blockchain client is available here:
https://github.com/artis-eco/openethereum
gauravagarwaltal
@gauravagarwaltal
@dforsten Thanks. I will look at this.
Sameroom
@sameroom-bot
<Sameroom> Whoops! You've exceeded your daily message limit on this Sameroom account (it will reset in 24 hours and 0 minutes). If you have too many Tubes for your budget, pause or delete some Tubes on the Manage page. If you dont have a subscription, visit pricing to upgrade to unlimited messaging.