Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: problem with current

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

current
Discussion topic

Back to topic list

Re: problem with current

Reply

Author theslack
Full name Jack Neely
Date 2005-06-20 17:51:35 PDT
Message Jose,

Sorry for the delay in getting back to you. Also, please keep
discusion of Current on the Current mailing lists. That way others
can benifit from out conversations and possibly offer different ideas.

In the 1.6.x series of Current the cadmin tool sorta has the idea that
you might want to be able to admin the Current server remotely.
Although, this is not tested or supported. In cases where I'm using
Current on a machine that I also want to get packages/information from
an RHN source I keep two copes of the config files in
/etc/sysconfig/rhn/. One setup for RHN and one for the Current
server. I switch them out as needed.

Jack Neely

On 6/13/05, Jose Vicente Ortega <jvortega at txwes dot edu> wrote:
> Jack,
>
> I am gong to give it another shot at installing current, but would you be
> kind enough to briefly explain how to go about setting up a current server?
>
> RHN--------up2date/current server-----------Server1
> |
> |
> ------------Server2
> |
> |
> ------------Server3
>
> Would I set up a db on the current server and then create channels on
> server 1, 2 and 3.... using cadmin create_channel ######### ???
>
> Thanks,
>
> JV
> At 08:40 PM 4/6/2005, you wrote:
> >Jose,
> >
> >This is just something that has to be worked carefully around. In
> >Current 1.6.x and below cadmin always uses the server specificed in
> >/etc/sysconfig/rhn/up2date. In 1.7.1 cadmin can do the same or you
> >can provide a -s option to manuallt specify a server URL. Run "cadmin
> >--help" for details.
> >
> >Cadmin does this for two reasons. In most cases your up2date client
> >should be pointed at your Current server for it to work with Current.
> >(This is a little different in your case.) Secondly, because up2date
> >has some very handy code for working with XMLRPC servers such as RHN
> >and Current.
> >
> >Although cadmin has been designed to run on a different machine that
> >the Current server, in practice I'm not sure this has been done. I am
> >planning to make a subpackage that contains cadmin so you can easily
> >install it on a different machine than the Current server. But, I
> >haven't gotten there yet.
> >
> >Hope this helps,
> >Jack
> >
> >On Apr 6, 2005 12:00 AM, Jose Vicente Ortega <jvortega at txwes dot edu> wrote:
> > > Jack. I must be confused on what I am doing.
> > >
> > > I want to have a local server pull down updates from redhat and other
> > > servers to point to this local server. I am currently working on the local
> > > server.
> > >
> > > Should I be configuring this on the clients and no configuration is
> > > required on the local server where updates will help??
> > >
> > > JV
> > >
> > > At 10:45 PM 4/5/2005, you wrote:
> > > >You are running cadmin as a user that cannot access
> > > >/etc/sysconfig/rhn/up2date and the up2date rpc server code is using
> > > >the default server to contact. (Although, I put some code in there to
> > > >catch this.) But in any way, you are running cadmin against a real
> > > >RHN server versus your Current server.
> > > >
> > > >Use the -s option to cadmin, or fix /etc/sysconfig/rhn/up2date and see
> > > >what that does for you.
> > > >
> > > >Jack
> > > >
> > > >On Apr 5, 2005 11:26 PM, Jose Vicente Ortega <jvortega at txwes dot edu> wrote:
> > > > > Good call Jack. It worked, but now I have another issue.
> > > > >
> > > > > When I ran
> > > > >
> > > > > cadmin create_channel -r AS4 -a i386 -l AS4 -n rhel-i386-as-4
> > > > >
> > > > > I got the following error.
> > > > >
> > > > > CADMIN - Current Administration Text Interface
> > > > > Licensed under the GNU GPL version 2.0 or greater.
> > > > > Traceback (most recent call last):
> > > > > File "/usr/sbin/cadmin", line 123, in ?
> > > > > main()
> > > > > File "/usr/sbin/cadmin", line 118, in main
> > > > > module.run(server, commandOpts)
> > > > > File "/usr/share/current/​admin/create_channel​.py", line 58, in run
> > > > > result = rpcServer.doCall(ser​ver.cadmin.createCha​nnel, chan)
> > > > > File "/usr/share/rhn/up2d​ate_client/rpcServer​.py", line 309, in
> > doCall
> > > > > ret = apply(method, args, kwargs)
> > > > > File "/usr/lib/python2.3/​xmlrpclib.py", line 1029, in __call__
> > > > > return self.__send(self.__name, args)
> > > > > File "/usr/share/rhn/up2d​ate_client/rpcServer​.py", line 45, in
> > _request1
> > > > > ret = self._request(methodname, params)
> > > > > File "/usr/lib/python2.3/​site-packages/rhn/rp​clib.py", line 308, in
> > > > _request
> > > > > verbose=self._verbose
> > > > > File "/usr/lib/python2.3/​site-packages/rhn/tr​ansports.py", line
> > 184, in
> > > > > request
> > > > > return self._process_response(fd, connection)
> > > > > File "/usr/lib/python2.3/​site-packages/rhn/tr​ansports.py", line
> > 212, in
> > > > > _process_response
> > > > > return self.parse_response(fd)
> > > > > File "/usr/lib/python2.3/​site-packages/rhn/tr​ansports.py", line
> > 236, in
> > > > > parse_response
> > > > > return u.close()
> > > > > File "/usr/lib/python2.3/​xmlrpclib.py", line 742, in close
> > > > > raise Fault(**self._stack[0])
> > > > > xmlrpclib.Fault: <Fault -1: "While running 'cadmin.createChannel':
> > > > > caught\nserver.apac​heRequest.UnknownXML​ : Invalid request received
> > (class
> > > > > xmlrpc.cadmin is not defined (function = createChannel)).\n">
> > > > >
> > > > >
> > > > > At 09:05 AM 4/5/2005, you wrote:
> > > > > >Your db_type isn't recognized. Did you try "pysqlite"? The SQLlite
> > > > > >db is the only database supported so far in 1.7.x. Saves me from
> > > > > >having to beat on all three all the time.
> > > > > >
> > > > > >Jack
> > > > > >
> > > > > >On Apr 5, 2005 12:49 AM, Jose Vicente Ortega <jvortega at txwes dot edu>
> > wrote:
> > > > > > > I tried using Version: 1.7.1 on RHEL AS4 and installed
> > > > > > >
> > > > > > > python-sqlite-0.5.0-​1.2.el4.rf.i386.rpm
> > > > > > > sqlite-2.8.16-1.2.el​4.rf.i386.rpm
> > > > > > >
> > > > > > > I get the following error when I issue the cinstall initdb
> > > > > > >
> > > > > > > Traceback (most recent call last):
> > > > > > > File "/usr/sbin/cinstall", line 191, in ?
> > > > > > > main()
> > > > > > > File "/usr/sbin/cinstall", line 158, in main
> > > > > > > db.selectBackend(config)
> > > > > > > File "/usr/share/current/​db/__init__.py", line 37, in
> > selectBackend
> > > > > > > raise Exception("unknown backend type")
> > > > > > > Exception: unknown backend type
> > > > > > >
> > > > > > > This used to work when I had the current.conf configured for
> > mysql and
> > > > > > > running ver 1.6 but failed when I tried to create a channel, so I
> > > > decided
> > > > > > > to upgrade....
> > > > > > >
> > > > > > > Any ideas....
> > > > > > >
> > > > > > > JV
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > >
> > >
>
>

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

Re: problem with current theslack Jack Neely 2005-06-20 17:51:35 PDT
Messages per page: