[error] No close tag in scheduler reply

Fehler und Wünsche zum Projekt yoyo@home
Bugs and wishes for the project yoyo@home
Nachricht
Autor
jondi_hanluc
Taschenrechner
Taschenrechner
Beiträge: 7
Registriert: 29.09.2013 09:00

[error] No close tag in scheduler reply

#1 Ungelesener Beitrag von jondi_hanluc » 14.05.2017 18:20

Hello,

I have two machines, each with around 300 completed ECM tasks on them that I cant report. They have uploaded to the server but when it comes to reporting them I get this error message in the title. They were working fine yesterday.

I added debug to the cc_config and below is the result.

Computer ID: 372313 (also Computer ID 373693 gives the same error)
14/05/2017 18:10:58 | yoyo@home | [sched_op] Starting scheduler request
14/05/2017 18:10:58 | yoyo@home | Sending scheduler request: To report completed tasks.
14/05/2017 18:10:58 | yoyo@home | Reporting 359 completed tasks
14/05/2017 18:10:58 | yoyo@home | Not requesting tasks: some task is suspended via Manager
14/05/2017 18:10:58 | yoyo@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
14/05/2017 18:10:58 | yoyo@home | [sched_op] AMD/ATI GPU work request: 0.00 seconds; 0.00 devices
14/05/2017 18:10:58 | yoyo@home | [http] HTTP_OP::init_post(): http://www.rechenkraft.net/yoyo_cgi/cgi
14/05/2017 18:10:58 | yoyo@home | [http] HTTP_OP::libcurl_exec(): ca-bundle set
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Info: Connection 44 seems to be dead!
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Info: Closing connection 44
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Info: Trying 78.47.191.249...
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Info: Connected to http://www.rechenkraft.net (78.47.191.249) port 80 (#45)
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: POST /yoyo_cgi/cgi HTTP/1.1
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Host: http://www.rechenkraft.net
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: User-Agent: BOINC client (windows_x86_64 7.6.22)
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Accept: */*
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Accept-Language: en_GB
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Content-Length: 621972
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server: Expect: 100-continue
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Sent header to server:
14/05/2017 18:10:59 | yoyo@home | [http] [ID#1] Received header from server: HTTP/1.1 100 Continue
14/05/2017 18:11:01 | yoyo@home | [http] [ID#1] Info: We are completely uploaded and fine
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: HTTP/1.1 200 OK
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: Date: Sun, 14 May 2017 17:10:59 GMT
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.4.16
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: Content-Type: text/xml
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: Vary: Accept-Encoding
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: Content-Encoding: gzip
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server: Transfer-Encoding: chunked
14/05/2017 18:11:45 | yoyo@home | [http] [ID#1] Received header from server:
14/05/2017 18:11:46 | yoyo@home | [http] [ID#1] Info: Connection #45 to host http://www.rechenkraft.net left intact
14/05/2017 18:11:46 | yoyo@home | [error] No close tag in scheduler reply
14/05/2017 18:11:46 | yoyo@home | [sched_op] Deferring communication for 00:07:57
14/05/2017 18:11:46 | yoyo@home | [sched_op] Reason: can't parse scheduler reply

Benutzeravatar
yoyo
Vereinsvorstand
Vereinsvorstand
Beiträge: 7971
Registriert: 17.12.2002 14:09
Wohnort: Berlin
Kontaktdaten:

Re: [error] No close tag in scheduler reply

#2 Ungelesener Beitrag von yoyo » 14.05.2017 22:51

Maybe you are reporting too much tasks.
There is somehow an option to limit the amount of tasks which should be reported.
HILF mit im Rechenkraft-WiKi, dies gibts zu tun.
Wiki - FAQ - Verein - Chat

Bild Bild

jondi_hanluc
Taschenrechner
Taschenrechner
Beiträge: 7
Registriert: 29.09.2013 09:00

Re: [error] No close tag in scheduler reply

#3 Ungelesener Beitrag von jondi_hanluc » 15.05.2017 00:28

I don't know how that is possible, I did try pausing all work units except 1 but it tried to report them all. That machine tried to report 359 tasks, the other tried to report 216 which has the same problem. There must have been much larger uploads than that at the start of the pentathlon that went through fine.

I'm stuck in limbo at the moment, I am reluctant to continue crunching my existing work units in case they never upload and I can't run another boinc instance in the meantime as your project doesn't allow it.

I'm crunching in the pentathlon, yoyo@home challenge finishes in 24 hours and I'm stuck with 575 work units and I can't crunch any more of them in case it's pointless, very frustrating.

jondi_hanluc
Taschenrechner
Taschenrechner
Beiträge: 7
Registriert: 29.09.2013 09:00

Re: [error] No close tag in scheduler reply

#4 Ungelesener Beitrag von jondi_hanluc » 15.05.2017 00:39

I see now how to limit the amount of reported tasks via cc_config. I set it at 10, then 1 and the problem continues.

Benutzeravatar
yoyo
Vereinsvorstand
Vereinsvorstand
Beiträge: 7971
Registriert: 17.12.2002 14:09
Wohnort: Berlin
Kontaktdaten:

Re: [error] No close tag in scheduler reply

#5 Ungelesener Beitrag von yoyo » 15.05.2017 11:03

It seems to be the same issue as analysed here: viewtopic.php?f=57&t=13342

Please send me the hostID and the wrong sched reply.

If it is the same as in mentioned topic, then the results were already reported and the anser from the server is too long for your Boinc client so the Boinc client doesn't find the close tag.
HILF mit im Rechenkraft-WiKi, dies gibts zu tun.
Wiki - FAQ - Verein - Chat

Bild Bild

jondi_hanluc
Taschenrechner
Taschenrechner
Beiträge: 7
Registriert: 29.09.2013 09:00

Re: [error] No close tag in scheduler reply

#6 Ungelesener Beitrag von jondi_hanluc » 15.05.2017 12:54

These are the two machines effected

http://www.rechenkraft.net/yoyo/show_ho ... tid=372313
http://www.rechenkraft.net/yoyo/show_ho ... tid=373693

Thanks

When you say: 'wrong sched reply' - do you want me to email you the sched_reply_www.rechenkraft.net_yoyo.xml file?

jondi_hanluc
Taschenrechner
Taschenrechner
Beiträge: 7
Registriert: 29.09.2013 09:00

Re: [error] No close tag in scheduler reply

#7 Ungelesener Beitrag von jondi_hanluc » 15.05.2017 16:04

Machine 372313 has reported, with 2 work unit listed as errors, HOWEVER! the seem to have dissappeared into cyberspace, no credit has been awarded for them and non of them are listed as pending :worry:

The other rig still won't upload.
15/05/2017 15:49:41 | | cc_config.xml not found - using defaults
15/05/2017 15:49:41 | | Starting BOINC client version 7.6.22 for windows_x86_64
15/05/2017 15:49:41 | | log flags: file_xfer, sched_ops, task
15/05/2017 15:49:41 | | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
15/05/2017 15:49:41 | | Data directory: C:\ProgramData\BOINC
15/05/2017 15:49:41 | | Running under account main
15/05/2017 15:49:42 | | OpenCL: AMD/ATI GPU 0: Hawaii (driver version 2117.14 (VM), device version OpenCL 2.0 AMD-APP (2117.14), 4096MB, 4096MB available, 3200 GFLOPS peak)
15/05/2017 15:49:42 | | OpenCL: AMD/ATI GPU 1: Hawaii (driver version 2117.14 (VM), device version OpenCL 2.0 AMD-APP (2117.14), 4096MB, 4096MB available, 3200 GFLOPS peak)
15/05/2017 15:49:42 | | OpenCL CPU: Intel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 2117.14 (sse2,avx), device version OpenCL 1.2 AMD-APP (2117.14))
15/05/2017 15:49:43 | | Host name: DESKTOP-66RLLHL
15/05/2017 15:49:43 | | Processor: 72 GenuineIntel Intel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz [Family 6 Model 63 Stepping 2]
15/05/2017 15:49:43 | | 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 htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx smx tm2 dca pbe fsgsbase bmi1 smep bmi2
15/05/2017 15:49:43 | | OS: Microsoft Windows 10: Professional x64 Edition, (10.00.14393.00)
15/05/2017 15:49:43 | | Memory: 63.89 GB physical, 68.63 GB virtual
15/05/2017 15:49:43 | | Disk: 118.75 GB total, 4.77 GB free
15/05/2017 15:49:43 | | Local time is UTC +1 hours
15/05/2017 15:49:43 | | VirtualBox version: 5.1.22
15/05/2017 15:49:43 | Cosmology@Home | Found app_config.xml
15/05/2017 15:49:43 | Cosmology@Home | URL http://www.cosmologyathome.org/; Computer ID 309799; resource share 100
15/05/2017 15:49:43 | Moo! Wrapper | URL http://moowrap.net/; Computer ID 832374; resource share 100
15/05/2017 15:49:43 | yoyo@home | URL http://www.rechenkraft.net/yoyo/; Computer ID 372313; resource share 100
15/05/2017 15:49:43 | yoyo@home | General prefs: from yoyo@home (last modified 13-May-2017 17:49:57)
15/05/2017 15:49:43 | yoyo@home | Host location: none
15/05/2017 15:49:43 | yoyo@home | General prefs: using your defaults
15/05/2017 15:49:43 | | Reading preferences override file
15/05/2017 15:49:43 | | Preferences:
15/05/2017 15:49:43 | | max memory usage when active: 58878.48MB
15/05/2017 15:49:43 | | max memory usage when idle: 58878.48MB
15/05/2017 15:49:43 | | max disk usage: 5.29GB
15/05/2017 15:49:43 | | max CPUs used: 70
15/05/2017 15:49:43 | | don't use GPU while active
15/05/2017 15:49:43 | | (to change preferences, visit a project web site or select Preferences in the Manager)
15/05/2017 15:49:49 | yoyo@home | work fetch suspended by user
15/05/2017 15:49:56 | yoyo@home | update requested by user
15/05/2017 15:49:59 | yoyo@home | Sending scheduler request: Requested by user.
15/05/2017 15:49:59 | yoyo@home | Reporting 379 completed tasks
15/05/2017 15:49:59 | yoyo@home | Not requesting tasks: suspended via Manager
15/05/2017 15:50:07 | yoyo@home | Scheduler request completed
15/05/2017 15:50:07 | yoyo@home | Completed result ecm_cw_1494693686_GW_8_676A_2385_0 refused: result already reported as error Completed result ecm_cw_1494693686_GW_8_676A_2440_0 refused: result already reported as error

ozaudio
Fingerzähler
Fingerzähler
Beiträge: 1
Registriert: 15.05.2017 15:54

Re: [error] No close tag in scheduler reply

#8 Ungelesener Beitrag von ozaudio » 15.05.2017 16:04

hi.

can you please check my ID aswell?

http://www.rechenkraft.net/yoyo/show_ho ... tid=372331
im getting the same , no close tags


Benutzeravatar
yoyo
Vereinsvorstand
Vereinsvorstand
Beiträge: 7971
Registriert: 17.12.2002 14:09
Wohnort: Berlin
Kontaktdaten:

Re: [error] No close tag in scheduler reply

#10 Ungelesener Beitrag von yoyo » 15.05.2017 19:47

Please read the link I posted above.
"no close tag in scheduler reply" is a problem of the boinc client, nothing what I can solve on the server.
The server just replies that some workunits which you try to report are already reported.
This answer is too long. Boinc client has just a limited buffer for it. So it misses the end tag.

The only thing you can do is to reset the project.
Or in your own risk, I do not know the side effects,
- Shutdown boinc,
- read the sched_reply you got
- remove the mentioned results from your client_state.xml

Don't know if this works.

yoyo
HILF mit im Rechenkraft-WiKi, dies gibts zu tun.
Wiki - FAQ - Verein - Chat

Bild Bild

Antworten

Zurück zu „Fehler, Wünsche / Bugs, Wishes“