Lueton commented on issue #6716:
URL: https://github.com/apache/cloudstack/issues/6716#issuecomment-1249202252

   @weizhouapache thats good to know, i was very confused!  
     
   this is my `/agent/setup.log` after trying to add this machine as a new 
host, maybe you can identify the issue.
   ```
   root@delta:~# cat /var/log/cloudstack/agent/setup.log
   DEBUG:root:execute:uname -r
   DEBUG:root:execute:uname -m
   DEBUG:root:execute:hostname -f
   DEBUG:root:execute:kvm-ok
   DEBUG:root:execute:awk '/MemTotal/ { printf "%.3f \n", $2/1024 }' 
/proc/meminfo
   DEBUG:root:execute:ip a | grep "^\w" | grep -iv "^lo" | wc -l
   DEBUG:root:execute:service apparmor status
   DEBUG:root:execute:apparmor_status |grep libvirt
   DEBUG:root:Failed to execute:
   DEBUG:root:execute:/bin/systemctl mask libvirtd.socket
   DEBUG:root:execute:/bin/systemctl mask libvirtd-ro.socket
   DEBUG:root:execute:/bin/systemctl mask libvirtd-admin.socket
   DEBUG:root:execute:/bin/systemctl mask libvirtd-tls.socket
   DEBUG:root:execute:/bin/systemctl mask libvirtd-tcp.socket
   DEBUG:root:execute:systemctl restart libvirtd
   DEBUG:root:execute:ufw allow 22
   DEBUG:root:execute:ufw allow 1798
   DEBUG:root:execute:ufw allow 16509
   DEBUG:root:execute:ufw allow 16514
   DEBUG:root:execute:ufw allow proto tcp from any to any port 5900:6100
   DEBUG:root:execute:ufw allow proto tcp from any to any port 49152:49216
   DEBUG:root:execute:sudo /usr/sbin/service ufw status
   DEBUG:root:execute:sudo /usr/sbin/service ufw stop
   DEBUG:root:execute:sudo /usr/sbin/service ufw status
   DEBUG:root:Failed to execute:● ufw.service - Uncomplicated firewall
        Loaded: loaded (/lib/systemd/system/ufw.service; enabled; vendor 
preset: enabled)
        Active: inactive (dead) since Fri 2022-09-16 10:17:25 UTC; 23ms ago
          Docs: man:ufw(8)
       Process: 2354 ExecStop=/lib/ufw/ufw-init stop (code=exited, 
status=0/SUCCESS)
      Main PID: 396 (code=exited, status=0/SUCCESS)
   
   Sep 16 10:16:19 delta systemd[1]: Finished Uncomplicated firewall.
   Sep 16 10:17:25 delta systemd[1]: Stopping Uncomplicated firewall...
   Sep 16 10:17:25 delta systemd[1]: ufw.service: Succeeded.
   Sep 16 10:17:25 delta systemd[1]: Stopped Uncomplicated firewall.
   DEBUG:root:execute:sudo /usr/sbin/service ufw start
   DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
   DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent stop
   DEBUG:root:execute:sleep 30
   DEBUG:root:execute:sudo update-rc.d -f cloudstack-agent remove
   DEBUG:root:execute:sudo update-rc.d -f cloudstack-agent defaults
   DEBUG:root:Failed to execute:update-rc.d: error: unable to read 
/etc/init.d/cloudstack-agent
   DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
   DEBUG:root:Failed to execute:● cloudstack-agent.service - CloudStack Agent
        Loaded: loaded (/lib/systemd/system/cloudstack-agent.service; enabled; 
vendor preset: enabled)
        Active: failed (Result: exit-code) since Fri 2022-09-16 10:17:28 UTC; 
30s ago
          Docs: http://www.cloudstack.org/
      Main PID: 2216 (code=exited, status=143)
   
   Sep 16 10:17:23 delta systemd[1]: Started CloudStack Agent.
   Sep 16 10:17:23 delta java[2216]: SLF4J: Failed to load class 
"org.slf4j.impl.StaticLoggerBinder".
   Sep 16 10:17:23 delta java[2216]: SLF4J: Defaulting to no-operation (NOP) 
logger implementation
   Sep 16 10:17:23 delta java[2216]: SLF4J: See 
http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
   Sep 16 10:17:27 delta systemd[1]: Stopping CloudStack Agent...
   Sep 16 10:17:28 delta systemd[1]: cloudstack-agent.service: Main process 
exited, code=exited, status=143/n/a
   Sep 16 10:17:28 delta systemd[1]: cloudstack-agent.service: Failed with 
result 'exit-code'.
   Sep 16 10:17:28 delta systemd[1]: Stopped CloudStack Agent.
   DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent start
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to