native applications after logging into the portal No response after clicking Connect button

Daniel_Kavan — Sat, 05 Nov 2022 19:34:07 GMT

Hi all,

RE: R81.10 JHF75

After an upgrade this morning, I can log into the MAB portal successfully. However, when I click the Connect button, there is absolutely NO response, as if I never clicked it. I tried cvpnrestart, re-installing policy, no joy. I've tried all the major browsers as well. Also, I cannot log into the webui. I have 5200 running JHF75 and its working with out an issue.

Hmmm… can't reach this page

172.1.1.1 refused to connect.

Check your Internet connection

Check your network cables, modem, and routers.

Allow Microsoft Edge to access the network in your firewall or antivirus settings.

If it's already listed as a program allowed to access the network, try removing it from the list, and adding it again.

If you use a proxy server:

Check your proxy settings. You might need to ask your organization if the proxy server is working. If you don't think you should be using a proxy server, go to Settings > System > Open your computer's proxy settings

Re: native applications after logging into the portal No response after clicking Connect button

the_rock — Sat, 05 Nov 2022 20:08:04 GMT

Reach out to TAC, it might need some debugging to try figure out what happened. Personally, never heard of such an issue, upgrade or not.

Re: native applications after logging into the portal No response after clicking Connect button

Daniel_Kavan — Sat, 05 Nov 2022 21:25:48 GMT

I have, in the meantime, I'm seeing these in vpnd.elg. Also, tried turning acceleration off, no difference.

[5 Nov 8:50:55] T_event_fdclr_epoll: failed to clear socket: 92 from epoll set: Bad file descriptor
[5 Nov 8:58:22] T_event_fdclr_epoll: failed to clear socket: 54 from epoll set: Bad file descriptor
[5 Nov 8:58:22] T_event_fdclr_epoll: failed to clear socket: 55 from epoll set: Bad file descriptor
[5 Nov 8:58:22] T_event_fdclr_epoll: failed to clear socket: 56 from epoll set: Bad file descriptor
[5 Nov 9:14:04] T_event_fdclr_epoll: failed to clear socket: 82 from epoll set: Bad file descriptor
[5 Nov 9:14:04] T_event_fdclr_epoll: failed to clear socket: 84 from epoll set: Bad file descriptor
[5 Nov 9:14:04] T_event_fdclr_epoll: failed to clear socket: 85 from epoll set: Bad file descriptor
[5 Nov 9:47:49] T_event_fdclr_epoll: failed to clear socket: 53 from epoll set: Bad file descriptor
[5 Nov 9:47:49] T_event_fdclr_epoll: failed to clear socket: 54 from epoll set: Bad file descriptor
[5 Nov 9:47:49] T_event_fdclr_epoll: failed to clear socket: 55 from epoll set: Bad file descriptor
[5 Nov 10:13:07] T_event_fdclr_epoll: failed to clear socket: 56 from epoll set: Bad file descriptor
[5 Nov 10:13:07] T_event_fdclr_epoll: failed to clear socket: 64 from epoll set: Bad file descriptor
[5 Nov 10:13:07] T_event_fdclr_epoll: failed to clear socket: 65 from epoll set: Bad file descriptor
[5 Nov 10:18:38] T_event_fdclr_epoll: failed to clear socket: 140 from epoll set: Bad file descriptor
[5 Nov 10:18:38] T_event_fdclr_epoll: failed to clear socket: 142 from epoll set: Bad file descriptor
[5 Nov 10:18:38] T_event_fdclr_epoll: failed to clear socket: 143 from epoll set: Bad file descriptor
[5 Nov 10:20:34] T_event_fdclr_epoll: failed to clear socket: 94 from epoll set: Bad file descriptor
[5 Nov 10:20:34] T_event_fdclr_epoll: failed to clear socket: 95 from epoll set: Bad file descriptor
[5 Nov 10:20:34] T_event_fdclr_epoll: failed to clear socket: 96 from epoll set: Bad file descriptor
[Cvpnd 20930]@dred[5 Nov 10:47:37] Warning:cp_timed_blocker_handler: A handler [0xf6eaf980] blocked for 3 seconds.
[Cvpnd 20930]@dred[5 Nov 10:47:37] Warning:cp_timed_blocker_handler: Handler info: Library [/opt/CPsuite-R81.10/fw1/lib/libCvpnIsRpc.so], Function offset [0x9980].
[Cvpnd 20930]@dred[5 Nov 10:47:37] Warning:cp_timed_blocker_handler: Handler info: Nearest symbol name [_ZN4Cvpn17RpcRequestHandler19s_responseSendingCbEP7_FwConnPvj], offset [0x9980].
[Cvpnd 20930]@dred[5 Nov 10:47:37] Warning:cp_timed_blocker_handler: A handler [0xf68da660] blocked for 3 seconds.
[Cvpnd 20930]@dred[5 Nov 10:47:37] Warning:cp_timed_blocker_handler: Handler info: Library [/opt/CPshrd-R81.10/lib/libComUtils.so], Function offset [0x1e660].
[5 Nov 10:47:37] T_event_fdclr_epoll: failed to clear socket: 74 from epoll set: Bad file descriptor
[5 Nov 10:47:37] T_event_fdclr_epoll: failed to clear socket: 76 from epoll set: Bad file descriptor
[5 Nov 10:47:37] T_event_fdclr_epoll: failed to clear socket: 77 from epoll set: Bad file descriptor
[5 Nov 15:50:55] T_event_fdclr_epoll: failed to clear socket: 43 from epoll set: Bad file descriptor
[5 Nov 15:50:55] T_event_fdclr_epoll: failed to clear socket: 54 from epoll set: Bad file descriptor
[5 Nov 15:50:55] T_event_fdclr_epoll: failed to clear socket: 56 from epoll set: Bad file descriptor
[5 Nov 15:59:53] T_event_fdclr_epoll: failed to clear socket: 200 from epoll set: Bad file descriptor
[5 Nov 15:59:53] T_event_fdclr_epoll: failed to clear socket: 202 from epoll set: Bad file descriptor
[5 Nov 15:59:53] T_event_fdclr_epoll: failed to clear socket: 203 from epoll set: Bad file descriptor
[5 Nov 17:05:38] RADIUS Servers Cannot Be Reached. Dropping Request
[5 Nov 17:08:57] T_event_fdclr_epoll: failed to clear socket: 96 from epoll set: Bad file descriptor
[5 Nov 17:08:57] T_event_fdclr_epoll: failed to clear socket: 98 from epoll set: Bad file descriptor
[5 Nov 17:08:57] T_event_fdclr_epoll: failed to clear socket: 99 from epoll set: Bad file descriptor
[5 Nov 17:12:50] T_event_fdclr_epoll: failed to clear socket: 129 from epoll set: Bad file descriptor
[5 Nov 17:12:50] T_event_fdclr_epoll: failed to clear socket: 131 from epoll set: Bad file descriptor
[5 Nov 17:12:50] T_event_fdclr_epoll: failed to clear socket: 132 from epoll set: Bad file descriptor
[5 Nov 17:16:29] T_event_fdclr_epoll: failed to clear socket: 103 from epoll set: Bad file descriptor
[5 Nov 17:16:29] T_event_fdclr_epoll: failed to clear socket: 106 from epoll set: Bad file descriptor
[5 Nov 17:16:29] T_event_fdclr_epoll: failed to clear socket: 107 from epoll set: Bad file descriptor

Re: native applications after logging into the portal No response after clicking Connect button

the_rock — Sun, 06 Nov 2022 00:56:44 GMT

See if below post helps (another post at the bottom with POSSIBLE solution)

https://community.checkpoint.com/t5/Remote-Access-VPN/Mobile-Access-Blade-with-CIFS-segfault/td-p/81873

Andy

Re: native applications after logging into the portal No response after clicking Connect button

Daniel_Kavan — Sun, 06 Nov 2022 01:10:52 GMT

Thanks so much for the suggestion but I literally just got it working again. I had a throttle hot fix still installed sk173765 Once removed I was able to connect.

topic native applications after logging into the portal No response after clicking Connect button in Mobile

native applications after logging into the portal No response after clicking Connect button

Re: native applications after logging into the portal No response after clicking Connect button

Re: native applications after logging into the portal No response after clicking Connect button

Re: native applications after logging into the portal No response after clicking Connect button

Re: native applications after logging into the portal No response after clicking Connect button