Re: 7.2 & Problems...

Did it expire? I know that sounds silly, but my own current server
certificate expired, and some of the clients were new enough (and thus
checked carefully enough) that they didn't want to work.


On Thu, 2003-01-30 at 10:20, Christian Titulaer wrote:
> On Thu, Jan 30, 2003 at 03:46:50PM +0200, Alex Kramarov wrote:
> > i have seen that if you generate a certificate on a 7.3 machine, 7.1's didn
> > t want to connect to the server with the same error, but when i generated
> > the cert on the 7.1 - all was well. try generating the cert  on the 7.2, and
> > copy it to the 7.3 server, see what happends.
> > 
> > it seems to me like some compatibility issue between different openssl
> > versions on different rh distros
> 
> Don't think that this is an issue here, as it was running for...
> can't remember... very long...
> 
> *searchingthroughlogfiles*
> 
> Ok... the error first occured after new python was installed on
> 01/23... before this, it worked fine... so I assume that
> python-1.5.2-42.72 is broken in some way...
> 
> Here comes the log:
> [Thu Jan 23 12:29:13 2003] up2date new up2date run started
> [Thu Jan 23 12:29:13 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:13 2003] up2date updating login info
> [Thu Jan 23 12:29:13 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:13 2003] up2date logging into up2date server
> [Thu Jan 23 12:29:14 2003] up2date successfully retrieved authentication token from up2date server
> [Thu Jan 23 12:29:14 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:14 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:14 2003] up2date availablePackageList from network
> [Thu Jan 23 12:29:16 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:16 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:17 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:18 2003] up2date installing packages: ['python-1.5.2-42.72']
> [Thu Jan 23 12:29:18 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:19 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 1
> [Thu Jan 23 12:29:21 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 12:29:21 2003] up2date Removing packages from package profile: ['python-1.5.2-35']
> [Thu Jan 23 12:29:21 2003] up2date Adding packages to package profile: ['python-1.5.2-42.72']
> [Thu Jan 23 12:29:22 2003] up2date deleting /var/spool/up2date/python-1.5.2-42.72.i386.hdr
> [Thu Jan 23 12:29:22 2003] up2date deleting /var/spool/up2date/python-1.5.2-42.72.i386.rpm
> 
> But after that, there following lines are written to the log for
> a couple of times:
> [Thu Jan 23 23:58:19 2003] up2date new up2date run started
> [Thu Jan 23 23:58:19 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Thu Jan 23 23:58:19 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> 
> (but the timestamps let me think that this is rhnsd, don't ask
> why it's still running there :/
> 
> And some hours after that:
> [Fri Jan 24 04:09:03 2003] up2date new up2date run started
> [Fri Jan 24 04:09:03 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Fri Jan 24 04:09:03 2003] up2date updating login info
> [Fri Jan 24 04:09:03 2003] up2date Opening rpmdb in /var/lib/rpm/ with option 0
> [Fri Jan 24 04:09:03 2003] up2date logging into up2date server
> [Fri Jan 24 04:09:03 2003] up2date A socket error occurred: SSL_connect error, attempt #1
> [Fri Jan 24 04:09:08 2003] up2date A socket error occurred: SSL_connect error, attempt #2
> [Fri Jan 24 04:09:13 2003] up2date A socket error occurred: SSL_connect error, attempt #3
> [Fri Jan 24 04:09:19 2003] up2date A socket error occurred: SSL_connect error, attempt #4
> [Fri Jan 24 04:09:24 2003] up2date A socket error occurred: SSL_connect error, attempt #5
> [Fri Jan 24 04:09:24 2003] up2date Error communicating with server.  The message was:
> SSL_connect error
> 
> And I have no clue how to fix this :/
> 
> Regards
>   Christian
> _______________________________________________
> 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.