Re: 1.4.0 released

well, the error is even shorter now :

[Tue Sep 24 18:37:46 2002] [error] PythonHandler current_apache:   File 
/usr/lib/python1.5/site-packages/mod_python/apache.py", line 185, in
Dispatch
    result = object(req)
[Tue Sep 24 18:37:46 2002] [error] PythonHandler current_apache:   File 
/usr/share/current/current_apache.py", line 190, in handler
    apacheLog('Result = %s' % pprint.pformat(result), NOTICE)
[Tue Sep 24 18:37:46 2002] [error] PythonHandler current_apache: NameError:
NOTICE

current log logs the same data i send earlier. i can send it privatelly if
you need it
 
-------Original Message-------
 
From: [email protected]
Date: éåí ùìéùé 24 ñôèîáø 2002 17:29:17
To: Current Server Mailing List
Cc: Anthony Mendoza; Alex Kramarov
Subject: Re: [Current-server] 1.4.0 released
 
There's two bugs here:
 
1) Somethings breaking in one of the server code paths, and I'm not sure
what yet.
 
2) The logging isn't including enough information to identify #1
 
Please apply the following patch to current_apache.py
(Its in /usr/share/current/ by default)
 
and restart the server. This too may fail, but it'll get me closer.
I'm looking through the API code paths now to see if I can find whats
doing this.
 
 
===== current_apache.py 1.23 vs edited =====
--- 1.23/src/current_apache.py Thu Sep 19 00:37:11 2002
+++ edited/current_apache.py Tue Sep 24 11:24:37 2002
@@ -64,18 +64,20 @@
apacheLog("Starting backend", 'NOTICE')
 
# Config object
+ apacheLog("Getting the server configuration", 'INFO')
config.cfg = config.Config(config.defaults)
config.cfg.load()
 
# Logging
# We need logging running before we can init the database.
apacheLog("Starting logging", 'INFO')
-
logfile = config.cfg.getItem('log_file')
level = int(config.cfg.getItem('log_level'))
logconfig(level, open(logfile, "a", 0))
apacheLog("Using current log %s" % logfile, 'INFO')
 
+ log("Current v%s starting up" % config.VERSION, MANDATORY)
+
# Database 
# In the future, the database may need to be up before auth
packagedb.db = packagedb.PackageDB()
@@ -184,6 +186,8 @@
except:
logException()
return apache.HTTP_BAD_REQUEST
+
+ apacheLog('Result = %s' % pprint.pformat(result), NOTICE)
 
return sendClientResult(req, result)
 
 
 
On Mon, 2002-09-23 at 22:58, Anthony Mendoza wrote:
> Seems to be broken for me... I deleted "current/db" and "current/www", 
> and re-ran cadmin create. the error I'm getting is:
> 
> Internal Server Error (from up2date -l)
> 
> cadmin checkperms runs fine (says everything is ok)
> cadmin checkdb runs fine (no ouput)
> 
> output snippet of apache error log:
> 
> [Mon Sep 23 19:57:18 2002] [notice] Inside the PythonHandler
> [Mon Sep 23 19:57:18 2002] [error] PythonHandler current_apache: 
> Traceback (innermost last):
> [Mon Sep 23 19:57:18 2002] [error] PythonHandler current_apache: File 
> "/usr/lib/python1.5/site-packages/mod_python/apache.py", line 185, in 
> Dispatch result = object(req)
> [Mon Sep 23 19:57:18 2002] [error] PythonHandler current_apache: File 
> "/usr/share/current/current_apache.py", line 188, in handler
> return sendClientResult(req, result)
> [Mon Sep 23 19:57:18 2002] [error] PythonHandler current_apache: File 
> "/usr/share/current/current_apache.py", line 221, in sendClientResult
> if result['type'] == 'xml':
> [Mon Sep 23 19:57:18 2002] [error] PythonHandler current_apache: 
> AttributeError: __getitem__
> 
> current.conf:
> 
> [current]
> valid_channels = redhat-i386-7.3 redhat-i386-7.2 redhat-i386-7.1 
> redhat-i386-7.0
> log_file = /fs0/log/current
> #pid_file = ./current.pid
> log_level = 0
> apache_config_file = ./current.httpd.conf
> access_check_type = user
> access_check_arg = apache
> http_port = 80
> https_port = 443
> server_secret = cookie monster mmmm good
> server_id = vioxx
> key_file = /etc/current/current.pem
> current_dir = /fs0/current
> welcome_message = Welcome to Embrace IT's up2date server.
> privacy_statement = "Privacy Statement for IT's up2date server:"
> # other channels configured same as this
> [redhat-i386-7.3]
> name = Red Hat Linux i386 7.3
> parent_channel =
> arch = i386
> os_release = 7.3
> description = Red Hat i386 7.3, with all errata applied.
> srpm_check = 0
> 
> rpm_dirs = /fs1/mirror/redhat/linux/updates/7.3/en/os/i386
> xrpm_dirs = /fs1/updates
> src_dirs =
> db_dir = /fs0/current/redhat-7.3/i386/current
> 
> On 9/20/2002 12:19 PM, Hunter Matthews had said:
> > All,
> > 6 months after 1.0 escaped, 1.4.0 has been released. Tar balls and
> > rpms on the web site/ftp site.
> > 
> > Changes from 1.3.90 to 1.4.0 were VERY minor - I fixed up the client
> > authentication checking to be consistent, and fixed one very small bug
> > in error handling code you would only hit with a database with bad
> > perms.
> > 
> > As always, test carefully and report bugs to the list. Before sending
> > your email, I'd appreciate you running cadmin checkdb and cadmin
> > checkperms first.
> > 
> > If you'd like, I'm usually hanging out on irc.openprojects.org in
> > #current.
> > 
> > 
> 
> -- 
> Anthony Mendoza
> IT & Customer Support
> [email protected]
> t: 408-585-5612 / c: 408-314-5038
> p: 888-886-7205 / f: 208-247-5501
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
-- 
Hunter Matthews Unix / Network Administrator
Office: BioScience 145/244 Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.
 
_______________________________________________
Current-server mailing list
[email protected]
http://lists.dulug.duke.edu/mailman/listinfo/current-server
 
.