[Spacewalk-list] errors on registration

64 views
Skip to first unread message

Bill Gunter

unread,
Mar 30, 2012, 10:32:28 AM3/30/12
to spacewa...@redhat.com
I recently upgraded from Spacewalk 1.0 to 1.2 (yes, we're really
behind) and I'm having problems with new system registration. The
error on using rhnreg_ks is only "Internal Server Error." The apache
error_log on the spacewalk server has something more ominous:

RHN 12257 2012/03/30 09:24:18 -05:00: ('SQLError',
<spacewalk.server.rhnSQL.sql_base.SQLError instance at 0x933f6ec>)
Exception reported from stan.natinst.com
Time: Fri Mar 30 09:19:55 2012
Exception type spacewalk.common.rhnException.rhnException
Exception while handling function registration.new_system
Request object information:
URI: /XMLRPC
Remote Host: rhel5test.natinst.com
Server Name: stan.natinst.com:443
Headers passed in:
Accept-Encoding: identity
Content-Length: 1721
Host: stan.natinst.com:443
content-type: text/xml
user-agent: rhn.rpclib.py/$Revision$
x-client-version: 1
x-info: RPC Processor (C) Red Hat, Inc (version $Revision$)
x-rhn-client-capability:
packages.verifyAll(1)=1,caneatCheese(1)=1,packages.extended_profile(2)=1,reboot.reboot(1)=1,packages.verify(1)=1,packages.runTransaction(1)=1,packages.update(2)=2,packages.rollBack(1)=1
x-rhn-transport-capability: follow-redirects=3
x-transport-info: Extended Capabilities Transport (C) Red Hat, Inc
(version $Revision$)
x-up2date-version: 1.0.6-1.el5

Exception Handler Information
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/spacewalk/server/apacheRequest.py",
line 118, in call_function
response = apply(func, params)
File "/usr/share/rhn/server/handlers/xmlrpc/registration.py", line
552, in new_system
architecture, data)
File "/usr/share/rhn/server/handlers/xmlrpc/registration.py", line
415, in create_system
newserv.use_token()
File "/usr/lib/python2.4/site-packages/spacewalk/server/rhnServer/server_class.py",
line 347, in use_token
tokens_obj, self.virt_type)
File "/usr/lib/python2.4/site-packages/spacewalk/server/rhnServer/server_token.py",
line 1022, in process_token
history["channels"] = token_channels(server, server_arch, tokens_obj)
File "/usr/lib/python2.4/site-packages/spacewalk/server/rhnServer/server_token.py",
line 115, in token_channels
rhnChannel._subscribe_sql(server_id, bc["id"], commit=0)
File "/usr/lib/python2.4/site-packages/spacewalk/server/rhnChannel.py",
line 1510, in _subscribe_sql
raise rhnException(e)
rhnException: (4068, 'ORA-04068: existing state of packages has been
discarded\nORA-04065: not executed, altered or dropped stored
procedure "SPACEWALK.QUEUE_SERVER"\nORA-06508: PL/SQL: could not find
program unit being called: "SPACEWALK.QUEUE_SERVER"\nORA-06512: at
"SPACEWALK.RHN_CHANNEL", line 149\nORA-06512: at line 1\n')

RHN 14566 2012/03/30 09:24:23 -05:00: ('SQLError',
<spacewalk.server.rhnSQL.sql_base.SQLError instance at 0x9352c4c>)
RHN 15357 2012/03/30 09:24:28 -05:00: ('SQLError',
<spacewalk.server.rhnSQL.sql_base.SQLError instance at 0x90b9bcc>)


I had a problem with the upgrade where I hit the Oracle XE size
limitation during the schema upgrade step, specifically in
103-rhnPackageChangeLog-refactoring.sql. I was eventually able to get
all the schema upgrade scripts to run but it looks like maybe it
wasn't as successful as I'd hoped? Or possibly it's the size
limitation I'm running into, but the error looks more serious than
that. We will be moving to a standard Oracle DB as soon as it's
provisioned but if I have a problem with the schema that won't help.

Any suggestions?

Thanks,

Bill
--
Bill Gunter
tula...@gmail.com
http://www.gunternation.com

"I think we delight to praise what we enjoy because the praise not
merely expresses but completes the enjoyment; it is its appointed
consummation." Reflections on the Psalms, C.S. Lewis

Spread Firefox!
http://www.spreadfirefox.com/?q=affiliates&id=22494&t=1

_______________________________________________
Spacewalk-list mailing list
Spacewa...@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Jan Pazdziora

unread,
Mar 30, 2012, 11:03:06 AM3/30/12
to spacewa...@redhat.com
On Fri, Mar 30, 2012 at 03:32:28PM +0100, Bill Gunter wrote:
> I recently upgraded from Spacewalk 1.0 to 1.2 (yes, we're really
> behind) and I'm having problems with new system registration. The
> error on using rhnreg_ks is only "Internal Server Error." The apache
> error_log on the spacewalk server has something more ominous:

[...]

> rhnException: (4068, 'ORA-04068: existing state of packages has been
> discarded\nORA-04065: not executed, altered or dropped stored
> procedure "SPACEWALK.QUEUE_SERVER"\nORA-06508: PL/SQL: could not find
> program unit being called: "SPACEWALK.QUEUE_SERVER"\nORA-06512: at
> "SPACEWALK.RHN_CHANNEL", line 149\nORA-06512: at line 1\n')

You've upgraded the schema while your Apache was still running and
application having its connections to it. That's not advisable. On the
other hand, restarting Apache should fix the problem just fine.

--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

Michael Mraka

unread,
Mar 30, 2012, 11:07:28 AM3/30/12
to spacewa...@redhat.com
Bill Gunter wrote:
% I recently upgraded from Spacewalk 1.0 to 1.2 (yes, we're really
% behind) and I'm having problems with new system registration. The
% error on using rhnreg_ks is only "Internal Server Error." The apache
% error_log on the spacewalk server has something more ominous:
%
% RHN 12257 2012/03/30 09:24:18 -05:00: ('SQLError',
% <spacewalk.server.rhnSQL.sql_base.SQLError instance at 0x933f6ec>)
...
% rhnException: (4068, 'ORA-04068: existing state of packages has been
% discarded\nORA-04065: not executed, altered or dropped stored
% procedure "SPACEWALK.QUEUE_SERVER"\nORA-06508: PL/SQL: could not find
% program unit being called: "SPACEWALK.QUEUE_SERVER"\nORA-06512: at
% "SPACEWALK.RHN_CHANNEL", line 149\nORA-06512: at line 1\n')
...
% I had a problem with the upgrade where I hit the Oracle XE size
% limitation during the schema upgrade step, specifically in
% 103-rhnPackageChangeLog-refactoring.sql. I was eventually able to get
% all the schema upgrade scripts to run but it looks like maybe it
% wasn't as successful as I'd hoped? Or possibly it's the size
% limitation I'm running into, but the error looks more serious than
% that. We will be moving to a standard Oracle DB as soon as it's
% provisioned but if I have a problem with the schema that won't help.
%
% Any suggestions?

Backend attempted to call package which was modified from another session.
So the cached state of the package in this session is no more valid.
The easiest solution is to restart Oracle XE.

% Thanks,
%
% Bill

Regards,

--
Michael Mráka
Satellite Engineering, Red Hat

Reply all
Reply to author
Forward
0 new messages