Monero Support

[sanyok]

I can' transfer my mined coins on testnet:

Starting refresh...
Height 543984, transaction <2f79d1207b58140fb6c70f0186288b756ede78eea61e5f2d3f1afb77877fc683>, received 0.001960964009
Height 543984, transaction <2f79d1207b58140fb6c70f0186288b756ede78eea61e5f2d3f1afb77877fc683>, received 0.070000000000
Height 543984, transaction <2f79d1207b58140fb6c70f0186288b756ede78eea61e5f2d3f1afb77877fc683>, received 0.400000000000
Height 543984, transaction <2f79d1207b58140fb6c70f0186288b756ede78eea61e5f2d3f1afb77877fc683>, received 10.000000000000
Height 543985, transaction <474145d7f3138443d9f683ea6de1d98fb1fc5db66190e8184be898b79a1b213e>, received 0.001950977168
Height 543985, transaction <474145d7f3138443d9f683ea6de1d98fb1fc5db66190e8184be898b79a1b213e>, received 0.070000000000
Height 543985, transaction <474145d7f3138443d9f683ea6de1d98fb1fc5db66190e8184be898b79a1b213e>, received 0.400000000000
Height 543985, transaction <474145d7f3138443d9f683ea6de1d98fb1fc5db66190e8184be898b79a1b213e>, received 10.000000000000
Height 543986, transaction <af5fed11c5edb1b1995c8839bfbdef3015e6d9ac36a8e7e5564aa31535e1646c>, received 0.001940990338
Height 543986, transaction <af5fed11c5edb1b1995c8839bfbdef3015e6d9ac36a8e7e5564aa31535e1646c>, received 0.070000000000
Height 543986, transaction <af5fed11c5edb1b1995c8839bfbdef3015e6d9ac36a8e7e5564aa31535e1646c>, received 0.400000000000
Height 543986, transaction <af5fed11c5edb1b1995c8839bfbdef3015e6d9ac36a8e7e5564aa31535e1646c>, received 10.000000000000
Refresh done, blocks received: 3                               
balance: 125.663951016974, unlocked balance: 0.000000000000, including unlocked dust: 0.000000000000
**********************************************************************
Use "help" command to see the list of available commands.
**********************************************************************
[wallet A1QQC5]: save
Wallet data saved
[wallet A1QQC5]: transfer 9wrwukvvQgwcPnLaAEnoSqHzQtXdKbcSb5ZhQ6Rcn1Uqd8KbBF2zjQWc4VsCFVujewMdsHfbeUEUfDw pZdt5zq3UE6bB715 1
Error: not enough money to transfer, available only 0.000000000000, transaction amount 1.000000000000 = 1.000000000000 + 0.000000000000 (fee)

Anybody can tell me why?
And sometime input transactions are disappers after simplewallet restart..
Once I restarted this wallet and found balance "0.000000000000, unlocked balance: 0.000000000000, including unlocked dust: 0.000000000000"


versions:
wallet v0.8.8.7-0193bfc
bitmonero v0.8.8.7-0193bfc

thanks for any  help..

[smooth]

balance: 125.663951016974, unlocked balance: 0.000000000000

Newly mined coins take a while to mature.

[sanyok]

Hmm. "Unlocked balance" is a confirmed coins? Thank's

Another problem is actual.. Coins from balance disappears before going confirmed.
How can I check, are my block makes orphaned?
Today night I mined ~100 block's, and only last 30 of them I seen in my wallet.
After wallet restart, balance was 0

[smooth]

Hmm. "Unlocked balance" is a confirmed coins? Thank's

Another problem is actual.. Coins from balance disappears before going confirmed.
How can I check, are my block makes orphaned?
Today night I mined ~100 block's, and only last 30 of them I seen in my wallet.
After wallet restart, balance was 0

Sounds like it. I know some tests have been using testnet having to do with hard forking, so that may be an issue.

[sanyok]

Looks like I'm mining my own chain, and when somebody else mining chain longer - another chain is accepting by my bitmonerod..
Becides, no one of my blocks aren't accepted by the network, why this can occurs?   Port 28080 visible under NAT.

[smooth]

Looks like I'm mining my own chain, and when somebody else mining chain longer - another chain is accepting by my bitmonerod..
Becides, no one of my blocks aren't accepted by the network, why this can occurs?  Port 28080 visible under NAT.

I'm not sure, really. As I said the testnet is used for tests, you should expect usual behavior and if you aren't a developer its probably not for you.

If you want to experiment with mining another option is to try QuazarCoin (QCN). Not maintained or anything but the code was forked from Monero last year so things like simplewallet look much the same. The difficulty is very low.

[sanyok]

I'll try Quazarcoin mainnet, thanks for idea bro

[akaman]

I am having some compilation difficulties today, whilst setting up a couple of new Monero nodes on Ubuntu servers. I am following these instructions:
https://antanst.com/blog/2015/05/22/how-to-set-up-a-monero-node-in-ubuntu-14.04/

I have cloned the current dev branch (https://github.com/monero-project/bitmonero.git) and am running `make release-static`. Then this:

Code:

[ 71%] Building CXX object src/common/CMakeFiles/common.dir/command_line.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/common/CMakeFiles/common.dir/command_line.cpp.o] Error 4
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[2]: *** [src/common/CMakeFiles/common.dir/all] Error 2
make[2]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make: *** [release-static-64] Error 2

Any suggestions appreciated!!


Here is the full output of `make`:

Code:

bitmonerod@ubuntu:~/bitmonero$ make release-static
mkdir -p build/release
cd build/release && cmake -D STATIC=ON -D ARCH="x86-64" -D BUILD_64=ON -D CMAKE_BUILD_TYPE=release ../.. && make
-- Could not find DEVELOPER_LOCAL_TOOLS in env (not required)
-- BOOST_IGNORE_SYSTEM_PATHS defaults to OFF
-- Could not find DEVELOPER_LIBUNBOUND_OLD in env (not required)
-- Building for a 64-bit system
-- Could not find DATABASE in env (not required unless you want to change database type from default: lmdb)
-- Using LMDB as default DB type
-- Detecting version of miniupnpc in path: /usr/include/miniupnpc
-- Found miniupnpc version is pre v1.7
-- Using miniupnpc from local source tree for static build
-- Looking for libunbound
-- Using 64-bit LMDB from source tree
-- Enabling AES support
-- Found Git: /usr/bin/git
Doxygen: graphviz not found - graphs disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /home/bitmonerod/bitmonero/build/release
make[1]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[2]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[  0%] Built target version
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[  8%] Built target upnpc-static
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 55%] Built target unbound
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 57%] Built target lmdb
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 60%] Built target otshell_utils
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 71%] Built target crypto
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
[ 71%] Building CXX object src/common/CMakeFiles/common.dir/command_line.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/common/CMakeFiles/common.dir/command_line.cpp.o] Error 4
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[2]: *** [src/common/CMakeFiles/common.dir/all] Error 2
make[2]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make: *** [release-static-64] Error 2

[GingerAle]

I am having some compilation difficulties today, whilst setting up a couple of new Monero nodes on Ubuntu servers. I am following these instructions:
https://antanst.com/blog/2015/05/22/how-to-set-up-a-monero-node-in-ubuntu-14.04/

I have cloned the current dev branch (https://github.com/monero-project/bitmonero.git) and am running `make release-static`. Then this:

Code:

[ 71%] Building CXX object src/common/CMakeFiles/common.dir/command_line.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/common/CMakeFiles/common.dir/command_line.cpp.o] Error 4
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[2]: *** [src/common/CMakeFiles/common.dir/all] Error 2
make[2]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make: *** [release-static-64] Error 2

Any suggestions appreciated!!


Here is the full output of `make`:

Code:

bitmonerod@ubuntu:~/bitmonero$ make release-static
mkdir -p build/release
cd build/release && cmake -D STATIC=ON -D ARCH="x86-64" -D BUILD_64=ON -D CMAKE_BUILD_TYPE=release ../.. && make
-- Could not find DEVELOPER_LOCAL_TOOLS in env (not required)
-- BOOST_IGNORE_SYSTEM_PATHS defaults to OFF
-- Could not find DEVELOPER_LIBUNBOUND_OLD in env (not required)
-- Building for a 64-bit system
-- Could not find DATABASE in env (not required unless you want to change database type from default: lmdb)
-- Using LMDB as default DB type
-- Detecting version of miniupnpc in path: /usr/include/miniupnpc
-- Found miniupnpc version is pre v1.7
-- Using miniupnpc from local source tree for static build
-- Looking for libunbound
-- Using 64-bit LMDB from source tree
-- Enabling AES support
-- Found Git: /usr/bin/git
Doxygen: graphviz not found - graphs disabled
-- Configuring done
-- Generating done
-- Build files have been written to: /home/bitmonerod/bitmonero/build/release
make[1]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[2]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[  0%] Built target version
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[  8%] Built target upnpc-static
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 55%] Built target unbound
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 57%] Built target lmdb
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 60%] Built target otshell_utils
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
[ 71%] Built target crypto
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[3]: Entering directory `/home/bitmonerod/bitmonero/build/release'
[ 71%] Building CXX object src/common/CMakeFiles/common.dir/command_line.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[3]: *** [src/common/CMakeFiles/common.dir/command_line.cpp.o] Error 4
make[3]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[2]: *** [src/common/CMakeFiles/common.dir/all] Error 2
make[2]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/bitmonerod/bitmonero/build/release'
make: *** [release-static-64] Error 2

I don't know for sure, but that might be a memory issue. Try increasing your swap on your server, or try to move to an instance with more memory. Compiling monero can take over 1 gig of ram or something ridiculous.

[akaman]

I am having some compilation difficulties today...

I don't know for sure, but that might be a memory issue. Try increasing your swap on your server, or try to move to an instance with more memory. Compiling monero can take over 1 gig of ram or something ridiculous.

Thank you!! I just had 512MB RAM assigned to each server. Bumped that up to 2048MB and monero now compiles OK :-)

[smooth]

I am having some compilation difficulties today...

I don't know for sure, but that might be a memory issue. Try increasing your swap on your server, or try to move to an instance with more memory. Compiling monero can take over 1 gig of ram or something ridiculous.

Thank you!! I just had 512MB RAM assigned to each server. Bumped that up to 2048MB and monero now compiles OK :-)

Once you are done compiling you can reduce the memory. It only needs <100 MB (somewhat more may give better performance due to caching)

[papa_lazzarou]

I am having some compilation difficulties today...

I don't know for sure, but that might be a memory issue. Try increasing your swap on your server, or try to move to an instance with more memory. Compiling monero can take over 1 gig of ram or something ridiculous.

Thank you!! I just had 512MB RAM assigned to each server. Bumped that up to 2048MB and monero now compiles OK :-)

No need to waste money. Just add swap as GingerOpolusAle said. Here is a nice guide (it works in any debian based distro, I think): https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04

And as smooth said, after compile you will be fine with your 512MB.

The main issue for me has been the size of the data.mdb file. The one I have now has a 20GB size, even though it only uses 11GB or so. The good news is it won't grow until the next threshold is met which should take a while. So, if you're going to maintain that node medium/long term you should choose a VPS provider with easy expandable HD space.

[akaman]

I am having some compilation difficulties today...

I don't know for sure, but that might be a memory issue. Try increasing your swap on your server, or try to move to an instance with more memory. Compiling monero can take over 1 gig of ram or something ridiculous.

Thank you!! I just had 512MB RAM assigned to each server. Bumped that up to 2048MB and monero now compiles OK :-)

No need to waste money. Just add swap as GingerOpolusAle said....

I got a good deal and the extra memory came at no additional cost. Anyway, I'm back down to 512MB and will keep it that way long term. Threw up 2 more nodes, in addition to an existing one.

By the way, what do you reckon the CPU/disk (HDD) load of running a node is? It seems low to me, at least after syncing. I'm tempted to throw up another 5 nodes on existing servers...

[smooth]

I am having some compilation difficulties today...

I don't know for sure, but that might be a memory issue. Try increasing your swap on your server, or try to move to an instance with more memory. Compiling monero can take over 1 gig of ram or something ridiculous.

Thank you!! I just had 512MB RAM assigned to each server. Bumped that up to 2048MB and monero now compiles OK :-)

No need to waste money. Just add swap as GingerOpolusAle said....

I got a good deal and the extra memory came at no additional cost. Anyway, I'm back down to 512MB and will keep it that way long term. Threw up 2 more nodes, in addition to an existing one.

By the way, what do you reckon the CPU/disk (HDD) load of running a node is? It seems low to me, at least after syncing. I'm tempted to throw up another 5 nodes on existing servers...

It's low for normal use, but if you have some CPU cores/threads/cycles included with your servers and you are running the node anyway (and not using the CPU for anything else), you can solo mine, either for yourself or to donate to the project. It's a long shot to get blocks of course, but you might as well help secure the network rather than have them sit idle.

[newb4now]

At what efficiency rate do you see people leaving claymore for the new open source AMD miner being developed?
https://forum.getmonero.org/9/work-in-progress/2400/open-source-amd-miner-by-wolf0

If the theory about the 2.5% claymore dev donation continually being dumped is true then that downward pressure will go away as soon as people stop using claymore.

[sanyok]

On mainnet had the same problem as on testnet:

2015-10-09 11:40:46 (Thread 2) Block a06635 found at height 774359 by miner ***@192.168.0.100 - submit result: {"status":"OK"}
2015-10-09 11:40:46 (Thread 2) Accepted valid share at difficulty 10000/991117366 from ***@192.168.0.100

Blocks mined by me don't accept's by network
Same time on quazarcoin all good.. strange..

[GingerAle]

On mainnet had the same problem as on testnet:

2015-10-09 11:40:46 (Thread 2) Block a06635 found at height 774359 by miner ***@192.168.0.100 - submit result: {"status":"OK"}
2015-10-09 11:40:46 (Thread 2) Accepted valid share at difficulty 10000/991117366 from ***@192.168.0.100

Blocks mined by me don't accept's by network
Same time on quazarcoin all good.. strange..

oh, is this for the new AMD miner?

[medusa13]

hello guys, please help!

i am trying to restore one of my walllets but i have no sucess.
it has the word hoisting in it and i think this causes problems....seems like i can only restore the wallet with "noisting", but this is not an english word is it?
wallet was created with 8.8.6, it has hoisting and incline in it.

could it be we have/had a bug there? think about it, the letters n and h are close together on the keyboard + the difference is hard to spot by eye...please check this. it seems to me like in the word changing process, you replaced "hoi" with "noi"...possible?

i am restoring now using 8.8.6 and using "noisting" and "incline" and since its 8.8.6 it will take some time.

edit: i know i say two times 8.8.6, but it was not the same version. the 8.8.6-release that is offered for download now already has other words. but i can not tell you the real version since i deleted everything.

edit, it looks like it will be empty again...shit really guys my heart is stoping...but its logical since i use "noi" instead of "hoi" in the process....but, does "hoi" even still exist..?


if not, please point me to an older version i can use

[GingerAle]

hello guys, please help!

i am trying to restore one of my walllets but i have no sucess.
it has the word hoisting in it and i think this causes problems....seems like i can only restore the wallet with "noisting", but this is not an english word is it?
wallet was created with 8.8.6, it has hoisting and incline in it.

could it be we have/had a bug there? think about it, the letters n and h are close together on the keyboard + the difference is hard to spot by eye...please check this. it seems to me like in the word changing process, you replaced "hoi" with "noi"...possible?

i am restoring now using 8.8.6 and using "noisting" and "incline" and since its 8.8.6 it will take some time.

edit: i know i say two times 8.8.6, but it was not the same version. the 8.8.6-release that is offered for download now already has other words. but i can not tell you the real version since i deleted everything.

For the incline thing, try https://github.com/monero-project/bitmonero/issues/235

im confused by the fact that you say you *can* restore the wallet with "noisting"... so can you restore the wallet or not?

[medusa13]

yes i tried "noisting"but wallet is empty....with "hoisting" i can not restore it. (but it says hoisting on my paper here)
incline or incur is not the problem, its always "inc".