Was bedeutet diese Meldung ?

[Tomes]

Hiho Leute :)

Was bedeutet diese Meldung die ich seit einiger Zeit bei Boinc habe...

--- - 2004-12-23 19:40:34 - Couldn't write state file: -109


Grüße Tomes

[Ed]

Sieht so aus, als könne BOINC nicht in eine der .xml Dateien schreiben (z.B. client_state.xml). Vielleicht ist die betreffende Datei schreibgeschützt, dann ließe sich das Problem einfach dadurch beheben, dass man für diese Datei das Schreibrecht setzt. Aber das ist nur eine Vermutung, genaueres weiss ich auch nicht.

[Ed]

Hier (http://homepage.mac.com/pauldbuck/site-boinc/oman-app/app-msg-err.html) gibt es eine Erklärung des Fehlers, vielleicht hilft das weiter.

[SnakeKaplan]

Die vollständige Liste aller Fehlercodes sind:

Error number
Internal name
Explanation
0
SUCCESS
You might argue that success is not an error. You'd be right. Still, I've put it in this list for completeness.

-10
NAME_EXISTS
You've tried to create a new account, but somebody already exists with that user name. You should choose another.

-11
FILE_DELETE_FAILED
Your work unit was complete, the client uploaded it and tried to delete the old files, but couldn't. You've probably accidentally delete-protected the files.

-12
CANT_OPEN_DIR
The client cannot access the directory where its files should be. You have probably moved it.

-14
FTRUNCATE_FAILED
The client could no truncate the file. You've probably accidentally write-protected the files.

-15
NOTHING_TO_DO
The client has no data to work on. If you're using a dial-up connection, connect and download a new work unit. Otherwise, the server is probably down, so you'll just have to wait a while.

-16
CANT_CONNECT
The client was unable to connect to the internet. If you are using a dial-up connection, make sure the connection is established before trying to send a result. Otherwise, there may be a problem with you internet connection.

-17
CANT_CREATE_FILE
The client tried to create a file, but couldn't. You've probably accidentally write-protected the directory.

-18
WRITE_FAILED
The client tried to write some data to one of the files, but couldn't. You've probably accidentally write-protected the files.

-19
MALLOC_FAILED
The client couldn't allocate any memory for its process. Either enable virtual memory on your computer, or buy some more RAM.

-20
FD_READLN_EOF
The data file ended unexpectedly. It is probably corrupt, in which case delete the files and download new ones.

-21
DELIM_MISSING
An expected delimiter (usually LF-CR) is missing. The data files must be corrupt so delete them and download new ones.

-22
FOPEN_FAILED
The client tried to open one of the files to read some data, but couldn't. You've probably accidentally read-protected one of the files.

-23
BAD_HEADER
The header of one of the files was corrupt. Either the data was corrupted while transmitting, or you've corrupted it yourself (maybe while trying to cheat...). Delete the files and download new ones.

-24
BAD_DECODE
The work unit data is stored in base-64 encoding. One of the symbols is outside the range. The data files are corrupt, so delete them and download new ones.

-26
CANT_FIND_HOST
By far the most common error. It means the SETI servers are down. Just try again later.

-27
CANT_OPEN_SOCKET
See the ERR_SOCKS errors below.

-29
BUFFER_OVERFLOW
There is too much data waiting to be written. Just let the client continue.

-30
OUTFILE_OVERFLOW
Your work unit was so interesting there was too much data to put in the output file. Most likely caused by a faulty work unit, so download a new one.

-31
USER_ID_NOT_FOUND
The SETI@Home server didn't recognise your user ID. The user file has probably become corrupted. Go into the client menus, and tell it your e-mail address again, and it should get the correct user data.

-33
USER_NAME_NOT_FOUND
The SETI@Home server didn't recognise your user name. The user file has probably become corrupted. Go into the client menus, and tell it your e-mail address again, and it should get the correct user data.

-34
OBSOLETE_VERSION
The client has download a work unit whose header says it needs a newer version of the client. Your version is obsolete, so you should download the new one.

-35
NEW_MINOR_VERSION
A new version of the client is available, and you might like to download it.

-36
DB_ERROR
There is an error retrieving data from the science database. You can carry on, as it probably means the database is down for maintenance for a short while.

-37
NET_NOTIFYME
Similar to the ERR_SOCKS errors, see below.

-38
NET_WAIT
-39
PLATFORM_NOT_FOUND
The client has requested data specific to its platform, but the SETI@Home server does not recognise this platform. The data may have been corrupted on the way to the server, so try again. Otherwise, the client has become corrupted and you'll need to reinstall SETI@Home.

-40
NO_NEW_ACCOUNTS
The SETI@Home server was unable to create a new account for you. It's probably full. This has not occured at the time of writing.

-41
VERSION_NOT_FOUND
The client has requested data specific to its version, but the SETI@Home server does not recognise this platform. The data may have been corrupted on the way to the server, so try again. Otherwise, the client has become corrupted and you'll need to reinstall SETI@Home.

-42
THREAD_TIMEOUT
The server didn't respond within a set time limit. It may be a little busy, so try again later.

-50
GOT_HTTP_ERROR
The client connected with the SETI@Home server, but there was an error in the data transfer. Better try again.

-51
MALFORMED_HTTP_HEADER
The error was so bad, the http header was damaged. Better try again.

-52
FTELL_FAILED
Similar to the ERR_SOCKS errors, see below.

-53
ERR_SOCKS_NEED_USER_PASS
-61
CHECKSUM_MISMATCH
One of the data files is corrupt. Delete them and download new ones.

-62
MEMORY_MODIFIED
Some malicious program's trashed the memory the client was using. This really shouldn't happen, and may be a sign of a virus (or a Microsoft operating system...).

-63
PROGRAM_MODIFIED
Some vandal's modified the program - either a virus or you were hacking into it. You'd better reinstall it.

-64
PRINT_MESSAGE
The SETI@Home server wants to tell you something it can't express through the existing error message. The client will tell you what this is.

-65
ACCESS_DENIED
The client has been denied access to the SETI@Home server. This sometimes happens when it is busy, so wait a while and try again later.

-66
DUPLICATE_RESULT
You've already submitted this work unit. Either you've been most unfortunate and had the same work unit twice, the work unit was already sent but an error stopped the client from deleting the old files, or you've been trying to cheat. In the first and third cases, the problem will fix itself, in the remaining case delete the files and download new ones.

-70
CHECKSUM_FILE_NONEXISTENT
There isn't a checksum file, so the client can't tell whether the data is corrupt. Delete the files and download new ones.

-71
STATE_FILE_NONEXISTENT
The client can't find the state file. Unless you've moved it somewhere and can move it back, you're going to have to start that work unit again.

-127
TERMINATE_CLIENT
The client was told to terminate - you probably told your computer to shut down. This command is represented as an error message to insure quick termination of the client process.


-1101
ERR_SOCKS_SERVER_NOT_FOUND
These are all errors relating to communication between your computer and the internet. If one of these occurs, you are probably access the internet through a newtwork (e.g. at an office) and there are communication problems or security features making the client unable to function. A search engine will provide you with more detail on these errors.

-1102
ERR_SOCKS_SOCKET_OPEN_FAILED
-1103
ERR_SOCKS_CONNECT_FAILED
-1104
ERR_SOCKS_UNKNOWN_SOCKS_VERSION
-1105
ERR_SOCKS_BAD_USER_PASS
-1106
ERR_SOCKS_NO_COMPAT_METHOD
-1107
ERR_SOCKS_DEST_SERVER_NOT_FOUND
-1108
ERR_SOCKS_GENERAL_SERVER_FAILURE
-1109
ERR_SOCKS_RULESET_DENY
-1110
ERR_SOCKS_NETWORK_UNREACHABLE
-1111
ERR_SOCKS_HOST_UNREACHABLE
-1112
ERR_SOCKS_CONNECTION_REFUSED
-1113
ERR_SOCKS_TTL_EXPIRED
-1114
ERR_SOCKS_CMD_NOT_SUPPORTED
-1115
ERR_SOCKS_ADDR_TYPE_NOT_SUPPORTED
-1116
ERR_SOCKS_UNKNOWN_ERR
-1117
ERR_SOCKS_IPV6_NOT_SUPPORTED
-1118
ERR_SOCKS_IO_FAILURE
-1119
ERR_SOCKS_NO_IDENTD
-1120
ERR_SOCKS_TRY_VERSION_4
-1121
ERR_SOCKS_TRY_VERSION_5


Hab mal ne offizielle Liste gesehen. Wenn ich die wiederfind, poste ich nen Link