MORE HELP NEEDED PLEASE :)

"Jeremy Johnson" <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <F8BFD92C1373964E9327067C96AF43692D7754@EXCHSBA1.supplysolution.com>
well John Berninger helped me out on my first speed bump(thanks, duh on my part), but now im at this point.
 
When i run the up2date on the client i get the following 
[root@foo1 rhn]# up2date
Error communicating with server.  The message was:
SSL_connect error

Now im sure its a server issue, here is my problem with that:
[root@up2date docs]# /etc/init.d/current start
Starting Current(stunnel):                                 [  OK  ]
Starting Current(daemon):                                  [  OK  ]
[root@up2date docs]# !tail
tail -f /var/log/messages
Apr  5 04:46:31 up2date stunnel[3513]: remote connect: Connection refused (111)
Apr  5 04:46:32 up2date stunnel[3514]: 8080 connected from 192.168.18.201:1065
Apr  5 04:46:32 up2date stunnel[3514]: remote connect: Connection refused (111)
Apr  5 04:46:56 up2date stunnel[3384]: Received signal 15; terminating
Apr  5 04:46:57 up2date current: stunnel shutdown succeeded
Apr  5 04:46:57 up2date current: current shutdown failed
Apr  5 04:50:57 up2date stunnel[3582]: Using '8080' as tcpwrapper service name
Apr  5 04:50:57 up2date stunnel[3582]: stunnel 3.19 on i386-redhat-linux-gnu PTHREAD+LIBWRAP
Apr  5 04:50:57 up2date current: stunnel startup succeeded
Apr  5 04:50:58 up2date current: current startup succeeded
====WHEN I CONNECT FROM THE CLIENT THE FOLLOWING SHOWS===
Apr  5 04:51:41 up2date stunnel[3595]: 8080 connected from 192.168.18.201:1067
Apr  5 04:51:41 up2date stunnel[3595]: remote connect: Connection refused (111)
Apr  5 04:51:42 up2date stunnel[3596]: 8080 connected from 192.168.18.201:1069
Apr  5 04:51:42 up2date stunnel[3596]: remote connect: Connection refused (111)
Apr  5 04:51:43 up2date stunnel[3597]: 8080 connected from 192.168.18.201:1071
Apr  5 04:51:43 up2date stunnel[3597]: remote connect: Connection refused (111)
Apr  5 04:51:44 up2date stunnel[3598]: 8080 connected from 192.168.18.201:1073
Apr  5 04:51:44 up2date stunnel[3598]: remote connect: Connection refused (111)
Apr  5 04:51:45 up2date stunnel[3599]: 8080 connected from 192.168.18.201:1075
Apr  5 04:51:45 up2date stunnel[3599]: remote connect: Connection refused (111)

 
so of course 8080 isnt open,  so at this point i realized i could do 
log_file = /var/current.log
which i had hashed out, and low and behold i got more logs....great but this is what i got
 
tail -f /var/current.log
Apr 04 04:58:47 Current server v1.0.2 starting, released under the GPL
Apr 04 04:58:47 Error opening channel 'redhatalpha6.2'
Apr 04 04:58:47 Shutting down because we could not start the server

OK sooooo i just hashed that section and removed it from valid_channels = so now i have valid_channels = redhatalpha7.1 redhati386-6.2 redhati386-7.2
 
so i reastart the daemons and this is what i ended up with
 
Apr 04 05:00:09 Current server v1.0.2 starting, released under the GPL
Apr 04 05:00:09 Error opening channel 'redhatalpha7.1'
Apr 04 05:00:09 Shutting down because we could not start the server

ok now im thinking its maybe cause of this littttle line db_dir = /var/ftp/pub/errata/alpha/
and not actually having a db in it or any files just a folder to my rpms, but i dont know what to put in this file. which leads me to here and the irc channel.
 
Here is what my entrys look like
[alpha71]
label = redhatalpha7.1
name = Alpha71
parent_channel =
arch = alpha
os_release = 7.1
description = alpha 7.1 release

rpm_dirs = /var/ftp/pub/errata/alpha/7.1/
xrpm_dirs =
src_dirs =
db_dir = /var/ftp/pub/errata/alpha/

My question is what can i do to get current to listen on 8080. i know this has gotta be simple.  i am a bit lost on what  db_dir   = directory containing the current databases is, ive seen people talking about sql patch and i thought i saw some db files to download but i cant find that source.  Can someone point me to the right area. Thanks in advance
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.