running parity 1.6.6 on a pi 3

[Corto77]

dear Diglos
I wanted to ask my question on reddit.com, but i was not able to create an account there...
I try to run parity on a pi 3, but it's not possible to change the OS to your ethraspbian.
So I have a pi3 with jessie and I get parity from the official binaries
http://d1h4xl4cr1h0mo.cloudfront.net/v1.6.6/armv7-unknown-linux-gnueabihf/parity_1.6.6_armhf.deb
and I run it as service
I used these Args : --warp --cache=256 --pruning-history 128 --logging info
But regularly parity stops with 2 kinds of error

1. terminate called after throwing an instance of 'std::bad_alloc'
2. fatal runtime error: out of memory

Do you encounter these problems.
There was an issue on github openethereum/parity-ethereum#4694...

Is there something special to configure Jessie ?

Kind Regards

[diglos]

Hi, yeah, it can happen eventually. Keep in mind that the Rpi has only 1GB of RAM. You can try to lower the cache value to 128, get rid of pruning history and reduce the videoram memory (Ethraspbian is set to 16MB instead of the 64MB Raspbian default): Edit /boot/config.txt and add this line (need a reboot): gpu_mem=16 Other than that I don't think there's much difference between your SO and my image. Hope this works :-) Diego Losada 2017-04-22 11:21 GMT+02:00 Corto77 <notifications@github.com>:

…

dear Diglos I wanted to ask my question on reddit.com, but i was not able to create an account there... I try to run parity on a pi 3, but it's not possible to change the OS to your ethraspbian. So I have a pi3 with jessie and I get parity from the official binaries http://d1h4xl4cr1h0mo.cloudfront.net/v1.6.6/armv7-unknown-linux-gnueabihf/ parity_1.6.6_armhf.deb and I run it as service I used these Args : --warp --cache=256 --pruning-history 128 --logging info But regularly parity stops with 2 kinds of error 1. terminate called after throwing an instance of 'std::bad_alloc' 2. fatal runtime error: out of memory Do you encounter these problems. There was an issue on github openethereum/parity-ethereum#4694 <openethereum/parity-ethereum#4694>... Is there something special to configure Jessie ? Kind Regards — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQDugB9PSS6ujnXgW8o0as8EOOU6KPV-ks5rycZ-gaJpZM4NFB0F> .

[Corto77]

Thank you for your answer. I had already the videoram memory to 16 MB (with raspi-config). In fact I did the inverse about the cache : I set the value to 512 and also I delete the log-file. And now it seems to work correctly : no more error kind Regards Le 23/04/2017 à 00:18, Diego Losada a écrit :

…

Hi, yeah, it can happen eventually. Keep in mind that the Rpi has only 1GB of RAM. You can try to lower the cache value to 128, get rid of pruning history and reduce the videoram memory (Ethraspbian is set to 16MB instead of the 64MB Raspbian default): Edit /boot/config.txt and add this line (need a reboot): gpu_mem=16 Other than that I don't think there's much difference between your SO and my image. Hope this works :-) Diego Losada 2017-04-22 11:21 GMT+02:00 Corto77 ***@***.***>: > dear Diglos > I wanted to ask my question on reddit.com, but i was not able to create > an account there... > I try to run parity on a pi 3, but it's not possible to change the OS to > your ethraspbian. > So I have a pi3 with jessie and I get parity from the official binaries > http://d1h4xl4cr1h0mo.cloudfront.net/v1.6.6/armv7-unknown-linux-gnueabihf/ > parity_1.6.6_armhf.deb > and I run it as service > I used these Args : --warp --cache=256 --pruning-history 128 --logging info > But regularly parity stops with 2 kinds of error > > 1. terminate called after throwing an instance of 'std::bad_alloc' > 2. fatal runtime error: out of memory > > Do you encounter these problems. > There was an issue on github openethereum/parity-ethereum#4694 > <openethereum/parity-ethereum#4694>... > > Is there something special to configure Jessie ? > > Kind Regards > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#2>, or mute the > thread > <https://github.com/notifications/unsubscribe-auth/AQDugB9PSS6ujnXgW8o0as8EOOU6KPV-ks5rycZ-gaJpZM4NFB0F> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aacb0iJ-u4zagj0AXp-s74NzalhHNE0jks5rynywgaJpZM4NFB0F>.