-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Boinc client unable to properly communicate with BOINC server (internal 500 error) #16
Comments
Good to hear about the progress! Re: the error, I don't think its related to no workunits, probably something is actually wrong. Do you see anything in You could also try enabling some client debug flags, although I'm not sure that'll help, my guess is it'll be in one of aforementioned logs. |
Error 500 means the scheduler crashed.
This gives you a stack trace for the crash, -- David On 8/29/2016 8:14 AM, grctest wrote:
|
I'll look into the debug flags, in the meantime these are the logs you mentioned: Apache2 - Access.log: (IP omitted)
Apache2 - Errors.log (Best bet @ what's gone wrong?)
log_boincserver - antique_file_deleter.out
log_boincserver - notify (no timestamp, could be old) A couple of the other logs in log_boincserver were similar to the above log, but that's probably because the message boards were disabled.. Edit: @davidpanderson I've added the <debug_req_reply_dir> entry to my config.xml file & generated the following files: I'll install gdb on the project server to get the stack trace soon, thanks. Edit:
|
I think that error indicates you ran "gdb" instead of "gdb cgi" ? Or maybe you didn't run from "project/cgi-bin" so the executable wasn't found ? |
I tested the following:
I did not run gdb from the project/cgi-bin folder. Schedule request file collected from the client.
Schedule request debug file created by the server:
Could this have been caused by adding new fields to the BOINC website and SQL table? |
Sounds very plausible. I don't think boinc-server-docker compiles the scheduler with debug info which makes reading that above stack trace difficult, you could add Alternatively, the only place in the BOINC source that I see a call to |
Added --enable-debug to the ./configure command, and successfully ran the command but it shows a very similar output:
Most likely culprits: Going to try edit the 3 files above to fix this ongoing issue. I'm most uncertain about these lines: (Perhaps I need to split it up into multiple lines instead of 1?) I don't recall adding any new 'double' fields anywhere.. |
Sounds like you're on the right track so this may not be necessary, but just remembered you also need to execute |
Relevant line in boinc_db.cpp: https://github.com/grctest/project-rain-site/blob/master/BOINC%20Server%20files/db/boinc_db.cpp#L427 The lines before 427 were where I added the new fields, I pretty much just copied the format of the postal code. I believe I need to redo the boinc_db and boinc_db_types files.
|
If you need to add more per-user info to the database, you might want to do this using a new table that references the user table. See, e.g. the user_submit table. |
Ok, I've begun moving the new fields out of the user table into dedicated tables: I'll close this issue for the time being - I've got to figure out what to edit in the BOINC web server PHP to apply the new user data to the new table. Cheers, guys! |
I've moved the new fields into its own table called project_rain, however I've hit a new issue due to my lack of c++ knowledge (only the linked bottom log is relevant, the prior logs are previous builds). I'd appreciate some pointers as to what I've done wrong if you've got some spare time: https://github.com/grctest/project-rain-site/issues/3#issuecomment-243955881 Cheers :) |
This means that a derived class doesn't define one of the virtual functions On 9/1/2016 3:18 PM, grctest wrote:
|
Quick follow up: https://steemit.com/beyondbitcoin/@cm-steem/project-rain-update-regarding-development TL;DR: I managed to create the new table & present the data on the web server. Thanks for the help with this issue! :) |
Hey,
I've been making some good progress with my BOINC project, but I've run into an issue with my project:
https://github.com/grctest/project-rain-site/issues/2
This is preventing me from properly connecting to my project within the BOINC manager client - the account name and team fields do not appear as a result.
My main aim is to provide the ability to match one's CPID (which needs to merge with other project's CPIDs) to multiple cryptocurrency addresses/accounts, so distributing work units isn't planned at the moment.
Without work units, will I continue to encounter this 'internal 500 error'? Or has something else potentially caused this issue?
I'm going to re-fork the boinc-server-docker repo with the aim of not breaking.. what I may have broken.. lol..
Cheers.
The text was updated successfully, but these errors were encountered: