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

XG 550 Web interface VERY SLOW

We have an XG 550 and from the beginning the web interface has been sluggish. It has gotten worse and now sometimes moving between windows takes 30 seconds or more depending on what we are doing. We just get the spinning wheel most of the time. Memory/CPU utilization aren't very high at all (memory is less than 60%). The main "control center" screen sometimes takes over a minute to fully load everything just so we can see bandwidth usage. Is there any trick to speeding this up to a workable level?

Edited TAGs
[edited by: emmosophos at 6:49 PM (GMT -7) on 7 Jun 2021]

Top Replies

LuCar Toni over 4 years ago +2

Assuming a object is broken, which cannot be loaded und runs into timeouts within the GUI. You could go to the shell, check the applog.log and csc.log to verify, if you click on firewall rules, there…

Parents

0 LuCar Toni over 4 years ago

Assuming a object is broken, which cannot be loaded und runs into timeouts within the GUI.

You could go to the shell, check the applog.log and csc.log to verify, if you click on firewall rules, there get any kind of errors, which could lead to timeouts of loading.
Cancel
Vote Up +2 Vote Down

Cancel
0 Josh Rogalski over 4 years ago in reply to LuCar Toni

Would this happen with a broken object even if the page does eventually load? And why would I experience slowness on so many pages? The "Control Center" doesn't spin, but is just very slow to load every time. Is that just normal because it does so many things? Would those logs show that page as well? Sorry I realize I am bombarding with questions here.
Cancel
Vote Up +1 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Josh Rogalski

The Webadmin will load all the time all the objects and access them. This can eventually slow down everything, if there is a corrupt item.
Cancel
Vote Up +2 Vote Down

Cancel

Reply

0 LuCar Toni over 4 years ago in reply to Josh Rogalski

The Webadmin will load all the time all the objects and access them. This can eventually slow down everything, if there is a corrupt item.
Cancel
Vote Up +2 Vote Down

Cancel

Children

0 Josh Rogalski over 4 years ago in reply to LuCar Toni

in csc.log, I did notice this set of messages, but am unsure if they are related. Are these objects fixable without a factory default of the appliance?

WARNING   Mar 05 09:55:46 [/fwcm/fwcm-heartbeatd.conf:2317]: Action with NOFAIL Failed.
MESSAGE   Mar 05 09:55:46 [worker:28220]: {"request":{"method":"opcode","name":"getpublickey","version":"1.6","type":"text","length":0}}
MESSAGE   Mar 05 09:55:46 [getpublickey:28220]: nvram_get(newkey:1) succeed
IFNAME_PREFIX: PortA
IFNAME_SUFFIX: NUM
IFLIST: A8_B8_C8_D8_M2
MESSAGE   Mar 05 09:55:46 [worker:28239]: {"request":{"method":"opcode","name":"readobject","version":"1.2","type":"json","length":26,"data":{"Entity":"parentproxyv4"}}}
########## Package: system::parentproxyv4
********** parentproxyv4 Read Without ORM
MESSAGE   Mar 05 09:55:47 [worker:28244]: {"request":{"method":"opcode","name":"readobject","version":"1.2","type":"json","length":26,"data":{"Entity":"parentproxyv6"}}}
########## Package: system::parentproxyv6
********** parentproxyv6 Read Without ORM
ERROR     Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: csc_execve: Child exited with status 240
ERROR     Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: log_exec: Failed Command: /bin/nvram get #fwcm.trx
WARNING   Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: Action with NOFAIL Failed.
ERROR     Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: csc_execve: Child exited with status 240
ERROR     Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: log_exec: Failed Command: /bin/nvram get #fwcm.trx_sts
WARNING   Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: Action with NOFAIL Failed.
ERROR     Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: csc_execve: Child exited with status 240
ERROR     Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: log_exec: Failed Command: /bin/nvram get #fwcm.grp_id
WARNING   Mar 05 09:55:47 [/fwcm/fwcm-heartbeatd.conf:2317]: Action with NOFAIL Failed.
Cancel
Vote Up 0 Vote Down

Cancel
0 LuCar Toni over 4 years ago in reply to Josh Rogalski

Those are normal alerts of CSC. As you are using one of the biggest appliances, both Logs will be under load, therefore its hard to debug within a community thread. You should interact with Sophos Support to get this looked at.
Cancel
Vote Up +2 Vote Down

Cancel