[freeside] New error on install

[Gerald V. Livingston II]

BINGO!

OK, for the archives.

It appears that installs of postgres 7.4.x default to using UNICODE
databases.

What happened to me is that my Debian Sarge install of a few weeks ago was
installing an earlier version of postgresql. When I wiped the machine and
did a new install/update it upgraded to the latest 7.4.6

When one reaches the "Create database" step of the Freeside install
instructions it needs to be done MANUALLY using:

su freeside
createdb -E sql_ascii freeside

The 'make create-database' section could probably be adjusted to use the -E
option to "createdb" -- or is that in the perl DBI module somewhere?

'freeside-setup user' or 'freeside-setup -s user' work as planned when the
database is created in this fashion.

If you have no need for UNICODE databases you could locate the database
named "template1" on your system and replace it with a new database created
with sql_ascii encoding. All new databases should then be created as
sql_ascii (untested at this point by me) because template1 is the database
used to create new databases.

Gerald


On Mon, 29 Nov 2004 19:44:55 -0600 (Central Standard Time) "Gerald V.
Livingston II" <gerald.freeside at sysmatrix.net> wrote: 

> Well crap!
> 
> I just apt-get --purge removed all postgresql packages and reinstalled
> them
> clean so there would be no leftover config files. I still get the same
> error after reinstall.
> 
> Using Debian Sarge because of the hardware (and it'll be the stable
> branch
> soon anyway).
> 
> postgres 7.4.6
> freeside 1.5.0pre6
> 
> I think I'll rip it apart one more time and get the debian base installed
> before I go home tonight. That way I can try again from home if the rain
> doesn't let up enough to allow me time to work on my VW (no garage
> sucks).
> 
> Yes, I'm rambling now. Trying to learn something new in days tends to do
> that to me. I'm glad I told the boss this would take a while.
> 
> Thanks all, needed a place to vent and am hoping someone else may have
> seen
> this problem. I'll dig in the postgres docs once more to see if I can see
> where to tell it NOT to use UNICODE when creating databases.
> 
> zgrep /usr/share/doc/postgres* to the rescue
> 
> Gerald
> 
> On Mon, 29 Nov 2004 15:22:23 -0600 (Central Standard Time) "Gerald V.
> Livingston II" <gerald.freeside at sysmatrix.net> wrote: 
> 
> > Yeah, that's what I decided but I can't figure out what's different
> > between
> > this postgresql install and the last. I just reinstalled the exact same
> > things on this machine that I did last tme (that worked) except for
> using
> > CPAN to get all perl modules rather than using the debian packages.
> > 
> > That error seems to relate to a client trying to use UTF-8 or UNICODE
> > when
> > the database isn't set up for it (that's what I got from google
> anyway). 
> > 
> > Hmmm -- revision to that statement. It seems I did something screwey
> upon
> > postgresql install and it;s creating databases to USE "UNICODE" and
> > anything sent in non-UNICODE (which is normal for western text) will
> > crash
> > it.
> > 
> > <SIGH>
> > 
> > Going to rip out the whole postgres install and re-do it. I've dug
> > through
> > the configs and I din't see where it's setting the database creation
> > type.
> > 
> > Gerald
> > 
> > On Mon, 29 Nov 2004 12:54:35 -0700 Scott
> > <mailinglists-freeside at sisna.com> wrote:
> > 
> > > That Error output appears to be postgres releated.  Knowing this
> setup
> > > script 
> > > works with other installs, the finger starts to point to Pg.  What
> > > version of 
> > > Postgres are you using, where did you obtain it from, and how was it 
> > > installed?.  What branch(es) of Debian are you tracking?
> > > 
> > > Thanks,
> > > 
> > > Scott Edwards
> > > http://www.daxal.com/
> > > 
> > > On Monday 29 November 2004 03:19 am, Gerald V. Livingston II wrote:
> > > > Then I ran 'freeside-setup -s gerald' and the final two lines
> before
> > it
> > > > dies are: (manually wrapped here)
> > > > 
> > > > DBD::Pg::st execute failed: ERROR:  invalid byte sequence for
> > encoding
> > > >         "UNICODE": 0xed6f73 at
> > /usr/local/share/perl/5.8.4/FS/Record.pm
> > > >          line 654.
> > > > 
> > > > ERROR:  invalid byte sequence for encoding "UNICODE": 0xed6f73 at
> > > >          /usr/local/bin/freeside-setup line 267. 
> > > > 
> > > > 
> > > > The complete output that the command generates to STDERR is at 
> > > > 
> > > > http://www.sysmatrix.net/imgtest/freeside-setup.log.txt
> > > > 
> > > > Ideas??