Installation on Redhat ES 4.

MiniMe
Posts: 210
Joined: Thu Mar 15, 2001 4:30 pm

Installation on Redhat ES 4.

Post by MiniMe »

Does Texis 4.x work ok on Redhat 4?? I am seeing cases where montior runs wild and the database locks up..

Server: 30 Process Id: 1632 monitor

Server: 31 Process Id: 1634 monitor

Server: 32 Process Id: 1636 monitor

Server: 33 Process Id: 1639 monitor

Server: 34 Process Id: 1640 monitor

Server: 35 Process Id: 1645 monitor

Server: 36 Process Id: 1647 monitor

Server: 37 Process Id: 1649 monitor

Server: 38 Process Id: 1652 monitor

Server: 39 Process Id: 1654 monitor

Server: 40 Process Id: 1650 monitor

Server: 41 Process Id: 1656 monitor

Server: 42 Process Id: 1658 monitor

Server: 43 Process Id: 1630 monitor

Server: 44 Process Id: 1661 monitor

Server: 45 Process Id: 1662 monitor

Server: 46 Process Id: 1665 monitor

Server: 47 Process Id: 1659 monitor

Server: 48 Process Id: 1666 monitor

Server: 49 Process Id: 1671 monitor

Server: 50 Process Id: 1675 monitor

Server: 51 Process Id: 1676 monitor

Server: 52 Process Id: 1668 monitor

Server: 53 Process Id: 1677 monitor

Server: 54 Process Id: 1679 monitor

Server: 55 Process Id: 1680 monitor

Server: 56 Process Id: 1681 monitor

Server: 57 Process Id: 1682 monitor

=====================================================
User avatar
John
Site Admin
Posts: 2597
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Installation on Redhat ES 4.

Post by John »

32 or 64 bit ES4? Which Linux build of Texis? The ES4 kernel does something different with semaphores which may cause an issue under heavy load. Anything in monitor.log?
John Turnbull
Thunderstone Software
MiniMe
Posts: 210
Joined: Thu Mar 15, 2001 4:30 pm

Installation on Redhat ES 4.

Post by MiniMe »

It is 32 bit Linux with Texis version..

Texis Web Script (Vortex) Copyright (c) 1996-2002 Thunderstone - EPI, Inc.
Commercial Version 4.02.1033632267 of Oct 3, 2002 (i686-unknown-linux2.4.2-64)

Lots and lots of these in monitor.log

200 Apr 12 13:04:25 (11664) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:04:25 (11837) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:05:25 (11837) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:05:25 (12014) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:06:25 (12014) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:06:25 (12198) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:07:25 (12198) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:07:26 (12373) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:08:26 (12373) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:08:26 (12557) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:09:26 (12557) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:09:27 (12731) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:10:27 (12731) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:10:27 (12902) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:11:27 (12902) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:11:28 (13063) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:12:28 (13063) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:12:28 (13225) Database Monitor on /db/tables/prod/ starting
200 Apr 12 13:12:28 (13225) Database Monitor on /db/tables/prod/ exiting
200 Apr 12 13:12:28 (13228) Database Monitor on /db/tables/prod/ starting
User avatar
John
Site Admin
Posts: 2597
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Installation on Redhat ES 4.

Post by John »

How is that file system mounted? What file system type, and any options such as noatime?
John Turnbull
Thunderstone Software
MiniMe
Posts: 210
Joined: Thu Mar 15, 2001 4:30 pm

Installation on Redhat ES 4.

Post by MiniMe »

The filesystem is a multipath system into our SAN fabric. The FS type is ext2.. Here is the mount output..

/dev/mapper/VolGroup01-DataVol1 on /db/tables/prod type ext2 (rw,noatime)
/dev/mapper/VolGroup02-IndexVol1 on /db/indexes/prod type ext2 (rw,noatime)
/dev/mapper/VolGroup03-MaintVol1 on /db/tables/maint type ext2 (rw,noatime)
User avatar
John
Site Admin
Posts: 2597
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Installation on Redhat ES 4.

Post by John »

The noatime is part of the problem, the database monitor doesn't see anybody accessing the tables, and quits. I'm not quite sure why that would cause the stacking up behaviour though.
John Turnbull
Thunderstone Software
MiniMe
Posts: 210
Joined: Thu Mar 15, 2001 4:30 pm

Installation on Redhat ES 4.

Post by MiniMe »

I have reset the fstab on one of the two servers that is doing this to the defaults and remounted the FS on those slices. Ill wait and see if it continues to act out. Is there anything else I should look at?
User avatar
John
Site Admin
Posts: 2597
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Installation on Redhat ES 4.

Post by John »

Are the servers sharing the same files? Are they read-only applications?
John Turnbull
Thunderstone Software
MiniMe
Posts: 210
Joined: Thu Mar 15, 2001 4:30 pm

Installation on Redhat ES 4.

Post by MiniMe »

None of the servers see the same files.. we rsync them across at night to the different virtual volumes. The applications are read only in the production database. We have one maintenance database which we have never had a problem with ironically.
User avatar
John
Site Admin
Posts: 2597
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

Installation on Redhat ES 4.

Post by John »

A couple things you might try then, one is in the texis.cnf increase the DB Quiet setting, so the monitor won't exit as quickly (you could go up to 3000000) for a week or so, not sure what the atime actually is on the files.

Are you using the singleuser mode if they are read only? That will be of a performance benefit, not sure if it will affect this issue though.
John Turnbull
Thunderstone Software
Post Reply