Message boards : Server programs : local server help
Message board moderation
Author | Message |
---|---|
Send message Joined: 14 May 13 Posts: 5 |
Hi, im new to boinc, and new to ubuntu Im doing a locar sever to host BOINC projects trough account management as part of my Ing. thesis So for now im testing on my network. I have my server on ubuntu 12.04 lts 64bits and my BOINC clients (7.0.64) will use windows. Ive installed lamp for the server, and i changed the bin-address to the IP on the server so that i can reach it locally trough my windows users. When i connect with windows with my browser to the local server i can create users or as root and i can delete users. The funny stuff is when i try to connect it to boinc trough account management. I put my ip =192.168.0.7/myserver on the account manager And then boinc asks for user and account witch i already created on the web page, i hit enter and it gives me this error connect() fail. I already have my public and private keys. And i put the public key on my conf file on the server. Made them with cryp_prog file So i downloaded the client on ubuntu just to test it on the same computer and i did the same and no problem there. The problem is when i try to connect with windows clients. So i thinking its a network issue My boinc.exe is on TCP 127.0.0.1:49192 127.0.0.1:31416 established boincmgr.exe is on TCP 192.168.0.2:49296 31.13.70.1:443 established the above ports or ip's change every time i reboot my windows. also I dont know if i need to port potforward something on my router or firewall Also i removed the 32bts of boinc and installed the 64 bit version and the 32bts left a file called stderrgfx.txt i open it and it gave me this error repeatedly TRACE [5616]: RPC_CLIENT::init connect 2: Winsock error '10061' TRACE [5616]: RPC_CLIENT::init connect on 508 returned -1 Any helpt will be of great help! thnks Im from mexico, sorry for my english |
Send message Joined: 4 Jul 12 Posts: 321 |
What do you mean with " i changed the bin-address to the IP on the server". The server hostname is stored in two places config.xml and html/user/schedulers.txt you must change it everywhere and than restart the project. Also check the config.xml as the hostname is referenced more than once. A better way to circumvent this kind of problem is to change the drivers/etc/hosts file on your windows machine to resolve the name of your ubuntu server to the correct IP. This way you won't have to fiddle with server configuration stuff. |
Send message Joined: 14 May 13 Posts: 5 |
What ive meant by that was that i changed the bin address of the server on my etc/mysql/my.conf to match its IP from =127.0.0.1 to 192.168.0.7 all on ubuntu... Do i need to add something to my etc/hosts ?? |
Send message Joined: 4 Jul 12 Posts: 321 |
Changing the mysql configuration has no effect on the BOINC Client to Server connectivity which I assume is the problem you described. This is solved easily by adding the server hostname and IP-address to your C:\Windows\system32\drivers\etc\hosts file. You should than be able to connect via browser to your project website running on the server and also the BOINC-Client should be able to attach to the project. I still don't know what you mean by "host BOINC projects trough account management". Do you create multiple projects on your local server? Or do you run an Account Manager (like GridRepublic and BAM!)? |
Send message Joined: 14 May 13 Posts: 5 |
Okey, so i returned my bind addres to 127.0.0.1 on mysql on my /etc/hosts y changed the name localhost to http://www.jarifa.com/ on my windows seven y added the host 192.168.0.7 http://www.jarifa.com/jarifa/ and still the same problem. I can connect to the server with my web browser but BOINC keeps giving me the same error... |
Send message Joined: 14 May 13 Posts: 5 |
ive fix it ! I had to change the local host and master URL in the .conf of the server. sorry for the trouble... And thanks a lot. One problem fixed now to figure out how to creat a project! |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.