Ryszard Musielak
Member
Hi Everybody,
I am wondering why Progress doesn't seem to clean old sessions lingering in the DB sessions. Some users run reports that can use a lot of space in /tmp, so I have to terminated them manually. This is what I see:
Notice the old sessions from 2 March are as "batch", the actual proper sessions today 6 March are connected from Citrix server (XAWPU09029).
When I check the first PID=26704 there is a process associated with it:
When I terminate the old sessions no one complains, so I assume I can kill them safely. Also, when I terminated some old ones I freed a lot of space in /tmp from Used=90% down to Used=44%.
My question is, why wouldn't Progress terminate those old sessions? Is there a background process responsible for this?
Should I see them as "Limbo? = Yes"?
I know this can happen mainly when users loose network connections at their sites or have a session hang, so they reboot their machines.
Is there any DB settings in the config files that is not set?
Kind Regards,
Richard
I am wondering why Progress doesn't seem to clean old sessions lingering in the DB sessions. Some users run reports that can use a lot of space in /tmp, so I have to terminated them manually. This is what I see:
Code:
$ proshut /bcp/pack/package -C list | grep -v "\." | grep -v root
usr pid time of login user id Type tty Limbo?
56 26704 Mon Mar 2 08:42:31 2020 gjohn BAT batch no
57 27167 Mon Mar 2 08:44:48 2020 gjohn BAT batch no
58 27185 Mon Mar 2 08:44:58 2020 gjohn BAT batch no
59 27284 Mon Mar 2 08:45:22 2020 gjohn BAT batch no
60 27672 Mon Mar 2 08:47:56 2020 MWojcik BAT batch no
61 27341 Mon Mar 2 08:45:52 2020 gjohn BAT batch no
62 27740 Mon Mar 2 08:48:19 2020 MWojcik BAT batch no
63 27794 Mon Mar 2 08:48:47 2020 gjohn BAT batch no
64 28438 Mon Mar 2 08:52:13 2020 gjohn BAT batch no
65 27782 Mon Mar 2 08:48:39 2020 gjohn BAT batch no
66 28459 Mon Mar 2 08:52:24 2020 gjohn BAT batch no
67 28509 Mon Mar 2 08:52:50 2020 gjohn BAT batch no
68 28579 Mon Mar 2 08:53:37 2020 MWojcik BAT batch no
99 26492 Mon Mar 2 08:40:59 2020 gjohn BAT batch no
100 26768 Mon Mar 2 08:43:10 2020 gjohn BAT batch no
101 27298 Mon Mar 2 08:45:31 2020 gjohn BAT batch no
102 28555 Mon Mar 2 08:53:27 2020 gjohn BAT batch no
103 28726 Mon Mar 2 08:54:22 2020 kmaj BAT batch no
172 28727 Mon Mar 2 08:54:22 2020 gjohn BAT batch no
173 28729 Mon Mar 2 08:54:22 2020 gjohn BAT batch no
483 17388 Fri Mar 6 07:44:54 2020 pstephens REMC XAWPU09029 no
484 25596 Fri Mar 6 07:36:20 2020 MWojcik REMC XAWPU19112 no
Notice the old sessions from 2 March are as "batch", the actual proper sessions today 6 March are connected from Citrix server (XAWPU09029).
When I check the first PID=26704 there is a process associated with it:
Code:
$ ps -ef | grep 26704
root 26704 3587 0 Mar02 ? 00:09:10 /bcp/dlc/bin/_proapsv -logginglevel 4 -logfile /bcp/log/AccordLive.server.012477.log -ubpid 3587 -Ms 1 -logn ame AccordLive -logentrytypes ASPlumbing,DB.Connects -logthreshold 1024000 -numlogfiles 2 -ASID 42 -ubpropfile /bcp/dlc/properties/ubroker.properties -ipver IPv4 -db /bcp/pack/package -pf back.pf
When I terminate the old sessions no one complains, so I assume I can kill them safely. Also, when I terminated some old ones I freed a lot of space in /tmp from Used=90% down to Used=44%.
My question is, why wouldn't Progress terminate those old sessions? Is there a background process responsible for this?
Should I see them as "Limbo? = Yes"?
I know this can happen mainly when users loose network connections at their sites or have a session hang, so they reboot their machines.
Is there any DB settings in the config files that is not set?
Kind Regards,
Richard