This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Restart clientless service not possible from CLI - Bug

I was having a look at clientless feature and I would like to see more logs inside the clientless_access.log so I decided to enable debug on clientless_access service.

Clientless_access service does not exist!

Running service -S gives you the service list and the output is:

"clientless_acce RUNNING"

Running the command: service clientless_acce:debug -dsnosync returns "400 Service not found"

Running the command: service clientless_access:stop -dsnosync returns "200 ok"

So the service name under service list is wrong. Also, why it is not possible to debug clientless_access service? Maybe because it depends on another service?

Hope to get more info regarding it for troubleshooting purposes.

Thanks

This thread was automatically locked due to age.

Parents

0 sachingurung over 8 years ago

Hi Luk,

Look into the access_server debug logs.

Any help with that?
Cancel
Vote Up 0 Vote Down

Cancel
0 lferrara over 8 years ago in reply to sachingurung

Thanks,

Sachin. Even restarting ipsec into debug mode is not possible.

It seems that some services cannot be restarted by CLI, is it correct?

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 sachingurung over 8 years ago in reply to lferrara

Hi Luk,

You can restart IPSec VPN services from option 6. VPN management menu from the console.

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 lferrara over 8 years ago in reply to sachingurung

Thanks Sachin,

I know I can restart VPN service from console, but this is not the purpose of this thread. Some systems cannot be restarted in debug mode using the advanced shell.

Is it a bug/limitation? Please provide us a way to enable debug on every services under "system -S" from advanced shell for troubleshooting.

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 sachingurung over 8 years ago in reply to lferrara

Hi Luk,

IPSec logs that you capture under ipsec.log file contains the debug logs information by default. Same would be available for the other services.

Thanks
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 sachingurung over 8 years ago in reply to lferrara

Hi Luk,

IPSec logs that you capture under ipsec.log file contains the debug logs information by default. Same would be available for the other services.

Thanks
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data