AW: [opencms-dev] Problems with publishing / Gray Flags

[Roth Olivier]

Hi,

I don't see the problem on the mySql side but rather on the OpenCms side.
The sleeping connections I'm killing in mySql are connections with
time<wait_timeout, i.e. mySql doesn't have to kill them.

I'm investigating in deeper and am trying to reproduce the problem, but when
you need it, it doesn't happen.
In opencms.properties I switched the pool loggin on.
Now I'm watching closer what is happening during publishing and how many
connections are used.
max _connections for mysql is set to 200 and I have 3 opencms instances
running
with max. 80,40 and 40 connections in each pool.
The next time the problem is happening I'll see if opencms uses more
connections
than expected.

MfG,
	Olivier Roth


-----Ursprüngliche Nachricht-----
Von: opencms-dev-admin at opencms.org
[mailto:opencms-dev-admin at opencms.org]Im Auftrag von Kai Schliemann
Gesendet: Mittwoch, 17. Dezember 2003 09:51
An: opencms-dev at opencms.org
Betreff: AW: [opencms-dev] Problems with publishing / Gray Flags


Hi Olivier,

thanks for your hint. It helped.

I did a little investigation on this problem. In the mySQL-Reference I found
the following:

################### start #####################
A.2.9 Communication Errors / Aborted Connection

Starting with MySQL 3.23.40 you only get the Aborted connection error of you
start mysqld with --warnings.
If you find errors like the following in your error log.
010301 14:38:23  Aborted connection 854 to db: 'users' user: 'josh'
See section 4.9.1 The Error Log.
This means that something of the following has happened:
    * The client program did not call mysql_close() before exit.

############ start - could one of these two be the problem? ##############
    * The client had been sleeping more than wait_timeout or
interactive_timeout without doing any requests. See section 4.5.6.4 SHOW
VARIABLES. See section 4.5.6.4 SHOW VARIABLES.
    * The client program ended abruptly in the middle of the transfer.
############ end - could one of these two be the problem? ##############

When the above happens, the server variable Aborted_clients is incremented.
The server variable Aborted_connects is incremented when:
    * When a connection packet doesn't contain the right information.
    * When the user didn't have privileges to connect to a database.
    * When a user uses a wrong password.
    * When it takes more than connect_timeout seconds to get a connect
package. See section 4.5.6.4 SHOW VARIABLES.
Note that the above could indicate that someone is trying to break into your
database!
Other reasons for problems with Aborted clients / Aborted connections.
    * Usage of duplex Ethernet protocol, both half and full with Linux. Many
Linux Ethernet drivers have this bug. You should test for this bug by
transferring a huge file via ftp between these two machines. If a transfer
goes in burst-pause-burst-pause ... mode then you are experiencing a Linux
duplex syndrome. The only solution to this problem is switching of both half
and full duplexing on hubs and switches.
    * Some problem with the thread library that causes interrupts on reads.
    * Badly configured TCP/IP.
    * Faulty Ethernets or hubs or switches, cables ... This can be diagnosed
properly only by replacing hardware.
    * max_allowed_packet is too small or queries require more memory than
you have alloacated for mysqld. See section A.2.8 Packet too large Error.
################### end #####################

See also:
http://toker.hum.gu.se/manualer/mysql/manual_toc.html#Communication_errors

Mit freundlichen Grüßen

i.A. Kai Schliemann
IT-Consultant
____________________________________________

comundus Unternehmensberatung GmbH
Schüttelgrabenring 3, 71332 Waiblingen

Tel:    +49 (0) 71 51-5 00 28-0   Fax: -99

www.comundus.com www.comundus-e-quality.com
____________________________________________


> -----Ursprüngliche Nachricht-----
> Von: opencms-dev-admin at opencms.org
> [mailto:opencms-dev-admin at opencms.org]Im Auftrag von Roth Olivier
> Gesendet: Dienstag, 16. Dezember 2003 11:38
> An: opencms-dev at opencms.org
> Betreff: AW: [opencms-dev] Problems with publishing / Gray Flags
>
>
> Hi,
>
> I often have a similar problem: resources not getting published and then
> being marked with a gray flag.
> My solutions for this is to manually login into the database (mySql in my
> case) and to kill some of the sleeping connections.
> After that publishing is possible again.
>
> The big question is: why is this happening ?
> Why aren't these sleeping connections being resumed or terminated ?
>
> Some info about my settings:
> - in opencms.properties:
> pool.mysql.minConn=10
> pool.mysql.maxConn=20
> pool.mysql.increaseRate=5
> pool.mysql.timeout=120
> pool.mysql.maxage=360
> (online and backup pool same values)
>
> - for mySql:
> 'max_connections','200'
> 'wait_timeout','14400'
>
> Greetings,
> 	Olivier Roth
>
> -----Ursprüngliche Nachricht-----
> Von: opencms-dev-admin at opencms.org
> [mailto:opencms-dev-admin at opencms.org]Im Auftrag von Kai Schliemann
> Gesendet: Dienstag, 16. Dezember 2003 10:33
> An: opencms-dev at opencms.org
> Betreff: AW: [opencms-dev] Problems with publishing
>
>
> Hi Mario,
>
> may I ask if you already solved this problem? I am having the
> same problems
> you have. But there is one difference. Before publishing a resource it is
> marked as changed with a red flag. After publishing it, it has a gray flag
> and the alt-text says "belongs to project ''". The '' indicating a empty
> string.
>
> Can you or anyone else help me?
>
> TIA
>
> Kai
>
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev