A_31_AGBBA_B_18_AGBBA_6h_3l_i4_blue_1.82_10.22_93.74_66.67_0.00.Loop.Res.SurMod.inQQ..REsiSemi.ciL__fold_SAVE_ALL_OUT_149002_483

128 characters for the WU name, 2 x "no reply" already and I didn't receive it either - I guess you violated a max. filename limit there.

p.s.: my BOINC path is rather short ( D:BOINCprojectsboinc.bakerlab.org_rosetta for Rosetta), so it should not be a problem typical for my installation. The BOINC database allows 254 characters so that's not the limit either. Maybe some string in the BOINC sources that transports the result name or the base path on server side is too long for such a filename - or Apache doesn't handle that.


p.p.s.: I just saw a similar error report here, the problems are probably caused by the same thing

Yep, got one of those too. Here what was in the log:

22/03/2014 09:54:13	rosetta@home	Sending scheduler request: To fetch work.
22/03/2014 09:54:13	rosetta@home	Requesting new tasks for CPU
22/03/2014 09:54:18	rosetta@home	[error] Can't parse file info in scheduler reply: file name is empty or has '..'
22/03/2014 09:54:18	rosetta@home	[error] Can't parse file info in scheduler reply: file name is empty or has '..'
22/03/2014 09:54:18	rosetta@home	Scheduler request completed: got 1 new tasks
22/03/2014 09:54:18	rosetta@home	[error] State file error: missing file A_31_AGBBA_B_11_AGBBBA_6h_3l_i4_blue_1.82_10.30_94.44_66.67_0.00_1.09.Loop.SurMod..SurREstaples.Yfull__data.zip
22/03/2014 09:54:18	rosetta@home	[error] State file error: missing input file A_31_AGBBA_B_11_AGBBBA_6h_3l_i4_blue_1.82_10.30_94.44_66.67_0.00_1.09.Loop.SurMod..SurREstaples.Yfull__data.zip
22/03/2014 09:54:18	rosetta@home	[error] Can't handle task A_31_AGBBA_B_11_AGBBBA_6h_3l_i4_blue_1.82_10.30_94.44_66.67_0.00_1.09.Loop.SurMod..SurREstaples.Yfull__fold_SAVE_ALL_OUT_148997_837 in scheduler reply
22/03/2014 09:54:18	rosetta@home	[error] State file error: missing task A_31_AGBBA_B_11_AGBBBA_6h_3l_i4_blue_1.82_10.30_94.44_66.67_0.00_1.09.Loop.SurMod..SurREstaples.Yfull__fold_SAVE_ALL_OUT_148997_837
22/03/2014 09:54:18	rosetta@home	[error] Can't handle task A_31_AGBBA_B_11_AGBBBA_6h_3l_i4_blue_1.82_10.30_94.44_66.67_0.00_1.09.Loop.SurMod..SurREstaples.Yfull__fold_SAVE_ALL_OUT_148997_837_2 in scheduler reply

Unfortunately BOINC didn't report it back as error, so it will have to time out.

---

.

Thank you for spotting this and reporting the details. I've EMailed the Project Team to ensure they address the issue.

---

Rosetta Moderator: Mod.Sense

It is not (or not only?) the name length, in Link's report can be seen that it complains about the two dots. Two consecutive dots might be seen as a security risk (but from my understanding that would only be the case next to a slash).

p.s.: Here we have it (client_types.cpp) :

        if (match_tag(buf, "</file_info>")) {
            if (!strlen(name)) return ERR_BAD_FILENAME;
            if (strstr(name, "..")) return ERR_BAD_FILENAME; <======
            if (strstr(name, "%")) return ERR_BAD_FILENAME;
            return 0;
        }

The core client doesn't like that.

A too long filename is a risk too though, especially since BOINC switched the default data directory on Windows to reside in the profile area. Drive letter + path + filename are limited to 256.

A too long filename is a risk too though, especially since BOINC switched the default data directory on Windows to reside in the profile area. Drive letter + path + filename are limited to 256.

No, filenames are limited to 255, full path to 32,767. See NTFS, chapter "Internals". The filename from my example is just 111 characters long, that's not even near the limit. So it must be the "..".

---

.