OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki

PKP Support

Support forums for the Public Knowledge Project

Skip to content


Software Hosting and Development Services available at PKP Publishing Services

As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

User Login Error

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, michael, jheckman, barbarah, btbell, bdgregg, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.
Post a reply

User Login Error

Postby zulfi » Sat Sep 30, 2006 8:30 am

Some of my users are getting this error at login:

DB Error: Data too long for column 'ip_address' at row 1

Seems like these registrants are from overseas.
Any suggestions? Thanks.

Zulfi
zulfi
 
Posts: 14
Joined: Sat Feb 18, 2006 8:50 pm
Location: Mississippi, USA
Top

Postby asmecher » Mon Oct 02, 2006 1:25 am

Hi Zulfi,

If you're using OJS 2.1.1, try installing the most current version of classes/core/Request.inc.php, available from CVS at http://research2.csci.educ.ubc.ca/cgi-bin/cvsweb/ojs2/classes/core/Request.inc.php -- there's a possibility that sime clients supply multiple IP addresses, depending on their proxy configuration, and the newest version drops additional IPs. (Please do a little testing with this file in place, though, as this combination of versions hasn't been heavily tested.)

Regards,
Alec Smecher
Open Journal Systems Team
asmecher
 
Posts: 5909
Joined: Wed Aug 10, 2005 12:56 pm
Top

Thanks

Postby zulfi » Mon Oct 02, 2006 5:51 pm

Hi Alec,

Thanks for quick response, as usual. I have replaced the file as you suggested, and asked the author from New Zealand to login again. He has not responded yet. I will keep you posted on any issues that seem related.

Regards,

Zulfi
zulfi
 
Posts: 14
Joined: Sat Feb 18, 2006 8:50 pm
Location: Mississippi, USA
Top

Postby zulfi » Tue Oct 03, 2006 5:57 am

Hi Alec,

Got the same message from a potential author from South Africa while trying to login:

"DB Error: Data too long for column 'ip_address' at row 1"

What would be the implications of changing the length of the field 'ip_address" in the 'sessions' table?

Thanks,

Zulfi
http://journal.dnsalias.org
zulfi
 
Posts: 14
Joined: Sat Feb 18, 2006 8:50 pm
Location: Mississippi, USA
Top

Postby asmecher » Wed Oct 04, 2006 3:52 am

Hi Zulfi,

Hmm... I'm curious what data OJS is attempting to insert. Would it be possible for you to enable DBMS logging, capture the offending SQL statement, and post it here? Is it possible that you're dealing with IPv6 addresses?

Regards,
Alec Smecher
Open Journal Systems Team
asmecher
 
Posts: 5909
Joined: Wed Aug 10, 2005 12:56 pm
Top

Postby zulfi » Wed Oct 04, 2006 4:46 am

Hi Alec,

Here's a recent portion of the DB log:

061002 7:57:58 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

061002 7:58:00 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 51 user: 'root'

061002 7:58:00 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 50 user: 'root'

061002 7:58:00 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 38 user: 'root'

061002 7:58:00 InnoDB: Starting shutdown...
061002 7:58:04 InnoDB: Shutdown completed; log sequence number 0 5626124
061002 7:58:04 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

061002 7:59:46 InnoDB: Started; log sequence number 0 5626124
061002 7:59:46 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.18-nt' socket: '' port: 3306 MySQL Community Edition (GPL)
061002 19:46:16 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Normal shutdown

061002 19:46:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 6 user: 'root'

061002 19:46:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 5 user: 'root'

061002 19:46:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 4 user: 'root'

061002 19:46:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 3 user: 'root'

061002 19:46:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 2 user: 'root'

061002 19:46:18 [Warning] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Forcing close of thread 1 user: 'root'

061002 19:46:18 InnoDB: Starting shutdown...
061002 19:46:22 InnoDB: Shutdown completed; log sequence number 0 6315024
061002 19:46:22 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Shutdown complete

061002 19:48:05 InnoDB: Started; log sequence number 0 6315024
061002 19:48:05 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: ready for connections.
Version: '5.0.18-nt' socket: '' port: 3306 MySQL Community Edition (GPL)

I might not be logging all events; let me know how & I can get it to log full details.

Thanks,

Zulfi
http://journal.dnsalias.org
zulfi
 
Posts: 14
Joined: Sat Feb 18, 2006 8:50 pm
Location: Mississippi, USA
Top

Postby asmecher » Wed Oct 04, 2006 5:18 am

Hi Zulfi,

Using the "log" directive in my.cnf, you should be able to temporarily configure MySQL to log all queries. I'd need the specific insert statement that triggers the error.

Regards,
Alec Smecher
Open Journal Systems Team
asmecher
 
Posts: 5909
Joined: Wed Aug 10, 2005 12:56 pm
Top

Postby zulfi » Sun Oct 08, 2006 6:55 pm

Hi Alec,

Your directives must refer to linux/unix environments. I am running W2K3. Could you elaborate a bit more for this lower life form!

Thanks,

Zulfi
zulfi
 
Posts: 14
Joined: Sat Feb 18, 2006 8:50 pm
Location: Mississippi, USA
Top

Postby asmecher » Mon Oct 09, 2006 2:13 am

Hi Zulfi,

There should be a my.cnf configuration file for MySQL somewhere, even on Windows environments -- look for it using "Find" in the Start menu. There may also be a GUI tool to configure MySQL, and you might be able to configure logging there.

Regards,
Alec Smecher
Open Journal Systems Team
asmecher
 
Posts: 5909
Joined: Wed Aug 10, 2005 12:56 pm
Top
Post a reply

Return to OJS Technical Support

Who is online

Users browsing this forum: No registered users and 3 guests

Powered by phpBB® Forum Software © phpBB Group