HtmlToText
-- aller au contenu développeur web passionné menu et widgets j’aime les jolies nèfles me contacter mon cv rechercher : profils @overnetcity 27 juillet 2018 bye @hipchat , long live @slackhq atlassian.com/blog/announcem… @overnetcity 16 juillet 2018 hi @younited , i just can't login to my investor account, and the "forgot password" doesn't seem to work either... any help? @overnetcity 6 juillet 2018 elle est pour toi celle-ci @tejerka wiki.php.net/rfc/object-com… @overnetcity 28 juin 2018 great plans for #php8 ! externals.io/message/102415 @overnetcity 15 juin 2018 victoire !! #composte #collectif https://t.co/xgfa8qowm0 articles récents how storj farming monitoring made me optimize my rpi3 setup? real time monitoring for your storj farming nodes with grafana, influxdb and collectd build your own storj.io farming node with raspberry and meccano my garage door is accessible through a rest api entreprises, libérez la créativité de vos développeurs implémenter un « annuler / rétablir » avec angularjs et le command pattern react.js, grunt, browserify et cdn facebook reactjs – quelques ressources pour bien commencer array.foreach n’est pas toujours la meilleure solution ! accéder à un service angularjs depuis la console catégories angularjs développement web elasticsearch emberjs insa iphone javascript node.js non classé php raspberry pi reactjs ressources utiles storj symfony how storj farming monitoring made me optimize my rpi3 setup? in the last couple of weeks, i wrote 2 articles about the storj.io project : build your own storj.io farming node with raspberry and meccano real time monitoring for your storj farming nodes with grafana, influxdb and collectd the first explains how to build a farming node with a raspberry pi and the second how to monitor your node with grafana . what i learned from monitoring? i’m now monitoring my nodes for a few days and noticed some interesting patterns that worth be mentioned. first of all, the sharing amount increase step by step every day on the same period of time, between 10pm and noon in france which basically corresponds to working hours in usa. you can see the beautifull stairs drawn on the graph below: without surprise, we can also notice this pattern in the upload / download rate graph below: more surprisingly, i noticed that one of my nodes was restarting with the same pattern: after a bit of inspection, it appears that memory usage hits the limit on download / upload peaks and make storjshare daemon restart. of course, the rpi3 memory amount is very limited ( 1gb of ram ) and the daemon quickly consume all of it when shards are uploaded to the node: that is very uncool because, when storjshare daemon crashes, you potentially loose the current contract and the corresponding data. loose of contracts means less data, which obviously means, less money! how to optimize your raspberry pi for storj farming? i presume that you have a raspberry pi 3 , setup with raspbian jessie lite (without user interface). if you don’t, you likely won’t have enough power to host an efficient storj farming node. to setup raspbian lite, please refer to the official doc here . so what now? is there a way to optimize the raspberry pi to efficiently farm with storj? the good news is, you can customize a few things in the rpi « bios ». the closest thing to a traditional bios for the raspberry pi can be found in /boot/config.txt. in that file, you can tweak a lot of parameters, all described here . to optimize your raspberry, insert the following lines in your config file: # settings to optimize storj farming force_turbo=1 boot_delay=1 disable_splash=1 # reduce amount of memory dedicated to gpu gpu_mem=16 # reduce power consumption dtoverlay=pi3-disable-wifi dtoverlay=pi3-disable-bt the most interesting parameter is gpu_mem=16. it reduces to a minimum the amount of ram dedicated to your the rpi gpu which in turns, frees some usefull megabytes for your storjshare-daemon . removing wifi and bt should reduce consumption a little and also deactivate associated services. do not forget to reboot your raspberry pi to see the changes take effect. of course, do not install anything else on your raspberry pi that consume ram or cpu. finally, if you have setup a monitoring solution as i mentionned in one of my previous articles, please be aware that sending metrics with collectd too often is very inefficient and consume a lot of cpu/ram. you should send metrics at most each 2 minutes in my opinion. with this config, your farming node should be a lot more stable and efficient. at least, it’s what happened to mine! publié le 17 mai 2017 28 février 2018 auteur catégories raspberry pi , storj mots-clés blockchain , farming , mining , storj , storj.io laisser un commentaire sur how storj farming monitoring made me optimize my rpi3 setup? real time monitoring for your storj farming nodes with grafana, influxdb and collectd a couple of weeks ago, i put online three storj farming nodes. two of them are hosted on my ovh dedicated servers and i even built my own node with meccano, a raspberry pi and four old used hard drives . after putting them online, i found myself connecting every day on those three different machines to run storjshare status , htop , iotop and even ifconfig to gather metrics and understand how my nodes were behaving. while this could be ok at first, this doesn’t seem to be a good solution in the long run. monitoring your nodes and their host is really important to help you understand how they perform, how to improve their efficiency over time and of course, being alerted if something goes wrong. as you know, the more your node is online, the more data it will collect. to simplify the monitoring process, i setup a very classic combination of grafana , influxdb and collectd . feel free to replace each one of these components by one of their many alternatives, according to your likings. have a look at telegraf for example to replace collectd. setup your storj monitoring stack first thing to do is to setup collectd which will be responsible to collect metrics from your host and from storj-daemon rpc port. assuming your using debian, run the following command: sudo apt install collectd then setup the storj collectd plugin by running: npm install -g storj-collectd-plugin now, edit config file /etc/collectd/collectd.conf to enable the plugins your interested in. at least, configure the network plugin with the ip address or domain name of the webserver on which you will setup influxdb (127.0.0.1 if influxdb is on same host) and add a plugin exec entry for the collectd-storj-exec-plugin : loadplugin ... loadplugin exec loadplugin network <plugin network> server "ip_server_influxdb" "25826" </plugin> <plugin exec> interval 120 exec "youruser" "collectd-storj-exec-plugin" </plugin> finally, add the following lines in /usr/share/collectd/types.db : peers value:gauge:0:u shared value:gauge:0:u restarts value:gauge:0:u don’t forget to restart collectd service: systemctl restart collectd repeat the operation on every node’s host. it’s now time to setup influxdb . assuming your still using debian, run the following commands: curl -sl https://repos.influxdata.com/influxdb.key | sudo apt-key add - source /etc/os-release test $version_id = "7" && echo "deb https://repos.influxdata.com/debian wheezy stable" | sudo tee /etc/apt/sources.list.d/influxdb.list test $version_id = "8" && echo "deb https://repos.influxdata.com/debian jessie stable" | sudo tee /etc/apt/sources.list.d/influxdb.list sudo apt update && sudo apt install influxdb see documentation for more informations on the setup process. then, enable influxdb collectd listener by adding the following lines in /etc/influxdb/influxdb.conf : [collectd] enabled = true bind-address = ":25826" database = "collectd_db" typesdb = "/usr/share/collectd/types.db" restart influxdb: sudo systemctl restart influxdb finally, install grafana wherever you w
Informations Whois
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
Domain Name: overnetcity.com
Registry Domain ID: 111946577_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2017-01-16T14:35:13Z
Creation Date: 2004-02-16T15:12:32Z
Registrar Registration Expiration Date: 2018-02-16T15:12:32Z
Registrar: GANDI SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: abuse@support.gandi.net
Registrar Abuse Contact Phone: +33.170377661
Reseller:
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status:
Domain Status:
Domain Status:
Domain Status:
Registry Registrant ID:
Registrant Name: Olivier Balais
Registrant Organization:
Registrant Street: Obfuscated whois Gandi-63-65 boulevard Massena
Registrant City: Obfuscated whois Gandi-Paris
Registrant State/Province: Paris
Registrant Postal Code: 75013
Registrant Country: FR
Registrant Phone: +33.170377666
Registrant Phone Ext:
Registrant Fax: +33.143730576
Registrant Fax Ext:
Registrant Email: e287da4ff1daa50d551b58ab01894c50-1310609@contact.gandi.net
Registry Admin ID:
Admin Name: Olivier Balais
Admin Organization:
Admin Street: Obfuscated whois Gandi-63-65 boulevard Massena
Admin City: Obfuscated whois Gandi-Paris
Admin State/Province: Paris
Admin Postal Code: 75013
Admin Country: FR
Admin Phone: +33.170377666
Admin Phone Ext:
Admin Fax: +33.143730576
Admin Fax Ext:
Admin Email: e287da4ff1daa50d551b58ab01894c50-1310609@contact.gandi.net
Registry Tech ID:
Tech Name: Olivier Balais
Tech Organization:
Tech Street: Obfuscated whois Gandi-63-65 boulevard Massena
Tech City: Obfuscated whois Gandi-Paris
Tech State/Province: Paris
Tech Postal Code: 75013
Tech Country: FR
Tech Phone: +33.170377666
Tech Phone Ext:
Tech Fax: +33.143730576
Tech Fax Ext:
Tech Email: e287da4ff1daa50d551b58ab01894c50-1310609@contact.gandi.net
Name Server: B.DNS.GANDI.NET
Name Server: C.DNS.GANDI.NET
Name Server: A.DNS.GANDI.NET
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
Name Server:
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2017-07-12T12:41:28Z <<<
For more information on Whois status codes, please visit
https://www.icann.org/epp
Reseller Email:
Reseller URL:
Personal data access and use are governed by French law, any use for the purpose of unsolicited mass commercial advertising as well as any mass or automated inquiries (for any intent other than the registration or modification of a domain name) are strictly forbidden. Copy of whole or part of our database without Gandi's endorsement is strictly forbidden.
A dispute over the ownership of a domain name may be subject to the alternate procedure established by the Registry in question or brought before the courts.
For additional information, please contact us via the following form:
https://www.gandi.net/support/contacter/mail/
REGISTRAR GANDI SAS
REFERRER http://www.gandi.net
SERVERS
SERVER com.whois-servers.net
ARGS domain =overnetcity.com
PORT 43
SERVER whois.gandi.net
ARGS overnetcity.com
PORT 43
TYPE domain
RegrInfo
DOMAIN
NAME overnetcity.com
NSERVER
A.DNS.GANDI.NET 173.246.98.1
B.DNS.GANDI.NET 213.167.229.1
C.DNS.GANDI.NET 217.70.179.1
STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
CHANGED 2017-01-16
CREATED 2004-02-16
EXPIRES 2018-02-16
REGISTERED yes
Go to top
overnetcity.com rapport :
Visitez le site