GreenSQL
Sorry for bringing up this
Sorry for bringing up this old post.
I have the same problem with the actual release 1.2.0 of greensql.
The system is build up this way:
webserver -> GreenSQL with Proxy <-> MySQL Cluster
We run an typo3 based web system and when i want to go to an subsite of the main page it stops with this error:
[04/Dec/2009 12:17:18] NET_DEBUG connection close(), proxy socket 9, backend socket 10
[04/Dec/2009 12:17:18] NET_DEBUG [9] Failed to read socket, closing socket
[04/Dec/2009 12:17:18] NET_DEBUG [9] Socket read error 0
[04/Dec/2009 12:17:18] NET_DEBUG [4]frontend socket fired 9
[04/Dec/2009 12:15:06] NET_DEBUG Send data to client
[04/Dec/2009 12:15:06] NET_DEBUG Socket_write
[04/Dec/2009 12:15:06] SQL_DEBUG server packet 79
[04/Dec/2009 12:15:06] NET_DEBUG packet size expected 4 bytes (received 1160)
[04/Dec/2009 12:15:06] NET_DEBUG [4]backend socket fired 10
[04/Dec/2009 12:15:06] NET_DEBUG Send data to client
[04/Dec/2009 12:15:06] NET_DEBUG Socket_write
When i directly connect to an node it doesn't work either.
@ramp:
How can i obtain the 1.0 Version? Can you offer me the source (i'm not experienced with svn)
@yuli:
Web Contact doensn't work. When i try to send an mail to an user i get an access denied error.
Hello
Can you provide more details about your production server - linux version you use, CMS software you use so we can try to reproduce this error here ?
Thanks,
Yuli
PS. Recently we started to provide commercial email support with an SLA with a next business day response time.
http://support.greensql.com/
@Yuli:
We use an CentOS 5.4 Linux Server as Backend Server.
- MySQL CLuster with ndb 7.0.9b
- MySQL Server Version 5.1.39
2 x Nodes with each 4 CPUs and 32 GB Memory
1 x Management Server acts as LoadBalancer with ldirector from Heartbeat Project
GreenSQL Server:
CentOS 5.4 with own small MySQL Database
- 512 MB Memory
- 1 CPU
Hosted as VMware Machine
Intranet <-> GreenSQL <-> MySQL Management Server
The CMS System is Typo3 Version 4.2.10
MySQL Tables are stored diskbased with ndbcluster engine
hey there oldschool,
I have tried running Typo3 with the corresponding mysql version.
Everything seemed to work smoothly for me once i setup the localconf configuration file to 127.0.0.1:3305
the only thing that was odd happend in the specific typo3 version you are using in which warning messages came on the page due to greensql IPS blocks.
The site continued to work as intended though.
After i changed the database policy to Learning mode the warning messages disappeared.
in the newest typo3 version you didnt have this warning messages at all and it was all smooth.
I didnt try to setup heartbeat or NDB clustering since they are supposed to be transparent to greensql.
@elishemer:
I've tried the Learning mode and a non blocking IPS Mode but it fails with the large result set.
Newer typo3 versions doenst work too (tested with another instance of typo3).
So other things (piwik monitoring) work on initial setup but if they have a good footprint of data ( approx 30 MB) it doesn't work anymore.
UPDATE:
Ok with Learning mode it works like a charm. Trying to find where the problem is (IDS with no blocking doesn't work..).
Thanks for the tip! (Don't know why learning mode works now. Perhaps of the boost of ram :) )
would you provide information about your linux version you use and cms software
Thanks,
SMIT
Mario Games
I really do not understand why you are still stuck up with the old release of the Green SQL; I mean just take a look at the new one. I do not whether there is any other word than “Perfect” to describe it. The one and the only reason you should get it, if at all anything prevents you from upgrading, is that the ability of the Green SQL in protecting the database from injection attacks is absolutely remarkable.
Brown | Contact Center
i want to tell u that i have tried the Learning mode and a non blocking IPS Mode but it fails with the large result set.
Newer typo3 versions doenst work too (tested with another instance of typo3).