• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1930
  • Last Modified:

Dead Server in progress 9.1B

Dear Srs. We have a progress 9.1b server with a database with 1 Gb of information. Sudently, all users receive an error message "Incomplet Write when writing on server (735) and all the users kill her sesions. In eventviever there are an entry that BROKER detect a dead server 1153.

Can somebody help me to prevent this dead server event?

Thanyou QRT
0
qrt
Asked:
qrt
  • 5
  • 3
1 Solution
 
prairieitsCommented:
I am assuming you have restarted the db service with Procontrol, and it still happens, right?

Thanks,
Jerod
0
 
prairieitsCommented:
BROKER detects death of server <pid>. (1153)

In the shared memory with networking model of PROGRESS, one of the PROGRESS
servers for a database has crashed, and the PROGRESS controlling server or
BROKER has detected it. If you need to clear out any clients that may have
hung because of this, you should use PROSHUT <dbname> and take the
appropriate choice from the menu. You should not have to take any other
action, although your <dbname>.lg file should tell you why the server
crashed.
0
 
makhanCommented:
Hi,

If you are on windows this may help.

I suppose your problem is bec. you have single volume database on a FAT FILE SYSTEM.

In windows there is a max limit of 1.2 Gb for a file size.

You can do the following...

1. Convert to Multivolume database .....
    or
2. Convert to NTFS file system.

Let me know if you need any help in doing the conversion to multivolume.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
qrtAuthor Commented:
Dear makhan, we have NTFS file system ang 1 Gb database.

Dear prairieits, The exact message that apear in eventviewer is:
 Message from PROGRESS database C:\aswin\autosoft (5199)

SERVER : BROKER detects death of server 2828. (1153)

In Autosoft.lg apear next entrys when this error happen, in this case at 9:50

09:21:45 SRV     4: Logout usernum 11, userid Concesion, on es321yb010001. (739)
09:22:23 SRV     4: Login usernum 11, userid Concesion, on es321yb010001. (742)
09:22:47 SRV     2: Login usernum 9, userid fabian, on parts1. (742)
09:26:19 SRV     3: Login usernum 8, userid Cars1, on laura. (742)
09:26:39 SRV     4: Login usernum 7, userid Concesion, on es321yb010001. (742)
09:26:43 SRV     4: Logout usernum 7, userid Concesion, on es321yb010001. (739)
09:28:17 SRV     4: AVISO: Excedido -l. Incrementando automáticamente de 240 a 250. (5408)
09:28:17 SRV     4: Previous message sent on behalf of user 29. (5512)
09:29:23 SRV     3: AVISO: excedido -nb. Incrementando automáticamente de 128 a 160. (5407)
09:29:23 SRV     3: Previous message sent on behalf of user 8. (5512)
09:33:33 SRV     1: AVISO: excedido -nb. Incrementando automáticamente de 128 a 160. (5407)
09:33:33 SRV     1: Previous message sent on behalf of user 14. (5512)
09:37:51 SRV     4: AVISO: Excedido -l. Incrementando automáticamente de 250 a 260. (5408)
09:37:51 SRV     4: Previous message sent on behalf of user 29. (5512)
09:41:06 SRV     4: Login usernum 7, userid worksho1, on meritxell. (742)
09:47:46 SRV     4: AVISO: Excedido -l. Incrementando automáticamente de 260 a 270. (5408)
09:47:46 SRV     4: Previous message sent on behalf of user 29. (5512)
09:50:04 SRV     1: You have attempted to connect to a database with too many
users connected to it. Retry the connection later,
or increase -n on the server. (5291)
09:50:13 SRV     2: You have attempted to connect to a database with too many
users connected to it. Retry the connection later,
or increase -n on the server. (5291)
09:50:25 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:25 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:25 SRV     3: You have attempted to connect to a database with too many
users connected to it. Retry the connection later,
or increase -n on the server. (5291)
09:50:30 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:30 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:30 SRV     4: You have attempted to connect to a database with too many
users connected to it. Retry the connection later,
or increase -n on the server. (5291)
09:50:31 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:31 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:34 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:34 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:34 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:35 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:35 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:35 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:37 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:37 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:37 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:40 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:40 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:40 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:40 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:40 BROKER  0: No servers are available.  Try again later. (1154)
09:50:42 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:42 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:42 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:42 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:42 BROKER  0: No servers are available.  Try again later. (1154)
09:50:45 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:45 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:45 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:45 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:45 BROKER  0: No servers are available.  Try again later. (1154)
09:50:45 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:45 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:45 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:45 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:45 BROKER  0: No servers are available.  Try again later. (1154)
09:50:46 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:46 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:46 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:46 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:46 BROKER  0: No servers are available.  Try again later. (1154)
09:50:47 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:47 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:47 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:47 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:47 BROKER  0: No servers are available.  Try again later. (1154)
09:50:49 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:49 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:49 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:49 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:49 BROKER  0: No servers are available.  Try again later. (1154)
09:50:49 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:49 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:49 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:49 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:49 BROKER  0: No servers are available.  Try again later. (1154)
09:50:51 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:51 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:51 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:51 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:51 BROKER  0: No servers are available.  Try again later. (1154)
09:50:53 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:53 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:53 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:53 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:53 BROKER  0: No servers are available.  Try again later. (1154)
09:50:53 BROKER  0: BROKER detects death of server 2312. (1153)
09:50:53 BROKER  0: BROKER detects death of server 2648. (1153)
09:50:53 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:53 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:53 BROKER  0: No servers are available.  Try again later. (1154)
09:50:53 BROKER  0: Disconnecting client 10 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting client 14 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting client 18 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting client 24 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting client 28 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting client 33 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting client 34 of dead server 1. (2526)
09:50:53 BROKER  0: Disconnecting dead server 1. (2525)
09:50:53 BROKER  0: Disconnecting client 9 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting client 13 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting client 17 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting client 21 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting client 27 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting client 31 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting client 32 of dead server 2. (2526)
09:50:53 BROKER  0: Disconnecting dead server 2. (2525)
09:50:56 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:56 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:56 SRV     1: Started on port 3020 using TCP, pid 2592. (5646)
09:50:57 SRV     1: Login usernum 34, userid worksho1, on meritxell. (742)
09:50:58 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:58 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:58 SRV     2: Started on port 3021 using TCP, pid 2168. (5646)
09:50:59 SRV     2: Login usernum 33, userid recanviintern, on . (742)
09:50:59 BROKER  0: BROKER detects death of server 2292. (1153)
09:50:59 BROKER  0: BROKER detects death of server 1648. (1153)
09:50:59 SRV     1: Login usernum 32, userid worksho1, on meritxell. (742)
09:51:00 BROKER  0: BROKER detects death of server 2292. (1153)
09:51:00 BROKER  0: BROKER detects death of server 1648. (1153)
09:51:00 SRV     2: Login usernum 31, userid formacio, on Marta. (742)
09:51:05 BROKER  0: BROKER detects death of server 2292. (1153)
09:51:05 BROKER  0: BROKER detects death of server 1648. (1153)
09:51:05 SRV     1: Login usernum 28, userid EVAY, on evay. (742)
09:51:12 BROKER  0: Disconnecting client 8 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting client 12 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting client 16 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting client 20 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting client 23 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting client 26 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting client 30 of dead server 3. (2526)
09:51:12 BROKER  0: Disconnecting dead server 3. (2525)
09:51:12 BROKER  0: Disconnecting client 7 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting client 11 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting client 15 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting client 19 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting client 22 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting client 25 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting client 29 of dead server 4. (2526)
09:51:12 BROKER  0: Disconnecting dead server 4. (2525)
09:51:14 SRV     3: Started on port 3022 using TCP, pid 1480. (5646)
09:51:15 SRV     3: Login usernum 30, userid Silvia, on Elisacaixa. (742)
09:51:47 SRV     2: AVISO: excedido -nb. Incrementando automáticamente de 128 a 160. (5407)
09:51:47 SRV     2: Previous message sent on behalf of user 33. (5512)
09:52:11 SRV     4: Started on port 3023 using TCP, pid 1460. (5646)
09:52:12 SRV     4: Login usernum 29, userid EVAY, on evay. (742)
09:54:44 SRV     3: Login usernum 27, userid mseuba, on jordipuig. (742)
09:57:24 SRV     4: Login usernum 26, userid fabian, on parts1. (742)
09:57:53 SRV     2: Login usernum 25, userid Cars1, on laura. (742)
09:58:41 SRV     3: Login usernum 24, userid Concesion, on es321yb010001. (742)
09:59:15 SRV     4: Login usernum 23, userid Administrador, on . (742)

Thankyou



0
 
prairieitsCommented:
qrt,

2 things.

First, you didn't respond to makhan's question about whether or not you have a multivolume database.  If you only have a single db file, that could be causing the problem.

Second, from looking at the log, it appears that after you exceed the number of licensed connections to the db, the servers die.  As the log suggests, try increasing that to see if it goes away.  You can do that from your Procontrol Control Panel.  You will need to stop the server, change the licensed number of users and then restart the server.  See if that helps and if it does, you may need to purchase more licenses.

Thanks,
Jerod
0
 
qrtAuthor Commented:
Dear makhan, I have a single volume database in NTFS file system.

Dear prairieits, I try to incease number of users this night, and tomorrow I respond you, but the vendor of my application say that it is not the problem.

Thankyou qrt
0
 
prairieitsCommented:
Qrt,

The single volume db is the problem.  Like makhan said, NTFS has a 1.2GB file size limitation.   You need to split your db up into multiple extents.  I haven't supported a Progress 9.1 db for some time (we switched to MS-SQL) so I don't recall the directions to do that, but I would suggest backing your db up to a couple of different locations prior to starting the conversion process.

Thanks,
Jerod
0
 
qrtAuthor Commented:
Dear  prairieits, I increas number of users and now it work fine.

Thankyou QRT
0
 
prairieitsCommented:
qrt,

That's great.  I guess you have some bad news for the vendor of your application (since that is what it was).

Thanks for the points.

Take care,
Jerod
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now