SocketServer Error - "Interrupted system call" about django-pam HOT 6 CLOSED

A few questions.

1. Is the system user a UNIX user or a Django superuser?
2. If you comment out my PAM backend in your settings does the problem still happen?

The errors seem to be happening in the socket server during a request. This would indicate the issue is not in any of the backend auth plugins. Also, there is nothing in your traceback that mentions any of my code.

from django-pam.

Thanks for responding! Answers inline

On Tue, Jun 7, 2016 at 11:59 PM, Carl J. Nobile [email protected]
wrote:

A few questions.

1. Is the system user a UNIX user or a Django superuser?

The user in question for which the login was failing was a linux system
user. With the same settings a Django superuser logs in fine.

1. If you comment out my PAM backend in your settings does the problem
   still happen?

I switched to an older fork from here (
https://github.com/tehmaze/django-pam) (looks like 1.0) and that works fine
for both system users as well as Django superusers. Using that one for now.
Can also try and do a test with the 1.0 release from your repo and revert,
though that will take me a couple of weeks to get around to as Im just
starting off travel.

The errors seem to be happening in the socket server during a request.
This would indicate the issue is not in any of the backend auth plugins.
Also, there is nothing in your traceback that mentions any of my code.

The forum posts around the internet seem to agree with your analysis.
However, since it works with the older release, I figured it might be
linked.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABMaHEoSZNwKUjrgAQgxy9S5_zIG-Y7Cks5qJbiagaJpZM4IwLSS
.

Arjun Venkatraman
हैकर (hacker)/浪人(ronin)/Open Solutions Architect, prefer animals to people,
jungles to cities and linux to windows
E-mail: [email protected]
Mobile: +91 89891 61881 (BHO + Roaming)

Web: http://mojolab.org, http://hackergram.org
Twitter: @themojolab, @arjunven, @hackergram

from django-pam.

I think you guys have the wrong Arjun!

On Thu, 9 Jun 2016 at 15:29 MojoLab [email protected] wrote:

Thanks for responding! Answers inline

On Tue, Jun 7, 2016 at 11:59 PM, Carl J. Nobile [email protected]
wrote:

A few questions.

1. Is the system user a UNIX user or a Django superuser?

The user in question for which the login was failing was a linux system
user. With the same settings a Django superuser logs in fine.

1. If you comment out my PAM backend in your settings does the problem
   still happen?

I switched to an older fork from here (
https://github.com/tehmaze/django-pam) (looks like 1.0) and that works
fine
for both system users as well as Django superusers. Using that one for now.
Can also try and do a test with the 1.0 release from your repo and revert,
though that will take me a couple of weeks to get around to as Im just
starting off travel.

The errors seem to be happening in the socket server during a request.
This would indicate the issue is not in any of the backend auth plugins.
Also, there is nothing in your traceback that mentions any of my code.

The forum posts around the internet seem to agree with your analysis.
However, since it works with the older release, I figured it might be
linked.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
#1 (comment)
,
or mute the thread
<
https://github.com/notifications/unsubscribe/ABMaHEoSZNwKUjrgAQgxy9S5_zIG-Y7Cks5qJbiagaJpZM4IwLSS

.

Arjun Venkatraman
हैकर (hacker)/浪人(ronin)/Open Solutions Architect, prefer animals to people,
jungles to cities and linux to windows
E-mail: [email protected]
Mobile: +91 89891 61881 (BHO + Roaming)

Web: http://mojolab.org, http://hackergram.org
Twitter: @themojolab, @arjunven, @hackergram

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AK8GPe_j_6x4waVSlYIfLTYbmgflrpPLks5qKBUigaJpZM4IwLSS
.

from django-pam.

Not sure how you got looped in! How do I unloop you?
On 09-Jun-2016 7:36 pm, "Arjun Venkatesh" [email protected] wrote:

I think you guys have the wrong Arjun!

On Thu, 9 Jun 2016 at 15:29 MojoLab [email protected] wrote:

Thanks for responding! Answers inline

On Tue, Jun 7, 2016 at 11:59 PM, Carl J. Nobile <
[email protected]>
wrote:

A few questions.

1. Is the system user a UNIX user or a Django superuser?

The user in question for which the login was failing was a linux system
user. With the same settings a Django superuser logs in fine.

1. If you comment out my PAM backend in your settings does the problem
   still happen?

I switched to an older fork from here (
https://github.com/tehmaze/django-pam) (looks like 1.0) and that works
fine
for both system users as well as Django superusers. Using that one for
now.
Can also try and do a test with the 1.0 release from your repo and
revert,
though that will take me a couple of weeks to get around to as Im just
starting off travel.

The errors seem to be happening in the socket server during a request.
This would indicate the issue is not in any of the backend auth
plugins.
Also, there is nothing in your traceback that mentions any of my code.

The forum posts around the internet seem to agree with your analysis.
However, since it works with the older release, I figured it might be
linked.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<

#1 (comment)

,
or mute the thread
<

https://github.com/notifications/unsubscribe/ABMaHEoSZNwKUjrgAQgxy9S5_zIG-Y7Cks5qJbiagaJpZM4IwLSS

.

Arjun Venkatraman
हैकर (hacker)/浪人(ronin)/Open Solutions Architect, prefer animals to
people,
jungles to cities and linux to windows
E-mail: [email protected]
Mobile: +91 89891 61881 (BHO + Roaming)

Web: http://mojolab.org, http://hackergram.org
Twitter: @themojolab, @arjunven, @hackergram

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
#1 (comment)
,
or mute the thread
<
https://github.com/notifications/unsubscribe/AK8GPe_j_6x4waVSlYIfLTYbmgflrpPLks5qKBUigaJpZM4IwLSS

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABMaHKTLFXg4CeM49IMpVWmaJ42b5I1rks5qKB37gaJpZM4IwLSS
.

from django-pam.

I'm not asking you to use a different version. What you need to do is comment out the entry in the settings file like this:

# Django auth backends.
AUTHENTICATION_BACKENDS = [
    #'django_pam.auth.backends.PAMBackend',
    'django.contrib.auth.backends.ModelBackend',
    ]

This will effectively remove my backend from your django app. If your problem still exists after you do this it is definitely not the fault of django-pam.

You should be installing it through pip anyway unless you just want to see my test site running.

Also, remember the user that is doing the authenticating needs to be in the UNIX shadow group or all authentications will fail.

from django-pam.

@arjunven, if you follow me or stared my project you may get emails depending on your settings. In other words you may need to change the settings on getting emails.

from django-pam.