Message boards :
Questions and problems :
Error: Cannot get the official hostname (error 0: Success)
Message board moderation
Author | Message |
---|---|
Send message Joined: 13 Apr 08 Posts: 16 |
I just fetched the latest sources for BOINC in order to run them on Gentoo X64. I ran first the run_client script in one terminal, and then the run_manager script in another terminal. For some odd reason however, the manager is unable to connect, and the terminal in which I ran the run_client script does not respond to other commands than ctrl+c. I had this issue for the latest package 6.4.5 and the package available on portage. I would like to have more insight on what I should do instead so that BOINC runs peacefully. Thanks for your help! |
Send message Joined: 29 Jan 09 Posts: 1 |
I'm using Fedora Core 9 and have installed the boinc-manager and boinc-client packages via yum. I run the boinc in background then run boincmgr to configure the client. I get this message but only from the boinc-mgr. At least that is the way it looks to me. So after configuring the client I exit the manager and all is good. I have "hostname" issues with some proprietary packages so I suspect that my hostname configuration is not consistent. boincmgr should probably be a little more robust on this issue. On platforms with the same packages and where I haven't touched the hostname, that is it is what comes by default "localhost" I don't get this error So you should be able to get a peaceful run from the client after you exit the manager. |
Send message Joined: 13 Apr 08 Posts: 16 |
I followed the instructions in the Gentoo section of the Linux installation HOWTO. Everything is fine until this part: Open a terminal as root and enter the following commands, substitude your username for <username>: 1. ln -s /???/???/gui_rpc_auth.cfg /home/<username>/gui_rpc_auth.cfg 2. ln -s /???/???/gui_rpc_auth.cfg /var/lib/boinc-client/gui_rpc_auth.cfg 3. chown boinc:boinc /home/<username>/gui_rpc_auth.cfg 4. chown boinc:boinc /???/???/gui_rpc_auth.cfg 5. chmod g+rw /???/???/boinc-client 6. chmod g+rw /???/???/boinc-client/*.* There is no "boinc-client" folder in my /var/lib/ folder, there is just a "boinc" folder. I wonder before I go on if this is normal (and therefore the tutorial would need an update) or if there is something wrong with the ebuild I installed through portage. |
Send message Joined: 13 Apr 08 Posts: 16 |
I tried your recommendations just as an attempt. It did not worked unfortunately. Therefore, in order to make this easier, I have re-emerged the boinc ebuild. The relevant part of the log with the location of each file is here, as well as the installation notes: http://pastebin.ca/1325960 . It seems that the files are quite spread out. What would you recommend me to do then? |
Send message Joined: 13 Apr 08 Posts: 16 |
Oddly enough, it seems that BOINC is already running: xavier-pc xavier # /etc/init.d/boinc start * WARNING: boinc has already been started I first blanked gui_rpc_auth.cfg as you recommended it, I stopped and restarted boinc, and then I tried to load boinc_gui both as my regular user account and as root. here are the results. xavier@xavier-pc ~ $ boinc_gui 07:49:59: Error: Cannot get the official hostname (error 0: Success) connect: Operation now in progress xavier-pc xavier # boinc_gui connect: Connection refused execvp(/home/xavier/boinc, --redirectio, --launched_by_manager) failed with error 2! I don't understand however why it does redirect to my home directory when I launch the GUI as root.. |
Send message Joined: 13 Apr 08 Posts: 16 |
The manager tries to connect until I press ctrl+c. There was a shortcut in the menu (i accidentally deleted it..), but I know that the shortcut is boinc_gui, that's how I discovered how to load the boinc manager in the console. I run Gnome, hence will installing KBoincspy require the KDE package? |
Send message Joined: 13 Apr 08 Posts: 16 |
I gave a try to your suggestion with a random command. xavier@xavier-pc ~ $ boinc_cmd --host 127.0.0.1 --passwd --run_benchmarks Authorization failure: -155 The .cfg file is empty. |
Send message Joined: 13 Apr 08 Posts: 16 |
First things first xavier-pc xavier # /etc/init.d/boinc start * WARNING: boinc has already been started If I run this command xavier@xavier-pc ~ $ boinc_cmd --host 127.0.0.1 --run_benchmarks I have no console output. I guess that a positive outcome would have yielded console output. I still have the hostname error whether if I run boinc_gui as root or as my user account. I wonder if there are Gentoo users who could help me. The source build I downloaded has been erased. I am only using the build from Portage. |
Send message Joined: 13 Apr 08 Posts: 16 |
xavier-pc Antidote # ps aux | grep boinc boinc 5237 0.1 0.0 49116 3268 ? SNs Feb05 0:23 /usr/bin/boinc_client root 14929 0.0 0.0 3952 620 pts/0 S+ 00:38 0:00 grep --colour=auto boinc Interestingly enough, I searched for the two text files you talked about, and none can be located. But BOINC apparently runs.. xavier-pc Antidote # boinc_cmd --host 127.0.0.1 --get_state ======== Projects ======== ======== Applications ======== ======== Application versions ======== ======== Workunits ======== ======== Results ======== Obviously no projects running yet, but it seems that the client is running. Where would be the host file? Is it a Gentoo or BOINC specific file? If I type Gentoo in the search query, only this thread shows up. No luck :P |
Send message Joined: 20 Dec 07 Posts: 1069 |
Interestingly enough, I searched for the two text files you talked about, and none can be located. Did you really search all local filesystems ("find" from root /)? stdoutdae.txt is written when boinc_client starts. (typo? did you try stdoutdae*?) Where would be the host file? Is it a Gentoo or BOINC specific file? It's a unix system file. IIRC it's on /etc, but it's a long time that I last used unix. If I type Gentoo in the search query, only this thread shows up. No luck :P You could try the Advanced search link. There you can select to search for a whole year back, but "Gentoo" is really quite seldom on the fora. I did find three threads. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) |
Send message Joined: 13 Apr 08 Posts: 16 |
I do not understand why, but there is really no file named stdoutdae on my system xavier-pc ~ # find / -name stdout*.txt xavier-pc ~ # Updated host file. xavier-pc xavier # cat /etc/hosts # /etc/hosts: Local Host Database # # This file describes a number of aliases-to-address mappings for the for # local hosts that share this file. # # In the presence of the domain name service or NIS, this file may not be # consulted at all; see /etc/host.conf for the resolution order. # # IPv4 and IPv6 localhost aliases 127.0.0.1 hostname localhost ::1 localhost # # Imaginary network. #10.0.0.2 myname #10.0.0.3 myfriend # # According to RFC 1918, you can use the following IP networks for private # nets which will never be connected to the Internet: # # 10.0.0.0 - 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect directly to the Internet (i.e. not # behind a NAT, ADSL router, etc...), you need real official assigned # numbers. Do not try to invent your own network numbers but instead get one # from your network provider (if any) or from your regional registry (ARIN, # APNIC, LACNIC, RIPE NCC, or AfriNIC.) I noticed that boinc_client, boinc_cmd and boinc_gui are located in /usr/bin. Should I chown them to my username? |
Send message Joined: 20 Dec 07 Posts: 1069 |
I do not understand why, but there is really no file named stdoutdae on my system Perhaps you should try find / -name stdout* because the .txt suffix is not very unix-like and would be covered by the wildcard (asterisk) anyway. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) |
Send message Joined: 13 Apr 08 Posts: 16 |
New findings. xavier-pc xavier # find / -name stdout* /usr/share/man/man3/stdout.3.bz2 /usr/share/man/man3p/stdout.3p.bz2 /dev/stdout /dev/stdout is a device file I have X installed, yes. xavier-pc xavier # cat /etc/sysconfig/network cat: /etc/sysconfig/network: No such file or directory But I think that this is what you are looking for? xavier-pc etc # cat /etc/conf.d/hostname # Set to the hostname of this machine hostname="xavier-pc" I then tried xavier-pc xavier # boinc_cmd --host xavier-pc --run_benchmarks gethostbyname: Success can't connect to xavier-pc Ironically however, if I change the hostname to "localhost" and run xavier-pc xavier # boinc_cmd --host localhost --run_benchmarks I have no console output. I searched again for stdout*: xavier-pc dev # find / -name stdout* /dev/stdout This is getting interesting! |
Send message Joined: 20 Dec 07 Posts: 1069 |
I searched again for stdout*: Yes, indeed. The last thing I can come up with now is that boinc_client has no write access in its working directory, but that is pretty unlikely. Sorry, Gundolf |
Send message Joined: 20 Dec 07 Posts: 1069 |
I think there was a /dev/stdout even before Daseinhorn installed BOINC. I think maybe /dev/stdout is a virtual but empty device, in other words the bit bucket? No, that would be /dev/null (or was it nul?), /dev/stdout is the standard unix output device. But that has nothing to do with my answer ;-) I was just suspecting that the owner/access rights are not set properly in the BOINC directory, and since the installer should care for that, I found it rather unlikely to happen. Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) |
Send message Joined: 30 Oct 05 Posts: 1239 |
The logs might not even be called stdout* On my system (albeit not installed from a package manager) they're called boinc.log and error.log. Kathryn :o) |
Send message Joined: 13 Apr 08 Posts: 16 |
Hey folks, this is really weird, but when I loaded my computer this morning, BOINC suddently worked! I really do not know why, but it just plain works. I can boinc again = me happy! |
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.