Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: up2date -l several times in a row causes exception

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Back to topic list

Re: up2date -l several times in a row causes exception

Reply

Author hunterm
Full name Hunter Matthews
Date 2003-08-13 11:37:33 PDT
Message I've not tagged a 1.5.x release in the CVS repo lately because there
were a number of deep things that needed doing, and I'm trying NOT to
tag a release unless I've tested it here locally.

HOWEVER, you seem to be our heaviest tester in a while - is there any
chance you could give CVS head a try? There are _some_ fixes in CVS head
(and a number of cleanups) that might make your usage easier.

If you can't checkout CVS head, I'll tag and build a release for
everyone to play with.



On Wed, 2003-08-13 at 14:26, Dallas L. Engelken wrote:
> well, i've finally got a working channel on 1.5.5rc1/redhat8. woo hoo
> :). here is something i find very very strange...
>
>
> i run, up2date -l, 7 times in a row (random pauses between each) on my
> client.... all of them succeed with the folling information.
>
> [root@mailgw /]# up2date -l
>
> Fetching package list for channel: redhat-linux-i386-7.3...
> ####################​####################​
>
> Fetching Obsoletes list for channel: redhat-linux-i386-7.3...
> ####################​####################​
>
> Fetching rpm headers...
> ####################​####################​
>
> Name Version Rel
> --------------------​--------------------​------------------
> wget 1.8.2 4.73
>
>
> on the 8th time, i get
>
> [root@mailgw /]# up2date -l
> Error communicating with server. The message was:
> Broken response from the server.
>
> then, i can begin the sequence again. the communicating error occurs on
> every 7th or 8th consecutive attempt. it doesnt matter how long a pause
> you put in between each try.. has anyone else seen this yet? or has
> anyone else even tried this yet.. if not, please do and see if you get
> the same results.
>
>
> when the communication error occurs, the following info is in the log...
>
> Aug 13 13:04:50 Dispatching: up2date.login
> Aug 13 13:04:50 /usr/share/current/a​pi/up2date.py:login(​{'sysid_string':
> '<sysid_string not logged>'})
> Aug 13 13:04:50 /usr/share/current/a​rchtab.py:getCannonA​rch({'arch':
> 'i686'})
> Aug 13 13:04:50 arch: i386, rel: 7.3
> Aug 13 13:04:50 ERROR: Recognized function up2date.login blew up with
> undefined error
> Aug 13 13:0450 : EXCEPTION in /usr/share/current/c​urrent_apache.py,
> callAPIMethod(), 305 [logException()]
> Traceback (most recent call last):
> File "/usr/share/current/​current_apache.py", line 291, in
> callAPIMethod
> result = apply(func, params)
> File "/usr/share/current/​api/up2date.py", line 51, in login
> si.getattr('os_release'))
> File "/usr/share/current/​db/postgres/postgres​.py", line 684, in
> getCompatibleChannels
> self.cursor.execute("""select name, label, arch, description,
> File "/usr/lib/python2.2/​site-packages/pgdb.p​y", line 189, in execute
> self.executemany(operation, (params,))
> File "/usr/lib/python2.2/​site-packages/pgdb.p​y", line 210, in
> executemany
> raise OperationalError, "internal error in '%s'" % sql
> OperationalError: internal error in 'select name, label, arch,
> description,
> lastupdate from channel
> where arch = 'i386'
> and osrelease = '7.3''
> Aug 13 13:04:50 exception said: internal error in 'select name, label,
> arch, description,
> lastupdate from channel
> where arch = 'i386'
> and osrelease = '7.3''
>
>
> dallas
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
> For additional commands, e-mail: users-help at current dot tigris dot org
--
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.


--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
For additional commands, e-mail: users-help at current dot tigris dot org

« Previous message in topic | 2 of 3 | Next message in topic »

Messages

Show all messages in topic

up2date -l several times in a row causes exception dallase Dallas Engelken 2003-08-13 11:26:22 PDT
     Re: up2date -l several times in a row causes exception hunterm Hunter Matthews 2003-08-13 11:37:33 PDT
     Re: up2date -l several times in a row causes exception jwbernin John Berninger 2003-08-13 11:44:01 PDT
Messages per page: