I ran two tasks. Both timed out.

http://burp.renderfarming.net/result.php?resultid=7324830 after 2,255,494 seconds of CPU time (27 days)
http://burp.renderfarming.net/result.php?resultid=7322112 after 2,048,968 seconds of CPU time (24 days)

---

Reno, NV
Team: SETI.USA

Woah!

Very unfortunate - especially the first one which was almost done.
It seems we're getting extremely close to a hardcoded limit of 800 hours runtime on the reference BURP machine. At that point the client will abort the workunit.

I'll have to look into this a bit further to figure out if there is any way to change the limit on the fly with the current codebase.

Best option is to avoid session 1569 on that host for now.

Yeah, two different hosts, if it makes a difference. The first is 4 threads, the other is two threads. Both are VMs on i7 machines.

---

Reno, NV
Team: SETI.USA

Were they hibernated during this?

Were they hibernated during this?

Nope. Since they don't checkpoint, I don't shut down the VMs if BURP is running.

---

Reno, NV
Team: SETI.USA

Hi, on the main page stopped displaying the table Element Value Timestamp Event Log and Comments. Instead, there is an error message

Fatal error: Uncaught [[o:Exception]:"java.lang.Exception: Invoke failed: [[c:SessionStatisticsHandler]]->getCPUTimeRendered((o:Session)[o:Session]). Cause: com.mysql.jdbc.exceptions.jdbc4.MySQLDataException: '2.353767585E9' in column '1' is outside valid range for the datatype INTEGER. VM: 1.7.0_05@http://java.oracle.com/" at: #-40 sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) #-39 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) #-38 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) #-37 java.lang.reflect.Constructor.newInstance(Constructor.java:525) #-36 com.mysql.jdbc.Util.handleNewInstance(Util.java:406) #-35 com.mysql.jdbc.Util.getInstance(Util.java:381) #-34 com.mysql.jdbc.SQLError.createSQLException(SQLError.java:999) #-33 com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) #-32 com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) #-31 com.mysql.jdbc.ResultSetImpl.throwRangeExce in /mnt/hosting/www/burp_production/libraries/php-java-bridge/Java.inc on line 196

Thanks for the bug-report - it turns out that this session has been running for so long that the counter that is supposed to count how long it was running can no longer be shown.

Do these work units really take over a month to complete?
I spent over 4 hours downloading the work files before I found out how long they would run for.
Once I found out, I soon aborted it.
I can't keep my computer running for that long without turning it off.

---

The biggest threat to public safety and security is not terrorism, it is Government abuse of authority.

Bitcoin Donations: 1Le52kWoLz42fjfappoBmyg73oyvejKBR3

Hi All,

Has the server run out of work to distribute for this session?

I have been experimenting running BURP on a VirtualBox Ubuntu installation both as an exercise in supporting Ubuntu in a virtual environment and as a contribution to the final long workunits of Sunflower.

After successfully providing multi processor support and enough disk space I received the message "Sunflower Blender is not available for Linux running on an
AMD x86_64 or Intel EM64T CPU.

The computer details are: http://burp.renderfarming.net/show_host_detail.php?hostid=60720

Is there something I may have missed or is it simply a matter of limited work distribution at this time?

regards,
LumenDan

Yes, all work has been distributed for this session. Only workunit instances that fail on some host will be re-sent to another host. In other words the chance of getting another WU is pretty low. Since this is the last Sunflower session for linux I have just increased the number of machines working on it by 1/wu so if you are really lucky you will get one last WU for it.

You can follow the progress for each individual workunit and host here:
http://burp.renderfarming.net/session_workunits.php?id=1569&completed=true

You can also check the "BOINC" tab of the Serverstatus page; it will tell you how many WUs are available for each of the rendering engines.

---

Click here to see My Detailed BOINC Stats

Umm... how long has it been at 99.4%?