Czech Dutch English French German Spanish
Home | Search | About | Forum | Login

BOINC

FAQ Service (English)

 

00. Process exit codes 192 - 204

FAQ: 00. Process exit codes 192 - 204
Title: 00. Process exit codes 192 - 204
Author: Jorden
Views: 67277
Category: 06. BOINC Client Common Errors
Available in: Spanish English
Created: 18/06/2008 16:40:23
Last Modified: 11/07/2012 10:41:18

Contents:

Yes, positive error codes, to make things interesting. :-)

The following are process exit codes (not function return values). They are used by the client and applications.
NOTE: Unix passes only 8 bits of exit code, and Unix uses roughly 1-137, so BOINC errors start at 192.


EXIT_STATEFILE_WRITE 192

The client will exit if it cannot write to the client_state.xml file.
Make sure you have permission to write to the BOINC Data directory.

EXIT_SIGNAL 193

The client, Manager and/or application will exit when getting the exit signal.

EXIT_ABORTED_BY_CLIENT 194

Task was aborted by the BOINC client.

EXIT_CHILD_FAILED 195

The science application running the task failed for unknown reasons.

EXIT_DISK_LIMIT_EXCEEDED 196

The amount of disk space that the task could use was more than the limit set to the task.

EXIT_TIME_LIMIT_EXCEEDED 197

The amount of time that the task can run was estimated to be far greater than then time limit set to the task.

EXIT_MEM_LIMIT_EXCEEDED 198

The amount of memory that the task could use was greater than the limit set to the task.

EXIT_CLIENT_EXITING 199

The task was ended when the client was exited.

EXIT_UNSTARTED_LATE 200

Task was aborted due to it having not started and already past the deadline.

EXIT_MISSING_COPROC 201

A coprocessor that was detected earlier went missing. Work for it is being aborted.

EXIT_ABORTED_BY_PROJECT 202

Tasks on the computer were aborted by the project.

EXIT_ABORTED_VIA_GUI 203

Applications exit with this code after you told them to abort.

EXIT_UNKNOWN 204

Unknown exit.
 

01. Error code -100 to -110 explained.

FAQ: 01. Error code -100 to -110 explained.
Title: 01. Error code -100 to -110 explained.
Author: Jorden
Views: 77504
Category: 06. BOINC Client Common Errors
Available in: Spanish German English
Created: 14/02/2008 23:20:15
Last Modified: 27/12/2010 17:21:53

Contents:

BOINC_SUCCESS 0

Not an error, but a good thing. Success. Everything is working as it should. Rejoice.

ERR_SELECT -100

This error code is no longer used in any of the present versions of BOINC.

ERR_MALLOC -101

There is a problem with the memory allocation. If insufficient memory is found to store BOINC and the project's science application plus work unit in, you'll get an error -101.

Solution: Free up memory or add more memory to your computer.
See RAM Requirements for how much RAM you need free.

ERR_READ -102

BOINC has a problem reading from the drive. Maybe you do not have rights to read from the BOINC directory.

Solution: Make sure you have rights in your operating system to read from the drive.
Check your drive for consistency, in Windows using chkdsk.

ERR_WRITE -103

BOINC has a problem writing to the disk. Maybe you do not have rights to write to the BOINC directory.

Solution: Make sure you have rights in your operating system to write to the drive.
Check your drive for consistency, in Windows using chkdsk.

ERR_FREAD -104

BOINC can't read the memory. The memory segment BOINC is trying to read from may be in use by another application.

Solution: Exit BOINC completely and restart it.


ERR_FWRITE -105

BOINC can't write to memory. The memory segment BOINC is trying to write to may be in use by another application.

Solution: Exit BOINC completely and restart it.


ERR_IO -106

1. BOINC failed to read from or write to the disk drive. You may have problems with your hard drive.

Solution: Check your disk drive with drive tools or chkdsk.

2. BOINC failed to send or receive data through the network. The project servers may be down, a router between you and the project servers may be down.

Solution: Let BOINC retry to upload/download work by itself. No need to hamper with it.

ERR_CONNECT -107

BOINC couldn't connect to:
1. a project's server.
2. an account manager's server.
3. Boinc Manager cannot connect to BOINC. (Yes, a localhost error is also an error -107)

ERR_FOPEN -108

1. BOINC has a problem opening or writing one or more files. One of the ways to get this error is by hiding the BOINC / BOINC Data directory and its sub-directories. Then BOINC can't find where it is running from.

Solution: Do not hide your BOINC / BOINC Data directory.

2. BOINC finds that the file is open and in use by another process, or BOINC cannot write to the file.

Solution: Exit BOINC completely and restart it.

3. It may happen, that when an application hangs while opening/writing to a file and then terminates abnormally (e.g. via Task Manager or even BOINC), this (formerly opened) file may stay locked even if the application is terminated (due to file locks are handled by the OS - e.g. file locks on network shares are handled by the OS for the network PC/Server - the OS needs a definite "remove this lock!" from the calling application to remove it).

Solution: Restart your computer.

4. You installed BOINC as an administrator but run it as another user and didn't give that user rights to write to the BOINC or BOINC Data directory and sub-directories. The directories their read-only attributes are set.

Solution: Either run BOINC as administrator, or give the user you want to run under rights to write to the BOINC /BOINC Data directory and subdirectories.

ERR_RENAME -109

1. BOINC has a problem renaming files. One such file that gets renamed is the client_state.xml file. If for some reason it's set to Read-Only, you will get this error.

Solution: Don't make any files Read-Only.

2. See Error 3 and its solution at ERR_FOPEN above.

ERR_UNLINK -110

This is (probably) a problem removing a file. In Unix you "unlink" the file because there could be several links (names) for the same file. When all links are gone the file is actually removed.
 

02. Error code -111 to -120 explained.

FAQ: 02. Error code -111 to -120 explained.
Title: 02. Error code -111 to -120 explained.
Author: Jorden
Views: 75288
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:20:21
Last Modified: 14/02/2008 23:20:21

Contents:

ERR_OPENDIR -111

BOINC is unable to read the directory path.

ERR_XML_PARSE -112

BOINC found an unexpected XML tag or XML format in one of its XML files.
Possible files at error: cc_config.xml, client_state.xml, global_prefs_override.xml

Solution: Check your XML files for a broken XML tag.

ERR_GETHOSTBYNAME -113

BOINC couldn't resolve your computer's host name or IP address. Your firewall may be blocking communications on port 80, or you are behind a proxy server.

Solution: Make sure your firewall allows BOINC through on port 80. If using a proxy server, set it up in BOINC. If you are using your computer at work, ask your boss or IT department for permission to use BOINC.

ERR_GIVEUP_DOWNLOAD -114

BOINC cannot download from the project's server. It is giving up on trying to download again and deferring for x-minutes. If the server went down for some reason, an error 404 will give this same reaction.

Solution: Wait until the project is back up. Check your internet connection. Are you allowing BOINC through the firewall/proxy?

ERR_GIVEUP_UPLOAD -115

BOINC cannot upload to the project's server. It is giving up on trying to upload again and deferring for x-minutes. If the server went down for some reason, an error 404 will give this same reaction.

Solution: Wait until the project is back up. Check your internet connection. Are you allowing BOINC through the firewall/prox

ERR_NULL -116

This error is generated in general, when a reference to a certain URL, project or result's name is invalid. In detail that is:

- The project as stated in the state file can't be found.
- The result as stated in the state file can't be found.
- The requested version of a science application for a certain task can't be found.
- Missing or incorrect project URL.
- On Date/Time conversion (date/time informations are passed as a long float number), a given time value passed to the date/time converter is negative or the output buffer was not initialized correctly.
- The science app respectively it's corresponding file containing a soft link to the executable file can't be found.

This error may also be issued if a trickle (used by some projects) can't be generated due to a missing/wrong project/result name.

ERR_NEG -117

This error is generated when the requested slot number (the working directory for a result) is negative.

ERR_BUFFER_OVERFLOW -118

This error is generated, if e.g. the length of the path-/file name for a given file exceeds 1023 Bytes. May not happen on Windows systems, since AFAIK the maximum path-/file name allowed under Windows is 260 bytes.

ERR_MD5_FAILED -119

BOINC couldn't find a signature on the file it downloaded.

Solution: Complain about it on the project's forums. It may be their error.
Also try to reset your project. It could be that your public key got corrupted. A project reset fixes that.

ERR_RSA_FAILED -120

BOINC couldn't check the encryption key on a file it downloaded. Does the file have a signature?

Solution: Complain about it on the project's forums. BOINC will try to download the file again.
Also try to reset the project. It may be that your public key is corrupt. A project reset should fix that.
 

03. Error code -121 to -130 explained.

FAQ: 03. Error code -121 to -130 explained.
Title: 03. Error code -121 to -130 explained.
Author: Jorden
Views: 75581
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:20:28
Last Modified: 27/06/2011 23:57:30

Contents:

ERR_OPEN -121

This is old code that is no longer used by any of the present version of BOINC.

ERR_DUP2 -122

This is old code that is no longer used by any of the present version of BOINC.

ERR_NO_SIGNATURE -123

There is no signature on the file that BOINC downloaded. This file could now come from anywhere.

Solution: Complain about it on the project's forums. They should fix this.

ERR_THREAD -124

The BOINC Windows Runtime debugger wasn't enabled or can't be started. Corresponding message: "BOINC Windows Runtime Debugger has been disabled"

ERR_SIGNAL_CATCH -125

A Signal was caught from the OS. This is, the operating system is posting an error condition and the science application is/was terminated. See the messages tab/Event Log for further informations

UNIX/Linux/MAC related

ERR_UPLOAD_TRANSIENT -127

First an explanation what transient means. Transient refers to a module that, once loaded into main memory, is expected to remain in memory for a short time.

This is a server error.
The file you are trying to upload is locked on the server. The file_upload_handler put an advisory lock on the file, to prevent other file upload handlers to write to the file.

This can only be fixed by the project.

Extra messages in 5.8 branch of BOINC.
can't open file - Advisory file locking is not guaranteed reliable when used with stream buffered IO.
can't lock file - File Upload Handler can't put an advisory lock on the file to prevent it being overwritten by other FUHs.
Maintenance underway: file uploads are temporarily disabled. - You can't upload as the server is down for maintenance.

ERR_UPLOAD_PERMANENT -128

This is a permanent upload failure. This can happen when the result you are trying to return has been deleted on the server (return it too late, after it's been validated and purged from the server), or when the server is rejecting the result (server full).

ERR_IDLE_PERIOD -129

BOINC is trying to download an application but finds that it may exist already on your computer. Did you detach from the project and were not all files deleted automatically?

ERR_ALREADY_ATTACHED -130

You are trying to attach to a project you are already attached to. You cannot attach to the same project twice.
 

04. Error code -131 to -140 explained

FAQ: 04. Error code -131 to -140 explained
Title: 04. Error code -131 to -140 explained
Author: Jorden
Views: 73698
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:18:28
Last Modified: 14/02/2008 23:18:28

Contents:

ERR_FILE_TOO_BIG -131

One of the output files is bigger than the maximum set by the project for upload.
BOINC will not try to upload this file.

Solution: Go to the project's forums and report this behavior.

ERR_GETRUSAGE -132

On non-Windows systems only:

BOINC wasn't able to get the running time for a given process.

ERR_BENCHMARK_FAILED -133

BOINC couldn't start its benchmark. The CPU may be taken up by another application.

Solution: make sure nothing else but for BOINC runs when doing the benchmarking. Re-benchmark when your computer is fully idle. (Boinc Manager, Advanced, Retry benchmarks)

ERR_BAD_HEX_FORMAT -134

The data in the source file contains a non-hexadecimal character. Hexadecimal 'numbers' run from 0 to 9 and a to f. Any other character will trigger this error.

Solution: Report this behavior on the project's forums.

ERR_USER_REJECTED -135
    // user rejected executable file

Old code no longer used in the present forms of BOINC.

ERR_DB_NOT_FOUND -136

This is a problem with the MySQL database. The number of rows in the database is zero.

Solution: Report this behavior on the Project's forums.

ERR_DB_NOT_UNIQUE -137

An error code in Attach to Account Wizard: Database lookup not unique.

ERR_DB_CANT_CONNECT -138

Low level debugging of the MySQL database is enabled.

ERR_GETS -139

Same as ERR_BAD_HEX_FORMAT
The data in the source file contains a non-hexadecimal character. Hexadecimal 'numbers' run from 0 to 9 and a to f. Any other character will trigger this error.

Solution: Report this behavior on the project's forums.

ERR_SCANF -140

This has to do with scanning the hexadecimal format in the source file.
 

05. Error code -141 to -150 explained.

FAQ: 05. Error code -141 to -150 explained.
Title: 05. Error code -141 to -150 explained.
Author: Jorden
Views: 73572
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:18:37
Last Modified: 14/02/2008 23:18:37

Contents:

ERR_STRCHR -141

The buffer contains a string that is empty. With no where to go to.

ERR_STRSTR -142

This code is no longer used in any present versions of BOINC.

ERR_READDIR -143

BOINC cannot read the directory, it is missing the correct path. It will try to find the correct path.

ERR_SHMGET -144

BOINC cannot find the shared memory segment. Shared memory is memory used by BOINC and the scinece application at the same time.

ERR_SHMCTL -145

BOINC cannot free the shared memory segment.

ERR_SHMAT -146

BOINC cannot use the shared memory segment.

ERR_FORK -147

Boinc cannot create a new process. Any errors with child processes in their description will have to do with this error.
See fork()

ERR_EXEC -148

BOINC cannot create a new process. Or BOINC is already running. Only one instance of BOINC can run at any time.

ERR_NOT_EXITED -149

A process that was supposed to exit, did not do so.

ERR_NOT_IMPLEMENTED -150

BOINC encountered a system call to memory that wasn't designed for this platform.
Use the correct version of BOINC for your CPU and operating system.
 

06. Error code -151 to -160 explained.

FAQ: 06. Error code -151 to -160 explained.
Title: 06. Error code -151 to -160 explained.
Author: Jorden
Views: 74264
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:18:49
Last Modified: 14/02/2008 23:18:49

Contents:

ERR_GETHOSTNAME -151

Old code no longer used in any present version of BOINC.

ERR_NETOPEN -152

Old code no longer used in any present version of BOINC.

ERR_SOCKET -153

A negative socket number was found. Socket numbers can only be 0 and above.

ERR_FCNTL -154

BOINC wasn't able to get a file's attributes. In general this has to do with socket-connections.

Applies only to non-Windows-systems or versions of Windows without WINSOCK-functionality.

ERR_AUTHENTICATOR -155

The scheduler request host ID number doesn't match with the authenticator.
You are missing your authenticator key. Detach from and re-attach to the project.

ERR_SCHED_SHMEM -156

A shared memory block received from the scheduler contains illegal data or cannot be processed.

ERR_ASYNCSELECT -157

Old code no longer used in any present version of BOINC.

ERR_BAD_RESULT_STATE -158

This can happen when there are two results occupying the same slot, or when the wrong state about the result is written to the Client_state.xml file.

ERR_DB_CANT_INIT -159

There is no MySQL database detected on the other side. This error message is used for low level debugging.

ERR_NOT_UNIQUE -160

The client_state.xml file has redundant entries about the science application or results.
 

07. Error code -161 to -170 explained.

FAQ: 07. Error code -161 to -170 explained.
Title: 07. Error code -161 to -170 explained.
Author: Jorden
Views: 74239
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:18:56
Last Modified: 14/02/2008 23:18:56

Contents:

ERR_NOT_FOUND -161

This happens when you have an inconsistent client_state.xml file. Files aren't written to it.
Task not found would be the error message.


ERR_NO_EXIT_STATUS -162

This happens when an exit status is not found in the scheduler request.

ERR_FILE_MISSING -163

Client_state.xml file has found that a file is missing that it should have. Found through verification process.

ERR_SEMGET -165

BOINC is unable to get a set of semaphores.

ERR_SEMCTL -166

BOINC is unable to free a set of semaphores.

ERR_SEMOP -167

BOINC is unable to use a set of semaphores.

ERR_FTOK -168

BOINC cannot get file token (key) for semaphores.

ERR_SOCKS_UNKNOWN_FAILURE -169

This is old code that is no longer used in any of the present versions of BOINC.

ERR_SOCKS_REQUEST_FAILED -170

This is old code that is no longer used in any of the present versions of BOINC.
 

08. Error code -171 to -180 explained.

FAQ: 08. Error code -171 to -180 explained.
Title: 08. Error code -171 to -180 explained.
Author: Jorden
Views: 75107
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:19:05
Last Modified: 27/06/2011 23:58:48

Contents:

ERR_SOCKS_BAD_USER_PASS -171

This is old code that is no longer in use by any version of Boinc.

ERR_SOCKS_UNKNOWN_SERVER_VERSION -172

This is old code that is no longer in use by any version of Boinc.

ERR_SOCKS_UNSUPPORTED -173

This is old code that is no longer in use by any version of Boinc.

ERR_SOCKS_CANT_REACH_HOST -174

This is old code that is no longer in use by any version of Boinc.

ERR_SOCKS_CONN_REFUSED -175

This is old code that is no longer in use by any version of Boinc.

ERR_TIMER_INIT -176

This is old code that is no longer in use by any version of Boinc.

ERR_RSC_LIMIT_EXCEEDED -177

Maximum disk usage is exceeded. The science application is aborted.
Check your disk usage settings in your general preferences.

Maximum disk usage exceeded or Maximum memory usage exceeded (check the messages tab/Event Log for more information) The science application is aborted. Check your disk/memory usage settings in your general preferences.

Maximum CPU time exceeded. The maximum granted CPU time for a work unit is exceeded, probably a stuck work unit. The science application is aborted. If a work unit gets stuck, exiting and restarting BOINC is a known workaround to fix this (if it's not already aborted ;-)).

ERR_INVALID_PARAM -178

This is an Auto-Update error, when the project has multiple science applications that you must choose from, or the application version for your BOINC version can not be found.

ERR_SIGNAL_OP -179

Exit of installing unhandled exception filters and signal traps.

ERR_BIND -180

GUI RPC bind failed.
 

09. Error code -181 to -190 explained.

FAQ: 09. Error code -181 to -190 explained.
Title: 09. Error code -181 to -190 explained.
Author: Jorden
Views: 73983
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:19:13
Last Modified: 01/02/2010 08:10:36

Contents:

ERR_LISTEN -181

GUI RPC listen failed

ERR_TIMEOUT -182

Too much time elapsed during persistent file transfer -- giving up.

ERR_PROJECT_DOWN -183

The project you are attached to is down, either for maintenance or for another reason.
Just wait until they are back up. Keep an eye on their homepage.

ERR_HTTP_ERROR -184

This is an error in the polling of the start of the HTTP/S transaction start in CurlEasy.
Report this on the BOINC forums.

ERR_RESULT_START -185

This is an error that will occur:
- if BOINC couldn't start the application
- if files are missing
- upon catch of other error returns
- on nonzero exit or signal
- if exceeded resource limit
- as catch-all for resume/start errors

Rebooting your machine will most of the times fix these.

ERR_RESULT_DOWNLOAD -186

BOINC will trigger this error when the work unit or application had a download error.

ERR_RESULT_UPLOAD -187

BOINC will trigger this error when the work unit had an upload error.

ERR_INVALID_URL -189

The Master URL is invalid. Check your typing and try again.

ERR_MAJOR_VERSION -190

This is old code that is no longer in use by any present version of BOINC.

 

10. Error code -191 to -200 explained.

FAQ: 10. Error code -191 to -200 explained.
Title: 10. Error code -191 to -200 explained.
Author: Jorden
Views: 73899
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:19:21
Last Modified: 14/02/2008 23:19:21

Contents:

ERR_NO_OPTION -191

This version of BOINC has no option to upload a trickle. A trickle is an intermediate upload of status for big work units, such as CPDN.

ERR_MKDIR -192

BOINC is unable to make a sub-directory. Make sure you use an account that has full read/write rights.

ERR_INVALID_EVENT -193

This is old code that is no longer in use by any present version of BOINC.

ERR_ALREADY_RUNNING -194

Another instance of BOINC Client is already running.

ERR_NO_APP_VERSION -195

BOINC couldn't find the application's version number.

ERR_WU_USER_RULE -196

BOINC tries to send the client this result and fails because:
- result needs more disk/mem/speed than host has
- already sent a result for this WU
- no app_version available

ERR_ABORTED_VIA_GUI -197

You have aborted the work unit through Boinc Manager.

ERR_INSUFFICIENT_RESOURCE -198

You do not have enough resources to run this work unit.
This can be a problem with the amount of RAM you have, the CPU you have, the amount of disk space.
Check RAM Requirements, check with the project if your CPU is alright to be used and check your general preferences if you have set enough disk space to be used. Check your hard drive if you still have enough space free.

ERR_RETRY -199

This error has to do with the snooze option, with sockets closed and when the GUI is in idle status.


ERR_WRONG_SIZE -200

Your files have the wrong file size.
 

11. Error code -201 to -210 explained.

FAQ: 11. Error code -201 to -210 explained.
Title: 11. Error code -201 to -210 explained.
Author: Jorden
Views: 73866
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:19:28
Last Modified: 06/02/2010 23:42:49

Contents:

ERR_USER_PERMISSION -201

The user forgot to set Netwotk/Internet permissions, or the file ownership or permissions are set does not allow SANDBOXED execution of the BOINC applications.
To use BOINC anyway, use the -insecure command line option. To change ownership/permission, reinstall BOINC.

ERR_SHMEM_NAME -202

ftok() only works if there's a file at the given location.

ERR_NO_NETWORK_CONNECTION -203

Dialup Manage failed to connect because of a modem error or a users credentials were wrong.

ERR_IN_PROGRESS -204

This error occurs in the background. It happens when you have problems with logging in and is used internally in the BOINC code.

ERR_BAD_EMAIL_ADDR -205

An email address was entered in Attach to Project Wizard or Account manager Wizard for an existing account, but the project has no record of a user with this email address.

ERR_BAD_PASSWD -206

You have filled in a wrong password in Boinc Manager.

ERR_NONUNIQUE_EMAIL -207

An error code in Attach to Account Wizard (I'm guessing this is returned if you try to sign up as a new user but project already has an account for this email address)


ERR_ACCT_CREATION_DISABLED -208

Account creation on the project is disabled. You will not be able to make an account through Boinc Manager.

ERR_ATTACH_FAIL_INIT -209

BOINC cannot attach to the project. Check if you used the correct URL.

ERR_ATTACH_FAIL_DOWNLOAD -210

BOINC failed to attach to the project. The project's servers may be down. Try again later.
 

12. Error code -211 to -220 explained.

FAQ: 12. Error code -211 to -220 explained.
Title: 12. Error code -211 to -220 explained.
Author: Jorden
Views: 73007
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:19:35
Last Modified: 14/02/2008 23:19:35

Contents:

ERR_ATTACH_FAIL_PARSE -211

The web page for the URL you used to attach to a "project" contains no BOINC information.
Check if you are using the correct URL to the project page.

ERR_ATTACH_FAIL_BAD_KEY -212
You tried to attach to a project using an incorrect account key. Check if you have the correct account key.
Copy and paste it from your email into the Boinc Manager attach to wizard.

ERR_ATTACH_FAIL_FILE_WRITE -213

BOINC was unable to create an account file for the project on your disk.
Make sure you have sufficient read/write rights on your operating system.

ERR_ATTACH_FAIL_SERVER_ERROR -214

BOINC failed to attach to the project.

ERR_SIGNING_KEY -215

No longer used in any version of BOINC.

ERR_FFLUSH -216

BOINC is unable to flush the file. Make sure you have sufficient read/write rights on your operating system.

ERR_FSYNC -217

Error trying to sync (flush) file to disk on a Windows system

ERR_TRUNCATE -218

File size couldn't be truncated.

ERR_WRONG_URL -219

You are using the wrong URL for this project. Check the URL and detach then re-attach with the correct URL.

ERR_DUP_NAME -220

This is a check that you aren't already attached to a project of the same name. You can only attach to a project once.
 

13. Error code -221 to -230 explained.

FAQ: 13. Error code -221 to -230 explained.
Title: 13. Error code -221 to -230 explained.
Author: Jorden
Views: 73927
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 14/02/2008 23:19:42
Last Modified: 18/06/2008 17:48:54

Contents:

ERR_ABORTED_BY_PROJECT -221

The project you are attached to aborted this result.

ERR_GETGRNAM -222

Sandbox security logic: group boinc_project does not exist

ERR_CHOWN -223

This is an error when changing the file ownership.

ERR_FILE_NOT_FOUND -224

This is the same as an HTTP error 404: File not found.

ERR_BAD_FILENAME -225

One of the files downloaded is found with a bad filename. Did you rename it?
Did the project name it incorrectly?

ERR_TOO_MANY_EXITS -226

An application has exited prematurely (unexpectedly) more than 99 times without generating a checkpoint, so giving up on that task.

ERR_RMDIR -227

In BOINC 6.0 and above: Remove (delete) directory failed.

ERR_CHILD_FAILED -228

On Unix if the application is non-executable, it will crash the task which BOINC will treat as recoverable and therefore restart itself. Since this is unwanted behaviour, BOINC returns this error code and exits itself.

Also used when the wrapper application exits when it finds that one of the sub-applications has failed.

ERR_SYMLINK -229

There's been an error detected in a symlink that the project uses to tell where its directories are. Report this error on the project's forums.

Symlinks are no longer used in the BOINC 6 clients.

ERR_DB_CONN_LOST -230

This is a server error. The connection to the database was lost while storing a result in its memory.
 

14. Error code -231 to -240 explained.

FAQ: 14. Error code -231 to -240 explained.
Title: 14. Error code -231 to -240 explained.
Author: Jorden
Views: 62181
Category: 06. BOINC Client Common Errors
Available in: English
Created: 09/04/2009 14:27:37
Last Modified: 11/07/2012 10:30:02

Contents:

ERR_CRYPTO -231

BOINC had a problem encrypting the private key, or decrypting the public key. You will probably have to detach and reattach to fix this. (Detaching/Reattaching forces a new download of the public key).

ERR_ABORTED_ON_EXIT -232

Error code showing when the "abort_jobs_on_exit" flag is present in cc_config.xml
You're aborting tasks and telling the projects about it.

ERR_UNSTARTED_LATE -233

BOINC will abort tasks that have not started yet and are over the deadline.

ERR_MISSING_COPROC -234

A coprocessor that was detected earlier has gone missing. Check your drivers, the seating of the card or see if rebooting the computer will re-detect the card again.

ERR_PROC_PARSE -235

A processing entry was not parsed correctly.
 

Application failed to initialize properly (0xc0150004)

FAQ: Application failed to initialize properly (0xc0150004)
Title: Application failed to initialize properly (0xc0150004)
Author: Jorden
Views: 60797
Category: 06. BOINC Client Common Errors
Available in: English
Created: 26/09/2009 02:46:13
Last Modified: 26/09/2009 02:46:13

Contents:

You can get this error when you try to install BOINC on a system that does not have all the latest Windows updates.

First update your system completely, if the error persists, you will have to find a computer with the same version of Windows and navigate to its %systemdrive%:\Windows\WinSxS\ directory.

From here copy all the x86_Microsoft.VC* directories with their contents to your own system. Make sure the directory names stay intact.

Then reboot the system and try to install again.
 

Authorization failure -155

FAQ: Authorization failure -155
Title: Authorization failure -155
Author: Jorden
Views: 70433
Category: 06. BOINC Client Common Errors
Available in: English
Created: 26/05/2008 18:53:41
Last Modified: 26/05/2008 18:53:41

Contents:

You can get this error when using boinccmd on BOINC 6.

If your data directory is at:
C:\Documents and Settings\All Users\Application Data\BOINC

Do a:
cd /d "C:\Documents and Settings\All Users\Application Data\BOINC"

then execute boinccmd like this:
"C:\program files\BOINC\boinccmd.exe" --commands

 

BOINC Manager pop-up: Communicating with client, please wait

FAQ: BOINC Manager pop-up: Communicating with client, please wait
Title: BOINC Manager pop-up: Communicating with client, please wait
Author: Jorden
Views: 58418
Category: 06. BOINC Client Common Errors
Available in: English
Created: 08/03/2010 11:55:03
Last Modified: 28/06/2011 00:01:23

Contents:

This pop-up will come up at any time that BOINC Manager cannot communicate with the client.

- This can happen when you didn't allow the BOINC binary and the BOINC Manager binary through your firewall on TCP port 31416.

In this case, just allow both of these binaries (in Windows boinc.exe and boincmgr.exe) to pass through your firewall. The BOINC binary needs to be able to get onto the internet on TCP ports 80 and 443 as well.

- This can happen when you have far too many tasks in queue for BOINC Manager to display in real-time.

BOINC Manager is a graphical user interface that makes it easier for you to give commands to the client (BOINC). It talks through remote procedure calls with the client (hence why it needs to go through the firewall). It will update the times on tasks that are running and show messages in the Messages tab/Event Log. The update rate for all this is once a second.

As an example, when you have 1,200 tasks in queue, it will take BOINC 1.5 seconds to read and digest that information. As you can imagine, there is no way to compress that into the 1 second refresh rate, while with the more tasks you have in queue this time will only go up.

Which is why the developers have chosen another thing, the "Show all tasks/Show active tasks" button, which is on (showing "Show all tasks") by default and which will hide all tasks that are not running.

This means that only the tasks that are actually running, have run for a bit and are waiting to run and those that are suspended, will show in your Tasks tab.

Those waiting to start, waiting to be reported, downloading, uploading and aborted will not show in this list, since they aren't considered active.

Um... but I pressed the "Show all tasks" button and now I can't get it to reverse. There's no time to press the button again.

On Windows:

Exit BOINC Manager.
Start->Run, type regedit, click OK.
Navigate to HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager\Tasks and change the value of ActiveTasksOnly from 0 to 1.
Then start BOINC Manager. Changes are immediate.

On Linux:

The configuration file is in your user home directory and called .BOINC Manager (e.g. /home/remco/.BOINC Manager, this file may be hidden)
Edit the value for ActiveTasksOnly from zero to one.

On the Mac (OS X):

The configuration file is saved in /Users/[username]/Library/Preferences/BOINC Manager Preferences, edit the key word ActiveTasksOnly in the [Tasks] section.
 

Can't rename state file; The process cannot access the file because it is being used by another process. (0x20)

FAQ: Can't rename state file; The process cannot access the file because it is being used by another process. (0x20)
Title: Can't rename state file; The process cannot access the file because it is being used by another process. (0x20)
Author: Jorden
Views: 59401
Category: 06. BOINC Client Common Errors
Available in: English
Created: 04/07/2008 15:47:06
Last Modified: 11/10/2009 13:20:24

Contents:

Something has put a lock on the client_state.xml file, so BOINC can't copy it to client_state_prev.xml and make it anew.

This usually happens when you have an anti-virus or anti-spyware program that's allowed to actively scan the computer. The solution is to either only scan when you have BOINC suspended or to exclude the BOINC directories from the scan. Since this cannot be done in most freeware versions of AV scanners (only in paid for versions), it's best to scan only with BOINC suspended.
 

error code -1073741502 (0xffffffffc0000142) / error code -1073741502 (0xc0000142)

FAQ: error code -1073741502 (0xffffffffc0000142) / error code -1073741502 (0xc0000142)
Title: error code -1073741502 (0xffffffffc0000142) / error code -1073741502 (0xc0000142)
Author: Jorden
Views: 70249
Category: 06. BOINC Client Common Errors
Available in: English
Created: 14/02/2008 23:16:29
Last Modified: 14/02/2008 23:16:29

Contents:

0xC0000142 means STATUS_DLL_INIT_FAILED which can happen when an application attempts to create a new process while the OS is shutting down, and when the desktop heap is fully utilized.

Mostly happening on Vista, but can also happen on older Windows versions, especially when you reset the computer at the time BOINC starts crunching new tasks, previously not crunched.

BOINC 5.10.30 and above have code included that will make sure these tasks are restarted on a reset of the computer. Older versions of BOINC will abort the tasks.
 

Error codes: Other BOINC errors

FAQ: Error codes: Other BOINC errors
Title: Error codes: Other BOINC errors
Author: Jorden
Views: 77949
Category: 06. BOINC Client Common Errors
Available in: English
Created: 26/01/2007 19:18:12
Last Modified: 25/11/2009 08:08:35

Contents:

404: return "HTTP file not found";

The 404 or Not Found error message is an HTTP standard response code indicating that the client was able to communicate with the server, but the server either could not find what was requested, or it was configured not to fulfill the request and not reveal the reason why.

407: return "HTTP proxy authentication failure";

The server thinks that the HTTP data stream sent from the BOINC client was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first.

416: return "HTTP range request error";

The server thinks that the HTTP data stream sent from the BOINC client contains a 'Range' request which specifies a range of bytes which can not be satisfied - because the resource being accessed does not cover this byte range. For example if the resource - an image file for example - has 1000 bytes and the Range requested is 500-1500, then it can not be satisfied.

500: return "HTTP internal server error";

This is NOT a problem with your PC or internet connection!

The server encountered an unexpected condition that prevented it from fulfilling the request by the BOINC client for access to the requested URL.

This is a 'catch-all' error generated by BOINC. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the server site to locate and analyse these logs.

501: return "HTTP not implemented";

The server does not support the HTTP method it finds in the HTTP data stream sent to it by the BOINC client. Or the method may be valid but not actually supported by the server.

502: return "HTTP bad gateway";

A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request.

This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed.

503: return "HTTP service unavailable";

The server is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.

Some projects have their own error message for this. For example Primegrid:
2007-01-03 23:07:17 [PrimeGrid] Message from server: The server is overloaded . You will be able to connect once the load level gets lower.

504: return "HTTP gateway timeout";

A server is acting as a gateway or proxy to fulfil the request by the BOINC client to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.

This usually means that the upstream server is down (no response to the gateway/proxy), rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.

system connect

This error means that the BOINC client couldn't connect to the IP address that the DNS server gave to BOINC.

See ERR_CONNECT -107

Error on file upload: socket read incomplete: asked for 12922, got 7422: No such file or directory
together with
Error on file upload: socket read incomplete: asked for 12922, got 7422: Transport endpoint is not connected

Your copy of BOINC is telling the project servers to expect a file of size 12922 bytes, but the file it's actually sending is only 7422 bytes. Basically, BOINC is trying to send the wrong file, or a file of the wrong size. See error -127 for more information.
 

Exit code -1073741502 (0xC0000142) - Einstein

FAQ: Exit code -1073741502 (0xC0000142) - Einstein
Title: Exit code -1073741502 (0xC0000142) - Einstein
Author: Jorden
Views: 71807
Category: 06. BOINC Client Common Errors
Available in: English
Created: 23/09/2007 14:06:14
Last Modified: 23/09/2007 14:06:14

Contents:

Exit code -1073741502 (0xC0000142): It means that a DLL failed to load properly. This error looks like it's happening more frequently on Windows Vista, but we also get it from machines running Windows XP. The Einstein developers would greatly appreciate any idea which DLL this might be - so far they haven't got a clue.
 

exit code -1073741510 (0xc000013a) (On Windows Vista)

FAQ: exit code -1073741510 (0xc000013a) (On Windows Vista)
Title: exit code -1073741510 (0xc000013a) (On Windows Vista)
Author: Jorden
Views: 83110
Category: 06. BOINC Client Common Errors
Available in: German English
Created: 22/05/2008 11:11:16
Last Modified: 22/05/2008 11:11:16

Contents:

The message exit code -1073741510 (0xc000013a) means that when you log off of Windows the application gets terminated quite abruptly. Apparently BOINC/the science applications don't like that too much. I understand Vista can shut down in 2 seconds... that's not enough time for BOINC to stop.

So before you shut down your computer next time, exit BOINC.
- If you run as a normal user install, it's done through Boinc Manager, File->Exit.
- If you run as a service install, you need to stop the service first. Start->Run, type net stop boinc and hit enter.

Or:
Copy the following text and paste it into the Notepad window, called WaitToKill.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
"WaitToKillServiceTimeout"="20000"


The 20000 is 20 seconds. Increase/decrease to your liking.
To add this to the registry double-click the file. The UAC will come up, press continue, press Yes on the next window and OK on the one there-after. You need to reboot to make the changes have effect.

You can also use the following bit of code in a batchfile (.bat).
Put it in Notepad, save it as Shutdown.bat (make sure the extension is .bat, not .txt)
Do change the path between %PROGRAMFILES% if your BOINC lives elsewhere.
Code:
cd %PROGRAMFILES%\BOINC
boinccmd --quit
shutdown -s -t 20


Updating to BOINC 5.10.45 can also fix this error. It has special code in for Vista to count this as a non-error.
 

exit code -1073741795 (0xc000001d)

FAQ: exit code -1073741795 (0xc000001d)
Title: exit code -1073741795 (0xc000001d)
Author: Jorden
Views: 59749
Category: 06. BOINC Client Common Errors
Available in: English
Created: 18/06/2008 17:18:19
Last Modified: 02/11/2009 20:37:32

Contents:

"Illegal Instruction (0xc000001d) at address 0x00402818" means that you are trying to run an application built with instruction sets that are newer than the ones that are built into the CPU.

For example, an optimized Seti application with SSE3, while the maximum the CPU can do is SSE2.

This can be fixed by running CPU-Z and then choosing the correct application from the optimized bunch (or in Seti's case, the Lunatics installer).
 

exit code -1073741811 (0xc000000d)

FAQ: exit code -1073741811 (0xc000000d)
Title: exit code -1073741811 (0xc000000d)
Author: Jorden
Views: 72754
Category: 06. BOINC Client Common Errors
Available in: English
Created: 02/10/2007 00:21:49
Last Modified: 02/10/2007 00:21:49

Contents:

Is an application error code you will find on Windows computers which use a (certain) video card.

Disabling the screen saver will give you a work-around for it. Report this error on the forums at all times.

From AppDebugWin in the Wiki:

Starting with Visual Studio 2005, Microsoft re-vamped the whole C Runtime Library. Part of the re-vamp process was to do parameter checking on each function. Places that would normally return a NULL value now cause a structured exception to be thrown.

The nature of this structured exception is different than most as they specifically coded it so that it will not engage the BOINC Runtime Debugger and it'll display a dialog box asking the user if they wish to debug the error. If the user cancels the error code 0xc000000d is returned without any more information.
 

Exit code -1073741819 (0xC0000005) - Einstein only (S5R1-5 runs only!)

FAQ: Exit code -1073741819 (0xC0000005) - Einstein only (S5R1-5 runs only!)
Title: Exit code -1073741819 (0xC0000005) - Einstein only (S5R1-5 runs only!)
Author: Jorden
Views: 72508
Category: 06. BOINC Client Common Errors
Available in: English
Created: 23/09/2007 14:06:44
Last Modified: 02/04/2010 11:25:56

Contents:

The below error was for the S5R1-5 runs only. It's no longer up-to-date for the S5R6 and above runs. Please look at the default exit code -1073741819 (0xc0000005) error instead.

Exit code -1073741819 (0xC0000005): This is the famous "General Access Violation". There a numerous reasons for this error to occur, from hardware problems to graphics drivers and more. Ideally when this happens, the "Windows Runtime Debugger" should start up and write a stack dump to stderr out that helps to further diagnose the problem. If the "Access Violation" is listed in the "*** Dump of the Graphics thread ***", it was almost certainly a problem with the graphics driver. The most common cause for an Access Violation listed in the "*** Dump of the Worker thread ***" shows "houghmap.c:" near the end of the first line of the Callstack. This is a problem that we might be able to do something about, we are currently hunting this. Apparently it only happens on certain machines, it might be related to the data these hosts are processing, but may also be a property of the hardware or other software on the system.
 

Fixing: The COM+ Event System failed to fire the ConnectionLost method on subscription {A8EDB33C-55FF-4D5D-965A-27769CC279AD}. The subscriber returned HRESULT 80010105.

FAQ: Fixing: The COM+ Event System failed to fire the ConnectionLost method on subscription {A8EDB33C-55FF-4D5D-965A-27769CC279AD}. The subscriber returned HRESULT 80010105.
Title: Fixing: The COM+ Event System failed to fire the ConnectionLost method on subscription {A8EDB33C-55FF-4D5D-965A-27769CC279AD}. The subscriber returned HRESULT 80010105.
Author: Jorden
Views: 81861
Category: 06. BOINC Client Common Errors
Available in: English
Created: 26/05/2008 18:36:44
Last Modified: 26/05/2008 18:36:44

Contents:

When checking the Event Viewer in Windows 2000/XP/Vista, you may come across a warning in the Application Log that goes a bit like this:

Event Type: Warning
Event Source: EventSystem
Event Category: Firing Agent
Event ID: 4098
Date: 20/02/2007
Time: 23:32:43
User: N/A
Computer: (YOUR COMPUTER NAME)
Description:
The COM+ Event System failed to fire the ConnectionLost method on subscription {A8EDB33C-55FF-4D5D-965A-27769CC279AD}. The subscriber returned HRESULT 80010105.

This works back to being a problem with BOINC and is easily fixed.

First and foremost, exit BOINC.
Open Boinc Manager, File -> Exit.

Go to: Start -> Run, type cmd and press Enter.

The next path is showing how to get to the default BOINC directory installation.

In the command line window that opened, type:
(If you use BOINC as a service, type net stop boinc and press Enter.)
cd\program files\boinc and press Enter.
regsvr32 /u boinc.dll and press Enter. Press OK on the popup window.
regsvr32 boinc.dll and press Enter. Press OK on the popup window.

You can now close the command line window by pressing the X in the top right corner.

The next path shows how to get to a different drive and BOINC directory.

In the command line window that opened, type:
(If you use BOINC as a service, type net stop boinc and press Enter.)
e: and press Enter.
cd\boinc and press Enter.
regsvr32 /u boinc.dll and press Enter. Press OK on the popup window.
regsvr32 boinc.dll and press Enter. Press OK on the popup window.

You can now close the command line window by pressing the X in the top right corner.

What you have done is unregister the BOINC.dll and re-register it in the Windows registry.
For some reason the prior installation had gotten corrupt. This simple handling will fix this error. No need to reboot Windows afterwards.

You can now restart BOINC.
Start->Programs->BOINC->Boinc Manager.

(Or if you use BOINC as a service, Start->Run, type net start boinc and press Enter.)

If you keep getting these errors, do the following:
Open the Services window. (Start->Run, type services.msc and hit Enter)
Scroll down to the System Event Notification service. Stop it and restart it.
 

HTTP Error 0

FAQ: HTTP Error 0
Title: HTTP Error 0
Author: Jorden
Views: 72428
Category: 06. BOINC Client Common Errors
Available in: English
Created: 30/08/2007 23:11:37
Last Modified: 17/09/2011 10:29:34

Contents:

When you find you are getting HTTP Error 0 in the message log, make sure the firewall on the clients is allowed to communicate on TCP port 80 and 443. HTTP Error 0 means as much as "It connected to the server, sent the request and got no response".
 

Message from server: Completed {task name} refused: result already reported as success

FAQ: Message from server: Completed {task name} refused: result already reported as success
Title: Message from server: Completed {task name} refused: result already reported as success
Author: Jorden
Views: 56435
Category: 06. BOINC Client Common Errors
Available in: English
Created: 17/03/2010 08:25:40
Last Modified: 17/03/2010 08:25:40

Contents:

This is not an error, it is an informational message.

It means that on an earlier attempt your BOINC was able to report all your tasks to the server, but the server was not able to send the acknowledgment about the report back to you, probably due to congestion on the line.

You will not lose any credits due to this message, you will not get double credit either. After the first time around that this message is sent to you, BOINC will discard of the to be reported tasks automatically, but in the off-chance it doesn't happen, you may have to abort them manually.
 

Message from server: Incomplete request received.

FAQ: Message from server: Incomplete request received.
Title: Message from server: Incomplete request received.
Author: Jorden
Views: 65340
Category: 06. BOINC Client Common Errors
Available in: English
Created: 02/07/2008 23:59:56
Last Modified: 03/07/2008 17:25:12

Contents:

So your BOINC is working for months without a problem and then all of a sudden it stops working, it has calculated all the work you had but is unable to upload the work, download new work or report anything. You're being stonewalled with a Message from server: Incomplete request received.

Going on forums, people can't help you as they don't know where to start. Or they give up after having tried everything in their book. Sorry, it happened to me as well, trying to help you but eventually giving up as I didn't know anymore.

But not this time. It looks like with the help of David Anderson, we've cracked this case.
The solution is simple.

OK, first off, what does the message mean?

As you may know, when BOINC contacts a project server it sends information about who you are, which computer you're on and what work you had or want to the project server. For this transfer of information it sends along some of your preferences.

And that is where the problem lies. When (the content of) your preferences file has become corrupted, it sends this corrupted information to the project server, which cannot compute this info and it gives you the Incomplete request received message.

The solution to this problem is simple.

In BOINC 5.10 and earlier:
- Exit BOINC.
- Navigate to your BOINC directory. Default at C:\Program Files\BOINC
- Find the global_prefs.xml file.
- Delete it.
- Restart BOINC.
- Contact any of the projects out there to get the preferences file rewritten.

In BOINC 6.1.0 and above:
- Exit BOINC.
- Navigate to your BOINC Data directory.
-- In Windows 98/SE/ME, default at either C:\Windows\All Users or C:\Windows\Profiles\All Users
-- In Windows 2000/XP, default at C:\Documents and Settings\All Users\Application Data\BOINC
-- In Windows Vista, default at C:\ProgramData\BOINC
- Find the global_prefs.xml file.
- Delete it.
- Restart BOINC.
- Contact any of the projects out there to get the preferences file rewritten.

How can this file become corrupted? Examining global_prefs.xml with an XML editor or changing its format can do this. The format used is legal XML, but it is not comprehensible by BOINC. Other possibilities are corruption of the hard drive (check the disk with chkdsk) or another program had a glitch while writing to a sector on the disk next to where this file was written.

When you edit any XML file used by BOINC, use a clear text editor only. In Windows, the default to use is Notepad. When saving make sure you don't let the editor add another extension to the XML file (.TXT, .DOC, .RTF etc.)
 

No URL for file transfer of {application name}

FAQ: No URL for file transfer of {application name}
Title: No URL for file transfer of {application name}
Author: Jorden
Views: 69505
Category: 06. BOINC Client Common Errors
Available in: English
Created: 21/09/2007 21:41:03
Last Modified: 21/09/2007 21:41:03

Contents:

Example given:

2007-09-20 10:35:17 [---] [error] No URL for file transfer of einstein_S5R2_4.40_windows_intelx86.exe
2007-09-20 10:35:17 [Einstein@Home] [error] Can't initialize file transfer for einstein_S5R2_4.40_windows_intelx86.exe
2007-09-20 10:35:17 [---] [error] No URL for file transfer of einstein_S5R2_4.40_windows_intelx86.pdb
2007-09-20 10:35:17 [Einstein@Home] [error] Can't initialize file transfer for einstein_S5R2_4.40_windows_intelx86.pdb

You see these errors at the top of the messages when starting BOINC.

This only happens when you have had an app_info.xml file and the applications plus debug file set manually in your projects directory, but later removed the app_info.xml file and not reset your project.

BOINC doesn't know where the entries of these files came from in client_state.xml as it has no recollection of downloading them by itself. And so it will give this error message and even try to download the files from the server, if necessary.

Solution: Reset the project. It will then download the correct applications.
 

Process got signal 11

FAQ: Process got signal 11
Title: Process got signal 11
Author: Jorden
Views: 67968
Category: 06. BOINC Client Common Errors
Available in: English
Created: 12/09/2008 15:13:03
Last Modified: 12/09/2008 15:15:34

Contents:

This error can be caused by the infamous segmentation error (SIGSEGV error), meaning that something broke. be it your memory, virtual memory (page file) or it's a bad batch of tasks.

Check your system with memtest86+, make your page file anew, keep a tab on whether you're the only one returning these errors, or that others have them at the same time as well. If you are the only one, it's something on your system, if there are lots more, it's a bad batch of work.

But it can also happen when you use a 64bit operating system, while the project you're getting the crashes on only gives out 32bit applications (such as Einstein does). Installing the ia32 library package will fix this problem. See also process exited with code 22 which is a similar error, on the application level.
 

Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down.

FAQ: Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down.
Title: Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down.
Author: Jorden
Views: 71720
Category: 06. BOINC Client Common Errors
Available in: English
Created: 12/02/2008 07:10:10
Last Modified: 12/02/2008 07:10:10

Contents:

Project communication failed: attempting access to reference site. Access to reference site succeeded - project servers may be temporarily down.

This can mean one of a few things:
a) The project server is down. Nothing you can do about it, except wait until it’s back up. If the project’s website is available for browsing, check the front-page news or message boards for information about outages.
b) The project server is up, but your internet connection isn’t reaching it. This is called a “black hole server”, where the line you’re following goes into a server node on the Internet and doesn't come out, usually because the node is down. Updating to a newer version of BOINC might help, especially if you’re still using v4.x or 5.4.x. Quitting and relaunching BOINC may refresh its routing information; failing that, try rebooting the computer.
c) The client is being blocked by a firewall or proxy, one that does allow pings through on port 80, but not much else by way of communication. Make sure BOINC has permission to go through the firewall and, if you’re behind a proxy, that BOINC is set up to use the correct proxy address.

The reference site that BOINC calls upon is www.google.com. Why Google? Because Google is always up. So if BOINC finds that it can reach Google but not the project, it’s not the client’s fault and the Internet connection itself is OK.
 

Project Scheduler request failed: Couldn't resolve host name

FAQ: Project Scheduler request failed: Couldn't resolve host name
Title: Project Scheduler request failed: Couldn't resolve host name
Author: Jorden
Views: 57849
Category: 06. BOINC Client Common Errors
Available in: English
Created: 06/03/2010 23:14:47
Last Modified: 09/03/2010 09:25:08

Contents:

This error shows up, when the communications part of BOINC not being able to find the correct URL to the project.

It's usually fixed by detaching from the project and reattaching to it, using the correct URL.

e.g.
Sat Mar 6 10:55:00 2010 World Community Grid Requesting new tasks
Sat Mar 6 10:55:01 2010 Project communication failed: attempting access to reference site
Sat Mar 6 10:55:02 2010 Internet access OK - project servers may be temporarily down.
Sat Mar 6 10:55:05 2010 World Community Grid Scheduler request failed: Couldn't resolve host name
 

Scheduler request failed: Error 417

FAQ: Scheduler request failed: Error 417
Title: Scheduler request failed: Error 417
Author: Jorden
Views: 63926
Category: 06. BOINC Client Common Errors
Available in: English
Created: 25/11/2009 11:56:36
Last Modified: 11/02/2010 14:30:13

Contents:

With BOINC the Error code 417 usually means that something in your internet connection changed. Perhaps that your ISP switched from using HTTP 1.1 to HTTP 1.0, or it has other problems.

By default BOINC uses HTTP 1.1 to communicate with projects. This does not always work, so then you can try to switch BOINC to use HTTP 1.0 instead.

To do so, make a cc_config.xml file in your BOINC Data directory. The default paths for this directory can be found in this FAQ, and else BOINC will tell you in its start-up messages - 3rd to 6th line from the top of the messages - where it is. This directory may be hidden, the other FAQ will detail how you can get it to show.

Back to the cc_config.xml file. When you made it and made sure it has the .xml extension, not a .txt or other extension, add into it these lines:

Code:
<cc_config>
  <options>
    <http_1_0>1</http_1_0>
  </options>
</cc_config>

Save the file, then exit and restart BOINC.

Now try to make contact with the project. This may take a couple of tries, depending on how big the internet cache is on your system.

You may want to flush your DNS-cache to make sure you make a clean contact. To do so click the Windows Start button->Run, type ipconfig /flushdns and press Enter. There is a space between the 'g' and the '/'.

If this still doesn't work, then there has been a change at your ISP. You will have to contact them to figure out what that was and how to get around it.
 

Scheduler request failed: Failed sending data to the peer

FAQ: Scheduler request failed: Failed sending data to the peer
Title: Scheduler request failed: Failed sending data to the peer
Author: Jorden
Views: 68681
Category: 06. BOINC Client Common Errors
Available in: English
Created: 19/05/2008 02:26:39
Last Modified: 09/03/2010 09:24:41

Contents:

This error is given by libCurl in BOINC, which handles the communications.
You will see it if you are blocking non-HTTP traffic on TCP port 80 and 443, either by not allowing BOINC through your software firewall, or not specifying that non-HTTP traffic can occur through your hardware firewall.

 

Scheduler request failed: HTTP internal server error

FAQ: Scheduler request failed: HTTP internal server error
Title: Scheduler request failed: HTTP internal server error
Author: Jorden
Views: 59695
Category: 06. BOINC Client Common Errors
Available in: English
Created: 25/11/2009 08:29:13
Last Modified: 25/11/2009 11:41:03

Contents:

Make note: First and foremost, this is not a problem with your PC or your internet connection, but always a problem with the server at the project. Even if you have multiple computers, where others can reach the project perfectly, just one or two cannot, it's not a problem with those computers.

PCSupport's page on HTTP 500 Server Error teaches us:

Quote:
Cause
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.

Resolution
The 500 Internal Server Error is a "server-side" error, meaning the problem is not with your PC or Internet connection but instead is a problem with the web site's server.


You have to know that on a lot of projects you're not dealing with just one server, but a whole range of them. Think of the entrance to a station, people going in will go left, right and center, depending on their destination.

It's the same with how your computers contact a project, some go left and make normal contact with the servers behind the main server. Others go right, but find that something is amiss down there. They will show the returned error messages.

What you can do?
First check on the project's front page in the News what it says there, check in the forums, and server status pages of the project if there are problems. If there are, just wait them out. You can post about your problem in one of the threads that have probably sprung up already, if only to voice your concern.

Second, check back at intervals if the problem has been fixed. Your BOINC client does the same thing, it will retry to do its thing every so many minutes to hours. It really doesn't help if you keep clicking Update, the problem at the servers won't be fixed earlier if you do that!

Third, be patient. Remember that most of these projects run on a shoestring budget, they really do not have crews of people slaving over the servers 24 hours a day, 7 days a week. These people have their own hobbies and family as well, just like you do. And in some cases they are right across on the other side of the world, so even if you're experiencing the middle of the day, they could be having the middle of their night, still.

In the end these problems usually fix themselves.
 

Scheduler request failed: Server returned nothing (no headers, no data)

FAQ: Scheduler request failed: Server returned nothing (no headers, no data)
Title: Scheduler request failed: Server returned nothing (no headers, no data)
Author: Jorden
Views: 58810
Category: 06. BOINC Client Common Errors
Available in: English
Created: 05/03/2010 09:20:42
Last Modified: 05/03/2010 09:20:42

Contents:

The message "Scheduler request failed: Server returned nothing (no headers, no data)" is generally a message that the Scheduler "refused" the connection (Retry x.xx seconds later) or that your communications couldn't get fully through to the server.

Anywhere between BOINC 5.10.45 and 6.10.18 a bug crept into libCurl (which handles the communications in BOINC), that would corrupt the TCP/IP DNS stack that your OS (and thus BOINC) uses to know where servers are.

If you are still on an older version of BOINC, try to flush the DNS cache.
In Windows this is done by typing ipconfig /flushdns from a command prompt.

Or update to the latest BOINC version. At the time of writing, BOINC 6.10.36 should be the new or upcoming recommended version.
 

Signals list used in BOINC.

FAQ: Signals list used in BOINC.
Title: Signals list used in BOINC.
Author: Jorden
Views: 73510
Category: 06. BOINC Client Common Errors
Available in: English
Created: 25/08/2007 13:54:21
Last Modified: 24/03/2010 19:22:17

Contents:

Signals are used to tell a process that an event has occurred. It's mainly used in the Linux/Unix versions of BOINC to relay information back to the user.

BOINC core client sends only signal 9, which is used to abort applications. (SIGKILL)

But BOINC also captures signals.
Signal 1: Hang up. (SIGHUP)
Signal 2: Interrupt signal. (SIGINT)
Signal 3: Quit signal. (SIGQUIT)
Signal 15: Termination signal. (SIGTERM)

SIGPWR is sent when a power failure is imminent; for example, when the battery is running low on a laptop or when a power failure forces a server to switch to an uninterruptible power supply. Programs would be expected to synchronise state to permanent storage to ensure that if the system powers off data is not lost.

In all cases BOINC makes a graceful exit.

The complete list of signals:

Quote:
1. SIGHUP: Hang up.

2. SIGINT: This Signal is sent to the foreground process when a user types C at the terminal keyboard.

3. SIGQUIT: Quit (ASCII FS)

4. SIGILL: Illegal instruction

5. SIGTRAP: Trace trap (not reset when caught)

6. SIGABRT/SIGIOT: The Abort signal or IO Terminate instruction. Currently only used by the assert macro to terminate the program when an assertion fails, and by the abort function.

7. SIGUNUSED: spare code

8. SIGFPE: Floating point exception

9. SIGKILL: The default action of this Signal (termination) cannot be changed. This provides a sure-fire means of stopping an otherwise unstoppable process.

10. SIGUSR1: A Signal reserved for application authors. The meaning will change from application to application.

11. SIGSEGV: Segmentation violation. The invalid storage access (Segmentation Violation) signal.

Generated in response to any of the following exceptions:

* Bound range exceeded in BOUND instruction (Interrupt 05h),
* Double Exception or an exception in the exception handler (Interrupt 08h),
* Segment Boundary violation by co-processor (Interrupt 09h),
* Invalid TSS (Interrupt 0Ah),
* Segment Not Present (Interrupt 0Bh),
* Stack Fault (Interrupt 0Ch),
* General Protection Violation (Interrupt 0Dh), or
* Page Fault (Interrupt 0Eh).

Note that Interrupt 09h is only generated on 80386 processor; i486 and later CPUs cause Interrupt 0Dh when the co-processor accesses memory out of bounds. The Double Exception, Invalid TSS, Segment Not Present, Stack Fault, GPF, and Page Fault exceptions will cause an error code to be printed, if it is non-zero.

12. SIGUSR2: A Signal reserved for application authors. The meaning will change from application to application.

13. SIGPIPE: Whenever a process tries to write on a pipe with no readers, it is sent this Signal. SIGALRM SIGALRM is sent when an alarm timer expires (counts down to zero). An application can start an alarm timer with the alarm(2) system call.

14. SIGALRM: Alarm clock

15. SIGTERM: This is the default Signal sent by kill(1). Use of this Signal allows applications to clean up (delete temporary files, free system resources like semaphores, etc) before terminating at the user's bequest.

16. SIGUSR1: A Signal reserved for application authors. The meaning will change from application to application.

17. SIGCHLD: A process receives this Signal whenever a child process is stopped or terminates. gsh uses this to keep track of jobs, and the wait system call waits for this Signal to arrive before exiting.

18. SIGCONT: To restart a stopped process, send this Signal.

19. SIGSTOP: This Signal is used to stop a process' execution temporarily. Like SIGKILL, processes are not allowed to install a handler for this Signal.

20. SIGTSTP: This is similar to SIGSTOP, but is sent when the user types Z at the keyboard. Unlike SIGSTOP, this Signal can be ignored, caught, or blocked.

21. SIGTTIN: 21 This signal also stops a process. It is sent to background jobs that try to get input from the terminal.

22. SIGTTOU: Similar to SIGTTIN, but is sent when a background process tries to write to the terminal. This behavior is optional and is by default turned off.
 

Time of day

FAQ: Time of day
Title: Time of day
Author: Jorden
Views: 71804
Category: 06. BOINC Client Common Errors
Available in: English
Created: 14/03/2007 13:29:57
Last Modified: 14/03/2007 13:29:57

Contents:

When you see the message "Time of day" in your messages log, you have set BOINC to only crunch between certain times. At all other times it will halt crunching and display that message.

This is set in your General Preferences, through "Do work only between the hours of X and Y" or through the Simple GUI (5.8 and above), Preferences, "Do work only between X and Y".

 

Waiting for memory (5.8 and above)

FAQ: Waiting for memory (5.8 and above)
Title: Waiting for memory (5.8 and above)
Author: Jorden
Views: 71930
Category: 06. BOINC Client Common Errors
Available in: English
Created: 14/03/2007 13:25:52
Last Modified: 14/03/2007 13:25:52

Contents:

When you're met by the message "waiting for memory" you have a BOINC client 5.8 or above, which makes use of the new memory options in your General Preferences.

Disk and memory usage
Use at most 100 GB disk space
Leave at least 0.1 GB disk space free
Use at most 90% of total disk space
Write to disk at most every 90 seconds
Use at most 75% of page file (swap space)

Use at most 50% of memory when computer is in use
Use at most 90% of memory when computer is idle


A striking example of this error is if you have 512MB of base memory, you run BOINC when the computer is in use. At that time you have only got 256MB of memory for your project(s). If you then also save applications to memory when switching between them, you will get into trouble.

Adjust the settings to your needs and save the changes, then update BOINC.
 

Copyright © Neil Munday 2008