topic Re: Commit Error (sslvpn) in General Topics

Commit Error (sslvpn)

rsaber — Tue, 19 Feb 2013 13:04:19 GMT

Hi,

I am recieving the following error when issuing a commit,

Management server failed to send phase 1 abort to client sslvpn

Management server failed to send phase 1 to client useridd

Commit failed

The only change in configuration is adding new local users which are used for global protect.

I am running 5.0.1

Regards

Re: Commit Error (sslvpn)

ssharma — Tue, 19 Feb 2013 16:36:27 GMT

Hi,

Can you run "show management-clients" next time you do a commit and see if the

"sslvpn 10 P2-ok 100"

is stuck at 98 or 99 instead of 100. If that is the case, restart management server "debug software restart management-server " and try to do a commit again and see that makes any difference. Thanks.

Re: Commit Error (sslvpn)

mbutt — Tue, 19 Feb 2013 19:42:35 GMT

Hi,

Can you see if you are getting any cores on the device.

You can do show system files from CLI and see if the system cores when commit fails.

Also what happens if you revert the changes you made. Does it allow you to commit then.

If it does then it is quite possible that the configuration might be incorrrect.

Thanks

Numan

Re: Commit Error (sslvpn)

rsaber — Sat, 23 Feb 2013 08:48:20 GMT

Thank you for the feedback,

The commit for the same configuration is happening sometimes and sometimes I receive the error

Regarding the "show management-clients" it is 0

As for cores I can see the following:

/opt/dpfs/var/cores/:

total 4.0K

drwxrwxrwx 2 root root 4.0K Dec 6 17:53 crashinfo

t/dpfs/var/cores/crashinfo:

total 0

/var/cores/:

total 27M

drwxrwxrwx 2 root root 4.0K Jan 31 10:04 crashinfo

-rw-r--r-- 1 root root 27M Jan 31 10:17 websrvr_5.0.1_2.tar.gz

/var/cores/crashinfo:

total 36K

-rw-rw-rw- 1 root root 9.2K Dec 10 09:48 websrvr_5.0.1_0.info

-rw-rw-rw- 1 root root 11K Jan 14 06:19 websrvr_5.0.1_1.info

-rw-rw-rw- 1 root root 10K Jan 31 10:04 websrvr_5.0.1_2.info

Re: Commit Error (sslvpn)

sdurga — Sun, 24 Feb 2013 19:41:42 GMT

Try restarting management server and see if this fixes the issue with subsequent commits. Management-Server restart has zero impact on traffic. You should log-out and log in back after the management server restart.

command for the same.

debug software restart management-server

Thanks,

Sandeep T