Posts by Daseinhorn

1) Message boards : Questions and problems : Buffer overflow at startup, leads to broken boinc (Message 24052)
Posted 1 Apr 2009 by Daseinhorn
Post:
If I run it as a user I do not get full debug output. It is from portage yes. It was working flawlessly until I did emerge -DuNva world today.
2) Message boards : Questions and problems : Buffer overflow at startup, leads to broken boinc (Message 24046)
Posted 31 Mar 2009 by Daseinhorn
Post:
Since my latest update on Gentoo, boinc is unable to start. Here is the output I get from running boinc_client as root

xavier-portable xavier # boinc_client
31-Mar-2009 18:59:17 [---] Starting BOINC client version 6.4.5 for x86_64-pc-linux-gnu
31-Mar-2009 18:59:17 [---] log flags: task, file_xfer, sched_ops
31-Mar-2009 18:59:17 [---] Libraries: libcurl/7.19.4 OpenSSL/0.9.8k zlib/1.2.3
31-Mar-2009 18:59:17 [---] Data directory: /home/xavier
31-Mar-2009 18:59:17 [---] Processor: 2 GenuineIntel Intel(R) Core(TM)2 Duo CPU P9500 @ 2.53GHz [Family 6 Model 23 Stepping 6]
31-Mar-2009 18:59:17 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_
31-Mar-2009 18:59:17 [---] OS: Linux: 2.6.29-gentoo
31-Mar-2009 18:59:17 [---] Memory: 3.86 GB physical, 0 bytes virtual
31-Mar-2009 18:59:17 [---] Disk: 275.07 GB total, 6.75 GB free
31-Mar-2009 18:59:17 [---] Local time is UTC +0 hours
31-Mar-2009 18:59:17 [---] Not using a proxy
31-Mar-2009 18:59:17 [---] Can't load library libcudart
31-Mar-2009 18:59:17 [---] No coprocessors
31-Mar-2009 18:59:17 [---] No general preferences found - using BOINC defaults
31-Mar-2009 18:59:17 [---] Preferences limit memory usage when active to 1974.17MB
31-Mar-2009 18:59:17 [---] Preferences limit memory usage when idle to 3553.51MB
*** buffer overflow detected ***: boinc_client terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x32)[0x7fbb4bd3e4d2]
/lib/libc.so.6[0x7fbb4bd3c4a0]
/lib/libc.so.6[0x7fbb4bd3b9e9]
/lib/libc.so.6(_IO_default_xsputn+0x88)[0x7fbb4bcd2848]
/lib/libc.so.6(_IO_vfprintf+0x38b1)[0x7fbb4bca8591]
/lib/libc.so.6(__vsprintf_chk+0xa7)[0x7fbb4bd3ba97]
/lib/libc.so.6(__sprintf_chk+0x80)[0x7fbb4bd3b9d0]
boinc_client[0x471d56]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x43bdf6]
boinc_client[0x41f7f8]
boinc_client[0x454963]
/lib/libc.so.6(__libc_start_main+0xf4)[0x7fbb4bc825e4]
boinc_client[0x405db9]
======= Memory map: ========
00400000-004a6000 r-xp 00000000 08:01 729288 /usr/bin/boinc_client
006a5000-006a6000 r--p 000a5000 08:01 729288 /usr/bin/boinc_client
006a6000-006a7000 rw-p 000a6000 08:01 729288 /usr/bin/boinc_client
006a7000-006f3000 rw-p 006a7000 00:00 0 [heap]
7fbb4b842000-7fbb4b84c000 r-xp 00000000 08:01 1036457 /lib64/libnss_files-2.9.so
7fbb4b84c000-7fbb4ba4b000 ---p 0000a000 08:01 1036457 /lib64/libnss_files-2.9.so
7fbb4ba4b000-7fbb4ba4c000 r--p 00009000 08:01 1036457 /lib64/libnss_files-2.9.so
7fbb4ba4c000-7fbb4ba4d000 rw-p 0000a000 08:01 1036457 /lib64/libnss_files-2.9.so
7fbb4ba4d000-7fbb4ba63000 r-xp 00000000 08:01 1209933 /lib64/libgcc_s.so.1
7fbb4ba63000-7fbb4bc62000 ---p 00016000 08:01 1209933 /lib64/libgcc_s.so.1
7fbb4bc62000-7fbb4bc63000 r--p 00015000 08:01 1209933 /lib64/libgcc_s.so.1
7fbb4bc63000-7fbb4bc64000 rw-p 00016000 08:01 1209933 /lib64/libgcc_s.so.1
7fbb4bc64000-7fbb4bda4000 r-xp 00000000 08:01 1036510 /lib64/libc-2.9.so
7fbb4bda4000-7fbb4bfa3000 ---p 00140000 08:01 1036510 /lib64/libc-2.9.so
7fbb4bfa3000-7fbb4bfa7000 r--p 0013f000 08:01 1036510 /lib64/libc-2.9.so
7fbb4bfa7000-7fbb4bfa8000 rw-p 00143000 08:01 1036510 /lib64/libc-2.9.so
7fbb4bfa8000-7fbb4bfad000 rw-p 7fbb4bfa8000 00:00 0
7fbb4bfad000-7fbb4c02d000 r-xp 00000000 08:01 1036486 /lib64/libm-2.9.so
7fbb4c02d000-7fbb4c22c000 ---p 00080000 08:01 1036486 /lib64/libm-2.9.so
7fbb4c22c000-7fbb4c22d000 r--p 0007f000 08:01 1036486 /lib64/libm-2.9.so
7fbb4c22d000-7fbb4c22e000 rw-p 00080000 08:01 1036486 /lib64/libm-2.9.so
7fbb4c22e000-7fbb4c244000 r-xp 00000000 08:01 1036471 /lib64/libpthread-2.9.so
7fbb4c244000-7fbb4c443000 ---p 00016000 08:01 1036471 /lib64/libpthread-2.9.so
7fbb4c443000-7fbb4c444000 r--p 00015000 08:01 1036471 /lib64/libpthread-2.9.so
7fbb4c444000-7fbb4c445000 rw-p 00016000 08:01 1036471 /lib64/libpthread-2.9.so
7fbb4c445000-7fbb4c449000 rw-p 7fbb4c445000 00:00 0
7fbb4c449000-7fbb4c53a000 r-xp 00000000 08:01 743548 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.3/libstdc++.so.6.0.10
7fbb4c53a000-7fbb4c739000 ---p 000f1000 08:01 743548 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.3/libstdc++.so.6.0.10
7fbb4c739000-7fbb4c740000 r--p 000f0000 08:01 743548 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.3/libstdc++.so.6.0.10
7fbb4c740000-7fbb4c742000 rw-p 000f7000 08:01 743548 /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.3/libstdc++.so.6.0.10
7fbb4c742000-7fbb4c755000 rw-p 7fbb4c742000 00:00 0
7fbb4c755000-7fbb4c769000 r-xp 00000000 08:01 1205357 /lib64/libz.so.1.2.3
7fbb4c769000-7fbb4c968000 ---p 00014000 08:01 1205357 /lib64/libz.so.1.2.3
7fbb4c968000-7fbb4c969000 r--p 00013000 08:01 1205357 /lib64/libz.so.1.2.3
7fbb4c969000-7fbb4c96a000 rw-p 00014000 08:01 1205357 /lib64/libz.so.1.2.3
7fbb4c96a000-7fbb4c96c000 r-xp 00000000 08:01 1036192 /lib64/libdl-2.9.so
7fbb4c96c000-7fbb4cb6c000 ---p 00002000 08:01 1036192 /lib64/libdl-2.9.so
7fbb4cb6c000-7fbb4cb6d000 r--p 00002000 08:01 1036192 /lib64/libdl-2.9.so
7fbb4cb6d000-7fbb4cb6e000 rw-p 00003000 08:01 1036192 /lib64/libdl-2.9.so
7fbb4cb6e000-7fbb4ccd1000 r-xp 00000000 08:01 726720 /usr/lib64/libcrypto.so.0.9.8
7fbb4ccd1000-7fbb4ced0000 ---p 00163000 08:01 726720 /usr/lib64/libcrypto.so.0.9.8
7fbb4ced0000-7fbb4cede000 r--p 00162000 08:01 726720 /usr/lib64/libcrypto.so.0.9.8
7fbb4cede000-7fbb4cef6000 rw-p 00170000 08:01 726720 /usr/lib64/libcrypto.so.0.9.8
7fbb4cef6000-7fbb4cefa000 rw-p 7fbb4cef6000 00:00 0
7fbb4cefa000-7fbb4cf44000 r-xp 00000000 08:01 726725 /usr/lib64/libssl.so.0.9.8
7fbb4cf44000-7fbb4d143000 ---p 0004a000 08:01 726725 /usr/lib64/libssl.so.0.9.8
7fbb4d143000-7fbb4d145000 r--p 00049000 08:01 726725 /usr/lib64/libssl.so.0.9.8
7fbb4d145000-7fbb4d14b000 rw-p 0004b000 08:01 726725 /usr/lib64/libssl.so.0.9.8
7fbb4d14b000-7fbb4d152000 r-xp 00000000 08:01 1036496 /lib64/librt-2.9.so
7fbb4d152000-7fbb4d352000 ---p 00007000 08:01 1036496 /lib64/librt-2.9.so
7fbb4d352000-7fbb4d353000 r--p 00007000 08:01 1036496 /lib64/librt-2.9.so
7fbb4d353000-7fbb4d354000 rw-p 00008000 08:01 1036496 /lib64/librt-2.9.so
7fbb4d354000-7fbb4d366000 r-xp 00000000 08:01 1036503 /lib64/libresolv-2.9.so
7fbb4d366000-7fbb4d566000 ---p 00012000 08:01 1036503 /lib64/libresolv-2.9.so
7fbb4d566000-7fbb4d567000 r--p 00012000 08:01 1036503 /lib64/libresolv-2.9.so
7fbb4d567000-7fbb4d568000 rw-p 00013000 08:01 1036503 /lib64/libresolv-2.9.so
7fbb4d568000-7fbb4d56a000 rw-p 7fbb4d568000 00:00 0
7fbb4d56a000-7fbb4d577000 r-xp 00000000 08:01 806798 /usr/lib64/liblber-2.3.so.0.2.31
7fbb4d577000-7fbb4d777000 ---p 0000d000 08:01 806798 /usr/lib64/liblber-2.3.so.0.2.31
7fbb4d777000-7fbb4d778000 r--p 0000d000 08:01 806798 /usr/lib64/liblber-2.3.so.0.2.31
7fbb4d778000-7fbb4d779000 rw-p 0000e000 08:01 806798 /usr/lib64/liblber-2.3.so.0.2.31
7fbb4d779000-7fbb4d7b0000 r-xp 00000000 08:01 806808 /usr/lib64/libldap-2.3.so.0.2.31
7fbb4d7b0000-7fbb4d9af000 ---p 00037000 08:01 806808 /usr/lib64/libldap-2.3.so.0.2.31
7fbb4d9af000-7fbb4d9b0000 r--p 00036000 08:01 806808 /usr/lib64/libldap-2.3.so.0.2.31
7fbb4d9b0000-7fbb4d9b2000 rw-p 00037000 08:01 806808 /usr/lib64/libldap-2.3.so.0.2.31
7fbb4d9b2000-7fbb4d9f7000 r-xp 00000000 08:01 814677 /usr/lib64/libcurl.so.4.1.1
7fbb4d9f7000-7fbb4dbf7000 ---p 00045000 08:01 814677 /usr/lib64/libcurl.so.4.1.1
7fbb4dbf7000-7fbb4dbf8000 r--p 00045000 08:01 814677 /usr/lib64/libcurl.so.4.1.1
7fbb4dbf8000-7fbb4dbf9000 rw-p 00046000 08:01 814677 /usr/lib64/libcurl.so.4.1.1
7fbb4dbf9000-7fbb4dbfa000 rw-p 7fbb4dbf9000 00:00 0
7fbb4dbfa000-7fbb4dc0e000 r-xp 00000000 08:01 1036201 /lib64/libnsl-2.9.so
7fbb4dc0e000-7fbb4de0d000 ---p 00014000 08:01 1036201 /lib64/libnsl-2.9.so
7fbb4de0d000-7fbb4de0e000 r--p 00013000 08:01 1036201 /lib64/libnsl-2.9.so
7fbb4de0e000-7fbb4de0f000 rw-p 00014000 08:01 1036201 /lib64/libnsl-2.9.so
7fbb4de0f000-7fbb4de11000 rw-p 7fbb4de0f000 00:00 0
7fbb4de11000-7fbb4de2d000 r-xp 00000000 08:01 1036491 /lib64/ld-2.9.so
7fbb4dff3000-7fbb4dffa000 rw-p 7fbb4dff3000 00:00 0
7fbb4e02a000-7fbb4e02c000 rw-p 7fbb4e02a000 00:00 0
7fbb4e02c000-7fbb4e02d000 r--p 0001b000 08:01 1036491 /lib64/ld-2.9.so
7fbb4e02d000-7fbb4e02e000 rw-p 0001c000 08:01 1036491 /lib64/ld-2.9.so
7fff5600e000-7fff5602d000 rw-p 7ffffffe0000 00:00 0 [stack]
7fff561fd000-7fff561fe000 r-xp 7fff561fd000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]
SIGABRT: abort called
Stack trace (32 frames):
boinc_client[0x4703bd]
/lib/libpthread.so.0[0x7fbb4c23c410]
/lib/libc.so.6(gsignal+0x35)[0x7fbb4bc95205]
/lib/libc.so.6(abort+0x10e)[0x7fbb4bc9657e]
/lib/libc.so.6[0x7fbb4bccede7]
/lib/libc.so.6(__fortify_fail+0x32)[0x7fbb4bd3e4d2]
/lib/libc.so.6[0x7fbb4bd3c4a0]
/lib/libc.so.6[0x7fbb4bd3b9e9]
/lib/libc.so.6(_IO_default_xsputn+0x88)[0x7fbb4bcd2848]
/lib/libc.so.6(_IO_vfprintf+0x38b1)[0x7fbb4bca8591]
/lib/libc.so.6(__vsprintf_chk+0xa7)[0x7fbb4bd3ba97]
/lib/libc.so.6(__sprintf_chk+0x80)[0x7fbb4bd3b9d0]
boinc_client[0x471d56]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x471ddf]
boinc_client[0x43bdf6]
boinc_client[0x41f7f8]
boinc_client[0x454963]
/lib/libc.so.6(__libc_start_main+0xf4)[0x7fbb4bc825e4]
boinc_client[0x405db9]

Exiting...

Running a revdep-rebuild command did not help for the library problems. Do you guys have any suggestions to troubleshoot this?

Thanks!
3) Message boards : Questions and problems : When reporting CUDA errors... (Message 23106)
Posted 14 Feb 2009 by Daseinhorn
Post:
I am using BOINC 6.4.5 compiled with the CUDA option on Gentoo X64. I have an Nvidia GeForce 8800GT with the latest nvidia-drivers ebuild from portage.

The boinc GUI works, but one of the messages during initialization is "No CUDA devices found", despite the fact that my Nvidia card is a CUDA device. How would you suggest fixing this? If you need any specific terminal output I'll try to produce it.

Thanks.
4) Message boards : BOINC client : NO CUDA DEVICE FOUND (Message 23012)
Posted 10 Feb 2009 by Daseinhorn
Post:
I do have a similar issue under Gentoo X64. I have a Nvidia 8800GT card, but the GUI client says No CUDA devices found. My boinc installation is compiled with the CUDA option, and at start-up it is loaded automatically with the /etc/init.d/boinc start script. Is the Vista issue a problem also with Linux? If yes, how do you suggest I load Boinc at start-up?

Thanks.
5) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22955)
Posted 8 Feb 2009 by Daseinhorn
Post:
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!
6) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22944)
Posted 7 Feb 2009 by Daseinhorn
Post:
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!
7) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22938)
Posted 7 Feb 2009 by Daseinhorn
Post:
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?
8) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22915)
Posted 6 Feb 2009 by Daseinhorn
Post:
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
9) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22894)
Posted 5 Feb 2009 by Daseinhorn
Post:
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.
10) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22876)
Posted 4 Feb 2009 by Daseinhorn
Post:
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.
11) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22864)
Posted 3 Feb 2009 by Daseinhorn
Post:
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?
12) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22859)
Posted 3 Feb 2009 by Daseinhorn
Post:
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..
13) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22856)
Posted 3 Feb 2009 by Daseinhorn
Post:
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?
14) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22849)
Posted 2 Feb 2009 by Daseinhorn
Post:
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.
15) Message boards : Questions and problems : Error: Cannot get the official hostname (error 0: Success) (Message 22508)
Posted 19 Jan 2009 by Daseinhorn
Post:
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!
16) Message boards : BOINC Manager : DEBIAN - Boinc versions different, start issue (Message 16637)
Posted 13 Apr 2008 by Daseinhorn
Post:
I have Debian 4.0 RC3, and I have at first installed the BOINC application with the Synaptic package manager. That part works. However, I noticed that the versions were very different from the one recommenced (5.4 vs 5.10.45). First part of the question, is this normal, or the Debian packages website has not been updated?

Second part now, I have downloaded versions 5.10.45 and the new development one, 6.1.14. I run the SH command in the terminal, but once I want to use the run_manager command, the terminal just shuts down. This happened with both versions. Is this because the new versions are not compatible with Debian 4, or I just don't know how to use the GNOME terminal?

Thanks!



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.