Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 3906 views
  • Users 0 members are here
Options
Suggested
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

UTM 9.710-1 not connecting to SUM

Rob Hall

SG-105, UTM Version 9.710-1. SUM Version 4.310013.

We replaced a 105 that was having severe power issues this morning. Deleted the old device from SUM, and powered up the new one. Reset the system ID via cc reset_system_id, and configured Central Management. Health is stuck at "starting  '/usr/sbin/acc-agent.plx'". The live log shows the following:

2022:05:03-10:21:07 fw01 device-agent[15983]: Connecting to SUM
2022:05:03-10:21:07 fw01 device-agent[15983]: Creating new SUM connection with id [1]
2022:05:03-10:21:07 fw01 device-agent[15983]: Updating SUM IP address for path: acc/server1/server
2022:05:03-10:21:07 fw01 device-agent[15983]: [1] Connecting to SUM (ip=192.168.0.8, port=4433).
2022:05:03-10:21:07 fw01 device-agent[15983]: [1] Using SUM SSL connection.
2022:05:03-10:21:07 fw01 device-agent[15983]: [1] We are now connected (ip=192.168.0.8, port=4433).
2022:05:03-10:21:07 fw01 device-agent[15983]: Connection to remote SUM established.
2022:05:03-10:21:07 fw01 device-agent[15983]: Starting watchers...
2022:05:03-10:21:07 fw01 device-agent[15983]: Starting connection...
2022:05:03-10:21:07 fw01 device-agent[15983]: Entering event loop...
2022:05:03-10:21:07 fw01 device-agent[15983]: SUM ehlo notification from [1]
2022:05:03-10:21:07 fw01 device-agent[15983]: Found SUM version 4.310013. Treating it as release 4.3.
2022:05:03-10:21:07 fw01 device-agent[15983]: Full SUM support is granted as the current SUM version isn't lower than the minimal required SUM version of: 4.2
2022:05:03-10:21:07 fw01 device-agent[15983]: [1] Received 0 bytes (eof).
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 1 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 2 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 3 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 4 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 5 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 6 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: timer2 -> module 7 not executing: denied by role
2022:05:03-10:21:12 fw01 device-agent[15983]: 1 is not connected. Trying to connect
Then repeats over and over.
I've reset the ID, I've shut down Central Management and ran a cleanup, deleted the objects, restarted the sum server. Nothing seems to be working. 


This thread was automatically locked due to age.
Parents
  • +1

    That last log entry led me to the answer.

    I shut down Central Management on the SG105, logged into the device via SSH. Then I deleted the guid file (rm /etc/guid), and restarted Central Management. The device registered successfully.

Reply
  • +1

    That last log entry led me to the answer.

    I shut down Central Management on the SG105, logged into the device via SSH. Then I deleted the guid file (rm /etc/guid), and restarted Central Management. The device registered successfully.

Children
No Data
Unfiltered HTML