Monero Support

[bitebits]

I feel almost ashamed to ask. But since support was so quick last time, I do it anyway

Setting up my second Monero node on a VPS. But instead of downloading the blockchain, I like to upload it from my local harddisk (to decrease the change of being kicked from the VPS while syncing).

But where under Ubuntu Server Linux is the blockchain stored? Been googling without any result.

In OS X it's [home directory] --> [.bitmonero] --> [lmdb] --> [data.mdb].

I think it's the same in Linux. You can probably just copy and paste the lmdb subdirectory into the hidden .bitmonero directory.

Thanks pa, ArcticMine and GingerAle. Indeed found it in: /root/.bitmonero/lmdb/
Standard Winscp for FTP does not show hidden files:

Display hidden files in WinSCP

Solution
Click on the "view" menu (or "options", if using the Norton Commander interface).

Click on "preferences".

In the preferences window, click on "Panels" on the left menu.

Uncheck (or check) the "Show Hidden Files" box to show or hide the files.

[bitowl]

How big is the blockchain now?

[owm123]

How big is the blockchain now?

7.9 GB on my hardrive.

[americanpegasus]

How big is the blockchain now?

7.9 GB on my hardrive.

Just goes to show that even if we could have mathematically designed this in say, 1995 - it would have been impossible to implement on a global scale.  We need gigabytes of storage to be cheap and easy... and that didn't happen until the two-thousand-teens. 

[bitebits]

I am running three full nodes (./bitmonerod --limit-rate 128000) on two different VPS providers located in Europe. There is a remarkable difference regarding the number of connections:

- VPS1 (high end specs) consistently has barely any outgoing connections. Simultaneously runs a Bitcoin node.
- VPS2 (low end specs) has plenty of incoming and outgoing connections, same VPS provider as VPS3.
- VPS3 (low end specs) has barely any outgoing connections, same VPS provider as VPS2.

VPS1 (4GB RAM, non-ssd, 2CPU, plenty of bandwidth, Ubuntu 15.1)

Height: 969051/969051 (100.0%) on mainnet, not mining, net hash 15.46 MH/s, v1, up to date, 8+4 connections

VPS2 (512MB RAM, non-ssd, 1CPU, 256GB bandwidth, Ubuntu 15.1) Same host as VPS3

Height: 969053/969053 (100.0%) on mainnet, not mining, net hash 15.56 MH/s, v1, up to date, 25+114 connections

VPS3 (512MB RAM, non-ssd, 1CPU, 256GB bandwidth, Ubuntu 15.1) Same host as VPS2

Height: 969071/969071 (100.0%) on mainnet, not mining, net hash 15.55 MH/s, v1, up to date, 8+3 connections

Strange behavior, especially between VPS 2 and VPS 3. Any possible ideas why this could happen?

[smooth]

Anything more than 8 outgoing connections means you have some in a "stuck" state (some of the incoming connections may be stuck as well). This is a known issue that is being worked on. As a workaround you can restart the node.

As far as other differences I can't think of a reason. As long as you are getting any incoming connections it means the port is unblocked and there isn't much more you can do other than wait. It does take some time for the IP address to propagate around the p2p and other nodes to start using it.

[bitebits]

Anything more than 8 outgoing connections means you have some in a "stuck" state (some of the incoming connections may be stuck as well). This is a known issue that is being worked on. As a workaround you can restart the node.

As far as other differences I can't think of a reason. As long as you are getting any incoming connections it means the port is unblocked and there isn't much more you can do other than wait. It does take some time for the IP address to propagate around the p2p and other nodes to start using it.

Thanks for the reply smooth, I will (restart and) keep on monitoring it for a bit (actually the reason why I fired up VPS number 3 for comparison).
Regarding the bold part, what would an average amount of incoming connections be?

[smooth]

Anything more than 8 outgoing connections means you have some in a "stuck" state (some of the incoming connections may be stuck as well). This is a known issue that is being worked on. As a workaround you can restart the node.

As far as other differences I can't think of a reason. As long as you are getting any incoming connections it means the port is unblocked and there isn't much more you can do other than wait. It does take some time for the IP address to propagate around the p2p and other nodes to start using it.

Thanks for the reply smooth, I will keep on monitoring it for a bit (actually the reason why I fired up VPS number 3 for comparison).
Regarding the bold part, what would an average amount of incoming connections be?

There is no set answer. It depends on the number of nodes on the network and the number configured to allow incoming connections. It should be >8 as an average, but an average means some nodes will be higher and some lower.

[birr]

I'm considering running a node on my ubuntu laptop, which is 32bit.  I found this on reddit, from hyc

I built on Debian with multilib installed, so the same compiler can be used for both 64 and 32 bit builds. To force it to do a 32 bit build, I run cmake with
LDEMULATION=elf_i386 make CC="gcc -m32" CXX="g++ -m32"
The LDEMULATION is needed to tell ld the right format for blocks.o etc.
There are a few other build tweaks needed to reproduce the binaries I built - played games with -Bdynamic and -Bstatic to force it to use static crypto and boost libraries, while leaving the rest (-lpthreads, -lrt) dynamic.
https://www.reddit.com/r/Monero/comments/433w2u/new_32bit_binaries_for_v091/

This makes it look difficult.  Does a coherent set of instructions even exist for someone without advanced problem-solving skills?

[binaryFate]

I'm considering running a node on my ubuntu laptop, which is 32bit.  I found this on reddit, from hyc

I built on Debian with multilib installed, so the same compiler can be used for both 64 and 32 bit builds. To force it to do a 32 bit build, I run cmake with
LDEMULATION=elf_i386 make CC="gcc -m32" CXX="g++ -m32"
The LDEMULATION is needed to tell ld the right format for blocks.o etc.
There are a few other build tweaks needed to reproduce the binaries I built - played games with -Bdynamic and -Bstatic to force it to use static crypto and boost libraries, while leaving the rest (-lpthreads, -lrt) dynamic.

This makes it look difficult.  Does a coherent set of instructions even exist for someone without advanced problem-solving skills?

You don't need to do that. Just do "make release-static-32" (or whatever it is called, can't remember, just check the makefile targets).

[birr]

I'll try to figure out what that means.
You're talking to someone who just opened the google search page and typed in
"What is a makefile target?"
Computer says,
A makefile consists of “rules” in the following form: target: dependencies system command(s) A target is usually the name of a file that is generated by a program; examples of targets are executable or object files. A target can also be the name of an action to carry out, such as "clean".
bedtime reading:
https://en.wikipedia.org/wiki/Makefile
When I arrive at the point that I can ask useful questions, I'll get back to you.

[saddambitcoin]

`make` is what compiles the source code.

birr, you can download the binaries in that reddit post you linked. they already have been compiled, so you don't even need to worry about building them. hyc seems to be just saying what he did to get to that point. you can extract the tar.bz2 file and then run bitmonerod

[birr]

`make` is what compiles the source code.

birr, you can download the binaries in that reddit post you linked. they already have been compiled, so you don't even need to worry about building them. hyc seems to be just saying what he did to get to that point. you can extract the tar.bz2 file and then run bitmonerod

I downloaded and extracted the files.
It's been a couple of years since I've done any command line stuff.  The programs have been compiled already?
What's the terminal command to run bitmonerod or simplewallet?

[ArticMine]

...
I downloaded and extracted the files.
It's been a couple of years since I've done any command line stuff.  The programs have been compiled already?
What's the terminal command to run bitmonerod or simplewallet?

To run bitmonerod

Code:

./bitmonerod

To run simplewallet
First time

Code:

./simplewallet 

With an existing wallet where <name> is replaced by the name of the wallet file eg: wallet.bin

Code:

./simplewallet --wallet <name>

This is from the directory that contains the binaries. Also one has to make sure that the execute permission on the binaries is set

Edit 1: The above is for GNU/Linux since you mentioned terminal.

Edit 2: For Microsoft Windows command prompt replace ./bitmonerod with bitmonerod.exe and ./simplewallet with simplewallet.exe in the above.

[TaurusBit]

I'm launching the simplewallet daemon with:

Code:

monero@server:~/monero$ /home/monero/simplewallet --rpc-bind-ip=0.0.0.0 --rpc-bind-port 18082 --password [password] --wallet-file [pathToWallet].bin --daemon-address=127.0.0.1:18081
Creating the logger system
Monero 'Hydrogen Helix' (v0.9.1.0-release)
Logging at log level 0 to /home/monero/simplewallet.log
2016-Feb-29 14:13:41.132865 Loading wallet...
2016-Feb-29 14:13:41.165504 Unknown refresh-type value (32767), using default
2016-Feb-29 14:13:41.165818 Loaded wallet keys file, with public address: [....]

But it's not listening on the specified port (18082), I also tried with other ports but no luck.

Code:

root@server:~# netstat -nat | grep 18082
root@server:~#

Anybody can help? 

[GingerAle]

I'm launching the simplewallet daemon with:

Code:

monero@server:~/monero$ /home/monero/simplewallet --rpc-bind-ip=0.0.0.0 --rpc-bind-port 18082 --password [password] --wallet-file [pathToWallet].bin --daemon-address=127.0.0.1:18081
Creating the logger system
Monero 'Hydrogen Helix' (v0.9.1.0-release)
Logging at log level 0 to /home/monero/simplewallet.log
2016-Feb-29 14:13:41.132865 Loading wallet...
2016-Feb-29 14:13:41.165504 Unknown refresh-type value (32767), using default
2016-Feb-29 14:13:41.165818 Loaded wallet keys file, with public address: [....]

But it's not listening on the specified port (18082), I also tried with other ports but no luck.

Code:

root@server:~# netstat -nat | grep 18082
root@server:~#

Anybody can help?  

I use this and it works fine:

Code:

 --rpc-bind-port 8082 --rpc-bind-ip 127.0.0.1 --wallet-file /monerodo/wallets/pwallet.bin --password poop

I'm guessing that binding it to 18082 is causing some kind of conflict. 18082 is the rpc port that the daemon uses. So basically, you have your daemon running, and its using port 18082 to communicate to simplewallet. Now you need another port for your application to talk to simplewallet. So, I think you need to specify a different port.

edited to add: I've also had a lot of *fun* troubleshooting different permission spaces. It looks like your running simplewallet from a user directory, and then checking to see what the port is doing in a root space.

[TaurusBit]

I use this and it works fine:

Code:

 --rpc-bind-port 8082 --rpc-bind-ip 127.0.0.1 --wallet-file /monerodo/wallets/pwallet.bin --password poop

I'm guessing that binding it to 18082 is causing some kind of conflict. 18082 is the rpc port that the daemon uses. So basically, you have your daemon running, and its using port 18082 to communicate to simplewallet. Now you need another port for your application to talk to simplewallet. So, I think you need to specify a different port.

edited to add: I've also had a lot of *fun* troubleshooting different permission spaces. It looks like your running simplewallet from a user directory, and then checking to see what the port is doing in a root space.

Tried port 8082 but nothing changed. By the way, the netstat command shows no application is listening on port 18082, so I don't think the problem was the one you mentioned.

[GingerAle]

I use this and it works fine:

Code:

 --rpc-bind-port 8082 --rpc-bind-ip 127.0.0.1 --wallet-file /monerodo/wallets/pwallet.bin --password poop

I'm guessing that binding it to 18082 is causing some kind of conflict. 18082 is the rpc port that the daemon uses. So basically, you have your daemon running, and its using port 18082 to communicate to simplewallet. Now you need another port for your application to talk to simplewallet. So, I think you need to specify a different port.

edited to add: I've also had a lot of *fun* troubleshooting different permission spaces. It looks like your running simplewallet from a user directory, and then checking to see what the port is doing in a root space.

Tried port 8082 but nothing changed. By the way, the netstat command shows no application is listening on port 18082, so I don't think the problem was the one you mentioned.

I'm just checking all options here.... you have the port open, right? if this is ubuntu, sudo ufw allow 8082

[TaurusBit]

I'm just checking all options here.... you have the port open, right? if this is ubuntu, sudo ufw allow 8082

UFW is disabled, I'm using CSF but simplewallet won't listen on the port even with CSF disabled.

[GingerAle]

I'm just checking all options here.... you have the port open, right? if this is ubuntu, sudo ufw allow 8082

UFW is disabled, I'm using CSF but simplewallet won't listen on the port even with CSF disabled.

hrm. I'm trying to find some log files for my simplewallet that I've used like this, but I think its on another device that is off right now. I'm not 100% sure, but what you might be experiencing is the fact that simplewallet might have to refresh your wallet. A wallet refresh, even on a brand new wallet, can take a while.

as with all things Monero, patience is your best resource.

So, my advice - set it to port 8082, and keep an eye on the log file or on the screen session and see when the status changes. Indeed, I think i recall seeing the final log entry being something like "listening on port blah blah blah". so if the above was the extent of your log for simplewallet, that means the wallet didn't finish refreshing.