I rebuilt, verified that the new systemvm.iso was put into place, even
destroyed the console proxy system vm to ensure that it would pull in
the new code. Maybe you guys are using a system vm in an existing
environment that has code from pre-spring?

root@v-11-VM:~# tail /var/log/cloud/cloud.out
+ tot_mem_k=96180
+ let 'tot_mem_m=tot_mem_k>>10'
+ let 'eightypcnt=93*8/10'
+ let maxmem=93-80
+ '[' 13 -gt 74 ']'
+ java -Djavax.net.ssl.trustStore=./certs/realhostip.keystore -mx13m
-cp 
./:./conf:aopalliance-1.0.jar:apache-log4j-extras-1.1.jar:aspectjrt-1.7.1.jar:aspectjweaver-1.7.1.jar:aws-java-sdk-1.3.21.1.jar:backport-util-concurrent-3.1.jar:bcprov-jdk16-1.46.jar:cglib-nodep-2.2.2.jar:cloud-agent-4.1.0-SNAPSHOT.jar:cloud-api-4.1.0-SNAPSHOT.jar:cloud-console-proxy-4.1.0-SNAPSHOT.jar:cloud-core-4.1.0-SNAPSHOT.jar:cloud-utils-4.1.0-SNAPSHOT.jar:commons-codec-1.6.jar:commons-collections-3.2.1.jar:commons-configuration-1.8.jar:commons-dbcp-1.4.jar:commons-discovery-0.5.jar:commons-httpclient-3.1.jar:commons-lang-2.6.jar:commons-logging-1.1.1.jar:commons-pool-1.6.jar:dom4j-1.6.1.jar:ehcache-1.5.0.jar:ejb-api-3.0.jar:gson-1.7.1.jar:guava-14.0-rc1.jar:httpclient-4.1.jar:httpcore-4.1.jar:jackson-core-asl-1.8.9.jar:jackson-mapper-asl-1.8.9.jar:jasypt-1.9.0.jar:java-ipv6-0.8.jar:javassist-3.12.1.GA.jar:javax.inject-1.jar:javax.persistence-2.0.0.jar:jsch-0.1.42.jar:jsr107cache-1.0.jar:log4j-1.2.16.jar:reflections-0.9.8.jar:spring-aop-3.1.2.RELEASE.jar:spring-asm-3.1.2.RELEASE.jar:spring-beans-3.1.2.RELEASE.jar:spring-context-3.1.2.RELEASE.jar:spring-core-3.1.2.RELEASE.jar:spring-expression-3.1.2.RELEASE.jar:spring-web-3.1.2.RELEASE.jar:trilead-ssh2-build213-svnkit-1.3-patch.jar:xml-apis-1.0.b2.jar
com.cloud.agent.AgentShell template=domP type=consoleproxy
host=172.17.10.10 port=8250 name=v-11-VM premium=true zone=1 pod=1
guid=Proxy.11 proxy_vm=11 disable_rp_filter=true
eth2ip=192.168.100.188 eth2mask=255.255.255.0 gateway=192.168.100.1
eth0ip=169.254.0.85 eth0mask=255.255.0.0 eth1ip=172.17.10.180
eth1mask=255.255.255.0 mgmtcidr=192.168.100.0/24 localgw=172.17.10.1
internaldns1=8.8.4.4 dns1=8.8.8.8
log4j:WARN No appenders could be found for logger
(org.apache.commons.httpclient.params.DefaultHttpParams).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig
for more info.
Unable to start agent: Instantiation excetion when loading resource:
com.cloud.agent.resource.consoleproxy.ConsoleProxyResource due to:
java.lang.InstantiationException

On Wed, Feb 6, 2013 at 12:27 PM, Marcus Sorensen (JIRA) <j...@apache.org> wrote:
>
>     [ 
> https://issues.apache.org/jira/browse/CLOUDSTACK-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572711#comment-13572711
>  ]
>
> Marcus Sorensen commented on CLOUDSTACK-1173:
> ---------------------------------------------
>
> Saw this on master last night, with "mvn -P developer,systemvm clean
> install". I'll try again today.
>
>
>
>> ConsoleProxyResource instantiation exception
>> --------------------------------------------
>>
>>                 Key: CLOUDSTACK-1173
>>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1173
>>             Project: CloudStack
>>          Issue Type: Bug
>>      Security Level: Public(Anyone can view this level - this is the 
>> default.)
>>          Components: VNC Proxy
>>    Affects Versions: 4.1.0
>>         Environment: devcloud
>>            Reporter: Marcus Sorensen
>>             Fix For: 4.1.0
>>
>>
>> Looks like ConsoleProxy software is not coming up in the latest branches:
>> log4j:WARN No appenders could be found for logger 
>> (org.apache.commons.httpclient.params.DefaultHttpParams).
>> log4j:WARN Please initialize the log4j system properly.
>> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for 
>> more info.
>> Unable to start agent: Instantiation excetion when loading resource: 
>> com.cloud.agent.resource.consoleproxy.ConsoleProxyResource due to: 
>> java.lang.InstantiationException
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to