Yes its definitely possible, look for configuration table in cloud db.

For ease of use, install mysql workbench, if you haven't done so already.

On 6/2/14, 3:04 PM, dimas yoga pratama wrote:
I accidentally unset vm limit in global settings, how to restore it? is it
possible to change it via database?


On Tue, Jun 3, 2014 at 4:38 AM, dimas yoga pratama <smid...@gmail.com>
wrote:

Ok I found the error now, How I revert back my configuration?


2014-06-03 04:13:41,608 ERROR [c.c.r.ResourceLimitManagerImpl] (main:null)
NumberFormatException during configuration
java.lang.NumberFormatException: null
         at java.lang.Long.parseLong(Long.java:404)
         at java.lang.Long.parseLong(Long.java:483)
         at
com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:231)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59)
         at
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167)
         at
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
         at
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)
         at
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143)
         at
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108)
         at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:945)
         at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)

2014-06-03 04:13:41,609 ERROR [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) Failed to configure ResourceLimitManagerImpl
javax.naming.ConfigurationException: Configuration failed due to
NumberFormatException, see log for the stacktrace
         at
com.cloud.resourcelimit.ResourceLimitManagerImpl.configure(ResourceLimitManagerImpl.java:241)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle$3.with(CloudStackExtendedLifeCycle.java:117)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.with(CloudStackExtendedLifeCycle.java:156)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.configure(CloudStackExtendedLifeCycle.java:113)
         at
org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:59)
         at
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167)
         at
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
         at
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)



On Tue, Jun 3, 2014 at 4:22 AM, Bret Mette <bret.me...@dbihosting.com>
wrote:

You should probably start by including what parameter(s) you changed and
any relavent log entries.

On Jun 2, 2014, at 2:20 PM, dimas yoga pratama <smid...@gmail.com>
wrote:
Hi,
Ok this is my problem, I change parameter in global settings, and I
unset
some value and I restarted the management server using "service
cloudstack-management restart".
I tried to access the MS back in http://10.151.32.51:8080/client/ and
no
luck, it returned 404 resource not available.
Is it a bug or something? How I can get my MS back?

looking forward for your answer,


Reply via email to