Community
 
 
 

CloudPlatform 4.x

284 followers
 
Avatar
Sadanand Patel

Secondary Storage Problem

Hi All,

After upgrading CloudPlatform 4.5.1 to 4.7.0, secondary storage showing 0.00 kb. and system vm's not up after reboot or destroy.

3 comments
0
 
 

Official comment

Avatar
Kiran Manohar Chavala

Hi Sadanand patel

Could you please send us the logs to investigate the issue 


/var/log/cloudstack/management/management-server.log

Comment actions Permalink

Please sign in to leave a comment.

 
 

Previous 3 comments

Avatar
Sadanand Patel

Hi Kiran,

 
we have successfully upgraded from 4.5.1 to 4.7, earlier we were facing some problem with Storage but that has been resolved, but still having one issue while rebooting management server, services got failed on every reboot and then we have to give permission manually on /var/run and same will happen again if i reboot the server again. so any idea about this ? Selinux is also disabled. 
 
Anyways We are doing testing and will keep you posted if i will get anything.
  
Errors:
Sep 19 16:58:33 ccp0-testing systemd: Unit cloudstack-management.service entered failed state.
Sep 19 16:58:33 ccp0-testing systemd: cloudstack-management.service failed.
Sep 19 17:01:01 ccp0-testing systemd: Started Session 2 of user root.
Sep 19 17:01:01 ccp0-testing systemd: Starting Session 2 of user root.
Sep 19 17:04:38 ccp0-testing systemd: Starting CloudStack Management Server...
Sep 19 17:04:38 ccp0-testing tomcat-sysd: /usr/sbin/tomcat-sysd: line 50: /var/run/cloudstack-management.pid: Permission denied
Sep 19 17:04:38 ccp0-testing systemd: cloudstack-management.service: control process exited, code=exited status=1
Sep 19 17:04:38 ccp0-testing systemd: Failed to start CloudStack Management Server.
Sep 19 17:04:38 ccp0-testing systemd: Unit cloudstack-management.service entered failed state.
Sep 19 17:04:38 ccp0-testing systemd: cloudstack-management.service failed.
Comment actions Permalink
Avatar
Kiran Manohar Chavala

Hi Sadandand 

yes we are aware of the issue and will be fixing the issue in a hotfix 4.7 HF1 and also upcoming release 4.7.1.



as a workaround , 

#vi /etc/rc/rc.local

Please add the entry
chmod -R 777 /var/run

Save and exit the file and execute the below commands

# chmod u+x /etc/rc.d/rc.local
# systemctl start rc-local
 

Comment actions Permalink

Top Contributors