hi guy, someone can generate a node at port 80 or 8080 for bypass firewall restriction? Thanks
up addnode 91.121.8.23:8080 add it's a new node, still to synch yet. Wait five minutes it's ready :-) FaSan
|
|
|
*/1 * * * * root /bin/ps -ef|grep -v grep|grep memorycoind >/dev/null || /usr/local/bin/memorycoind -daemon
change name of process and/or path about your installation This does not really help because a, the process is often there, but just hangs b, it's not there, but the database has been damaged c, it's not there, but the wallet has been damaged It's a fast and simple script for restart the daemon, if, of course, the crash are not damaged nothing. Need a more articolate script that check the integrity of all, but you will cannot execute it every minute. FaSan
|
|
|
A script to restart the daemon when this happens would be very handy.
A very simple script, I hope can help you : write it into the file /etc/crontab */1 * * * * root /bin/ps -ef|grep -v grep|grep memorycoind >/dev/null || /usr/local/bin/memorycoind -daemon
change name of process and/or path about your installation FaSan
|
|
|
+1, the rcpthreads or port setting is only used when you remotely access the server. Not when mining.
It's not. Your built-in miner talk with client with rcp protocol FaSan
|
|
|
tterminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error> >' what(): boost::thread_resource_error: Resource temporarily unavailable
does anyone getting this error in the deamon? me too ,10 servers ,same error,and other errors My miner is not working anymore with newest code. I get: EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_6system12system_errorEEEEE context: unable to load ssl2 md5 routines memorycoin in AppInit() What OS ? Looking some openssl bug. Try to update openssl and openssl-dev packages FaSan
|
|
|
how can i get all node of net for search if there is one on specific port? thanks
You cannot get all node on the net. You can get node from your client : or if you have time, port scanning over the web. Not all node use default port ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) FaSan
|
|
|
BULL. Post a pic of htop and i will believe you.
This for my smart friend. Client still up from the last update, 7 hours ago. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F6vQvX6o.jpg&t=663&c=rd1LEatkr8VmhQ) Last lines of debug.log : 2013-12-18 09:14:07 send version message: version 70001, blocks=606, us=xxxxxxxxx:1968, them=xxxxxxx:58284, peer=xxxxxxxxx:58284 2013-12-18 09:14:07 receive version message: version 70001, blocks=6, us=xxxxxxxxx:1968, them=xxxxxxxx:1968, peer=xxxxxxxxx:58284 2013-12-18 09:14:07 found solution - 4744 / 1968 / 2749664900 2013-12-18 09:14:12 socket closed 2013-12-18 09:14:12 disconnecting node xxxxxxxxxx:41668 2013-12-18 09:14:13 found solution - 8989 / 1968 / 729351395 2013-12-18 09:14:23 testHash 1603d4be08c4cfc75e52b27eb717022571eca3070b5de35eb6fe69da5dbe5df0, 4 2013-12-18 09:14:23 Start Search 2013-12-18 09:14:26 found solution - 12316 / 1968 / 3905085647
FaSan
|
|
|
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
try both last night, still got crash ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) , now will try only genproclimit. Any other suggestions? I still to look the source code, but I've not find nothing yet. Without rpcthreads my server was still up for three days without problems. Try and give a me a feedback. Now it's my time to sleep :-) Good luck ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) FaSan
|
|
|
Delete the "rpcthreads" setting and use only the "genproclimit". It's the onlyone solution for now
|
|
|
Usually forks start with block X, not with the release of the new client. So both old and the new clients can mine until that block. I didn't confirm this with with FreeTrade, but I think you can sleep well ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) X=750 Please download new clients or recompile source. New version should show v0.8.53.0-unk-beta Kind regards to Mister Kimoto. Kimoto Gravity Well ? Very interesting to look the code ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
Comunque io non capisco i developer di questa moneta
Hanno lanciato il Memorycoin (Forse era un alpha?) ed aveva problemi. Ora hanno lanciato il memorycoin 2.0 (forse una beta?) ed ha problemi.
Il bello è che il prezzo per un singolo MMC è inspiegabile...0.02 l'uno? e sulla base di che?! Comunque per chi deve acquistare io andrei cauto... per chi invece ci vuole solo speculare...sparate fuochi se trovare un blocco!
Ma guarda... in realtà in fase di pre-mine con il fatto che veniva cambiato 1:10 con le PTS le vendevano a 0.4 :-) e secondo me così dovrebbe essere. Un pò troppo alta la rew sui blocchi per mantenere un cambio simile. Cmq tornando al fattore K, guarda questo : http://www.chainbrowser.com/memorycoin/address/MLaBhkNB7iMKDKmPqCDTSKrPy4QiXPg9CA/FaSan
|
|
|
è assurdo.
Due pc a 3.3 hashes per minuto e niente. Ma che server ci vuole!
Per quello che ho potuto vedere in questi giorni, la velocità è si importante ma non fondamentale. C'è gente che ha minato blocchi anche con 0.6 E' il fattore K che ci manca ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif)
|
|
|
Thank you, I will look now :-) FaSan
|
|
|
Ok finally clean.
Set the "rpcthreads" = number of CPUs Cores and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
I little update. With this setting, very sometimes can be a collision for filled rpc calls. I still to try now "rpcthreads" = number of CPUs Cores + 4 I will update FaSan
|
|
|
Cant sync? Any good nodes, please?
Add me : addnode 69.30.254.58:1968 add FaSan
|
|
|
Ok finally clean.
Set the "rpcthreads" = number of CPUs and set the "genproclimit" = the same value.
To me still to work fine from more of one hour.
FaSan
Hi Fa, is that number of CPUs or number of core because genproclimit usually set to number of cores, not # of CPUs You right, my mistake, sorry. Number of cores
|
|
|
My server continue to work without stop. It's clean that we have some different config but I've not understand where yet.
I read in many thread that some people set the param "rpcthreads". I've never set it, I always use "genproclimit=-1". Can be a good test if you can try it.
FaSan
IS IT ! I've try to set the "rpcthreads" and my client crash in little minutes. With "genproclimit=-1" you tell to client to use all CPUs avalaible. Now I look the source code for try to fix ;-) FaSan Ok finally clean. Set the "rpcthreads" = number of CPUs Cores and set the "genproclimit" = the same value. To me still to work fine from more of one hour. FaSan
|
|
|
My server continue to work without stop. It's clean that we have some different config but I've not understand where yet.
I read in many thread that some people set the param "rpcthreads". I've never set it, I always use "genproclimit=-1". Can be a good test if you can try it.
FaSan
IS IT ! I've try to set the "rpcthreads" and my client crash in little minutes. With "genproclimit=-1" you tell to client to use all CPUs avalaible. Now I look the source code for try to fix ;-) FaSan
|
|
|
I've not vps, only dedicate servers. But I can try Amazon, still connect ;-)
|
|
|
|