Restnoded keep coring dump when running as3 container
Follow the document, run below commands: docker run --name as3_container --rm -d -p 8443:443 -p 8080:80 f5devcentral/f5-as3-container:latest The restnoded keep restarting: [root@k8s-node1 ~] docker exec -it 715941f037b07d01a5fbb3fe990540a6b73627d9d1ce9198614ed3dfe828888b /bin/bash bash-4.4 cd /etc/service/restnoded/ bash-4.4 ls core.13042 core.13189 core.13220 core.13240 core.13270 core.13291 core.13328 core.13349 core.13396 core.13420 core.13443 core.13503 core.13525 finish run core.13170 core.13206 core.13230 core.13253 core.13280 core.13314 core.13339 core.13364 core.13410 core.13433 core.13491 core.13515 core.13542 log supervise logs of the container: bash-4.4 cd /var/log bash-4.4 ls -lrt total 76 drwxrwxrwx 2 root root 6 Jul 25 16:14 restnoded -rw-r--r-- 1 root root 136 Nov 28 02:16 restjavad.out -rw-r--r-- 1 root root 0 Nov 28 02:16 restjavad.0.log.lck -rw-r--r-- 1 root root 2479 Nov 28 02:16 restjavad-api-usage.json -rw-r--r-- 1 root root 58719 Nov 28 02:16 restjavad.0.log -rw-r--r-- 1 root root 1342 Nov 28 02:17 restjavad-gc.log.0.current -rw-r--r-- 1 root root 79 Nov 28 02:17 restnoded.out bash-4.4 tail -f restnoded.out lowering process privileges to: root/root, groups:0,0,1,2,3,4,6,10,11,20,26,27 ^C bash-4.4 ls restnoded/ bash-4.4 tail -f restjavad-gc.log.0.current 2018-11-28T02:16:51.923+0000: 8.186: [GC 40516K->14918K(95040K), 0.0107790 secs] 2018-11-28T02:16:56.864+0000: 13.127: [GC 41158K->14976K(95040K), 0.0038870 secs] 2018-11-28T02:17:02.518+0000: 18.781: [GC 41216K->14982K(95040K), 0.0028530 secs] 2018-11-28T02:17:08.314+0000: 24.577: [GC 41222K->14957K(95040K), 0.0038880 secs] 2018-11-28T02:17:14.038+0000: 30.302: [GC 41197K->15010K(95040K), 0.0028630 secs] 2018-11-28T02:17:18.423+0000: 34.686: [GC 41250K->14592K(95040K), 0.0033240 secs] 2018-11-28T02:17:24.217+0000: 40.480: [GC 40832K->14486K(95040K), 0.0028170 secs] 2018-11-28T02:17:29.925+0000: 46.188: [GC 40726K->14569K(95040K), 0.0035090 secs] 2018-11-28T02:17:35.722+0000: 51.985: [GC 40809K->14492K(95040K), 0.0028700 secs] 2018-11-28T02:17:41.398+0000: 57.662: [GC 40732K->14561K(95040K), 0.0029170 secs] 2018-11-28T02:17:46.786+0000: 63.049: [GC 40801K->14345K(95040K), 0.0029630 secs] 2018-11-28T02:17:52.369+0000: 68.632: [GC 40585K->14375K(95040K), 0.0027940 secs] Go into the container,and check logs: bash-4.4 cd /var/log bash-4.4 ls -lrt total 76 drwxrwxrwx 2 root root 6 Jul 25 16:14 restnoded -rw-r--r-- 1 root root 136 Nov 28 02:16 restjavad.out -rw-r--r-- 1 root root 0 Nov 28 02:16 restjavad.0.log.lck -rw-r--r-- 1 root root 2479 Nov 28 02:16 restjavad-api-usage.json -rw-r--r-- 1 root root 58719 Nov 28 02:16 restjavad.0.log -rw-r--r-- 1 root root 1342 Nov 28 02:17 restjavad-gc.log.0.current -rw-r--r-- 1 root root 79 Nov 28 02:17 restnoded.out bash-4.4 tail -f restnoded.out lowering process privileges to: root/root, groups:0,0,1,2,3,4,6,10,11,20,26,27 ^C bash-4.4 ls restnoded/ bash-4.4 tail -f restjavad-gc.log.0.current 2018-11-28T02:16:51.923+0000: 8.186: [GC 40516K->14918K(95040K), 0.0107790 secs] 2018-11-28T02:16:56.864+0000: 13.127: [GC 41158K->14976K(95040K), 0.0038870 secs] 2018-11-28T02:17:02.518+0000: 18.781: [GC 41216K->14982K(95040K), 0.0028530 secs] 2018-11-28T02:17:08.314+0000: 24.577: [GC 41222K->14957K(95040K), 0.0038880 secs] 2018-11-28T02:17:14.038+0000: 30.302: [GC 41197K->15010K(95040K), 0.0028630 secs] 2018-11-28T02:17:18.423+0000: 34.686: [GC 41250K->14592K(95040K), 0.0033240 secs] 2018-11-28T02:17:24.217+0000: 40.480: [GC 40832K->14486K(95040K), 0.0028170 secs] 2018-11-28T02:17:29.925+0000: 46.188: [GC 40726K->14569K(95040K), 0.0035090 secs] 2018-11-28T02:17:35.722+0000: 51.985: [GC 40809K->14492K(95040K), 0.0028700 secs] 2018-11-28T02:17:41.398+0000: 57.662: [GC 40732K->14561K(95040K), 0.0029170 secs] 2018-11-28T02:17:46.786+0000: 63.049: [GC 40801K->14345K(95040K), 0.0029630 secs] 2018-11-28T02:17:52.369+0000: 68.632: [GC 40585K->14375K(95040K), 0.0027940 secs]
Can an F5 VIP and Pool have a container member?
I have a container running on a Server with port 80 (TCP) exposed. The container is up and running when you test it on the serverIP and container port for example 172.27.27.2:80. I would now like to point an F5 VIP at a pool containing the member 172.27.27.2:80. I don't want to set up anything fancy using the F5 K8s setup but configure the setup through the F5 as it is were a basic IIS site or windows service. I cannot think of one but is there a reason this is not possible ? & is there a specific health monitor that should be used? at the moment the F5 keeps marking the member as offline.
