Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 2300

BPDBM is choking system memory and making it hung eventually

$
0
0
I need a solution

NBU version is 7.1.0.4 and OS version is Solaris 10.

 

Issue started 2 days back when server starts hanging all of a sudden. Later got identifed that BPDBM was the one using very high memory.

 

Here are some outputs from prstat just before it got hung, system got 32GB of RAM

 

 

   PID USERNAME  SIZE   RSS STATE  PRI NICE      TIME  CPU PROCESS/NLWP
 14876 root       19G   18G cpu0    11    0   0:08:17 3.8% bpdbm/1
  2241 root     3029M 2960M cpu10   11    0  21:03:15 3.8% dbsrv11/64
  2387 root      468M  356M sleep   59    0   0:16:24 0.1% nbstserv/19
  2347 root      292M  213M sleep   59    0  13:01:21 2.6% nbemm/98
  2350 root      265M  209M sleep   59    0   1:26:17 0.4% nbrb/10
 

 

/var/adm/messages :-

 

Sep  8 06:09:24 nbupitsun002 tldcd[22500]: [ID 673158 daemon.error] TLD(1) fork failure, Resource temporarily unavailable

Sep  8 06:19:24 nbupitsun002 sendmail[1404]: [ID 702911 mail.info] runqueue: Skipping queue run -- fork() failed: Resource temporarily unavailable

Sep  8 06:25:44 nbupitsun002 sendmail[1402]: [ID 702911 mail.info] runqueue: Skipping queue run -- fork() failed: Resource temporarily unavailable

Sep  8 07:05:23 nbupitsun002 sshd[526]: [ID 800047 auth.error] error: fork: Error 0

 

If we kill that particular PID, all will come back to normal. But after sometime, another PID will start the same behaviour. All the BPDBM PID will start normally with a normal memory usage. But then one of them will grow in a metter of seconds and start using the whole memory and eventually making the system hang.

 

issue is running for ast 2 days and Symantec didnt find much from the logs. server is getting hung and keep on getting rebooted after that


Viewing all articles
Browse latest Browse all 2300

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>