On 12/20/06, Klaus Darilion <klaus.mailinglists@pernau.at > wrote:
Hi Mark!
Postgres should work well - I use it since ser 0.8. Just make sure that the hard disk does not get full, because this breaks the index inside postgres and postgres is getting real slow (re-create the index if it happens).
Last time I tested openser_postgres.sh it worked fine. If you find a bug please let us know.
Please check to use the latest versions from CVS (for 1.1 use CVS rel_1_1_0)
The latest version from cvs doesn't work out of the box with openser build from the release tarball, because the release tarball doesn't included /usr/sbin/openser_gen_ha1 (although I could get past this by replacing it with the md5sum equivelant).
However, the release tarball doesn't work because of this bug: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732...
So, 1. is the cvs version of rel_1_1_0 considered safe for production use? 2. if so and there are important fixes such as this in CVS, would openser.org consider releasing a point release containing such changes?
Thanks,
Mark Price
Hello,
On 12/20/06 19:36, Mark Price wrote:
On 12/20/06, *Klaus Darilion* < klaus.mailinglists@pernau.at mailto:klaus.mailinglists@pernau.at> wrote:
Hi Mark! Postgres should work well - I use it since ser 0.8. Just make sure that the hard disk does not get full, because this breaks the index inside postgres and postgres is getting real slow (re-create the index if it happens). Last time I tested openser_postgres.sh it worked fine. If you find a bug please let us know. Please check to use the latest versions from CVS (for 1.1 use CVS rel_1_1_0)The latest version from cvs doesn't work out of the box with openser build from the release tarball, because the release tarball doesn't included /usr/sbin/openser_gen_ha1 (although I could get past this by replacing it with the md5sum equivelant).
However, the release tarball doesn't work because of this bug: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732... https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732&group_id=139143
So, 1. is the cvs version of rel_1_1_0 considered safe for production use?
yes, it is the most recommended version to use -- several issues were found and fixed since 1.1.0 release.
2. if so and there are important fixes such as this in CVS,would openser.org http://openser.org consider releasing a point release containing such changes?
It is an option, and perhaps should be taken in consideration, as patch release with not so much packaging.
This may help some which want to maintain platforms updated, it is exampled with 1.0.x, bust just replace the version with 1.1.0 in the document and should work (rel_1_0_0 => rel_1_1_0) http://openser.org/dokuwiki/doku.php/install:openser-from-cvs
Cheers, Daniel
Thanks,
Mark Price
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Daniel!
I've checked the postgres script: rel_1_1_0 works fine, but there is a problem in unstable: The domain for the default admin user is asked not for serweb tables but for the plain openser tables as well. Also the subscriber table includes all the serweb columns even if serweb tables are not installed.
regards klaus
Daniel-Constantin Mierla wrote:
Hello,
On 12/20/06 19:36, Mark Price wrote:
On 12/20/06, *Klaus Darilion* < klaus.mailinglists@pernau.at mailto:klaus.mailinglists@pernau.at> wrote:
Hi Mark! Postgres should work well - I use it since ser 0.8. Just make sure that the hard disk does not get full, because this breaks the index inside postgres and postgres is getting real slow (re-create the index if it happens). Last time I tested openser_postgres.sh it worked fine. If you find a bug please let us know. Please check to use the latest versions from CVS (for 1.1 use CVS rel_1_1_0)The latest version from cvs doesn't work out of the box with openser build from the release tarball, because the release tarball doesn't included /usr/sbin/openser_gen_ha1 (although I could get past this by replacing it with the md5sum equivelant).
However, the release tarball doesn't work because of this bug: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732... https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732&group_id=139143
So, 1. is the cvs version of rel_1_1_0 considered safe for production use?
yes, it is the most recommended version to use -- several issues were found and fixed since 1.1.0 release.
2. if so and there are important fixes such as this in CVS,would openser.org http://openser.org consider releasing a point release containing such changes?
It is an option, and perhaps should be taken in consideration, as patch release with not so much packaging.
This may help some which want to maintain platforms updated, it is exampled with 1.0.x, bust just replace the version with 1.1.0 in the document and should work (rel_1_0_0 => rel_1_1_0) http://openser.org/dokuwiki/doku.php/install:openser-from-cvs
Cheers, Daniel
Thanks,
Mark Price
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello Klaus,
On 12/21/06 12:05, Klaus Darilion wrote:
Hi Daniel!
I've checked the postgres script: rel_1_1_0 works fine, but there is a problem in unstable: The domain for the default admin user is asked not for serweb tables but for the plain openser tables as well. Also the subscriber table includes all the serweb columns even if serweb tables are not installed.
I think a merge with mysql version, with an option to say the underlaying DB engine is the right solution, to be easy to maintain -- same as we did with openserctl. I will have that in mind, but the best will be to register it to tracker.
Cheers, Daniel
regards klaus
Daniel-Constantin Mierla wrote:
Hello,
On 12/20/06 19:36, Mark Price wrote:
On 12/20/06, *Klaus Darilion* < klaus.mailinglists@pernau.at mailto:klaus.mailinglists@pernau.at> wrote:
Hi Mark! Postgres should work well - I use it since ser 0.8. Just make sure that the hard disk does not get full, because this breaks the indexinside postgres and postgres is getting real slow (re-create the index if it happens).
Last time I tested openser_postgres.sh it worked fine. If you find a bug please let us know. Please check to use the latest versions from CVS (for 1.1 use CVS rel_1_1_0)The latest version from cvs doesn't work out of the box with openser build from the release tarball, because the release tarball doesn't included /usr/sbin/openser_gen_ha1 (although I could get past this by replacing it with the md5sum equivelant).
However, the release tarball doesn't work because of this bug: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732... https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732&group_id=139143
So, 1. is the cvs version of rel_1_1_0 considered safe for production use?
yes, it is the most recommended version to use -- several issues were found and fixed since 1.1.0 release.
2. if so and there are important fixes such as this in CVS,would openser.org http://openser.org consider releasing a point release containing such changes?
It is an option, and perhaps should be taken in consideration, as patch release with not so much packaging.
This may help some which want to maintain platforms updated, it is exampled with 1.0.x, bust just replace the version with 1.1.0 in the document and should work (rel_1_0_0 => rel_1_1_0) http://openser.org/dokuwiki/doku.php/install:openser-from-cvs
Cheers, Daniel
Thanks,
Mark Price
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello I just installed version 1.1.1 and Im getting this error: 0(17728) ERROR: load_module: could not open module </usr/local/lib/openser/modules/postgres.so>: libpq.so.5: cannot open shared object file: No such file or directory
But I have compiled OpenSER with postgres support. And postgres.so is in /usr/local/lib/openser/modules/
[root@vox openser-1.1.1-notls]# ls -la /usr/local/lib/openser/modules/postgres.so -rwxr-xr-x 1 root root 97117 Mar 6 12:42 /usr/local/lib/openser/modules/postgres.so [root@vox openser-1.1.1-notls]#
Whats the problem? Thanks Joao pereira
Is "libpq.so.5" located with you issue the "ldconfig -p" command ?
Regards, Norm
Joao Pereira wrote:
Hello I just installed version 1.1.1 and Im getting this error: 0(17728) ERROR: load_module: could not open module </usr/local/lib/openser/modules/postgres.so>: libpq.so.5: cannot open shared object file: No such file or directory
But I have compiled OpenSER with postgres support. And postgres.so is in /usr/local/lib/openser/modules/
[root@vox openser-1.1.1-notls]# ls -la /usr/local/lib/openser/modules/postgres.so -rwxr-xr-x 1 root root 97117 Mar 6 12:42 /usr/local/lib/openser/modules/postgres.so [root@vox openser-1.1.1-notls]#
Whats the problem? Thanks Joao pereira
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello No, I dont have libpq.so.5 ... :( I will seacrh the web for it Thanks Joao Pereira
[root@vox ~]# ldconfig -p | grep libpq libpq.so.4 (libc6) => /usr/lib/libpq.so.4 [root@vox ~]#
Norman Brandinger wrote:
Is "libpq.so.5" located with you issue the "ldconfig -p" command ?
Regards, Norm
Joao Pereira wrote:
Hello I just installed version 1.1.1 and Im getting this error: 0(17728) ERROR: load_module: could not open module </usr/local/lib/openser/modules/postgres.so>: libpq.so.5: cannot open shared object file: No such file or directory
But I have compiled OpenSER with postgres support. And postgres.so is in /usr/local/lib/openser/modules/
[root@vox openser-1.1.1-notls]# ls -la /usr/local/lib/openser/modules/postgres.so -rwxr-xr-x 1 root root 97117 Mar 6 12:42 /usr/local/lib/openser/modules/postgres.so [root@vox openser-1.1.1-notls]#
Whats the problem? Thanks Joao pereira
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hello I already have a SER runnig nicelly. Now I installed a second SER (with other domain) with the same database configuration and the same ser.cfg (except the IP). Everyting works fine... except the authentication... SER always answers 401 Unauthorized.
It only accepts clients when I comment this part:
if (!www_authorize("newdomain.com", "subscriber")) { www_challenge("newdomain.com", "0"); break; };
The users exist in the database and I know the username / password. Whats happening? Thanks regards Joao Pereira
Hi!
Joao Pereira wrote:
Everyting works fine... except the authentication... SER always answers 401 Unauthorized.
Are you using Radius or MySQL? My first guess was that your domain table was empty but a quick check revealed that neither auth_radius nor auth_db directly check for a valid domain (that's what is_local() et al are for anyway).
Do you see any Radius/MySQL communication trigged by your REGISTER?
Cheers, Hendrik
-
Daniel-Constantin Mierla -
Hendrik Scholz -
Joao Pereira -
Klaus Darilion -
Mark Price -
Norman Brandinger