Unconditional shutdown in 10.2A01 is very long

Posted by Valeriy Bashkatov on 23-Apr-2009 00:37

Hello,

When I start unconditional shutdown in 10.2А02 (Linux) at the connected user, stop of a database to occur very long. This situation is easily reproduced on a database Sports.
I shall notice, in 10.1С such problem was not.

Progress Permissions $DLC/bin:
-rwsr-xr-x 1 root root 4490665 Mar 7 04:07 /usr/dlc102a/bin/_bprowsdldoc
-rwsr-xr-x 1 root root 72338 Mar 7 04:03 /usr/dlc102a/bin/_dbagent
-rwsr-xr-x 1 root root 4012351 Mar 7 04:05 /usr/dlc102a/bin/_dbutil
-rwsr-xr-x 1 root root 25204 Oct 22 01:31 /usr/dlc102a/bin/_debugConfig
-rwsr-xr-x 1 root root 23306 Oct 22 01:31 /usr/dlc102a/bin/_debugEnable
-rwsr-xr-x 1 root root 4822 Sep 13 2008 /usr/dlc102a/bin/_isroot
-rwsr-xr-x 1 root root 5096 Sep 13 2008 /usr/dlc102a/bin/_lsfiles
-rwsr-xr-x 1 root root 3322895 Mar 7 03:59 /usr/dlc102a/bin/_mprosrv
-rwsr-xr-x 1 root root 3197111 Mar 7 03:59 /usr/dlc102a/bin/_mprshut
-rwsr-xr-x 1 root root 583290 Mar 7 04:07 /usr/dlc102a/bin/_orasrv
-rwsr-xr-x 1 root root 8516179 Mar 7 03:59 /usr/dlc102a/bin/_proapsv
-rwsr-xr-x 1 root root 373381 Mar 7 04:07 /usr/dlc102a/bin/_probrkr
-rwsr-xr-x 1 root root 8471383 Mar 7 03:58 /usr/dlc102a/bin/_progres
-rwsr-xr-x 1 root root 11444 Sep 13 2008 /usr/dlc102a/bin/_proutil
-rwsr-xr-x 1 root root 11771 Sep 13 2008 /usr/dlc102a/bin/_rfutil
-rwsr-xr-x 1 root root 1781132 Mar 7 04:30 /usr/dlc102a/bin/_sqldump
-rwsr-xr-x 1 root root 1796663 Mar 7 04:30 /usr/dlc102a/bin/_sqlload
-rwsr-xr-x 1 root root 1806798 Mar 7 04:31 /usr/dlc102a/bin/_sqlschema
-rwxr-xr-x 1 root root 7383081 Mar 7 04:29 /usr/dlc102a/bin/_sqlsrv2
-rwsr-xr-x 1 root root 84376 Mar 7 04:03 /usr/dlc102a/bin/_tlr
-rwxr-xr-x 1 root root 72486 Mar 7 04:03 /usr/dlc102a/bin/_waitfor

Database permissions:

-rw-rw---- 1 root bankier 327680 Apr 20 15:18 sports_10.d1
-rw-rw---- 1 root bankier 65536 Apr 20 15:18 sports_10.d2
-rw-rw---- 1 root bankier 1310720 Apr 20 15:18 sports_11.d1
-rw-rw---- 1 root bankier 1376256 Apr 20 15:18 sports_11.d2
-rw-rw---- 1 root bankier 327680 Apr 20 15:18 sports_12.d1
-rw-rw---- 1 root bankier 65536 Apr 20 15:18 sports_12.d2
-rw-rw---- 1 root bankier 327680 Apr 20 15:18 sports_7.d1
-rw-rw---- 1 root bankier 65536 Apr 20 15:18 sports_7.d2
-rw-rw---- 1 root bankier 655360 Apr 20 15:18 sports_8.d1
-rw-rw---- 1 root bankier 655360 Apr 20 15:18 sports_8.d2
-rw-rw---- 1 root bankier 327680 Apr 20 15:18 sports_9.d1
-rw-rw---- 1 root bankier 65536 Apr 20 15:18 sports_9.d2
-rw-rw---- 1 root bankier 2228224 Apr 20 15:18 sports.b1
-rw-rw---- 1 root bankier 1245184 Apr 20 15:18 sports.d1
-rw-rw---- 1 root bankier 32768 Apr 20 15:18 sports.db
-rw-rw---- 1 root bankier 7751 Apr 20 15:19 sports.lg
-rw-rw---- 1 root bankier 0 Apr 20 13:37 sports.lic
-r--r--r-- 1 root bankier 38 Apr 20 15:18 sports.lk
-rw-rw---- 1 root bankier 458 Apr 20 13:25 sports.st

All permissions set by as in "KB-12538: Progress and UNIX Permissions"

Example,
a. Start of a database by the user "user1".
          $DLC/bin/proserve sports

b. We are connected to a database by the user "user2", The user does not create activity. Is open only Progress Editor
          mpro sports

c. Stop database by "user1"
         $DLC/bin/proshut sports

5 5163 Mon Apr 20 15:18:42 2009 valeriy /dev/pts/7 no
     1 Disconnect a User
     2 Unconditional Shutdown
     3 Emergency Shutdown (Kill All)
     x Exit
Enter choice> 2
Shutdown is executing. (1613)
15:19:21 1 processes still connected. (2262)
15:19:51 1 processes still connected. (2262)
15:23:51 1 processes still connected. (2262)
...

In database log:

[2009/04/20@15:18:54.539+0400] P-5162 T-0 I BROKER 0: (2248) Begin normal shutdown
[2009/04/20@15:18:54.539+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 12 to user 5
[2009/04/20@15:19:24.585+0400] P-5162 T-0 I BROKER 0: (2261) Sending signal 14 to 1 connected user(s).
[2009/04/20@15:19:24.585+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 14 to user 5
[2009/04/20@15:19:54.632+0400] P-5162 T-0 I BROKER 0: (2261) Sending signal 2 to 1 connected user(s).
[2009/04/20@15:19:54.632+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 2 to user 5
[2009/04/20@15:20:24.676+0400] P-5162 T-0 I BROKER 0: (2263) Resending shutdown request to 1 user(s).
[2009/04/20@15:20:24.676+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 12 to user 5
[2009/04/20@15:23:54.995+0400] P-5162 T-0 I BROKER 0: (2261) Sending signal 14 to 1 connected user(s).
[2009/04/20@15:23:54.995+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 14 to user 5
[2009/04/20@15:24:25.038+0400] P-5162 T-0 I BROKER 0: (2261) Sending signal 2 to 1 connected user(s).
[2009/04/20@15:24:25.038+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 2 to user 5
[2009/04/20@15:24:55.085+0400] P-5162 T-0 I BROKER 0: (2261) Sending signal 15 to 1 connected user(s).
[2009/04/20@15:24:55.085+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 15 to user 5
[2009/04/20@15:25:56.175+0400] P-5162 T-0 I BROKER 0: (2251) Destroyed user 5 pid 5163.
[2009/04/20@15:26:26.223+0400] P-5162 T-0 I BROKER 0: (4029) Error opeing file /dsk3/bank/users/valeriy/sports/sports.lk, errno = 13.
[2009/04/20@15:26:26.223+0400] P-5162 T-0 I BROKER 0: (-----) Sending signal 12 to user 5
[2009/04/20@15:26:36.178+0400] P-5163 T-0 I ABL 5: (453) Logout by valeriy on /dev/pts/7.
[2009/04/20@15:26:36.225+0400] P-5162 T-0 I BROKER 0: (2251) Destroyed user 6 pid 5176.
[2009/04/20@15:26:41.226+0400] P-5162 T-0 I BROKER : (334) Multi-user session end.
[2009/04/20@15:26:41.226+0400] P-5162 T-0 I BROKER : (-----) Removed shared memory with segment_id: 48759241

shutdown was carried out 7 min 47 sec!

Problem is not present if:
0. use 10.1C
1. user connected by -H/-S (10.2A)
2. Previously user disconnected by "1 Disconnect a User" (10.2A)
3. Database start and stop by user "root", But use of this user is not authorized in the company for these purposes (10.2A)

I shall remind, that in 10.1C such problem is not present!

Somebody knows, what has changed in 10.2A? Why proshut carries out long Unconditional shutdown??

All Replies

Posted by ChUIMonster on 23-Apr-2009 09:32

I don't know what the problem is but I can confirm that it isn't just you.  I see it too.

Posted by Valeriy Bashkatov on 24-Apr-2009 03:13

Ok.

I want to  open "case" in PSC.

Posted by ChUIMonster on 24-Apr-2009 08:20

Good idea.  Keep us posted on the status!

Posted by Admin on 04-May-2009 01:56

I confirm this but I think is normal. When the userA start the database server and a userB connect to this server,

userA and userB has differents system rights. When the userA shutdown the database server, in the mean times

he try to disconnect properly _progres process and he send kill -12 system signal.

Unfortunately, the userA can not stop userA process because he dont have rights.

A ideea is to change userA/userB rights into the same system goup.

Posted by Valeriy Bashkatov on 04-May-2009 07:29

May be you right, and such behaviour database this it is correct, but why in 101С such was not?

>>A ideea is to change userA/userB rights into the same system goup.

userA and userB in same system group

In PSC is opened "case", but answer is not yet received.

Posted by Valeriy Bashkatov on 10-Jun-2009 07:37

Hello,

This is registered as Bag# OE00183967.

In ProKb is created Solution P145772.

This thread is closed