Unable to login to CP GUI

[Krishnutz]

Hi,

I have NGX60 on Solaris and since friday i have tried to log in and am told that a user is connected do i want to:
read only
disconnect user and connect and cancel.
I try to disconnect user and connect.

But what i found it that no one else was logged onto it therefore nonne to disconnect as the message would display 'failed to connect'
If i do a CPRESTART, it allows me in.
However this has reoccured twice today again.....
Any ideas much appreciated!

[Krishnutz]

As noticed that no one has responded to this post...dont know if its because i am not explaining it well...
but i found a link that exactly described the symptons

http://secureknowledge.checkpoint.co....do?id=sk14220

Although going through this procedure it as still reoccured...anyone seen this?

I am in need of desperate help......i hope someone can...

Thanks in advance

[melipla]

Hi.

I would try to identify who it thinks is connected, it should tell you which user is connected. Specifically:
---------------------------
"<USER> is already connected to the SmartCenter Server:
<IP>.
What would you like to do?"

Cancel
Connect in Read-only
Disconnect <USER> and connect in Read/Write Mode.
---------------------------

What do you see for <USER> and <IP>? Hopefully you don't share usernames or IPs.

I don't know what would cause this error. Perhaps the dashboard lock file isn't being removed. More then just the "SmartDashboard" can lock the database..like Gui DB edit or the commandline version of the GUI DB edit for SPLAT might as well. I know that "Backup" and "snapshot" check for a lock...not sure if they make one when they're running...just things to look out for.

HTH

[Krishnutz]

Hi,

Thanks for your suggestions but i have managed to find a solution.
Something i did not mention was once a CPSTOP/CPSTART was done i can access the GUI, however if you try and change or add a service/rule and error would occurr when verifying the policy - something on the lines of
applications.C could not verify. I found out this was due to /VAR being full....
we had 85GB of archive and the live log was getting large.
If the applications.C is renamed log is cleared this seemed to resolve the problem.
N.B - I cannot for sure say it was the applications.C as i had a colleaugue escelate this to a senior member of Checkpoint in Isreal

Thanks for suggestions