1. I get this when I log onto my account:

Warning: mysqli_query(): (HY000/3): Error writing file '/tmp/MYLsfLDA' (Errcode: 28 - No space left on device) in /home/boincadm/projects/collatz/html/inc/db.inc on line 57

Warning: mysqli_fetch_object() expects parameter 1 to be mysqli_result, boolean given in /home/boincadm/projects/collatz/html/inc/db.inc on line 67

Warning: mysqli_free_result() expects parameter 1 to be mysqli_result, boolean given in /home/boincadm/projects/collatz/html/inc/db.inc on line 76

2. Collatz is generating work units which frequently bounce computation errors -- they do this in seconds and there are a LOT of these -- I've seen this on different workstations, reboots, remove Collatz and reattach, change BOINC versions - seems to help *on some* workstations and not on others.

3) Upload reporting has become problematic. It is possible that the LARGE number of computation error work units are a factor here as it clearly loads the server when instantaneous bad results get reports. It might also strain the heck out of the work generator.

Anyway, I figured to share all three of these in one new thread to see what we can kick up.

On those workstations which for whatever reason can't be 'healed' of the computation error attack, I've shifted over to GPUGrid -- which works fine.

According to the server status page, those processes which might be cleaning up the WUs and removing them (freeing up space) are all kaput right now. With the bogus WUs that error right away, it would follow that the server is probably running out of space.

Let's all welcome Jon when he gets back :)

---

Don't bother trying to solve the problem by downloading and installing an updated version of BOINC - boinc.berkeley.edu is down, probably until Monday at the earliest:

setiathome.berkeley.edu/forum_thread.php?id=84081&postid=1999220

---

I was up in Wisconsin for a wedding this past weekend and was told to not bring any electronic devices (other than cameras). So, while you were having troubles with Collatz, my King of Avalon shields ended during a kill event and I lost all my troops which will now take months to heal and/or create new. So, at least we all had a bad weekend (even worse if you include the post wedding hangover, LOL)

Anyway.... the file_upload_handler daemon was set to log the maximum info in order to try and track possible missing file (corrupt file?) issues and mismatched database vs. file system. Unfortunately, the volunteers process so many WUs that it filled the drive. I reset the daemon to the minimum log settings, cleared the log files, and restarted all the daemons. Let me know if you still have trouble uploading work. It appears to have fixed the issue but I hate to jump to conclusions.

Welcome back, Jon, and thanks for taking care of the file_upload_handler daemon and providing us with an update. I am no longer having any trouble uploading work.

---

I don't have upload problem either. Although that may not be to surprising considering 99% of work now ends in computation error .