Questions and Answers :
Unix/Linux :
SETI 5.10.45 Problem
Message board moderation
Author | Message |
---|---|
mwhall Send message Joined: 18 May 99 Posts: 19 Credit: 6,342,632 RAC: 12 |
I am running Fedora Core 6.0 and SETI 5.10.45. It appears that the client will just hang. I downloaded a new work unit yesterday after having to abort the previous two since the report date had past. I have a Athlon 64 3200+ CPU and 1 GB of RAM. I am running x86_64 of Fedora 6. Does anyone else see this problem. I it could be that the client said it is for Fedora 7 and up. Any ideas? Thanks, Michael |
DJStarfox Send message Joined: 23 May 01 Posts: 1066 Credit: 1,226,053 RAC: 2 |
I am running Fedora Core 6.0 and SETI 5.10.45. It appears that the client will just hang. I downloaded a new work unit yesterday after having to abort the previous two since the report date had past. I have a Athlon 64 3200+ CPU and 1 GB of RAM. I am running x86_64 of Fedora 6. Does anyone else see this problem. I it could be that the client said it is for Fedora 7 and up. Any ideas? Perhaps some clarification will bring techs out of the woodwork. First, understand that there are 3 processes involved when you say "SETI": boinc = daemon that runs in the background; boincmgr = GUI that allows you to control boinc; setiathome_enhanced = science application that is called by the boinc daemon for each task/workunit that you download; Can you tell me which process is hanging and what the symptoms are? |
mwhall Send message Joined: 18 May 99 Posts: 19 Credit: 6,342,632 RAC: 12 |
I am running Fedora Core 6.0 and SETI 5.10.45. It appears that the client will just hang. I downloaded a new work unit yesterday after having to abort the previous two since the report date had past. I have a Athlon 64 3200+ CPU and 1 GB of RAM. I am running x86_64 of Fedora 6. Does anyone else see this problem. I it could be that the client said it is for Fedora 7 and up. Any ideas? I am talking about the GUI. The CPU time does not increment or the % complete does not increment either. Appears that it just locks up. I had two work units that passed the reply by date. This machine usually cranks them out. Michael |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
I am running Fedora Core 6.0 and SETI 5.10.45. It appears that the client will just hang. I downloaded a new work unit yesterday after having to abort the previous two since the report date had past. I have a Athlon 64 3200+ CPU and 1 GB of RAM. I am running x86_64 of Fedora 6. Does anyone else see this problem. I it could be that the client said it is for Fedora 7 and up. Any ideas? The BOINC GUI (BONCMGR.EXE) should almost never have CPU time increment unless you have the BOINC Manager window open and are actively using it. The BOINC Core Client (BOINC.EXE) handles all scheduling and uploading/downloading of files, so it's CPU usage should also be minimal. The SETI@Home science app (SETIATHOME_Enhanced) should be the only process actively using CPU time while it processes the data. |
DJStarfox Send message Joined: 23 May 01 Posts: 1066 Credit: 1,226,053 RAC: 2 |
I am talking about the GUI. The CPU time does not increment or the % complete does not increment either. Appears that it just locks up. I had two work units that passed the reply by date. This machine usually cranks them out. Pull up a linux console window and post back the output of these commands: hostname -f cat /etc/hosts Also, does your machine have a static IP or do you get an IP via DHCP? If you're not sure, post the output of this command: /sbin/ifconfig |
mwhall Send message Joined: 18 May 99 Posts: 19 Credit: 6,342,632 RAC: 12 |
I am talking about the GUI. The CPU time does not increment or the % complete does not increment either. Appears that it just locks up. I had two work units that passed the reply by date. This machine usually cranks them out. I get my IP from DHCP. Output of the two commands follows: [mwhall@TAZ ~]$ hostname -f hostname: Unknown host [mwhall@TAZ ~]$ cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. ::1 TAZ localhost.localdomain localhost |
DJStarfox Send message Joined: 23 May 01 Posts: 1066 Credit: 1,226,053 RAC: 2 |
I get my IP from DHCP. Add the following line to your /etc/hosts file using any text editor: 127.0.0.1 localhost.localdomain localhost Should fix your problem after networking is restarted. |
mwhall Send message Joined: 18 May 99 Posts: 19 Credit: 6,342,632 RAC: 12 |
I get my IP from DHCP. No luck. It is as if the SETI client is hung or gone south. The report deadline for the work unit it has is today at 11:00 PM. I have been watching the progress in the GUI and it has not moved in 15 minutes. I had this same issue with the previous version. However the one two versions back was working fine. I will keep searching. |
DJStarfox Send message Joined: 23 May 01 Posts: 1066 Credit: 1,226,053 RAC: 2 |
No luck. It is as if the SETI client is hung or gone south. The report deadline for the work unit it has is today at 11:00 PM. I have been watching the progress in the GUI and it has not moved in 15 minutes. I had this same issue with the previous version. However the one two versions back was working fine. I will keep searching. Did you recently update your system? A firewall may cause this. Disable your firewall if you have one running: /sbin/service iptables stop Open up "System Monitor" and make sure no boinc* processes are running. Then goto the command line and type: cd /usr/local/BOINC (or wherever your BOINC folder is) ./boinc --allow_remote_gui_rpc Observe the output and past it in here (in this thread). |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.