0

Vembu 3.7 strange issues

asked 2017-03-23 19:37:04 -0600

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

After installing fresh 3.7, Vembu BDR is acting weired. We are testing 500 VM and Vembu Service keeps crashing. After installing the fix of 3.7 to both BDR and ODR, inspite of services running, Unable to login to console. Also there are many postgres instance found running.

Please find below output

Look at the number of Postgres instances – is it not TOO many?

Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName ------- ------ ----- ----- ----- ------ -- ----------- 172 27 6284 13324 65 2.13 1932 Apache 399 61 48628 49864 151 5.39 2080 Apache 36 5 2116 4532 46 0.48 1528 conhost 175 13 1344 3816 26 0.34 1832 conhost 1072 20 5332 8104 50 31.67 412 csrss 75 8 1844 3968 37 0.94 460 csrss 207 11 3184 7788 115 0.45 1760 csrss 77 7 1964 5264 55 0.03 1800 dwm 632 41 25052 38664 182 2.48 4500 explorer 0 0 0 24 0 0 Idle 76 8 2168 4876 70 0.02 1352 jusched 168 23 8764 15440 82 0.17 820 LogonUI 1003 34 9232 17920 51 11.09 560 lsass 268 11 3924 6604 32 0.28 568 lsm 246 22 9600 16260 143 1.44 4092 mmc 47 6 1096 3336 14 0.02 1548 mounter 139 17 3500 7612 60 0.08 976 msdtc 89 8 2364 5888 61 0.03 1680 pg_ctl 4116 8 6860 16640 281 0.11 172 postgres 4124 8 6792 17596 281 0.22 1656 postgres 4108 8 6780 14032 281 0.09 1692 postgres 4128 8 6848 17048 281 0.17 1808 postgres 4197 57 3824 75272 285 0.88 1824 postgres 4079 7 3428 5156 274 0.06 1940 postgres 4080 7 3416 10432 270 0.03 1992 postgres 4079 7 3400 6956 270 0.06 2000 postgres 4080 7 3400 10028 270 0.02 2008 postgres 4080 7 5512 7228 273 0.59 2016 postgres 4079 7 3728 5536 270 12.48 2024 postgres 4153 8 6956 17900 281 1.19 2552 postgres 4159 8 7148 18388 281 0.34 2704 postgres 4151 8 7328 17992 281 0.14 2756 postgres 4115 8 6808 14624 281 0.09 2780 postgres 4142 8 6924 25268 281 0.22 2852 postgres 4183 8 6884 18068 281 0.36 2876 postgres 4197 8 7420 20080 281 0.77 2984 postgres 4220 8 8980 30720 282 9.31 3012 postgres 4213 8 10640 23200 282 0.84 3032 postgres 4161 8 7040 18448 281 0.31 3068 postgres 4134 8 7260 17804 281 0.19 3188 postgres 4147 8 7068 18428 281 0.20 3196 postgres 4119 8 6776 14868 281 0.13 3220 postgres 4186 8 7508 20412 281 0.31 3264 postgres 4123 8 6780 15332 281 0.16 3272 postgres 4136 8 7408 17472 281 4.89 3296 postgres 4163 8 6936 18400 281 0.27 3304 postgres 4125 8 6780 15512 281 0.13 3328 postgres 4139 ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2017-03-24 05:45:08 -0600

Udhaya gravatar image

Hi,

Please find our replies for the reported queries inline below.

-->After installing the fix of 3.7 to both BDR and ODR, inspite of services running, Unable to login to console

Please provide us the exact error message which you are getting while logging into Vembu BDR Backup Server console and server.log file to analyse this issue further. If you are getting 'Unable to login' error even if Vembu BDR service is running, then there is a possibility of database updates in progress for the previous interrupted jobs. If it takes more time, then please send us the above requested details for debugging purpose.

-->Also there are many postgres instance found running.

We have noticed that there are 72 instance of postgresql is running in your machine. Please note that for each new connection, postgresql will start a new process and normally that process will get closed when we close the respective connection. During backup/recovery process, there could be many db connections get established and will get closed when the backup/recovery process get completed. Also, in Vembu BDR, we have few threads which are active forever, and they will use some database connections. So, number of postgresql connections 72 is normal only.

-->Vembu Virtual Drive is GONE

Once Vembu BDR application is started, we will check and update the databases if previous db metadata files present in the location. Once after that, Vembu Virtual Drive will be listed in the explorer. It Virtual drive is not listed in explorer for more time even the BDR service is running, then please try to stop and then start the Vembu BDR service in your machine once and then verify whether Vembu Virtual Drive is listed in Windows explorer.

If the problem persists, please run Vembu BDR in command line (in administrative prompt) and send us the prints and screenshot of the explorer to analyse the issue.

-->I am looking at Windows application logs and notice, that every time Vembu server is rebooted – Apache Service triggers 2 exactly same errors on startup – is it normal?

${SRVROOT} is variable used in apache webserver configuration to mention the document root path, which we didn't use in our Vembu BDR web server configuration. This will create an undefined error in windows application log. This is a warning message and it will not affect the Vembu BDR web server. We will fix the same in our next release.

edit flag offensive delete link more
Login/Register to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2017-03-23 19:37:04 -0600

Seen: 138 times

Last updated: Mar 24

Copyright © Vembu Technologies 2017. All Rights Reserved.