PHP 5.3 problem

[coelho]

Hi

I need some help.

When I install PHP Version: 5.3.8-0.39.1 on Linux SUSE Enterprise postgree gives this error when accessing the page:

DB Error: ERROR: value too long for type character varying(40)

And psql log adds this entry every time I try to access the page:

2013-02-14 11:20:58 BRST ojs ojs ERROR: value too long for type character varying(40)
2013-02-14 11:20:58 BRST ojs ojs STATEMENT: INSERT INTO sessions
(session_id, ip_address, user_agent, created, last_used, remember, data, acting_as)
VALUES
( $1, $2, $3, $4, $5, $6, $7, $8)


I'm using ojs-2.3.8 with PHP version 5.2.14-0.7.30.46.1 on SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 2 on Linux 3.0.51-0.7.9-default #1 SMP x86_64 GNU/Linux

I want to install >PHP5.3 because security updates.


Thanks

[ramon]

Hello all,

We're receiving lots of reports of users with problems with SUSE + PostgreSQL.
Could it be a distro issue? Or something missing during the basic software installation?

This is the latest issue report we've received and couldn't replicate (as we tested on a local Windows server setup, and it worked):

Code: Select all

SGBD PostgreSQL - 8.3.11
Open Suze /Linux(4.3.2).
Apache 2.2.12
PHP 5.3.
OJS 2.3.8

Message is:
"Error BD: varyng (40)" .
According them, this is only happening in PHP 5.3
No problems when using in previous versions.

Since the IT department needs/wants to upgrade to 5.3, they need a fix, if possible.

We think that there may be an issue with character encoding the session strings.
In our tests, they are all below 40, which is the database field size, but, since the error message is showing that the value is greater than the field, could it be persistent connections or character normalization settings causing this?
Could be a possible Apache missing the default charset setting?

_______________________________
Ramón Martins Sodoma da Fonseca
Analista em C&T
Coordenação de Tecnologias de Informação
Instituto Brasileiro de Informação em Ciência e Tecnologia - IBICT
Ministério da Ciência e Tecnologia - MCT

[asmecher]

Hi Ramón,

Is that "varyng" your typo or is it part of the actual message?

I suspect that character sets are indeed the problem. An incorrect encoding will cause PostgreSQL to mis-measure the character counts of strings as longer than they actually are.

Regards,
Alec Smecher
Public Knowledge Project Team

[ramon]

Hello Alec,

That's how I got the message from the outsourced guys who receive the support questions.
According to them it's a typo. Theres an I in the name of the field.
It's varying.
I'll pass that along to see if they can find any charset issues or misconfiguration.
Thanks!

_______________________________
Ramón Martins Sodoma da Fonseca
Analista em C&T
Coordenação de Tecnologias de Informação
Instituto Brasileiro de Informação em Ciência e Tecnologia - IBICT
Ministério da Ciência e Tecnologia - MCT

[asmecher]

Hi Ramón,

Alternately, it's possible that the "session_id" column in the sessions table is encountering data that's too long. We had one report of a system using values for session_id longer than the 40-character standard that PHP has typically used thus far. If that appears to be the case, lengthening the session_id column should be enough to resolve the problem.

Regards,
Alec Smecher
Public Knowledge Project Team

[coelho]

I have filed a bug request
http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=8141

[JasonNugent]

coelho, I commented on your bug report. Please review and post the answer to my question in here.

Regards,
Jason