Member
Статус: Не в сети Регистрация: 07.03.2007 Откуда: Санкт-Петербург
Hil И тем не менее на 2 машинах я их получил http://imageshost.ru/links/0720120141/ http://imageshost.ru/links/0720120142 Причем это уже второй заход, первые жабы я получил 18го, они считались чуть более суток, и 19го получил новые. По поводу перезапуска клиента - абсолютно уверен, т.к. у меня стоит самописная система ускоренного получения новых жаб, которая каждые 2 минуты по сети перезапускает сервис, не допуская увеличения интервалов между попытками. Судя по логу клиенты около 15 минут безуспешно стучались на 160й, после чего наконец получили вожделенные жабки с 139го. Про 133й в логах ничего нет.
Advanced member
Статус: Не в сети Регистрация: 16.12.2002 Откуда: TSC! | Москва
B0NiQ писал(а):
тем не менее на 2 машинах я их получил
Так поставить-то можно любой тип. А перезапускался ли клиент после этой установки? Пока не перезапустишь, он будет использовать тип, который считал при запуске. Сейчас проверю сам, будет проще.
Цитата:
--- Opening Log file [July 20 10:58:34]
# Windows Console Edition ##################################################### ###############################################################################
Warning: By using the -forceasm flag, you are overriding safeguards in the program. If you did not intend to do this, please restart the program without -forceasm. If work units are not completing fully (and particularly if your machine is overclocked), then please discontinue use of the flag.
[10:58:34] - Ask before connecting: No [10:58:34] - User name: RU_Hil (Team 47191) [10:58:34] - User ID: 1FBE99B70A71EC17 [10:58:34] - Machine ID: 8 [10:58:34] [10:58:34] Work directory not found. Creating... [10:58:34] Could not open work queue, generating new queue... [10:58:34] + Benchmarking ... [10:58:37] The benchmark result is 10080 [10:58:37] - Preparing to get new work unit... [10:58:37] + Attempting to get work packet [10:58:37] - Will indicate memory of 1023 MB [10:58:37] - Autosending finished units... [10:58:37] - Connecting to assignment server [10:58:37] Trying to send all finished work units [10:58:37] Connecting to http://assign.stanford.edu:8080/ [10:58:37] + No unsent completed units remaining. [10:58:37] - Autosend completed [10:58:47] Posted data. [10:58:47] Initial: 40AB; - Successful: assigned to (171.64.122.133). [10:58:47] + News From Folding@Home: Welcome to Folding@Home [10:58:47] Loaded queue successfully. [10:58:47] Connecting to http://171.64.122.133:8080/ [10:58:50] Posted data. [10:58:50] Initial: 0000; + Could not connect to Work Server [10:58:50] - Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry. [10:58:55] + Attempting to get work packet [10:58:55] - Will indicate memory of 1023 MB [10:58:55] - Connecting to assignment server [10:58:55] Connecting to http://assign.stanford.edu:8080/ [10:58:58] Posted data. [10:58:58] Initial: 40AB; - Successful: assigned to (171.64.122.133). [10:58:58] + News From Folding@Home: Welcome to Folding@Home [10:58:58] Loaded queue successfully. [10:58:58] Connecting to http://171.64.122.133:8080/ [10:59:01] Posted data. [10:59:01] Initial: 0000; + Could not connect to Work Server [10:59:01] - Error: Attempt #2 to get work failed, and no other work to do. Waiting before retry. [10:59:11] + Attempting to get work packet [10:59:11] - Will indicate memory of 1023 MB [10:59:11] - Connecting to assignment server [10:59:11] Connecting to http://assign.stanford.edu:8080/ [10:59:13] Posted data. [10:59:13] Initial: 40AB; - Successful: assigned to (171.64.122.133). [10:59:13] + News From Folding@Home: Welcome to Folding@Home [10:59:13] Loaded queue successfully. [10:59:13] Connecting to http://171.64.122.133:8080/ [10:59:14] ***** Got a SIGTERM signal (2) [10:59:14] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [July 20 10:59:40]
# Windows Console Edition ##################################################### ###############################################################################
Warning: By using the -forceasm flag, you are overriding safeguards in the program. If you did not intend to do this, please restart the program without -forceasm. If work units are not completing fully (and particularly if your machine is overclocked), then please discontinue use of the flag.
[10:59:40] - Ask before connecting: No [10:59:40] - User name: RU_Hil (Team 47191) [10:59:40] - User ID: 1FBE99B70A71EC17 [10:59:40] - Machine ID: 8 [10:59:40] [10:59:40] Loaded queue successfully. [10:59:40] + Benchmarking ... [10:59:43] The benchmark result is 10080 [10:59:43] - Preparing to get new work unit... [10:59:43] + Attempting to get work packet [10:59:43] - Will indicate memory of 1023 MB [10:59:43] - Connecting to assignment server [10:59:43] - Autosending finished units... [10:59:43] Connecting to http://assign.stanford.edu:8080/ [10:59:43] Trying to send all finished work units [10:59:43] + No unsent completed units remaining. [10:59:43] - Autosend completed [10:59:46] Posted data. [10:59:46] Initial: 40AB; - Successful: assigned to (171.64.122.133). [10:59:46] + News From Folding@Home: Welcome to Folding@Home [10:59:46] Loaded queue successfully. [10:59:46] Connecting to http://171.64.122.133:8080/ [10:59:48] Posted data. [10:59:48] Initial: 0000; + Could not connect to Work Server [10:59:48] - Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry. [11:00:06] + Attempting to get work packet [11:00:06] - Will indicate memory of 1023 MB [11:00:06] - Connecting to assignment server [11:00:06] Connecting to http://assign.stanford.edu:8080/ [11:00:08] Posted data. [11:00:08] Initial: 40AB; - Successful: assigned to (171.64.122.133). [11:00:08] + News From Folding@Home: Welcome to Folding@Home [11:00:08] Loaded queue successfully. [11:00:08] Connecting to http://171.64.122.133:8080/ [11:00:10] Posted data. [11:00:10] Initial: 0000; + Could not connect to Work Server [11:00:10] - Error: Attempt #2 to get work failed, and no other work to do. Waiting before retry. [11:00:12] ***** Got a SIGTERM signal (2) [11:00:12] Killing all core threads
Folding@Home Client Shutdown.
1-й с bp=yes type=2, второй с bp=no type=2. Как видишь...
Member
Статус: Не в сети Регистрация: 07.03.2007 Откуда: Санкт-Петербург
Hil Точно перезапускался.
Еще раз - у меня при получении жаб каждые две минуты сервис перезапускаеться автоматически.
Type=2 я прописал еще 18го днем
Вот лог того же PC03, что на первом скриншоте
Цитата:
[18:07:47] Finished Work Unit: [18:07:47] - Reading up to 585764 from "work/wudata_01.arc": Read 585764 [18:07:47] - Reading up to 217008 from "work/wudata_01.xtc": Read 217008 [18:07:47] goefile size: 0 [18:07:47] logfile size: 15727 [18:07:47] Leaving Run [18:07:50] - Writing 831303 bytes of core data to disk... [18:07:50] ... Done. [18:07:50] - Shutting down core [18:07:50] [18:07:50] Folding@home Core Shutdown: FINISHED_UNIT [18:07:54] CoreStatus = 64 (100) [18:07:54] Unit 1 finished with 98 percent of time to deadline remaining. [18:07:54] Updated performance fraction: 0.956124 [18:07:54] Sending work to server
[18:07:54] + Attempting to send results [18:07:54] - Reading file work/wuresults_01.dat from core [18:07:54] (Read 831303 bytes from disk) [18:07:54] Connecting to http://171.64.122.139:8080/ [18:08:23] Posted data. [18:08:23] Initial: 0000; - Uploaded at ~28 kB/s [18:08:23] - Averaged speed for that direction ~101 kB/s [18:08:23] + Results successfully sent [18:08:23] Thank you for your contribution to Folding@Home. [18:08:23] + Number of Units Completed: 375
[18:08:27] Trying to send all finished work units [18:08:27] + No unsent completed units remaining. [18:08:27] - Preparing to get new work unit... [18:08:27] + Attempting to get work packet [18:08:27] - Will indicate memory of 300 MB [18:08:27] - Connecting to assignment server [18:08:27] Connecting to http://assign.stanford.edu:8080/ [18:08:29] Posted data. [18:08:29] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:08:29] + News From Folding@Home: Welcome to Folding@Home [18:08:29] Loaded queue successfully. [18:08:29] Connecting to http://171.65.103.160:8080/ [18:08:29] - Couldn't send HTTP request to server [18:08:29] + Could not connect to Work Server [18:08:29] - Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry. [18:08:47] + Attempting to get work packet [18:08:47] - Will indicate memory of 300 MB [18:08:47] - Connecting to assignment server [18:08:47] Connecting to http://assign.stanford.edu:8080/ [18:08:48] Posted data. [18:08:48] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:08:48] + News From Folding@Home: Welcome to Folding@Home [18:08:48] Loaded queue successfully. [18:08:48] Connecting to http://171.65.103.160:8080/ [18:08:48] - Couldn't send HTTP request to server [18:08:48] + Could not connect to Work Server [18:08:48] - Error: Attempt #2 to get work failed, and no other work to do. Waiting before retry. [18:09:11] + Attempting to get work packet [18:09:11] - Will indicate memory of 300 MB [18:09:11] - Connecting to assignment server [18:09:11] Connecting to http://assign.stanford.edu:8080/ [18:09:12] Posted data. [18:09:12] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:09:12] + News From Folding@Home: Welcome to Folding@Home [18:09:12] Loaded queue successfully. [18:09:12] Connecting to http://171.65.103.160:8080/ [18:09:12] - Couldn't send HTTP request to server [18:09:12] + Could not connect to Work Server [18:09:12] - Error: Attempt #3 to get work failed, and no other work to do. Waiting before retry. [18:09:30] Service stop request received. [18:09:30] ***** Got a SIGTERM signal (2) [18:09:30] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [July 19 18:09:30]
# Windows Console Edition ##################################################### ###############################################################################
Launched as a service. Entered c:\Program Files\FAH to do work.
Warning: By using the -forceasm flag, you are overriding safeguards in the program. If you did not intend to do this, please restart the program without -forceasm. If work units are not completing fully (and particularly if your machine is overclocked), then please discontinue use of the flag.
[18:09:30] - Ask before connecting: No [18:09:30] - Proxy: 192.168.0.1:3128 [18:09:30] - User name: BoNi (Team 47191) [18:09:30] - User ID: 13D6D5840D707758 [18:09:30] - Machine ID: 1 [18:09:30] [18:09:30] Loaded queue successfully. [18:09:30] + Benchmarking ... [18:09:33] The benchmark result is 6632 [18:09:33] - Preparing to get new work unit... [18:09:33] + Attempting to get work packet [18:09:33] - Autosending finished units... [18:09:33] Trying to send all finished work units [18:09:33] + No unsent completed units remaining. [18:09:33] - Autosend completed [18:09:33] - Will indicate memory of 300 MB [18:09:33] - Connecting to assignment server [18:09:33] Connecting to http://assign.stanford.edu:8080/ [18:09:34] Posted data. [18:09:34] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:09:34] + News From Folding@Home: Welcome to Folding@Home [18:09:34] Loaded queue successfully. [18:09:34] Connecting to http://171.65.103.160:8080/ [18:09:34] - Couldn't send HTTP request to server [18:09:34] + Could not connect to Work Server [18:09:34] - Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry. [18:09:50] + Attempting to get work packet [18:09:50] - Will indicate memory of 300 MB [18:09:50] - Connecting to assignment server [18:09:50] Connecting to http://assign.stanford.edu:8080/ [18:09:51] Posted data. [18:09:51] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:09:51] + News From Folding@Home: Welcome to Folding@Home [18:09:51] Loaded queue successfully. [18:09:51] Connecting to http://171.65.103.160:8080/ [18:09:51] - Couldn't send HTTP request to server [18:09:51] + Could not connect to Work Server [18:09:51] - Error: Attempt #2 to get work failed, and no other work to do. Waiting before retry. [18:10:15] + Attempting to get work packet [18:10:15] - Will indicate memory of 300 MB [18:10:15] - Connecting to assignment server [18:10:15] Connecting to http://assign.stanford.edu:8080/ [18:10:16] Posted data. [18:10:16] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:10:16] + News From Folding@Home: Welcome to Folding@Home [18:10:16] Loaded queue successfully. [18:10:16] Connecting to http://171.65.103.160:8080/ [18:10:16] - Couldn't send HTTP request to server [18:10:16] + Could not connect to Work Server [18:10:16] - Error: Attempt #3 to get work failed, and no other work to do. Waiting before retry. [18:10:48] + Attempting to get work packet [18:10:48] - Will indicate memory of 300 MB [18:10:48] - Connecting to assignment server [18:10:48] Connecting to http://assign.stanford.edu:8080/ [18:10:49] Posted data. [18:10:49] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:10:49] + News From Folding@Home: Welcome to Folding@Home [18:10:49] Loaded queue successfully. [18:10:49] Connecting to http://171.65.103.160:8080/ [18:10:49] - Couldn't send HTTP request to server [18:10:49] + Could not connect to Work Server [18:10:49] - Error: Attempt #4 to get work failed, and no other work to do. Waiting before retry. [18:11:30] Service stop request received. [18:11:30] ***** Got a SIGTERM signal (2) [18:11:30] Killing all core threads
Folding@Home Client Shutdown.
--- Opening Log file [July 19 18:11:30]
# Windows Console Edition ##################################################### ###############################################################################
Launched as a service. Entered c:\Program Files\FAH to do work.
Warning: By using the -forceasm flag, you are overriding safeguards in the program. If you did not intend to do this, please restart the program without -forceasm. If work units are not completing fully (and particularly if your machine is overclocked), then please discontinue use of the flag.
[18:11:30] - Ask before connecting: No [18:11:30] - Proxy: 192.168.0.1:3128 [18:11:30] - User name: BoNi (Team 47191) [18:11:30] - User ID: 13D6D5840D707758 [18:11:30] - Machine ID: 1 [18:11:30] [18:11:31] Loaded queue successfully. [18:11:31] + Benchmarking ... [18:11:33] The benchmark result is 6632 [18:11:33] - Preparing to get new work unit... [18:11:33] + Attempting to get work packet [18:11:33] - Autosending finished units... [18:11:33] Trying to send all finished work units [18:11:33] + No unsent completed units remaining. [18:11:33] - Autosend completed [18:11:33] - Will indicate memory of 300 MB [18:11:33] - Connecting to assignment server [18:11:33] Connecting to http://assign.stanford.edu:8080/ [18:11:34] Posted data. [18:11:34] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:11:34] + News From Folding@Home: Welcome to Folding@Home [18:11:34] Loaded queue successfully. [18:11:34] Connecting to http://171.65.103.160:8080/ [18:11:34] - Couldn't send HTTP request to server [18:11:34] + Could not connect to Work Server [18:11:34] - Error: Attempt #1 to get work failed, and no other work to do. Waiting before retry. [18:11:43] + Attempting to get work packet [18:11:43] - Will indicate memory of 300 MB [18:11:43] - Connecting to assignment server [18:11:43] Connecting to http://assign.stanford.edu:8080/ [18:11:44] Posted data. [18:11:44] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:11:44] + News From Folding@Home: Welcome to Folding@Home [18:11:44] Loaded queue successfully. [18:11:44] Connecting to http://171.65.103.160:8080/ [18:11:44] - Couldn't send HTTP request to server [18:11:44] + Could not connect to Work Server [18:11:44] - Error: Attempt #2 to get work failed, and no other work to do. Waiting before retry. [18:11:58] + Attempting to get work packet [18:11:58] - Will indicate memory of 300 MB [18:11:58] - Connecting to assignment server [18:11:58] Connecting to http://assign.stanford.edu:8080/ [18:11:59] Posted data. [18:11:59] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:11:59] + News From Folding@Home: Welcome to Folding@Home [18:11:59] Loaded queue successfully. [18:11:59] Connecting to http://171.65.103.160:8080/ [18:11:59] - Couldn't send HTTP request to server [18:11:59] + Could not connect to Work Server [18:11:59] - Error: Attempt #3 to get work failed, and no other work to do. Waiting before retry. [18:12:28] + Attempting to get work packet [18:12:28] - Will indicate memory of 300 MB [18:12:28] - Connecting to assignment server [18:12:28] Connecting to http://assign.stanford.edu:8080/ [18:12:29] Posted data. [18:12:29] Initial: 41AB; - Successful: assigned to (171.65.103.160). [18:12:29] + News From Folding@Home: Welcome to Folding@Home [18:12:29] Loaded queue successfully. [18:12:29] Connecting to http://171.65.103.160:8080/ [18:12:29] - Couldn't send HTTP request to server [18:12:29] + Could not connect to Work Server [18:12:29] - Error: Attempt #4 to get work failed, and no other work to do. Waiting before retry. [18:13:19] + Attempting to get work packet [18:13:19] - Will indicate memory of 300 MB [18:13:19] - Connecting to assignment server [18:13:19] Connecting to http://assign.stanford.edu:8080/ [18:13:20] Posted data. [18:13:20] Initial: 40AB; - Successful: assigned to (171.64.122.139). [18:13:20] + News From Folding@Home: Welcome to Folding@Home [18:13:20] Loaded queue successfully. [18:13:20] Connecting to http://171.64.122.139:8080/ [18:13:22] Posted data. [18:13:22] Initial: 0000; - Receiving payload (expected size: 641618) [18:13:40] - Downloaded at ~34 kB/s [18:13:40] - Averaged speed for that direction ~57 kB/s [18:13:40] + Received work. [18:13:40] + Closed connections
Это лог получения именно того задания, что считается на скриншоте
, то все запускается, но при этом на экране я вижу лог программы. Как сделать запуск 'сервисом' что-ли. Т.е. запустил, фах начал там себе чего-то делать и при этом мне ничего не видеть.
И еще - как в кроне прописывать запуск с ключами -freeBSD -verbosity 9 -forceasm. Вроде делаю все верно, фах запускается но без ключей.
Advanced member
Статус: Не в сети Регистрация: 16.12.2002 Откуда: TSC! | Москва
B0NiQ Хехе, вот ты и попался. Ключ -advmethods эквивалентен типу 3 (-betateam - типу 4) и имеет приоритет перед типом в client.cfg, так что все твои тесты велись впустую, машина с таким ключом всегда просила задания для типа 3.
Member
Статус: Не в сети Регистрация: 01.03.2007 Откуда: Новосибирск
Hil -betateam вроде не эквивалентен типу 4.
Судя по данным с оффа, -advmethods позволяет получать любые задания в статусе public beta, -betateam - в статусе "только для бета-тестеров".
Advanced member
Статус: Не в сети Регистрация: 16.12.2002 Откуда: TSC! | Москва
RU_i_no_k Эквивалентны. Ключ -betateam вообще является скрытым, но из подпольных источников известно, что он эквивалентен типу 4, а про тип 3 вполне определённо говорит сам консольный клиент, спрашивая тебя, хочешь ли ты использовать ключ -advmethods всегда, и при согласии устанавливая тип 3 в конфиге.
Member
Статус: Не в сети Регистрация: 01.03.2007 Откуда: Новосибирск
Hil Из опыта отлова жаб скажу, что при выставлении типа 4 или -betateam приходят совершенно различные жабы (а также в комбинациях 4+betateam, 4 без betateam, и т.п), т.о. они не эквивалентны. Про тип 3 такого сказать не могу - не проверял.
Про скрытость -betateam - да, на офф сайте мод стоит, который в общих форумах его вырезает из сообщений
Advanced member
Статус: Не в сети Регистрация: 16.12.2002 Откуда: TSC! | Москва
RU_i_no_k писал(а):
т.о. они не эквивалентны
Такие заявления стоит делать, обобщив статистику по минимум 40 - 50 попыткам подряд, с хаотичным изменением данных параметров. Я не думаю, что ты проводил такие опыты, а данные 10 - 15 попыток подряд не говорят ни о чём, если судить хотя бы по моим собственным попыткам ловли тех или иных жаб БЕЗ изменения типа. Простой перезапуск иногда приводит к самым неожиданным результатам и закономерности работы назначающего сервера без смены типа понять непросто, если они вообще имеются.
Member
Статус: Не в сети Регистрация: 01.03.2007 Откуда: Новосибирск
Hil Спорить не буду, (забыл ИМХО добавить) - у тебя опыта в фолдинге больше.
НО - можно судить даже на основании того, что использование ключа -betateam всячески скрывают, а вот тип 4 в конфиге клиента встречается везде и всюду - нелогично, если они означают одно и тоже.
По-поводу сужения - я специально статистику не вел, но по-памяти могу сказать, что на -betateam приходят жабы, которые никогда не приходят на тип 4 (спорить смысла нет, т.к. статистику привести не могу - но может кто-нибудь и соберется заняться анализом).ИМХО
Advanced member
Статус: Не в сети Регистрация: 16.12.2002 Откуда: TSC! | Москва
RU_i_no_k писал(а):
тип 4 в конфиге клиента встречается везде и всюду
НЕ встречается. Это только в нашей команде. Я лично, памятуя прошлые проблемы, при цитировании FahSpy в "их" форуме всегда удаляю строку с типом, ибо были прецеденты. Официально типа 4 не существует.
Member
Статус: Не в сети Регистрация: 01.03.2007 Откуда: Новосибирск
Hil А... Посмотрел на "их" форуме - действительно. Спасибо за разъяснение, приходится согласиться. Но частично остаюсь при своем мнении, что отличия есть - в свое время когда ловил жаб и клиент тупо ломился на .160 всегда выручал перезапуск с -betateam-мом, сразу уходил на другой сервак (хотя тип стоял 4-й). Спорить смысла не вижу (по крайней мере со своей стороны подтвердить правоту нечем).
P.S. Из команды никого нет, кто бы учавствовал в официальном бета-тестировании?
При запуске начинет выдавать логи на текущую консоль, я ее закрываю и fah продолжает крутиться в фоне.
Правда я сервак уже хз сколько не перезапускал, и отрабатывает ли этот скрипт при загрузке - не знаю.
Что-то мне подсказывает, что нет
B0NiQ, чтобы не было вывода в консоль, добавь >/dev/null 2>&1 в конец строки перед &.
Типа так: ./FAH504-Linux.exe -verbosity 9 -forceasm -advmethods -freeBSD >/dev/null 2>&1 &
Member
Статус: Не в сети Регистрация: 07.03.2007 Откуда: Санкт-Петербург
Biga у меня с самого начала так и было, потом выяснилось что почему-то fah вылетал через несколько сек после старта, я перенеправление вывода на время тестирования убрал, с глюком разобрался, да так скрипт и не поправил обратно
Ох и жулики это доктора , в очередной раз зажали очки за выполненную жабу. отправил одну ~200 очковую и две ~300 очковых, а они 500 очей засчитали и довольны. Ну и ладно, пусть им кошмары снятся.
Сейчас этот форум просматривают: нет зарегистрированных пользователей и гости: 5
Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения