RE: VMs unable to reach public network
If I understand network configuration correctly - you are not using VLANs in reality, because you don't add tag to your traffic. The same for Cisco switch - it just listens on different ports. Traffic for public/private is untagged. I am not 100% sure, because my set-up is based on single NIC, but probably you need to assign IP to your bridge in order to work correctly. The other option I can suggest - try to look into Cisco switch configuration and see if ARP proxy is enabled for your public port. Physically you have 2 different HW interfaces and none is configured to have IP - how packet will know which interface to take? Try to run arp -n in order to see if your server/client sees the other side. Vadim. -Original Message- From: john.ple...@gmail.com [mailto:john.ple...@gmail.com] On Behalf Of John Pletka Sent: Tuesday, October 07, 2014 9:18 PM To: users@cloudstack.apache.org Subject: Re: VMs unable to reach public network One other oddity - output from route -n on the secondary storage VM. It's creating routes for the public mgmt service that route back through the private VLAN gateway. route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 XX.47.90.1 0.0.0.0 UG0 00 eth2 10.1.40.0 0.0.0.0 255.255.255.0 U 0 00 eth1 10.1.40.0 0.0.0.0 255.255.255.0 U 0 00 eth3 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 XX.47.90.0 0.0.0.0 255.255.255.0 U 0 00 eth2 XX.47.90.4 10.1.40.1 255.255.255.255 UGH 0 00 eth1 On Tue, Oct 7, 2014 at 2:07 PM, John Pletka jple...@abraxis.com wrote: I have a new CloudStack install and am facing the situation where guests can't access the public network. It assigns the public IP and gateway correctly, but when I ssh into the VM, it can only reach the private side. Specifically, I'm testing the secondary storage VM. Sorry for the config dump below, but hopefully something will stand out. For my setup I have: 1) Cisco 4948 switch. 1/2 the ports are a private VLAN 10.1.40.0. 1/2 the ports are public and connect upstream to a router. 2) 3 host machines running XenServer 6.2 with dual NICs. ETH0 - private VLAN, ETH1= public side of the switch 3) The Management is on a 4th server, dual nic and communicates to public and private fine 4) Each of the host machines has a private address assigned to xenbr0 (10.1.40.4, 10.1.40.5, 10.1.40.6). Gateway is 10.1.40.1, which is owned by the switch VLAN 5) The Public range is setup as xx.47.90.0/24 (.10-.254 available to guests) 6) The host servers can't reach the public network because I have not assigned a public address to xenbr1 # #Here is the network setup of the host servers: # xe network-list uuid ( RO): 486aabce-1215-6e5a-b2d7-1b4c433b8728 name-label ( RW): Host internal management network name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI bridge ( RO): xenapi uuid ( RO): c56c81c5-a29e-c68f-bb3d-b6393ce5ba20 name-label ( RW): cloud_link_local_network name-description ( RW): link local network used by system vms bridge ( RO): xapi0 uuid ( RO): ce61e701-84a2-0699-421e-22022ffb901f name-label ( RW): cloud-private name-description ( RW): bridge ( RO): xenbr0 uuid ( RO): dab93467-688e-871d-f4f8-3cb27e759a7c name-label ( RW): cloud-public name-description ( RW): bridge ( RO): xenbr1 # # In the CloudStack management, it give the following info for the secondary storage VM # TypeSecondary Storage VMZoneATL01Public IP AddressXX.47.90.103Private IP Address10.1.40.100Link Local IP Address169.254.1.159Hostxenserver03Gateway XX.47.90.1 # # on the VM itself, here is the ifconfig. Strangely it has two IP addresses # assigned to the management network, in addition to the public one ## ifconfig eth0 Link encap:Ethernet HWaddr 0e:00:a9:fe:01:9f inet addr:169.254.1.159 Bcast:169.254.255.255 Mask:255.255.0.0 inet6 addr: fe80::c00:a9ff:fefe:19f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:955 errors:0 dropped:0 overruns:0 frame:0 TX packets:701 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:68196 (66.5 KiB) TX bytes:95098 (92.8 KiB) Interrupt:25 eth1 Link encap:Ethernet HWaddr 06:5d:94:00:00:45 inet addr:10.1.40.100 Bcast:10.1.40.255 Mask:255.255.255.0 inet6 addr: fe80::45d:94ff:fe00:45/64 Scope:Link
Templates and new primary storage
Hi all, I recently added a new primary NFS storage to my system CloudStack 4.3 because the first was overloading. Now when I create new VM, the system continues to crearele in the old storage but I would like to force it to create the new machines in the new storage. Does anyone have idea on how you can do this? -- U g o V a s iugo.v...@procne.it P r o c n e s.r.l) via Cotonificio 45 33010 Tavagnacco IT phone: +390432486523 fax: +390432486523 Le informazioni contenute in questo messaggio sono riservate e confidenziali ed è vietata la diffusione in qualunque modo eseguita. Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene gentilmente comunicazione. Per qualsiasi informazione si prega di contattare supp...@procne.it . Rif. D.L. 196/2003
RE: Templates and new primary storage
Hi Ugo, Tag the new storage and create a new disk offering and submit into it your taged storage, when creating the vm select the new disk offering, the vm will be forced to spin up in the new storage. -Original Message- From: Ugo Vasi [mailto:ugo.v...@procne.it] Sent: Wednesday, 8 October 2014 3:28 PM To: users@cloudstack.apache.org Subject: Templates and new primary storage Hi all, I recently added a new primary NFS storage to my system CloudStack 4.3 because the first was overloading. Now when I create new VM, the system continues to crearele in the old storage but I would like to force it to create the new machines in the new storage. Does anyone have idea on how you can do this? -- U g o V a s iugo.v...@procne.it P r o c n e s.r.l) via Cotonificio 45 33010 Tavagnacco IT phone: +390432486523 fax: +390432486523 Le informazioni contenute in questo messaggio sono riservate e confidenziali ed è vietata la diffusione in qualunque modo eseguita. Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo e a non leggerlo, dandocene gentilmente comunicazione. Per qualsiasi informazione si prega di contattare supp...@procne.it . Rif. D.L. 196/2003
RE: 60 recipes for CloudStack
Great. thanks Kind regards, Cees Doets DATACENTER Services B.V. From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: maandag 6 oktober 2014 10:46 To: users@cloudstack.apache.org Subject: 60 recipes for CloudStack Hi folks, This is a shameless plug but if you want to read some exciting examples on how to use CloudStack effectively and learn about all the tools that work with CloudStack, you might consider my book :) http://shop.oreilly.com/product/0636920034377.do I will do this only once, I swear. -sebastien
IPv6 support for ESXi?
Hi, Is there any IPv6 support in CS for ESXi hypervisors? I've read the documentation but only KVM and Xen are mentioned so I was wondering if this will change in the new releases. Thanks, Octavian
[ACS 43] [MGMT Server][High Availability]
Hello Folks, I'm trying new HA implementation of my mgmt server. I'm looking for HA for the mysql server. Could it be problematic if i install a drbd active/passive mysql cluster ? (drbd heartbeat) The reason is because if i a have a fail of my primary server (and so the cluster doing a failover and transmiting its VIP (heartbeat) to the other node), the mysql server doesn't respond during few seconds (due to the deadtime parameter). So is this scenario problematic for the integrity of the management server ? Thanks for your responses.
Re: [ACS 43] [MGMT Server][High Availability]
Put the ACS java app in the same server and it will always get working mysql server when it is working. Also I suggest you start using pacemaker, corosync or cman. My management server is actually a virtual instance on RHEL active/active drbd cluster (so live migration works). If you want to test how it behaves, stop mysql and check for yourself. I highly doubt anyone has tested it yet. Regards, F. On 08 Oct 2014, at 11:37, benoit lair kurushi4...@gmail.com wrote: Hello Folks, I'm trying new HA implementation of my mgmt server. I'm looking for HA for the mysql server. Could it be problematic if i install a drbd active/passive mysql cluster ? (drbd heartbeat) The reason is because if i a have a fail of my primary server (and so the cluster doing a failover and transmiting its VIP (heartbeat) to the other node), the mysql server doesn't respond during few seconds (due to the deadtime parameter). So is this scenario problematic for the integrity of the management server ? Thanks for your responses.
Fwd: ACS 4.1.1 - 4.3.1 = errorInfo: [XENAPI_PLUGIN_FAILURE, getSnapshotSize, CommandException, 2] vhd-util: libvhd::vhd_open: failed to open /dev/VG_XenStorage-197c3580-fc82-35e5-356d-1f0909a9cfd
Sending it here. Maybe here someone will respond.
Begin forwarded message:
From: France mailingli...@isg.si
Subject: ACS 4.1.1 - 4.3.1 = errorInfo: [XENAPI_PLUGIN_FAILURE,
getSnapshotSize, CommandException, 2] vhd-util: libvhd::vhd_open: failed
to open
/dev/VG_XenStorage-197c3580-fc82-35e5-356d-1f0909a9cfd9/VHD-3d732e11-8697-4a45-9518-44d4154ee6d6:
-2
Date: 7 Oct 2014 19:04:15 GMT+2
To: d...@cloudstack.apache.org d...@cloudstack.apache.org
Reply-To: d...@cloudstack.apache.org
Hi guys,
after upgrading ACS from 4.1.1 to 4.3.1 and upgrading XS 6.0.2 to latest
hotfixes and manually replacing NFSSR.py with one from ACS 4.3.1, amongst
other errors, I see this error.
Snapshot is created successfully. I have created templates from it and used
them to create new VMs, but in the log there is an error. (Also snapshots are
not working on volumes which have had snapshots before the upgrade. But i
will deal with that issue later. They might even be related.)
What should I check to provide you with more info about the issue, so we can
address it?
Google search came up empty for this issue. :-( Please help me sort this out.
To me, it looks like Xen removed
/dev/VG_XenStorage-197c3580-fc82-35e5-356d-1f0909a9cfd9/VHD-3d732e11-8697-4a45-9518-44d4154ee6d6
after the copy to secondary storage but before cloudstack ordered the
removal.
Should I open a bug for it?
This is where i believe the snapshot was ordered:
/
2014-10-07 16:51:16,919 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(http-6443-exec-42:ctx-6a64da65 ctx-e324e472) submit async job-2171, details:
AsyncJobVO {id:2171, userId: 28, accountId: 30, instanceType: Snapshot,
instanceId: 977, cmd:
org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd, cmdInfo:
{id:977,response:json,sessionkey”:X,cmdEventType:SNAPSHOT.CREATE,ctxUserId:28,httpmethod:GET,_:1412693528063,volumeid:72d5b956-fbaf-44c2-8aeb-df49354ddbb3,quiescevm:false,ctxAccountId:30,ctxStartEventId:60842},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 95545481387, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-10-07 16:51:16,920 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(Job-Executor-84:ctx-649dbc0e) Add job-2171 into job monitoring
2014-10-07 16:51:16,920 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(Job-Executor-84:ctx-649dbc0e) Executing AsyncJobVO {id:2171, userId: 28,
accountId: 30, instanceType: Snapshot, instanceId: 977, cmd:
org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd, cmdInfo:
{id:977,response:json,sessionkey”:X,cmdEventType:SNAPSHOT.CREATE,ctxUserId:28,httpmethod:GET,_:1412693528063,volumeid:72d5b956-fbaf-44c2-8aeb-df49354ddbb3,quiescevm:false,ctxAccountId:30,ctxStartEventId:60842},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 95545481387, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-10-07 16:51:16,920 DEBUG [c.c.a.ApiServlet]
(http-6443-exec-42:ctx-6a64da65 ctx-e324e472) ===END=== XX.XX.XX.XX -- GET
command=createSnapshotvolumeid=72d5b956-fbaf-44c2-8aeb-df49354ddbb3quiescevm=falseresponse=jsonsessionkey=XX%3D_=1412693528063
2014-10-07 16:51:16,928 DEBUG [c.c.u.AccountManagerImpl]
(Job-Executor-84:ctx-649dbc0e ctx-e324e472) Access to
Acct[7ff6cd6b-7400-4d44-980b-9dc3115264eb-XX] granted to
Acct[7ff6cd6b-7400-4d44-980b-9dc3115264eb-] by DomainChecker
2014-10-07 16:51:16,953 INFO [o.a.c.a.c.u.s.CreateSnapshotCmd]
(Job-Executor-84:ctx-649dbc0e ctx-e324e472) VOLSS: createSnapshotCmd
starts:1412693476953
2014-10-07 16:51:17,290 DEBUG [c.c.a.t.Request] (Job-Executor-84:ctx-649dbc0e
ctx-e324e472) Seq 2-1824254062: Sending { Cmd , MgmtId: 95545481387, via:
2(x2.XXX), Ver: v1, Flags: 100011,
Re: Unable to start a VM due to insufficient capacity
Hi Geoff,
I used this URL:
http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.bz2
Il 06/10/2014 12:55, Geoff Higginbottom ha scritto:
Hi Ugo,
What system VM template did you use? (exact download URL please)
Regards
Geoff Higginbottom
D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
geoff.higginbot...@shapeblue.com
-Original Message-
From: Ugo Vasi [mailto:ugo.v...@procne.it]
Sent: 06 October 2014 10:57
To: users@cloudstack.apache.org
Subject: Re: Unable to start a VM due to insufficient capacity
Hi Geoff,
the problem is occurring in different networks (all?) that are not changed.
For us is a big problem because I can not predict when it occurs and the
creation of new machines is blocked until a network restarts (this method,
among other things, cause a small interruption of service).
What can I do to fix the problem?
Il 11/09/2014 09:28, Geoff Higginbottom ha scritto:
Hi Ugo,
Did restarting the network with cleanup option resolve your issue last time, if
yes have you tried the same on this network?
Regards
Geoff Higginbottom
CTO / Cloud Architect
D: +44 20 3603 0542tel:+442036030542 | S: +44 20 3603
0540tel:+442036030540 | M: +447968161581tel:+447968161581
geoff.higginbot...@shapeblue.commailto:geoff.higginbottom@shapeblue.c
om | www.shapeblue.comhtp://www.shapeblue.com/ |
Twitter:@cloudstackguruhttps://twitter.com/#!/cloudstackguru
ShapeBlue Ltd, 53 Chandos Place, Covent Garden, London, WC2N
4HSx-apple-data-detectors://5
On 11 Sep 2014, at 08:17, Ugo Vasi
ugo.v...@procne.itmailto:ugo.v...@procne.it wrote:
Hi Geoff,
I still have the problem creating new VMs but in another isolated network. The
problem seems to be the same:
2014-09-11 08:55:27,048 DEBUG [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) VM is being created in
podId: 1
2014-09-11 08:55:27,050 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Network id=212 is already
implemented
2014-09-11 08:55:27,118 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,122 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Changing active number of
nics for network id=212 on 1
2014-09-11 08:55:27,174 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Asking VirtualRouter to
prepare for Nic[116-86-8429f13f-7c3b-4b8a-aea3-9b8e9a3f4c03-10.1.1.19]
2014-09-11 08:55:27,181 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is acquired for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,183 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Lock is released for
network id 212 as a part of router startup in
Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Po
ol(Id))] :
Dest[Zone(1)-Pod(1)-Cluster(1)-Host(7)-Storage(Volume(98|ROOT--Pool(6
))]
2014-09-11 08:55:27,189 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,198 DEBUG [c.c.n.NetworkModelImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Service SecurityGroup is
not supported in the network id=212
2014-09-11 08:55:27,202 DEBUG
[c.c.n.r.VirtualNetworkApplianceManagerImpl]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Applying dhcp entry in
network Ntwk[212|Guest|8]
2014-09-11 08:55:27,215 DEBUG [c.c.a.t.Request]
(Job-Executor-55:ctx-b5c34ec7 ctx-3715f5de) Seq 7-564304056: Sending
{ Cmd , MgmtId: 77916390353436, via: 7(csh1b), Ver: v1, Flags: 100011,
[{com.cloud.agent.api.routing.DhcpEntryCommand:{vmMac:02:00:15:76
:00:0e,vmIpAddress:10.1.1.19,vmName:giannitest,defaultRouter
:10.1.1.1,defaultDns:10.1.1.1,duid:00:03:00:01:02:00:15:76:0
0:0e,isDefault:true,executeInSequence:false,accessDetails:{rou
ter.guest.ip:10.1.1.1,zone.network.type:Advanced,router.name:
r-60-VM,router.ip:169.254.1.230},wait:0}}] }
2014-09-11 08:55:27,941 DEBUG [c.c.s.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-327037b2) Zone 1 is ready to launch secondary
storage VM
2014-09-11 08:55:28,022 DEBUG [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-a8ba3b1e) Zone 1 is ready to launch console proxy
2014-09-11 08:55:28,820 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-58e92382) ===START=== 192.168.130.89 -- GET
command=queryAsyncJobResultjobId=195bf80a-9823-4ec3-add4-8907b98fbaf0
response=jsonsessionkey=qGZA6KYoc1SB%2Bq2k70HoM%2BBBQTU%3D_=1410418
528731
2014-09-11 08:55:29,069 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-13:null) Seq 7-564304056: Processing: { Ans: ,
MgmtId: 77916390353436, via: 7, Ver: v1, Flags: 10,
Updated and new Cloudstack templates
Hello, I've updated the existing CentOS templates and added some new ones - FreeBSD and Ubuntu. The Ubuntu template is actually their own cloud image with the cloudstack data source defined in cloud-init and the password script added. Let me know if you have any comments etc. http://dl.openvm.eu/cloudstack/ Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
VIF isolation with shared network
Hello, I created shared network in advanced zone with network offering which don't have services. I want that user add this network, manually configure network in VM and use this network. But I stick with problem, that users can set different IP to VM and use this network anyway. Is it possible to use something like vif-locking which is available in XenServer? Thanks.
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I tried to attached the management-server.log file but is too big. In Catalina.out I see the following error: Oct 08, 2014 7:23:08 AM org.apache.catalina.startup.Catalina start SEVERE: Catalina.start: LifecycleException: service.getName(): Catalina; Protocol handler start failed: java.net.BindException: Address already in use null:8080 at org.apache.catalina.connector.Connector.start(Connector.java:1087) at org.apache.catalina.core.StandardService.start(StandardService.java:531) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Oct 08, 2014 7:23:08 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 77 ms Oct 08, 2014 7:23:21 AM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Oct 08, 2014 7:23:22 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 08, 2014 7:23:22 AM org.apache.catalina.connector.MapperListener destroy WARNING: Error unregistering MBeanServerDelegate java.lang.NullPointerException at org.apache.catalina.connector.MapperListener.destroy(MapperListener.java:176) at org.apache.catalina.connector.Connector.stop(Connector.java:1128) at org.apache.catalina.core.StandardService.stop(StandardService.java:593) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744) at org.apache.catalina.startup.Catalina.stop(Catalina.java:643) at org.apache.catalina.startup.Catalina.start(Catalina.java:618) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Oct 08, 2014 7:23:22 AM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Oct 08, 2014 7:23:22 AM org.apache.catalina.connector.Connector stop SEVERE: Coyote connector has not been started On Wed, Oct 8, 2014 at 6:53 AM, motty cruz motty.c...@gmail.com wrote: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: Updated and new Cloudstack templates
Thanks man. On 08 Oct 2014 2:12 PM, Nux! n...@li.nux.ro wrote: Hello, I've updated the existing CentOS templates and added some new ones - FreeBSD and Ubuntu. The Ubuntu template is actually their own cloud image with the cloudstack data source defined in cloud-init and the password script added. Let me know if you have any comments etc. http://dl.openvm.eu/cloudstack/ Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
should I revert the upgrade? if you think I should. Do you know the steps to revert? I really need this cluster up and running. Thanks for your help!. -Motty On Wed, Oct 8, 2014 at 9:29 AM, motty cruz motty.c...@gmail.com wrote: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Custom logos :)
Hello, Two of my colleagues made 4 custom logo to CS. :-) If intrested, you can see the logos here: http://fazy.info/CSLogo/ Regards, Peter
Re: Custom logos :)
Nice, are they under a certain licence? :-) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Erdősi Péter f...@niif.hu To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 19:17:22 Subject: Custom logos :) Hello, Two of my colleagues made 4 custom logo to CS. :-) If intrested, you can see the logos here: http://fazy.info/CSLogo/ Regards, Peter
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
can I run cloudstack-setup-management would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz motty.c...@gmail.com wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
How did you upgrade exactly? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 22:31:57 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 can I run cloudstack-setup-management would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz motty.c...@gmail.com wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I can't revert the upgrade because the cloudstack.repo point to directory with two version 4.4.0 and 4.4.1 please help!! here is the link to management-server.log http://pastebin.com/raw.php?i=6cuXJd3S Thanks On Wed, Oct 8, 2014 at 2:31 PM, motty cruz motty.c...@gmail.com wrote: can I run cloudstack-setup-management would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz motty.c...@gmail.com wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hi Nux, I follow this steps to upgrade http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html here is my cloudstack.repo [cloudstack] name=cloudstack baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ enabled=1 gpgcheck=0 cloudstack.repo (END) Thanks for your help! On Wed, Oct 8, 2014 at 2:40 PM, Nux! n...@li.nux.ro wrote: How did you upgrade exactly? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 22:31:57 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 can I run cloudstack-setup-management would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz motty.c...@gmail.com wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, The error you see about not being able to connect to a host on port 9090 is normal when the management server is starting. There must be another error or warning somewhere. Please try the steps below to shrink the log file to manageable size and upload the file to some file sharing site if paste bin restricts you. service cloudstack-management stop cat /dev/null /var/log/cloudstack/management/management-server.log service cloudstack-management start wait 10 minutes upload the whole file or contents of it to google drive or something similar. What is your umask is set to? Regards ilya On 10/8/14, 1:04 PM, motty cruz wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, Here's a repo that still has 4.4.0 http://cloudstack.apt-get.eu/rhel/4.4/ You could try to yum downgrade to 4.4.0 and restore your DB. Do take backups before you do that.. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 23:31:00 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Hi Nux, I follow this steps to upgrade http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html here is my cloudstack.repo [cloudstack] name=cloudstack baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ enabled=1 gpgcheck=0 cloudstack.repo (END) Thanks for your help! On Wed, Oct 8, 2014 at 2:40 PM, Nux! n...@li.nux.ro wrote: How did you upgrade exactly? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 22:31:57 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 can I run cloudstack-setup-management would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz motty.c...@gmail.com wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - --
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, Roughly it's like this: mysql -ucsuser -pcspass csdb csdb.sql, the same for cloud_usage and cloudbridge (though these are less critical) PhpMyAdmin or Webmin can be helpful it you are not good with the command line. It's also possible you will have to drop those databases or the tables within altogether to make sure your backup is used and nothing extra. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 23:38:34 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 very grateful, for your help, I did a backup of database, I apologize for the this but I can't think of the command to restore MySQL backup. Thank you very much. On Wed, Oct 8, 2014 at 3:35 PM, Nux! n...@li.nux.ro wrote: Motty, Here's a repo that still has 4.4.0 http://cloudstack.apt-get.eu/rhel/4.4/ You could try to yum downgrade to 4.4.0 and restore your DB. Do take backups before you do that.. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 23:31:00 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Hi Nux, I follow this steps to upgrade http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html here is my cloudstack.repo [cloudstack] name=cloudstack baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ enabled=1 gpgcheck=0 cloudstack.repo (END) Thanks for your help! On Wed, Oct 8, 2014 at 2:40 PM, Nux! n...@li.nux.ro wrote: How did you upgrade exactly? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 22:31:57 Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 can I run cloudstack-setup-management would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz motty.c...@gmail.com wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hi ilya, here is the management-server.log as you suggest, I waited 10 minutes http://pastebin.com/raw.php?i=AiYXmxSU my umask 002 cat /etc/profile Thank you very much. On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Motty, The error you see about not being able to connect to a host on port 9090 is normal when the management server is starting. There must be another error or warning somewhere. Please try the steps below to shrink the log file to manageable size and upload the file to some file sharing site if paste bin restricts you. service cloudstack-management stop cat /dev/null /var/log/cloudstack/management/management-server.log service cloudstack-management start wait 10 minutes upload the whole file or contents of it to google drive or something similar. What is your umask is set to? Regards ilya On 10/8/14, 1:04 PM, motty cruz wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev ilya.mailing.li...@gmail.com wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky and...@arhont.com wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: motty cruz motty.c...@gmail.com To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber terbol...@gmail.com wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev motty cruz motty.c...@gmail.com følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber terbol...@gmail.com wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev motty cruz motty.c...@gmail.com følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz motty.c...@gmail.com wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
RE: Custom logos :)
Very nice and looks innovative :-) -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: 09 October 2014 00:16 To: users@cloudstack.apache.org Subject: Re: Custom logos :) Nice, are they under a certain licence? :-) Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Erdősi Péter f...@niif.hu To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 19:17:22 Subject: Custom logos :) Hello, Two of my colleagues made 4 custom logo to CS. :-) If intrested, you can see the logos here: http://fazy.info/CSLogo/ Regards, Peter
