Bug 54483

Summary:	Error executing code for include callback.apm
Product:	Red Hat Web Site	Reporter:	Jay Turner <jturner>
Component:	Other	Assignee:	Web Development <webdev>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Web Development <webdev>
Severity:	high	Docs Contact:
Priority:	medium
Version:	current	CC:	srevivo
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-10-16 21:42:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jay Turner 2001-10-09 19:43:02 UTC

Description of Problem:
Getting this error on app[23].rwc-colo starting on 10/8:

error executing code for include /var/www/apps/panes/login/callback.apm:
Can't locate object method "password_verify" via package "WebUser::new:
Creation of contact object failed: WebContact::fill: No match found using
query (SELECT * FROM web_contact WHERE login_uc=?) (JCLK)" at
/var/www/apps/panes/login/callback.apm line 36. <--> ; compiled to
SCALAR(0x97947f8) at /usr/lib/perl5/site_perl/5.005/Apache/ASP.pm line
3818. <--> , /usr/lib/perl5/site_perl/5.005/Apache/ASP.pm line 1550

Version-Release number of selected component (if applicable):


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Randy J. Ray 2001-10-09 21:47:43 UTC

This error was detected and addressed (via change to
/var/www/apps/panes/login/callback.apm) yesterday. It should be wending its way
through QA already.

Comment 2 Jay Turner 2001-10-11 14:40:52 UTC

These were resulting from users that don't exist in the database attempting to
log into the site (best that I can tell) and we have not had this occur since
10/8.  In addition, when attempting to log in as a user who does not exist, I
get a message on the live site now stating that the user does not exist, so I
think  this is resolved.   Can someone confirm that changes were made to correct
this?

Comment 3 Jay Turner 2001-10-16 12:45:13 UTC

Actually, I will change that.  Just got another of these errors on 10/15/01.

Comment 4 Randy J. Ray 2001-10-16 21:42:42 UTC

I have no idea how this happened again. I have checked the QA box and all three
app servers (including app1), and all have the current version of
login/callback.apm, which fixes this (a test and an exit would prevent line 36
from even being reached in this case).

Comment 5 Tom Lancaster 2002-11-20 00:45:25 UTC

Haven't seen this one in donkey's years - closing out on the assumption that
Randy's fix actually fixed it.