Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2 cores with 2GB works fine indeedas for me very little ram or cpu.I have tested on 3 machines.I am getting segfaults on debian 7 64 bit 1 GB. With or without the script.I'm just getting Error Restarting.if minerd is down.Script write error message and restart.
Tested debian 7 64 bit.
Check thread , cpu size and memory size.
What is result minerd command?
What is you os?
ram or thread size problem test minerd manual.
minerd --url http://work.mmcpool.com/ --user MQoJDguWCMAug2J2rRUEsZPC9UjdSCppkS --threads 1
root@hertz1:~/mmcminer# ./minerd --url http://work.mmcpool.com/ --user <address> --threads 1
[02:47:24] Binding thread 0 to cpu 0
Segmentation fault
What is you server os and server cpu & ram size?
1. debian wheezy 2 cores 4 GB behind a firewall, keeps getting rejects (edit: not exactly firewall, but home lan, default settings, not mine to configure)
2. digital ocean debian 7 x64 1 core 1 GB, the above segfault
3. digital ocean ubuntu 13.04 x64 1 core, 1 GB, the above segfault
You need cpu+ram.
I am testing script digital ocean debian 7 x64 with 4 cpu.
make big droplet and test.
I have tested on 3 machines.I am getting segfaults on debian 7 64 bit 1 GB. With or without the script.I'm just getting Error Restarting.if minerd is down.Script write error message and restart.
Tested debian 7 64 bit.
Check thread , cpu size and memory size.
What is result minerd command?
What is you os?
ram or thread size problem test minerd manual.
minerd --url http://work.mmcpool.com/ --user MQoJDguWCMAug2J2rRUEsZPC9UjdSCppkS --threads 1
root@hertz1:~/mmcminer# ./minerd --url http://work.mmcpool.com/ --user <address> --threads 1
[02:47:24] Binding thread 0 to cpu 0
Segmentation fault
What is you server os and server cpu & ram size?
I am getting segfaults on debian 7 64 bit 1 GB. With or without the script.I'm just getting Error Restarting.if minerd is down.Script write error message and restart.
Tested debian 7 64 bit.
Check thread , cpu size and memory size.
What is result minerd command?
What is you os?
ram or thread size problem test minerd manual.
minerd --url http://work.mmcpool.com/ --user MQoJDguWCMAug2J2rRUEsZPC9UjdSCppkS --threads 1
I am getting segfaults on debian 7 64 bit 1 GB. With or without the script.I'm just getting Error Restarting.if minerd is down.Script write error message and restart.
Tested debian 7 64 bit.
Check thread , cpu size and memory size.
What is result minerd command?
What is you os?
Thinking in the other direction, does >>1GB, say 3-4GB benefit the speed of mining MMC (disregarding the possible use of more threads)?Should work at 1GB. It has to generate a set of data to perform hashes on which is why it uses so much RAMYes, i was guessing at a memory limit problem. Maybe I will try a 1 GB solution.You need 1gb ram to mine MMC and try disabling the firewall and setting up portforwarding.The first is behind a firewall at my home only getting rejects.I keep getting this, mining for an hourIf its two different machines we can rule out it being them (well, its unlikely).
PROOF OF WORK RESULT: Rejected
On another machine I start the miner
./minerd --url http://work.mmcpool.com/ --user <address> --threads 1
and it says "KIlled" after being. What can be wrong?
Whats your network setup?
The second is a cloud vps server (512MB, 1 virtual core)
Yes, i was guessing at a memory limit problem. Maybe I will try a 1 GB solution.You need 1gb ram to mine MMC and try disabling the firewall and setting up portforwarding.The first is behind a firewall at my home only getting rejects.I keep getting this, mining for an hourIf its two different machines we can rule out it being them (well, its unlikely).
PROOF OF WORK RESULT: Rejected
On another machine I start the miner
./minerd --url http://work.mmcpool.com/ --user <address> --threads 1
and it says "KIlled" after being. What can be wrong?
Whats your network setup?
The second is a cloud vps server (512MB, 1 virtual core)
The first is behind a firewall at my home only getting rejects.I keep getting this, mining for an hourIf its two different machines we can rule out it being them (well, its unlikely).
PROOF OF WORK RESULT: Rejected
On another machine I start the miner
./minerd --url http://work.mmcpool.com/ --user <address> --threads 1
and it says "KIlled" after being. What can be wrong?
Whats your network setup?
Ethereum is the future my friends. Coming soon
Powerball, DAC sounds cool, and allot faster to develop than BitShares.
What is the status on this one?
Have we found some people to develop it?
It is on our roadmap, to be undertaken when we are able to raise enough funds to pay for its development.
But if some other developer were to start credible work on it, we would be happy to cheer them on.
It doesn't matter to us who develops these DACs, we will invest in them on their merits like everyone else.
This generates decentralization in developers just like the DACs themselves.
Once we have multiple credible developers, hopefully on different continents, the whole industry will be much safer.
Stan,
I honestly think one of the first and most important tasks of Invictus Innovations should be to develop and release an exquisite DAC development kit. If this were any other industry, say the gaming industry for example and you're building a platform for construction of games then you release an easy to use development kit to facilitate the process. If it were mobile technology like Android then you'd release a kit which any programmer can make use of using whatever language they know.
The reason most developers (myself included) don't know where or how to get started right now is because there isn't a development kit. This would mean a lot of documentation, reference protocols and a high level interface. If there are enough programmers opening up the development so that other programmers can write reference implementations, or templates, that could help too.
I've taken a look at Keyhotee and I can figure out what it's doing, and I've looked at Protoshares as well. Protoshares is based mostly on Bitcoin and Bitcoin is very daunting for anybody to mess around with, as a result not a lot of people are able to make anything more than small changes. When I tried to compile Protoshares I could not get it to compile in Linux due to the various dependencies.
Bitshares in my opinion is where it really gets interesting. I hope the API for it is high level enough that I can build on top of it and that development can take place in many programming languages at once. I could easily see a scenario where we are building DACs on top of DACs.. A development kit would be very very helpful. Can a separate thread be started for the resources / tools / skills requirements - this will help us to plan ahead.
