cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wilderrodrigues <>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-8530: KVM hosts without active...
Date Tue, 02 Jun 2015 11:21:12 GMT
Github user wilderrodrigues commented on the pull request:
    After running this on my KVM host:
    [root@kvm1 ~]# systemctl stop cloudstack-agent
    [root@kvm1 ~]# 
    The management server said:
    Then I started it agains:
    [root@kvm1 ~]# systemctl start cloudstack-agent
    [root@kvm1 ~]# systemctl status cloudstack-agent
    cloudstack-agent.service - SYSV: Cloud Agent
       Loaded: loaded (/etc/rc.d/init.d/cloudstack-agent)
       Active: active (running) since Tue 2015-06-02 07:20:10 EDT; 3s ago
      Process: 20054 ExecStop=/etc/rc.d/init.d/cloudstack-agent stop (code=exited, status=0/SUCCESS)
      Process: 20090 ExecStart=/etc/rc.d/init.d/cloudstack-agent start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/cloudstack-agent.service
               ├─20106 jsvc.exec -Xms256m -Xmx2048m -cp /usr/share/java/commons-daemon.jar:/usr/share/cloudstack-agent/lib/activation-1.1.jar:/usr/share/cloudstack-agent/lib/antisamy-1.4.3.jar:/usr/share/cloudstack-agent/lib/aopalliance-1.0.jar:/usr/share/cloudstack-agent/...
               └─20107 jsvc.exec -Xms256m -Xmx2048m -cp /usr/share/java/commons-daemon.jar:/usr/share/cloudstack-agent/lib/activation-1.1.jar:/usr/share/cloudstack-agent/lib/antisamy-1.4.3.jar:/usr/share/cloudstack-agent/lib/aopalliance-1.0.jar:/usr/share/cloudstack-agent/...
    Jun 02 07:20:10 kvm1 systemd[1]: Starting SYSV: Cloud Agent...
    Jun 02 07:20:10 kvm1 cloudstack-agent[20090]: Starting Cloud Agent:
    Jun 02 07:20:10 kvm1 systemd[1]: Started SYSV: Cloud Agent.
    [root@kvm1 ~]# 
    And on the UI:
    Thanks, Rohit!
    I will merge.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message