Scheduler request initialization failed: fopen() failed
12 Jul 2011 21:15:19 UTC
Topic 195859
(moderation:
This started last night when I tried to send in a finished task.
After several tries I decided to let a couple more tasks finish and try again but none will send in and so I just tried to reset the project and I am still getting....
[error] Can't create HTTP response output file sched_reply_einstein.phys.uwm.edu.xml
Scheduler request initialization failed: fopen() failed.
http://einsteinathome.org/host/3406672/tasks
(I just tried to detach/reattach to the project and it won't do that either)
Scheduler request initialization failed: fopen() failed
)
Can't create XXX response output file is a permissions problem, more likely on the BOINC Data directory. Either the account you run BOINC with (at this time) has lost permission to write to the directory, or the directory is hidden.
Detaching/reattaching isn't going to help here, as it's a local problem, not a BOINC or Einstein one.
This one is running on the
)
This one is running on the same connection as the other pc's here.
And on the same account since Jan.18th 2005
This one has almost one million credits since it started on the same account and DSL on Sept.3rd 2010
Never had this happen since I started here.
It has no problem connecting to other Boinc projects.
RE: This one is running on
)
irrelevant
That was then; this is now.
irrelevant
That was then; this is now.
Irrelevant.
The problem is not a connection problem as you can see from the advice Jord gave you regarding the origin and meaning of the error message. Investigate the permissions of the account BOINC is running on and check to see if the BOINC data directory is hidden.
If you don't know how to do that just say so and someone will help you.
BOINC FAQ Service
Official BOINC wiki
Installing BOINC on Linux
RE: Can't create XXX
)
It went back to normal and downloaded new tasks after I did a reboot.
Normally I would have done that before mentioning it here but I didn't want to reboot while a T4T alpha was finishing up.
Just started running the new version cernvm_2.3.3_vmdk.gz last night.
So this quad is back to work here too.