Topic: Linux noob trying to run bitcoin via SSH - page 4. (Read 8953 times)

The error's your getting seems to suggest you've built bitcoin on another machine ? It's looking for libs it cannot find and failing. If you run that version locally you will get the same result. Why don't you just use the pre compiled binaries ?

The ampersand at the end is so bitcoind starts and runs in the background so you can still use the shell,

./bitcoind accomplishes the same thing, right?  That's basically what I tried to do, and got the following error message:


What is the ampersand at the end of the flag for?  I haven't seen that used previously...

that's why i covered both.

not to be an @$$ again. but we are not talking about starting bitcoind in X over ssh. bitcoind runs fine headless.

@OP

If you want to run bitcoind from SSH extract bitcoin and cd into the bin folder and type


If you want to run the client it's slightly different. You need to setup X11 forwarding and ssh into the machine. Then you can run the bitcoin software remotely. On the remote machine add the folloing lines to the bottom of /etc/ssh/ssh_config


Restart ssh on the remote machine and your good to go. If your using a linux box to connect then


Windows userscan grab putty and tick this ..



If you want to start the client on the server's screen then use


Here's it all setup and working




Hope this helps

Interesting regarding the teamviewer aspect... so it's basically VNCing into my desktop while I'm VNC'd or SSH'd into the server?  I can't see anything wrong with that.

Let me get an ok from the other person on the project, and then I'll send you a PM.

yes sometimes. i did only think that it was two noobs, who did not know what they where taking about. sorry for being an @$$.

sorry i did not see that possibility, but sure i will do it.

sure i will do the teamviewer thing, i what to help. and im quite capable of handling an linux server via ssh.

Kokjo you're quite an @$$.

Let's think about this for a minute. He has a VPS. So he doesn't have local access to the machine. So, a teamviewer session would work like this. Mr VPS user logs into SSH into the VPS on his windws/linux desktop. He then allows you to have teamviewer access to his desktop which has the SSH shell. Several other people appeared to understand what he was talking about. And you're the nice person trying to help? Come on.

And Maxim. We aren't talking about mining but I use teamviewer all the time for my remote machines. I am using ubuntu desktop for mining. You need to start teamviewer outside of an RDP protocol, like with a monitor. Set it to run automatically with start up and use a secure password. I have seen a sample from someone else where they were logged into a RDP desktop, started teamviewer and teamviewer logged them into the RDP session. They tried it again with closing out the RDP after opening teamviewer then logging into the machine with teamviewer and it worked just fine. Don't let the graphics controllers get locked into sending their signal to the RDP protocol.

Kokjo if you are really trying to be helpful pull the stick out of the hind end.

you people do know that we are talking about an rented headless linux server here, right?
which i will(if sgtspike whats it) get root access though ssh, right?

you cant teamview on this, sorry.
stupid windows users please go away and let us serious people work, or please read the thread before commenting.

@Maxim Gladkov: we are not talking about mining.
@Tasty, davidonpda: AFAIK, teamviewer cant be used on a headless linux server

Speaking about Teamviwer and other remote desktop software - it is impossible to use them with mining rigs, because they use your video graphics adapter to render image for your remote session, but VGA is already working hard to mine some bitcoins for you, so it's lagging awfully!

My last time, I wasd trying to use Teamviwer with my rig - I just saw black screen and nothing more so I don't think it will be a good wayfor this...

I not anyone or know any of these guys but I suggest letting one of these guys help you.
The web will often fail you with outdated info when comes to linux, it changes frequently.
Having someone that knows current info and can show you or help you fix things is invaluable.

Teamviewer is excellent too.
Teamviewer has an ability to record the session also, so you can go back and watch exactly what they did, in case you want to setup another one or ever need to set it up again for any reason.
it also has a browser interface.

I'll let you know, thanks for the offer!

you can't. but i will not do that, it would destroy my reputation.

no not if you give root access, i could hide anything.

i can do it if you like. but only if you thrust me, Nefario can vouch for me.

Wow, thanks for the responses all!  I'm not at home right now, but I'll give Joel's bitcoind a try when I do get home.

kokjo, I would love to allow you to do that, but how can I know that you won't install something malicious that could grant you access to the server down the road?  Would there be some way for me to verify that nothing like that is installed?

I was going to create a pull request, but I ran into some technical issues confirming that the patch didn't break the GUI build. I ran out of the time I could devote to doing it and I don't think it makes sense to issue a pull request without testing that.

Anyone?

Also, you probably want to start which will cause bitcoin to demonize so it will keep running even if you log out from your ssh session. no nohup required .


JoelKatz: That should really be in the official release.

I just uploaded a build of the git repository version of 'bitcoind' (0.3.25-beta). It was built for 64-bit Linux with no mods or options, but without the spurious 'libz' or 'libgthread' dependencies. You can fetch it at this URL:

http://davids.webmaster.com/~davids/bitcoind
The MD5 sum is:
469c47c2103fcdaca5c9fa23ce20bdd4
The SHA1 sum is:
5de7489f1b27bb3f291f10e3455786f8a7985925

$ ldd ./bitcoind  | cut -f 1 -d "("
        linux-vdso.so.1 =>  
        libdl.so.2 => /lib64/libdl.so.2
        libpthread.so.0 => /lib64/libpthread.so.0
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6
        libm.so.6 => /lib64/libm.so.6
        libgcc_s.so.1 => /lib64/libgcc_s.so.1
        libc.so.6 => /lib64/libc.so.6
        /lib64/ld-linux-x86-64.so.2

If you'd prefer a different build, such as the latest release, just let me know.

For reference, this is the only change:
--- a/src/makefile.unix
+++ b/src/makefile.unix
@@ -30,11 +30,13 @@ endif
 
 LIBS+= \
  -Wl,-Bdynamic \
-   -l gthread-2.0 \
-   -l z \
    -l dl \
    -l pthread
 
+GLIBS= \
+   -l gthread-2.0 \
+   -l z
+
 
 DEBUGFLAGS=-g -D__WXDEBUG__
 CXXFLAGS=-O2 -Wno-invalid-offsetof -Wformat $(DEBUGFLAGS) $(DEFS)
@@ -68,7 +70,7 @@ cryptopp/obj/%.o: cryptopp/%.cpp
        $(CXX) -c $(CXXFLAGS) -O3 -o $@ $<
 
 bitcoin: $(OBJS) obj/ui.o obj/uibase.o
-       $(CXX) $(CXXFLAGS) -o $@ $^ $(WXLIBS) $(LIBS)
+       $(CXX) $(CXXFLAGS) -o $@ $^ $(WXLIBS) $(LIBS) $(GLIBS)

may i get root access to it for an hour? i can install bitcoind, and fix all kind of unforeseen troubles(os upgrade, ...)

See above - it is running Debian.

Those two commands don't come up with useful information.  The first command seems to show some hardware information (amd64, x86_64, GNU/Linux, etc), and the second just says "No such file or directory".