128.143.231.201 - internal server error & failed http_ok

Moderators: Site Moderators, FAHC Science Team

Post Reply
n31l
Posts: 14
Joined: Wed Jun 01, 2011 9:58 pm

128.143.231.201 - internal server error & failed http_ok

Post by n31l »

Hi, my 2 servers seem to be both using the above assignment server and recently it can be hours before I get a WU, I restarted client but still got same assignment server? Can I select an assignment server manually somehow? as can be seen in second log when assignment server changes to 130.237.232.141 everything seems to be working fine.

example after a restart (Server 1);

Code: Select all

n31l@Lab-server-1:~/.FAHClient$ tail -fn 2000 ./log.txt
*********************** Log Started 13/Apr/2012-06:21:31 ***********************
06:21:31:************************* Folding@home Client *************************
06:21:31:    Website: http://folding.stanford.edu/
06:21:31:  Copyright: (c) 2009,2010 Stanford University
06:21:31:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:21:31:       Args: --child --lifeline 37078 /home/n31l/.FAHClient/config.xml --run-as
06:21:31:             n31l --pid-file=/var/run/fahclient.pid --daemon
06:21:31:     Config: /home/n31l/.FAHClient/config.xml
06:21:31:******************************** Build ********************************
06:21:31:    Version: 7.1.24
06:21:31:       Date: Apr 6 2011
06:21:31:Started thread 3 on PID 37084
06:21:31:       Time: 21:24:39
06:21:31:    SVN Rev: 2908
06:21:31:     Branch: fah/trunk/client
06:21:31:   Compiler: Intel(R) C++ g++ 4.3 mode 1110
06:21:31:    Options: -std=gnu++98 -O3 -funroll-loops -msse2 -axSSE3,SSSE3,SSE4.1,SSE4.2
06:21:31:             -restrict
06:21:31:   Platform: linux2 2.6.35-22-server
06:21:31:       Bits: 64
06:21:31:       Mode: Release
06:21:31:******************************* System ********************************
06:21:31:         OS: Linux 2.6.38-13-generic x86_64
06:21:31:        CPU: Intel(R) Xeon(R) CPU X7560 @ 2.27GHz
06:21:31:     CPU ID: GenuineIntel Family 6 Model 46 Stepping 6
06:21:31:       CPUs: 1288
06:21:31:     Memory: 992.14GiB
06:21:31:Free Memory: 973.57GiB
06:21:31:    Threads: POSIX_THREADS
06:21:31:       GPUs: 4
06:21:31:      GPU 0: Rage XL (Intel Corporation)
06:21:31:      GPU 1: ES1000
06:21:31:      GPU 2: Rage XL (Intel Corporation)
06:21:31:      GPU 3: Rage XL (Intel Corporation)
06:21:31:       CUDA: Not detected
06:21:31: On Battery: false
06:21:31: UTC offset: 2
06:21:31:        PID: 37084
06:21:31:        CWD: /home/n31l/.FAHClient
06:21:31:***********************************************************************
06:21:31:<config>
06:21:31:  <!-- Client Control -->
06:21:31:  <cycle-rate v='4'/>
06:21:31:  <cycles v='-1'/>
06:21:31:  <data-directory v='.'/>
06:21:31:  <exec-directory v='/usr/bin'/>
06:21:31:  <exit-when-done v='false'/>
06:21:31:  <max-delay v='21600'/>
06:21:31:  <min-delay v='60'/>
06:21:31:  <threads v='4'/>
06:21:31:
06:21:31:  <!-- Configuration -->
06:21:31:  <config-rotate v='true'/>
06:21:31:  <config-rotate-dir v='configs'/>
06:21:31:  <config-rotate-max v='16'/>
06:21:31:
06:21:31:  <!-- Debugging -->
06:21:31:  <assignment-servers>
06:21:31:    assign3.stanford.edu:8080 assign4.stanford.edu:80
06:21:31:  </assignment-servers>
06:21:31:  <capture-directory v='capture'/>
06:21:31:  <capture-sockets v='false'/>
06:21:31:  <debug-sockets v='false'/>
06:21:31:  <exception-locations v='true'/>
06:21:31:  <gpu-assignment-servers>
06:21:31:    assign-GPU.stanford.edu:80 assign-GPU.stanford.edu:8080
06:21:31:  </gpu-assignment-servers>
06:21:31:  <stack-traces v='false'/>
06:21:31:
06:21:31:  <!-- Error Handling -->
06:21:31:  <max-slot-errors v='5'/>
06:21:31:  <max-unit-errors v='5'/>
06:21:31:
06:21:31:  <!-- FahCore Control -->
06:21:31:  <checkpoint v='30'/>
06:21:31:  <core-dir v='cores'/>
06:21:31:  <core-priority v='low'/>
06:21:31:  <cpu-affinity v='true'/>
06:21:31:  <cpu-usage v='100'/>
06:21:31:  <no-assembly v='false'/>
06:21:31:
06:21:31:  <!-- Folding Slot Configuration -->
06:21:31:  <client-subtype v='LINUX'/>
06:21:31:  <client-type v='bigbeta'/>
06:21:31:  <cpu-species v='X86_PENTIUM_II'/>
06:21:31:  <cpu-type v='AMD64'/>
06:21:31:  <cpus v='128'/>
06:21:31:  <extra-core-args v='-forceasm'/>
06:21:31:  <gpu v='false'/>
06:21:31:  <gpu-id v='0'/>
06:21:31:  <max-packet-size v='big'/>
06:21:31:  <os-species v='UNKNOWN'/>
06:21:31:  <os-type v='LINUX'/>
06:21:31:  <project-key v='0'/>
06:21:31:  <smp v='true'/>
06:21:31:
06:21:31:  <!-- Logging -->
06:21:31:  <log v='log.txt'/>
06:21:31:  <log-color v='true'/>
06:21:31:  <log-crlf v='false'/>
06:21:31:  <log-date v='false'/>
06:21:31:  <log-debug v='true'/>
06:21:31:  <log-domain v='false'/>
06:21:31:  <log-header v='true'/>
06:21:31:  <log-level v='true'/>
06:21:31:  <log-no-info-header v='true'/>
06:21:31:  <log-redirect v='false'/>
06:21:31:  <log-rotate v='true'/>
06:21:31:  <log-rotate-dir v='logs'/>
06:21:31:  <log-rotate-max v='16'/>
06:21:31:  <log-short-level v='false'/>
06:21:31:  <log-simple-domains v='true'/>
06:21:31:  <log-thread-id v='false'/>
06:21:31:  <log-time v='true'/>
06:21:31:  <log-to-screen v='true'/>
06:21:31:  <log-truncate v='false'/>
06:21:31:  <verbosity v='5'/>
06:21:31:
06:21:31:  <!-- Network -->
06:21:31:  <proxy v='127.0.0.1:8081'/>
06:21:31:  <proxy-enable v='true'/>
06:21:31:  <proxy-pass v=''/>
06:21:31:  <proxy-user v=''/>
06:21:31:
06:21:31:  <!-- Process Control -->
06:21:31:  <child v='true'/>
06:21:31:  <daemon v='true'/>
06:21:31:  <pid v='false'/>
06:21:31:  <pid-file v='/var/run/fahclient.pid'/>
06:21:31:  <respawn v='false'/>
06:21:31:  <service v='false'/>
06:21:31:
06:21:31:  <!-- Remote Command Server -->
06:21:31:  <command-address v='0.0.0.0'/>
06:21:31:  <command-allow v='127.0.0.1'/>
06:21:31:  <command-allow-no-pass v='127.0.0.1'/>
06:21:31:  <command-deny v='0.0.0.0/0'/>
06:21:31:  <command-deny-no-pass v='0.0.0.0/0'/>
06:21:31:  <command-port v='36330'/>
06:21:31:  <password v=''/>
06:21:31:
06:21:31:  <!-- Slot Control -->
06:21:31:  <max-shutdown-wait v='60'/>
06:21:31:  <pause-on-battery v='false'/>
06:21:31:  <pause-on-start v='false'/>
06:21:31:
06:21:31:  <!-- User Information -->
06:21:31:  <machine-id v='0'/>
06:21:31:  <passkey v='********************************'/>
06:21:31:  <team v='2654'/>
06:21:31:  <user v='n31l'/>
06:21:31:
06:21:31:  <!-- Work Unit Control -->
06:21:31:  <dump-after-deadline v='true'/>
06:21:31:  <max-queue v='16'/>
06:21:31:  <max-units v='0'/>
06:21:31:  <next-unit-percentage v='100'/>
06:21:31:
06:21:31:  <!-- Folding Slots -->
06:21:31:  <slot id='1' type='SMP'/>
06:21:31:</config>
06:21:31:Switching to user n31l
06:21:31:Trying to access database...
06:21:31:Database locked
06:21:31:Enabled folding slot 01: READY smp:128
06:21:31:Started thread 2 on PID 37084
06:21:31:Started thread 5 on PID 37084
06:21:31:Started thread 6 on PID 37084
06:21:31:Started thread 7 on PID 37084
06:21:31:Started thread 4 on PID 37084
06:21:31:Connecting to 127.0.0.1:8081
06:21:32:News: Welcome to Folding@Home
06:21:32:Assigned to work server 128.143.231.201
06:21:32:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:21:32:Connecting to 127.0.0.1:8081
06:21:35:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
06:21:35:Started thread 8 on PID 37084
06:22:02:ERROR: Exception: Failed to read response packet: HTTP_OK
06:22:02:Connecting to 127.0.0.1:8081
06:22:03:News: Welcome to Folding@Home
06:22:03:Assigned to work server 128.143.231.201
06:22:03:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:22:03:Connecting to 127.0.0.1:8081
06:22:19:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
06:23:03:Connecting to 127.0.0.1:8081
06:23:03:News: Welcome to Folding@Home
06:23:03:Assigned to work server 128.143.231.201
06:23:04:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:23:04:Connecting to 127.0.0.1:8081
06:23:34:ERROR: Exception: Failed to read response packet: HTTP_OK
06:24:40:Connecting to 127.0.0.1:8081
06:24:41:News: Welcome to Folding@Home
06:24:41:Assigned to work server 128.143.231.201
06:24:41:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:24:41:Connecting to 127.0.0.1:8081
06:25:11:ERROR: Exception: Failed to read response packet: HTTP_OK
06:27:17:Connecting to 127.0.0.1:8081
06:27:18:News: Welcome to Folding@Home
06:27:18:Assigned to work server 128.143.231.201
06:27:18:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:27:18:Connecting to 127.0.0.1:8081
06:27:48:ERROR: Exception: Failed to read response packet: HTTP_OK
06:31:31:Connecting to 127.0.0.1:8081
06:31:32:News: Welcome to Folding@Home
06:31:32:Assigned to work server 128.143.231.201
06:31:32:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:31:32:Connecting to 127.0.0.1:8081
06:32:02:ERROR: Exception: Failed to read response packet: HTTP_OK
06:32:02:Cleaning up Unit 00
06:32:02:Connecting to 127.0.0.1:8081
06:32:04:News: Welcome to Folding@Home
06:32:04:Assigned to work server 128.143.231.201
06:32:04:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:32:04:Connecting to 127.0.0.1:8081
06:32:19:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
06:32:19:Connecting to 127.0.0.1:8081
06:32:20:News: Welcome to Folding@Home
06:32:20:Assigned to work server 128.143.231.201
06:32:20:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:32:20:Connecting to 127.0.0.1:8081
06:32:50:ERROR: Exception: Failed to read response packet: HTTP_OK
06:33:19:Connecting to 127.0.0.1:8081
06:33:20:News: Welcome to Folding@Home
06:33:20:Assigned to work server 128.143.231.201
06:33:20:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:33:20:Connecting to 127.0.0.1:8081
06:33:50:ERROR: Exception: Failed to read response packet: HTTP_OK
06:34:57:Connecting to 127.0.0.1:8081
06:34:58:News: Welcome to Folding@Home
06:34:58:Assigned to work server 128.143.231.201
06:34:58:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:34:58:Connecting to 127.0.0.1:8081
06:35:28:ERROR: Exception: Failed to read response packet: HTTP_OK
06:37:34:Connecting to 127.0.0.1:8081
06:37:35:News: Welcome to Folding@Home
06:37:35:Assigned to work server 128.143.231.201
06:37:35:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
06:37:35:Connecting to 127.0.0.1:8081
06:38:05:ERROR: Exception: Failed to read response packet: HTTP_OK
06:41:48:Connecting to 127.0.0.1:8081
06:41:49:News: Welcome to Folding@Home
example of second machine which shows after a server switch to 130.237.232.141 everything's working again (Server 2);

Code: Select all

19:38:57:Unit 00:- Writing 100179508 bytes of core data to disk...
19:38:58:Unit 00:  ... Done.
19:39:00:ERROR: Exception: Failed to read response packet: HTTP_OK
19:39:00:Connecting to 127.0.0.1:8081
19:39:02:News: Welcome to Folding@Home
19:39:02:Assigned to work server 128.143.231.201
19:39:02:Requesting new work unit for slot 01: RUNNING smp:128 from 128.143.231.201
19:39:02:Connecting to 127.0.0.1:8081
19:39:06:Unit 00:- Shutting down core
19:39:06:Unit 00:
19:39:06:Unit 00:Folding@home Core Shutdown: FINISHED_UNIT
19:39:07:FahCore, running Unit 00, returned: FINISHED_UNIT (100)
19:39:07:Sending unit results: id:00 state:SEND project:6900 run:39 clone:1 gen:113 core:0xa5 unit:0x000000a352be740d4de96b9747bd104f
19:39:07:Unit 00: Uploading 95.54MiB
19:39:07:Connecting to 127.0.0.1:8081
19:39:13:Unit 00: 8.72%
19:39:17:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:39:19:Unit 00: 19.10%
19:39:25:Unit 00: 29.52%
19:39:31:Unit 00: 39.73%
19:39:37:Unit 00: 49.78%
19:39:43:Unit 00: 59.92%
19:39:49:Unit 00: 70.00%
19:39:55:Unit 00: 80.12%
19:40:00:Connecting to 127.0.0.1:8081
19:40:01:Unit 00: 90.20%
19:40:02:News: Welcome to Folding@Home
19:40:02:Assigned to work server 128.143.231.201
19:40:02:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:40:02:Connecting to 127.0.0.1:8081
19:40:07:Unit 00: 98.85%
19:40:10:Unit 00: Upload complete
19:40:10:Server responded WORK_ACK (400)
19:40:10:Final credit estimate, 198137.00 points
19:40:10:Cleaning up Unit 00
19:40:32:ERROR: Exception: Failed to read response packet: HTTP_OK
19:41:38:Connecting to 127.0.0.1:8081
19:41:39:News: Welcome to Folding@Home
19:41:39:Assigned to work server 128.143.231.201
19:41:39:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:41:39:Connecting to 127.0.0.1:8081
19:42:09:ERROR: Exception: Failed to read response packet: HTTP_OK
19:44:15:Connecting to 127.0.0.1:8081
19:44:16:News: Welcome to Folding@Home
19:44:16:Assigned to work server 128.143.231.201
19:44:16:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:44:16:Connecting to 127.0.0.1:8081
19:44:46:ERROR: Exception: Failed to read response packet: HTTP_OK
19:48:29:Connecting to 127.0.0.1:8081
19:48:30:News: Welcome to Folding@Home
19:48:30:Assigned to work server 128.143.231.201
19:48:30:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:48:30:Connecting to 127.0.0.1:8081
19:49:00:ERROR: Exception: Failed to read response packet: HTTP_OK
19:49:01:Cleaning up Unit 01
19:49:01:Connecting to 127.0.0.1:8081
19:49:02:News: Welcome to Folding@Home
19:49:02:Assigned to work server 128.143.231.201
19:49:02:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:49:02:Connecting to 127.0.0.1:8081
19:49:17:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
19:49:17:Connecting to 127.0.0.1:8081
19:49:18:News: Welcome to Folding@Home
19:49:18:Assigned to work server 128.143.231.201
19:49:18:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:49:18:Connecting to 127.0.0.1:8081
19:49:48:ERROR: Exception: Failed to read response packet: HTTP_OK
19:50:17:Connecting to 127.0.0.1:8081
19:50:18:News: Welcome to Folding@Home
19:50:18:Assigned to work server 128.143.231.201
19:50:18:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
19:50:18:Connecting to 127.0.0.1:8081
19:50:47:ERROR: Exception: Failed to read response packet: HTTP_OK
~
~
~
~
~
21:37:53:ERROR: Exception: Failed to read response packet: HTTP_OK
21:41:36:Connecting to 127.0.0.1:8081
21:41:37:News: Welcome to Folding@Home
21:41:37:Assigned to work server 128.143.231.201
21:41:38:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:41:38:Connecting to 127.0.0.1:8081
21:42:08:ERROR: Exception: Failed to read response packet: HTTP_OK
21:42:08:Cleaning up Unit 00
21:42:08:Connecting to 127.0.0.1:8081
21:42:09:News: Welcome to Folding@Home
21:42:09:Assigned to work server 128.143.231.201
21:42:09:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:42:09:Connecting to 127.0.0.1:8081
21:42:24:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
21:42:24:Connecting to 127.0.0.1:8081
21:42:25:News: Welcome to Folding@Home
21:42:25:Assigned to work server 128.143.231.201
21:42:25:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:42:25:Connecting to 127.0.0.1:8081
21:42:55:ERROR: Exception: Failed to read response packet: HTTP_OK
21:43:24:Connecting to 127.0.0.1:8081
21:43:26:News: Welcome to Folding@Home
21:43:26:Assigned to work server 128.143.231.201
21:43:26:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:43:26:Connecting to 127.0.0.1:8081
21:43:56:ERROR: Exception: Failed to read response packet: HTTP_OK
21:45:02:Connecting to 127.0.0.1:8081
21:45:03:News: Welcome to Folding@Home
21:45:03:Assigned to work server 128.143.231.201
21:45:03:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:45:03:Connecting to 127.0.0.1:8081
21:45:33:ERROR: Exception: Failed to read response packet: HTTP_OK
21:47:39:Connecting to 127.0.0.1:8081
21:47:40:News: Welcome to Folding@Home
21:47:40:Assigned to work server 128.143.231.201
21:47:40:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:47:40:Connecting to 127.0.0.1:8081
21:48:10:ERROR: Exception: Failed to read response packet: HTTP_OK
21:51:53:Connecting to 127.0.0.1:8081
21:51:54:News: Welcome to Folding@Home
21:51:54:Assigned to work server 128.143.231.201
21:51:54:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:51:54:Connecting to 127.0.0.1:8081
21:52:24:ERROR: Exception: Failed to read response packet: HTTP_OK
21:52:25:Cleaning up Unit 01
21:52:25:Connecting to 127.0.0.1:8081
21:52:26:News: Welcome to Folding@Home
21:52:26:Assigned to work server 128.143.231.201
21:52:26:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
21:52:26:Connecting to 127.0.0.1:8081
21:52:41:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
21:52:41:Connecting to 127.0.0.1:8081
21:53:11:WARNING: Failed to get assignment from 'assign3.stanford.edu:8080': Failed to read response packet: HTTP_OK
21:53:11:Connecting to 127.0.0.1:8081
21:53:13:News: Welcome to Folding@Home
21:53:13:Assigned to work server 130.237.232.141
21:53:13:Requesting new work unit for slot 01: READY smp:128 from 130.237.232.141
21:53:13:Connecting to 127.0.0.1:8081
21:53:19:Slot 01: Downloading 23.72MiB
21:53:25:Slot 01: 35.24%
21:53:31:Slot 01: 74.80%
21:53:34:Slot 01: Download complete
Top
n31l
Posts: 14
Joined: Wed Jun 01, 2011 9:58 pm

Re: 128.143.231.201 - internal server error & failed http_ok

Post by n31l »

** quick update, eventually server 1 seems to have given up and moved to another assignment server and working ok again - so 128.143.231.201 doesn't seem to be too healthy :-(

Code: Select all

07:29:30:ERROR: Exception: Failed to read response packet: HTTP_OK
07:33:13:Connecting to 127.0.0.1:8081
07:33:14:News: Welcome to Folding@Home
07:33:14:Assigned to work server 128.143.231.201
07:33:14:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
07:33:14:Connecting to 127.0.0.1:8081
07:33:44:ERROR: Exception: Failed to read response packet: HTTP_OK
07:33:45:Cleaning up Unit 00
07:33:45:Connecting to 127.0.0.1:8081
07:33:46:News: Welcome to Folding@Home
07:33:46:Assigned to work server 128.143.231.201
07:33:46:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
07:33:46:Connecting to 127.0.0.1:8081
07:34:01:ERROR: Exception: Server responded: HTTP_INTERNAL_SERVER_ERROR
07:34:01:Connecting to 127.0.0.1:8081
07:34:02:News: Welcome to Folding@Home
07:34:02:Assigned to work server 128.143.231.201
07:34:02:Requesting new work unit for slot 01: READY smp:128 from 128.143.231.201
07:34:02:Connecting to 127.0.0.1:8081
07:34:32:ERROR: Exception: Failed to read response packet: HTTP_OK
07:35:01:Connecting to 127.0.0.1:8081
07:35:12:WARNING: Failed to get assignment from 'assign3.stanford.edu:8080': Server responded: HTTP_SERVICE_UNAVAILABLE
07:35:12:Connecting to 127.0.0.1:8081
07:35:13:News: Welcome to Folding@Home
07:35:13:Assigned to work server 130.237.232.141
07:35:13:Requesting new work unit for slot 01: READY smp:128 from 130.237.232.141
07:35:13:Connecting to 127.0.0.1:8081
07:35:20:Slot 01: Downloading 23.72MiB
07:35:26:Slot 01: 19.33%
07:35:32:Slot 01: 40.08%
07:35:38:Slot 01: 60.82%
07:35:44:Slot 01: 81.50%
07:35:49:Slot 01: Download complete
07:35:49:Received Unit: id:01 state:DOWNLOAD project:6900 run:4 clone:15 gen:155 core:0xa5 unit:0x000000c252be740d4de95912a67c4a3f
07:35:49:Starting Unit 01
07:35:49:Running core: /home/n31l/.FAHClient/cores/www.stanford.edu/~pande/Linux/AMD64/beta/Core_a5.fah/FahCore_a5 -dir 01 -suffix 01 -lifeline 37084 -version 701 -checkpoint 30 -np 128 -forceasm
07:35:49:Started core on PID 37323
07:35:49:FahCore 0xa5 started
07:35:49:Started thread 9 on PID 37084
07:35:49:Unit 01:
07:35:49:Unit 01:*------------------------------*
07:35:49:Unit 01:Folding@Home Gromacs SMP Core
07:35:49:Unit 01:Version 2.27 (Thu Feb 10 09:46:40 PST 2011)
07:35:49:Unit 01:
07:35:49:Unit 01:Preparing to commence simulation
07:35:49:Unit 01:- Assembly optimizations manually forced on.
07:35:49:Unit 01:- Not checking prior termination.
07:35:52:Unit 01:- Expanded 24876184 -> 30796292 (decompressed 123.7 percent)
07:35:52:Unit 01:Called DecompressByteArray: compressed_data_size=24876184 data_size=30796292, decompressed_data_size=30796292 diff=0
07:35:52:Unit 01:- Digital signature verified
07:35:52:Unit 01:
07:35:52:Unit 01:Project: 6900 (Run 4, Clone 15, Gen 155)
07:35:52:Unit 01:
07:35:52:Unit 01:Assembly optimizations on if available.
07:35:52:Unit 01:Entering M.D.
07:35:59:Unit 01:Mapping NT from 128 to 128
07:36:06:Unit 01:Completed 0 out of 250000 steps  (0%)
07:39:54:Unit 01:Completed 2500 out of 250000 steps  (1%)
07:43:39:Unit 01:Completed 5000 out of 250000 steps  (2%)
07:47:24:Unit 01:Completed 7500 out of 250000 steps  (3%)
07:51:09:Unit 01:Completed 10000 out of 250000 steps  (4%)
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 128.143.231.201 - internal server error & failed http_ok

Post by bruce »

You have no direct control over which Work Server will be assigned. Stanford uses the server assignment process to redirecty your requests from servers which can't assign work right not to another one which can -- information that you wouldn't have available to you when you need it.

I notice that 128.143.231.201 has "accept" STATUS rather than "full" STATUS. That probably means the problem has been recognized -- or somebody is changing things on that server.
Top
TheWasp
Posts: 2
Joined: Sun May 20, 2012 9:13 am

Re: 128.143.231.201 - internal server error & failed http_ok

Post by TheWasp »

It seems the problems with 128.143.231.201 are still not solved

My Server (EVGA-SR2 with two Xeon E5540) running UBUNTU 10.10 and the V7 with bigadv still gets the awfull messages

Exception: 10001: Server responded: HTTP_INTERNAL_SERVER_ERROR
and/or
Exception: Could not get an assignment
and/or
Exception: 10002: Received short response, expected 512 bytes, got 0

for hours and hours
only workaround in the moment:

I start a V6(.34)
After one or two minutes the V6 connects correctly and i disable it
While that, the V7 then connects to 130.237.232.141 and begin to fold - flawless

But this is a weak workaround; there has to be a better solution

Any suggestions??
Thanks in advance
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 128.143.231.201 - internal server error & failed http_ok

Post by bruce »

Does http://128.143.231.201/ give you an error or does it just give a blank page?

Have you done anything with the proxy settings?

Does your LAN support IPV6?
Top
TheWasp
Posts: 2
Joined: Sun May 20, 2012 9:13 am

Re: 128.143.231.201 - internal server error & failed http_ok

Post by TheWasp »

I forgot to mention one important fact

The server was folding well for about three month - this one is new
So yes, everything is set as it should - i guess
Top
Post Reply

Return to “Issues with a specific server”