No close tag in scheduler reply

Alles zum Projekt yoyo@home
Everything about the project yoyo@home
Nachricht
Autor
Benutzeravatar
zombie67
Prozessor-Polier
Prozessor-Polier
Beiträge: 114
Registriert: 26.07.2007 21:58
Wohnort: Reno, NV

No close tag in scheduler reply

#1 Ungelesener Beitrag von zombie67 » 04.12.2013 15:19

I have two machines that are trying to report tasks, and are getting this:

22924 yoyo@home 12/4/2013 6:16:38 AM update requested by user
22925 yoyo@home 12/4/2013 6:16:39 AM sched RPC pending: Requested by user
22926 yoyo@home 12/4/2013 6:16:39 AM [sched_op] Starting scheduler request
22927 yoyo@home 12/4/2013 6:16:39 AM Sending scheduler request: Requested by user.
22928 yoyo@home 12/4/2013 6:16:39 AM Reporting 50 completed tasks
22929 yoyo@home 12/4/2013 6:16:39 AM Not requesting tasks: "no new tasks" requested via Manager
22930 yoyo@home 12/4/2013 6:16:39 AM [sched_op] CPU work request: 0.00 seconds; 0.00 devices
22931 yoyo@home 12/4/2013 6:16:39 AM [sched_op] NVIDIA work request: 0.00 seconds; 0.00 devices
22932 yoyo@home 12/4/2013 6:16:49 AM [error] No close tag in scheduler reply
22933 yoyo@home 12/4/2013 6:16:49 AM [sched_op] Deferring communication for 01:35:35
22934 yoyo@home 12/4/2013 6:16:49 AM [sched_op] Reason: can't parse scheduler reply
Team: SETI.USA

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

Re: No close tag in scheduler reply

#2 Ungelesener Beitrag von yoyo » 04.12.2013 22:07

Which hostID's?
yoyo
HILF mit im Rechenkraft-WiKi, dies gibts zu tun.
Wiki - FAQ - Verein - Chat

Bild Bild


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

Re: No close tag in scheduler reply

#4 Ungelesener Beitrag von yoyo » 05.12.2013 06:46

The only thing I see in the logs is, that the host tries to report a lot of results which were already reported. Things like this:

Code: Alles auswählen

2013-12-05 03:42:29.4669 [PID=13374] [CRITICAL]   [HOST#104170] [RESULT#23241956 ogr_131203182003_42_0] result already over [outcome=3 validate_state=2]: result already reported as error
2013-12-05 03:42:29.4669 [PID=13374] [normal  ]   [HOST#104170] [RESULT#23241643 ogr_131203181913_31_0] got result (DB: server_state=5 outcome=3 client_state=6 validate_state=2 delete_stat\
e=0)
HILF mit im Rechenkraft-WiKi, dies gibts zu tun.
Wiki - FAQ - Verein - Chat

Bild Bild

Ananas
WU-Schieber
WU-Schieber
Beiträge: 1184
Registriert: 27.04.2008 18:37
Wohnort: Nordlichter Köln

Re: No close tag in scheduler reply

#5 Ungelesener Beitrag von Ananas » 05.12.2013 08:44

Usually the close tag isn't missing when such an error message occurs. BOINC just doesn't find it.

The core client doesn't contain a full XML parser, it can handle only one tag per line. So if any of the tags "hides" behind a different tag, the whole XML structure will be messed up and BOINC is unable to recognize it.

Maybe you could check the sched_reply for such duplicate XML tags, it might help to narrow down the problem, things like .

Code: Alles auswählen

</project_files></scheduler_reply>
I guess it helps to just search for which should not occur in a "line-by-line XML".
vi BOINC/checkin_notes
:1,$s/bug/feature/g
:wq!

Erzaehlen sich Biologen eigentlich Klein-RNA-Witze?

Benutzeravatar
zombie67
Prozessor-Polier
Prozessor-Polier
Beiträge: 114
Registriert: 26.07.2007 21:58
Wohnort: Reno, NV

Re: No close tag in scheduler reply

#6 Ungelesener Beitrag von zombie67 » 05.12.2013 15:24

I am not sure if that suggestion was directed to yoyo or me. But I could not find any "><" in the sched_reply_www.rechenkraft.net_yoyo.xml.

Here it is, if that helps:

https://dl.dropboxusercontent.com/u/558 ... t_yoyo.xml
Team: SETI.USA

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

Re: No close tag in scheduler reply

#7 Ungelesener Beitrag von yoyo » 05.12.2013 19:15

My browser doesn't complain, that this XML is wrong.
HILF mit im Rechenkraft-WiKi, dies gibts zu tun.
Wiki - FAQ - Verein - Chat

Bild Bild

Ananas
WU-Schieber
WU-Schieber
Beiträge: 1184
Registriert: 27.04.2008 18:37
Wohnort: Nordlichter Köln

Re: No close tag in scheduler reply

#8 Ungelesener Beitrag von Ananas » 05.12.2013 23:52

yoyo hat geschrieben:My browser doesn't complain, that this XML is wrong.
A web Browser (unlike the core client) has a full XML parser builtin.

I guess this is the problem (taken from an older CC version) :

Code: Alles auswählen

int SCHEDULER_REPLY::parse(FILE* in, PROJECT* project) {
    char buf[256], msg_buf[1024], pri_buf[256];
...
    while (fgets(buf, 256, in)) {
...
        } else if (parse_str(buf, "<message", msg_buf, sizeof(msg_buf))) {
but the XML has a lot of message text :

Code: Alles auswählen

<message priority="high">Completed result ogr_131202195243_3_0 refused: result already reported as error Completed result ogr_131202195136_9_0 refused: result already reported as error Completed result ogr_131202195013_45_0 refused: result already reported as error Completed result ogr_131202195243_52_0 refused: result already reported as error Completed result ogr_131202195228_70_0 refused: result already reported as error Completed result ogr_131202195136_52_0 refused: result already reported as error Completed result ogr_131202195136_38_0 refused: result already reported as error Completed result ogr_131202195243_11_0 refused: result already reported as error Completed result ogr_131202195136_40_0 refused: result already reported as error Completed result ogr_131202195136_76_0 refused: result already reported as error Completed result ogr_131202195145_25_0 refused: result already reported as error Completed result ogr_131202195145_37_0 refused: result already reported as error Completed result ogr_131202195243_31_0 refused: result already reported as error Completed result ogr_131203011517_38_0 refused: result already reported as error Completed result ogr_131202195145_23_0 refused: result already reported as error Completed result ogr_131202195228_44_0 refused: result already reported as error Completed result ogr_131202195145_2_0 refused: result already reported as error Completed result ogr_131202195243_13_0 refused: result already reported as error Completed result ogr_131202195216_22_0 refused: result already reported as error Completed result ogr_131202195216_25_0 refused: result already reported as error Completed result ogr_131203011517_92_0 refused: result already reported as error Completed result ogr_131202195216_5_0 refused: result already reported as error Completed result ogr_131202195216_6_0 refused: result already reported as error Completed result ogr_131202195216_19_0 refused: result already reported as error Completed result ogr_131202195216_8_0 refused: result already reported as error Completed result ogr_131202195243_82_0 refused: result already reported as error Completed result ogr_131202195228_75_0 refused: result already reported as error Completed result ogr_131202195216_15_0 refused: result already reported as error Completed result ogr_131202195216_20_0 refused: result already reported as error Completed result ogr_131203011517_60_0 refused: result already reported as error Completed result ogr_131202195216_26_0 refused: result already reported as error Completed result ogr_131203011517_91_0 refused: result already reported as error Completed result ogr_131203011610_77_0 refused: result already reported as error Completed result ogr_131202135223_26_0 refused: result already reported as error Completed result ogr_131203011517_89_0 refused: result already reported as error Completed result ogr_131203011610_63_0 refused: result already reported as error Completed result ogr_131203011517_3_0 refused: result already reported as error Completed result ogr_131203011610_78_0 refused: result already reported as error Completed result ogr_131202195013_41_0 refused: result already reported as error Completed result ogr_131203011610_69_0 refused: result already reported as error Completed result ogr_131202195228_8_0 refused: result already reported as error Completed result ogr_131202195228_7_0 refused: result already reported as error Completed result ogr_131202195228_9_0 refused: result already reported as error Completed result ogr_131202195228_17_0 refused: result already reported as error Completed result ogr_131202195228_14_0 refused: result already reported as error Completed result ogr_131203011621_89_0 refused: result already reported as error Completed result ogr_131203011621_88_0 refused: result already reported as error Completed result ogr_131202195228_16_0 refused: result already reported as error Completed result ogr_131202195243_35_0 refused: result already reported as error Completed result ogr_131202195243_2_0 refused: result already reported as error Result ogr_131203011655_42_0 is no longer usable  Result ogr_131203011655_37_0 is no longer usable  Result ogr_131203011655_61_0 is no longer usable  Result ogr_131203011645_99_0 is no longer usable  Result ogr_131203011655_11_0 is no longer usable  Result ogr_131203011708_13_0 is no longer usable  Result ogr_131203011645_71_0 is no longer usable  Result ogr_131203011655_38_0 is no longer usable  Result ogr_131203011621_77_0 is no longer usable  Result ogr_131203011621_52_0 is no longer usable  Result ogr_131203011655_39_0 is no longer usable  Result ogr_131203011708_4_0 is no longer usable  Result ogr_131203011655_41_0 is no longer usable  Result ogr_131203011655_40_0 is no longer usable  Result ogr_131202195216_85_0 is no longer usable  Result ogr_131203011621_79_0 is no longer usable  Result ogr_131203011621_51_0 is no longer usable  Result ogr_131203011645_74_0 is no longer usable  Result ogr_131203011655_56_0 is no longer usable  Result ogr_131203011621_76_0 is no longer usable  Result ogr_131203011724_82_0 is no longer usable  Result ogr_131203011655_73_0 is no longer usable  Result ogr_131203011635_13_0 is no longer usable  Result ogr_131203011724_43_0 is no longer usable  Result ogr_131203011724_41_0 is no longer usable  Result ogr_131203011724_44_0 is no longer usable  Result ogr_131203011635_62_0 is no longer usable  Result ogr_131203011655_67_0 is no longer usable  Result ogr_131203011724_42_0 is no longer usable  Result ogr_131203011743_24_0 is no longer usable  Result ogr_131203011645_67_0 is no longer usable  Result ogr_131203011733_73_0 is no longer usable  Result ogr_131203011733_61_0 is no longer usable  Result ogr_131203011635_52_0 is no longer usable  Result ogr_131203011724_1_0 is no longer usable  Result ogr_131203011733_97_0 is no longer usable  Result ogr_131203011733_91_0 is no longer usable  Result ogr_131202195243_61_0 is no longer usable  Result ogr_131203011517_94_0 is no longer usable  Result ogr_131203011733_62_0 is no longer usable  Result ogr_131203011645_69_0 is no longer usable  Result ogr_131203011733_65_0 is no longer usable  Result ogr_131203011743_65_0 is no longer usable  Result ogr_131203011743_66_0 is no longer usable  Result ogr_131203011621_47_0 is no longer usable  Result ogr_131203011733_63_0 is no longer usable  Result ogr_131203011733_100_0 is no longer usable  Result ogr_131203011733_64_0 is no longer usable  Result ogr_131203011655_5_0 is no longer usable  Result ogr_131203011724_6_0 is no longer usable  </message>
more than 6500 characters in a single line, not containing any linefeed - much longer than the size of the buffers involved in the parse method. My guess would be that the core client chokes on this one.

@zombie67 : If you don't want to hand-edit client_state.xml and remove those results, do a project reset. I guess that's the only other chance to get rid of that message. The results have been reported anyway so not too much should get lost.

Benutzeravatar
zombie67
Prozessor-Polier
Prozessor-Polier
Beiträge: 114
Registriert: 26.07.2007 21:58
Wohnort: Reno, NV

Re: No close tag in scheduler reply

#9 Ungelesener Beitrag von zombie67 » 06.12.2013 02:14

Thanks for the info! I'll reset the project.
Team: SETI.USA

Antworten

Zurück zu „Number crunching“