Login | Register
My pages Projects Community openCollabNet
Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Reply to message

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

* = Required fields
* Subject
* Body
Send reply to
Author (directly in email)
Please type the letters in the image above.

Original message

Author draco <manannan@cfl.rr.com>
Full name draco <manannan@cfl.rr.com>
Date 2003-04-25 15:25:44 PDT
Message On Fri, Apr 25, 2003 at 05:03:53PM -0500, Paul F. Williams wrote users:
> I believe I have installed the server and client
> in accordance with the documentation I found
> in current.


> File "/usr/share/current/​configfile.py", line 214, in options
> raise NoSectionError(section)
> NoSectionError: No section: current

> Anyone have any idea what is happening.

Your config file is broken. You're missing the [current] section, or the
[current] section header.

> I have several questions in addition.
> 1) Does the server name need to be the real name
> of the server (so reverse name lookup works)
> or can it be a CNAME?

For SSL, yes. Since up2date does as much as possible over SSL, yes, it
needs to be your A record, at least as far as config files and SSL
certificates go. Your hostname can be whatever.

> 2) Since it is documented that apache cannot be running
> when you run cadmin, I would recommend the notice
> be moved to the beginning of the documentation.
> Also, why can't you run cadmin when apache is running?

Because shelve (the python datastore used in 1.4) doesn't have any locking
or other advanced "hey, look! the data's changed/changing!" features.
Therefore, if you use cadmin while apache/current is running, you run the
risk of data corruption, screwed up clients, etc.

That said, the problem will be going away in 1.5+, as that is moving over
to a postgres backend, which has all that database yumminess.

> (it might even be a good idea for the software to fail
> if apache is running and notify you to stop apache before
> running it).

They used to do this when current was standalone. With apache, there's no
way to know that current is currently running. For all cadmin knows, it
could just be a bare httpd install that hasn't been outfitted with current

> 3) Do you know what ports the server needs to have open,
> we have most of our ports turned off and it refused
> to connect until I opened all ports to the particular
> client.

You need to have port 443 (https) and probably 80 open. Or whatever you
tell your clients, but as you're going to have to open 2 ports anyway,
you may as well just use the standard ones.

> 4)

"I know you think you thought you knew what you thought I said,
but I'm not sure you understood what you thought I meant." -- fortune