Couldn't perform authentication: AuthType not set

Message boards : Server programs : Couldn't perform authentication: AuthType not set
Message board moderation

To post messages, you must log in.

AuthorMessage
ThemePark

Send message
Joined: 8 Sep 13
Posts: 5
Denmark
Message 50424 - Posted: 8 Sep 2013, 9:40:58 UTC

I have been following the Quick Start guide, since the Project Cookbook is horribly outdated, and full of wrong information.

http://boinc.berkeley.edu/trac/wiki/QuickStart

I'm using the VM available from BOINC, and after setting the server up, I've downloaded the client on the host OS, which is Windows 7 in this case. I try to connect to my project, and BOINC on Windows tells me there's an error. So I end up looking at the Apache error.log and get the error mentioned in the title for the directory /test2/ and /test2/get_project_config.php

I've read a bit about .htaccess files, so I know I need to set those up, even though the Quick Start doesn't mention than being necessary. But it doesn't seem like I can make an .htaccess file for a file, only for directories, and get_project_config.php isn't in /test2/ but in /test2/html/user/

So how do I go about fixing this problem? I'm using BOINC 7.0.64, and it should be noted that I'm using a local IP, since I couldn't get it to work with my public IP.
ID: 50424 · Report as offensive
ChristianB
Volunteer developer
Volunteer tester

Send message
Joined: 4 Jul 12
Posts: 321
Germany
Message 50427 - Posted: 9 Sep 2013, 13:34:50 UTC

Hi,

what Cookbook did you use and what information is outdated? I updated the official cookbook not long ago.

What error does your BOINC Client tell you?

How did you create your project? Where did you put the project directory and have you restarted the apache after adding the http config?

A .htaccess for the user-visible webpage is not necessary so it is not mentioned. Everything is done in the apache config.

Regarding the local/public IP: I don't understand what you mean. The VM will get an IP from your local network (bridged mode, default) or share the IP of the host computer (NAT mode). In order to access the VM you have to use the IP of the VM or edit your hosts file on Windows to allow name resolution. If the VM should be accessible from outside your network (aka the Internet) you need to setup port forwarding or similar on your router.
ID: 50427 · Report as offensive
ThemePark

Send message
Joined: 8 Sep 13
Posts: 5
Denmark
Message 50502 - Posted: 14 Sep 2013, 20:06:06 UTC - in response to Message 50427.  
Last modified: 14 Sep 2013, 20:07:10 UTC

No, that is not the cookbook. This is the cookbook, and hasn't been updated for 4 years.

http://boinc.berkeley.edu/trac/wiki/CreateProjectCookbook

The error is in the topic, and I've done everything it says in this link.

http://boinc.berkeley.edu/trac/wiki/QuickStart

As for the IP, the Quick start guide tells you to use your IP for a.b.c.d, and since I'm running a virtual machine and sharing the internet connection, ifconfig gives me a local IP address which I have used.

Sorry for not responding earlier, but since I got an email when the topic was moved to another subforum, I thought I'd get one when there was an answer as well.
ID: 50502 · Report as offensive
Profile Gundolf Jahn

Send message
Joined: 20 Dec 07
Posts: 1069
Germany
Message 50505 - Posted: 15 Sep 2013, 0:41:17 UTC - in response to Message 50502.  

...I thought I'd get one when there was an answer as well.

For that, you'll have to subscribe to the thread (button at the top).

Gruß
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
ID: 50505 · Report as offensive
ChristianB
Volunteer developer
Volunteer tester

Send message
Joined: 4 Jul 12
Posts: 321
Germany
Message 50507 - Posted: 15 Sep 2013, 11:55:20 UTC

I scanned through the QuickStart you mentioned and can't find any really wrong information. Just some obsolete stuff about the test application that is already installed when running
./make_project --url_base http://a.b.c.d --test_app test

So back to troubleshooting your Apache error that I can't reproduce with the VmServer. Did you update some packages? There may be an issue with Apache 2.4 that is fixed in latest code.

Can you access http://a.b.c.d/test2/ with a browser from you host? It should display the default project website. If this is not possible please check what is in your generated test2.httpd.conf file. Did you append this to httpd.conf or did you copy it to /etc/apache2/sites-available/ ? I usually do the later which is better for future apache updates.

Regards
Christian
ID: 50507 · Report as offensive
ThemePark

Send message
Joined: 8 Sep 13
Posts: 5
Denmark
Message 50532 - Posted: 17 Sep 2013, 1:34:33 UTC - in response to Message 50507.  

@Gundolf, thanks, I'll do that right away.

@ChristianB:

It's mostly the Project Cookbook that's outdated. It mentions changing to the boinc directory early on, but there was no such directory. Using find I found some other directories with that name, but they didn't have the binaries the guide mentioned. Took me a while to realize that it's boinc-master, so that needs to be changed in both guides.

Then I was able to follow the cookbook guide until it tells you to copy the client. Only problem is that the VM doesn't come with the client installed, I looked everywhere for it to no avail. And the cookbook doesn't mention how to download it either. So maybe the VM had the client installed by default 4 years ago, but a lot has changed since then.

Yes, I have updated all packages with aptitude update and aptitude upgrade. I can access the url, but I get an Internal server error page from Apache when doing so. This is my test2.httpd.conf file:


    ## Settings for BOINC project test2

    Alias /test2 /home/boincadm/projects/test2/html/user
    Alias /test2_ops /home/boincadm/projects/test2/html/ops
    ScriptAlias /test2_cgi /home/boincadm/projects/test2/cgi-bin

    # Note: projects/*/keys/ should NOT be readable!

    <Directory "/home/boincadm/projects/test2/html">
	AuthType None
        Options Indexes FollowSymlinks MultiViews
        AllowOverride AuthConfig
        Require all granted
        Order allow,deny
        Allow from all
    </Directory>

    <Directory "/home/boincadm/projects/test2/cgi-bin">
        Options ExecCGI
        AllowOverride AuthConfig
        Require all granted
        Order allow,deny
        Allow from all
    </Directory>



As I have been following the quick start guide to a T, I have appended that file to /etc/apache2/httpd.conf. If the latter is better, then that is another thing that needs to be updated. But still, the error message is pretty clear about what needs to be done, I need another rule for html/user/get_project_config.php, but I couldn't find a way to add a rule for just a file. So I don't know what to add to the conf file.
ID: 50532 · Report as offensive
ChristianB
Volunteer developer
Volunteer tester

Send message
Joined: 4 Jul 12
Posts: 321
Germany
Message 50539 - Posted: 17 Sep 2013, 7:58:45 UTC

I will see what I can do to the Cookbook you mentioned but I can't change it to only reflect the VM. It should also give you some help when trying on your own.

Meanwhile I found the problem, which is a configuration option that was added recently to allow more security with apache 2.4 but is obviously not working well with apache 2.2. You have to comment or delete the two lines that say Require all granted in your httpd.conf than restart apache and everything is working.

The QuickStart and Cookbook is based on the Debian VM so using the /etc/apache2/sites-available/ directory would be good it may and is not available on other distributions. As long as the cat to httpd.conf is working it will be the default way. As a project administrator surely will know how to change this later in a real project because the server and project needs to be secured.
ID: 50539 · Report as offensive
ThemePark

Send message
Joined: 8 Sep 13
Posts: 5
Denmark
Message 50540 - Posted: 17 Sep 2013, 11:31:40 UTC - in response to Message 50539.  
Last modified: 17 Sep 2013, 12:09:39 UTC

Well, I'll be a monkey's uncle. That did the trick! Thank you very much.

I'm a bit confused as to what you mean with using the sites-available directory, are you saying it's not available on other distributions? Because then I don't see why using it is a good idea. As for securing the server and project, I know very little about that, which is why I'm training myself using the VM. But at least now I know two ways of doing this.

Also, I'm a bit surprised that Apache is at the 2.2 version, when I ran both aptitude update, aptitude upgrade, and aptitude dist-upgrade, and I would've expected to get the latest version then.

But at any rate, thanks for your help.

Edit: Okay, not completely true. At least I get the New user dialogue now, when I use the GUI to connect. But I still can't connect, and when checking the Error Log it says "17/09/2013 13:34:09 | | Project communication failed: attempting access to reference site", but there's nothing in the apache log for that timestamp. So could this be related?
ID: 50540 · Report as offensive
ChristianB
Volunteer developer
Volunteer tester

Send message
Joined: 4 Jul 12
Posts: 321
Germany
Message 50541 - Posted: 17 Sep 2013, 12:30:24 UTC - in response to Message 50540.  

I'm a bit confused as to what you mean with using the sites-available directory, are you saying it's not available on other distributions? Because then I don't see why using it is a good idea. As for securing the server and project, I know very little about that, which is why I'm training myself using the VM. But at least now I know two ways of doing this.

The sites concept of apache is for advanced users I presume and AFAIK only used on Debian based distributions. Using it on Debian is a good idea but making it a default in the documentation may mislead users of other distributions.

Also, I'm a bit surprised that Apache is at the 2.2 version, when I ran both aptitude update, aptitude upgrade, and aptitude dist-upgrade, and I would've expected to get the latest version then.

You will get the latest stable version from the wheezy branch of Debian which is at 2.2. The next stable version of Debian will ship with Apache 2.4

Edit: Okay, not completely true. At least I get the New user dialogue now, when I use the GUI to connect. But I still can't connect, and when checking the Error Log it says "17/09/2013 13:34:09 | | Project communication failed: attempting access to reference site", but there's nothing in the apache log for that timestamp. So could this be related?

That is a dns-lookup issue on your host. The master url of your project should be something like debian6.localdomain and your host can't resolve this name to an IP address. The simplest thing to do is add a line to your hosts file (on windows this is in C:\Windows\system32\drivers\etc) that resolves the hostname of the VM to the IP of the VM. You can find the hostname used by BOINC in your config.xml or html/user/scheduler.txt and the IP with "sudo ifconfig"
ID: 50541 · Report as offensive
ThemePark

Send message
Joined: 8 Sep 13
Posts: 5
Denmark
Message 50542 - Posted: 17 Sep 2013, 13:07:31 UTC - in response to Message 50541.  

I must apologize for this, this was actually not an issue with the hosts file, but an error on my part. I've made two projects, test and test2, one using my public IP, and one with the VMs local IP in the 192.168.xxx.xxx range. What I had done was to use the wrong IP for the test project. Once I changed the IP, my project got added just fine.

As for Debian, I'm actually using Squeeze. But I'll look into updating Apache to 2.4 myself, since Wheezy and Squeeze are still using 2.2.

Anyway, thank you so very much for your help. I would have never figured this out myself, so your help has been invaluable, and has actually taught me a few valuable things now. So thank you again.
ID: 50542 · Report as offensive

Message boards : Server programs : Couldn't perform authentication: AuthType not set

Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.