Changes between Initial Version and Version 3 of Ticket #74


Ignore:
Timestamp:
Oct 20, 2007, 7:35:49 PM (17 years ago)
Author:
Nicolas
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #74

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed

  • Ticket #74 – Description

    initial v3  
    66
    77If you don't edit the preferences (even though they may already be there in global_prefs.xml) it will report back that there is a change of venue but NOT trigger a change in General prefs thus not changing client_state.xml.
    8 
     8{{{
    9923/09/2006 3:45:48 AM|Einstein@Home|New host venue: home
    101023/09/2006 3:45:48 AM||General prefs: from Einstein@Home (last modified 2006-09-23 03:45:28)
    111123/09/2006 3:45:48 AM||General prefs: using separate prefs for home
    12 
    13 ^^^ Base setting, verified client state has venue of home
    14 
     12}}}
     13!^!^!^!^ Base setting, verified client state has venue of home
     14{{{
    151523/09/2006 3:47:31 AM|Einstein@Home|Sending scheduler request: Requested by user
    161623/09/2006 3:47:31 AM|Einstein@Home|(not requesting new work or reporting completed tasks)
    … …  
    191923/09/2006 3:47:36 AM||General prefs: from http://bam.boincstats.com/ (last modified 2006-09-23 03:47:19)
    202023/09/2006 3:47:36 AM||General prefs: using separate prefs for work
    21 
    22 ^^^^ Updated venue via BAM, edited preferences via BAM = correct update
    23 
     21}}}
     22!^!^!^!^ Updated venue via BAM, edited preferences via BAM = correct update
     23{{{
    242423/09/2006 3:53:12 AM|Einstein@Home|Sending scheduler request: Requested by user
    252523/09/2006 3:53:12 AM|Einstein@Home|(not requesting new work or reporting completed tasks)
    262623/09/2006 3:53:16 AM|Einstein@Home|Scheduler RPC succeeded [server version 505]
    272723/09/2006 3:53:16 AM|Einstein@Home|New host venue: home
    28 
    29 ^^^ Updated only venue via BAM = venue still showing as home in client state, ie continues to use incorrect General prefs
     28}}}
     29!^!^!^ Updated only venue via BAM = venue still showing as WORK in client state, ie continues to use incorrect General prefs
    3030
    3131I've verified that this is the case on two client PC's .. one running 5.6.4 and the other running 5.4.11.
    32 
    33 Posted by:
    34 Date: 6:28 PM 09-22-2006
    35 ^^^ Updated only venue via BAM = venue still showing as home in client state, ie continues to use incorrect General prefs
    36 
    37 SHOULD READ
    38 
    39 ^^^ Updated only venue via BAM = venue still showing as WORK in client state, ie continues to use incorrect General prefs
    4032
    4133Posted by:
    … …  
    4638Date: 5:18 AM 09-24-2006
    4739After moving my clients back to default prefs via removing host_venue from client_state, my workaround for getting the clients to accept new Venue selection isn't working.
    48 
     40{{{
    494124/09/2006 3:14:35 PM|Einstein@Home|Sending scheduler request: Requested by user
    504224/09/2006 3:14:35 PM|Einstein@Home|(not requesting new work or reporting completed tasks)
    … …  
    534524/09/2006 3:14:40 PM||General prefs: from http://bam.boincstats.com/ (last modified 2006-09-24 15:14:04)
    544624/09/2006 3:14:40 PM||General prefs: using separate prefs for work
    55 
     47}}}
    5648Even though the host venue changed to home, it's still using work preferences!
    5749
    … …  
    5951Date: 7:36 AM 11-01-2006
    6052The "New host venue" item in messages isn't actually doing anything but reporting a ficticious action for myself. This DOES NOT update client_state.xml with the new location and therefore doesn't trigger "General preferences: using separate preferences for xxxx"
    61 
     53{{{
    62542006-11-01 17:19:46 [---] General prefs: from http://bam.boincstats.com/ (last modified 2006-10-26 13:33:23)
    63552006-11-01 17:19:46 [---] Host location: global
    … …  
    85772006-11-01 17:24:16 [SETI@home] Scheduler RPC succeeded [server version 507]
    86782006-11-01 17:24:16 [SETI@home] New host venue: home
    87 
     79}}}
    8880I checked the client_state file manualy and also restarted the boinc client and confirmed that general preferences are still not being assigned correctly.
    8981
    … …  
    9890Posted by:
    9991Date: 8:54 AM 11-02-2006
     92{{{
    100932/11/2006 6:43:31 PM||Starting BOINC client version 5.7.2 for windows_intelx86
    101942/11/2006 6:43:31 PM||log flags: task, file_xfer, sched_ops, sched_op_debug 2/11/2006 6:43:31 PM||Libraries: libcurl/7.15.5 OpenSSL/0.9.8a zlib/1.2.3
    … …  
    1481412/11/2006 6:47:03 PM|Spinhenge@home|Scheduler request failed: couldn't connect to server
    1491422/11/2006 6:47:03 PM|Spinhenge@home|Deferring scheduler requests for 1 minutes and 0 seconds
    150 
     143}}}
    151144Ok .. not even fixed in 5.7.2. Started up with global preferences, updated location to HOME on BAM, checked with projects, projects report location changing to HOME yet boinc DIDN'T report "General prefs: using separate preferences for xxxx".
    152145
    … …  
    154147
    155148Restarted service with the following logs so that you will finally believe me that it's not working.
    156 
     149{{{
    1571502/11/2006 6:53:13 PM||Starting BOINC client version 5.7.2 for windows_intelx86
    1581512/11/2006 6:53:13 PM||log flags: task, file_xfer, sched_ops, sched_op_debug 2/11/2006 6:53:13 PM||Libraries: libcurl/7.15.5 OpenSSL/0.9.8a zlib/1.2.3
    … …  
    1731662/11/2006 6:53:13 PM||General prefs: no separate prefs for global; using your defaults
    1741672/11/2006 6:53:21 PM|rosetta@home|Restarting task FRA_2rio_154E_02_hom002_1_2rio_1_1a06__IGNORE_THE_REST_202_1327_88_0 using rosetta version 536
    175 
     168}}}
    176169As you can see is still set @ global even though the original logs show that venue is supposedly changing.