[EnVoy]

I'm getting this readout:

[10:53:56] Finished a frame (321)
[11:31:51] Finished a frame (322)
[11:33:39] - Autosending finished units...
[11:33:39] Trying to send all finished work units
[11:33:39] + Sent 0 completed units to the server
[11:33:39] - Autosend completed
[12:06:28] Finished a frame (323)
[12:38:44] Finished a frame (324)


Is this normal, or do I have a problem?

Another question, is the time intervals it's taking to complete frames normal? This is from a P3 600mhz running Linux. My OSX dual 1.25ghz (running CLI & GUI instances) seems to take about the same time.

[Welnic]

That just means that the last work unit that you did has not been successfully uploaded yet. It will keep trying until it manages to get it done. If this is a system that has sent units in the past I would not worry about it. If it is a new setup then there may be something about your internet connection that keeps it from being able to upload.

In order to tell anything about the times to do a frame you have to know what protein it is. Different proteins have different times that they should take.

[Shaktai]

What Welnic said.

As you can see, the machine was still processing its current protein, but the previous protein had not been sent, so it was trying to re-send it. Server .110 was down for a time.

This page http://folding.stanford.edu/psummary.html will give you information about the Proteins, how many points they are, deadlines, type, and what server they come from.

This page http://folding.stanford.edu/serverstat.html will give you actual server status information which is helpful in knowing if there is a server problem. F@H has multiple servers that give out different Proteins.

If you know the protein that you last worked on, you can find out what server it comes from and see if that server is up or down. You can also check on or report server problems at http://forum.folding-community.org/viewforum.php?f=11

[reader50]

I don't know about other people's experience, but my system is always logging that upload attempt to send 0 units, every 6 hours. There are no completed units in queue ... when a unit is done, it goes up.

It looks like a regular upload cycle, which should have been coded slightly differently. ie - if no completed units are in queue, skip logging for the check. Or revise the logged text to indicate it was only a regular check, which found nothing to upload.

[Welnic]

Originally posted by reader50:
I don't know about other people's experience, but my system is always logging that upload attempt to send 0 units, every 6 hours. There are no completed units in queue ... when a unit is done, it goes up.

It looks like a regular upload cycle, which should have been coded slightly differently. ie - if no completed units are in queue, skip logging for the check. Or revise the logged text to indicate it was only a regular check, which found nothing to upload.

I haven't seen that. I just looked at my logs for both my linux and OSX boxen and there is no periodic upload attempts. I have seen it though where it didn't successfully upload at first and it did later at some point in the middle of the next work unit.

[reader50]

Are you set to verbosity 9?

I do get it when there is a completed unit in queue. It presently gets it uploaded on the next try. But I get that message every 6 hours the rest of the time too.

OSX CLI v3.25 set to verbosity 9

[EnVoy]

Yeah, the verbosity is at 9.

I haven't seen this before, but I guess I'll keep an eye on it and see if it keeps doing it.