How to make permanent changes to agent.properties
Hi Folks, I'm running a very simple cloudstack setup on a single machine (I'm attempting to get more familiar with it) and for whatever reason, whenever I restart cloudstack.agent, the agent.properties file gets rewritten with the line: host=localhost@static This results in SSL communication errors in the log: 2018-10-10 10:07:01,565 DEBUG [o.a.c.c.p.RootCACustomTrustManager] (pool-252-thread-1:null) (logid:) A client/agent attempting connection from address=127.0.0.1 has presented these certificate(s): Certificate [1] : Serial: 348e41b92390b91d Not Before:Tue Oct 09 21:46:05 EDT 2018 Not After:Thu Oct 10 09:46:05 EDT 2019 Signature Algorithm:SHA256withRSA Version:3 Subject DN:C=cloudstack, O=cloudstack, OU=cloudstack, CN=nix.viviotech.net Issuer DN:CN=ca.cloudstack.apache.org Alternative Names:[[7, fe80:0:0:0:fc00:2eff:fe00:12], [7, fe80:0:0:0:fc00:fbff:fe00:3], [7, fe80:0:0:0:fc00:22ff:fe00:29], [7, 192.168.122.1], [7, fe80:0:0:0:fc00:a9ff:fefe:79], [7, fe80:0:0:0:e8b9:3fff:fe81:524d], [7, fe80:0:0:0:fc00:a9ff:fefe:2a8], [7, fe80:0:0:0:225:90ff:fed2:15da], [7, 192.168.253.2], [7, fe80:0:0:0:fc00:4bff:fe00:7], [2, 192.168.253.2]] Certificate [2] : Serial: d9fead25f9acaf6a Not Before:Mon Oct 08 02:17:06 EDT 2018 Not After:Wed Sep 30 14:17:06 EDT 2048 Signature Algorithm:SHA256withRSA Version:3 Subject DN:CN=ca.cloudstack.apache.org Issuer DN:CN=ca.cloudstack.apache.org Alternative Names:null 2018-10-10 10:07:01,566 ERROR [o.a.c.c.p.RootCACustomTrustManager] (pool-252-thread-1:null) (logid:) Certificate ownership verification failed for client: 127.0.0.1 If I change the agent.properties file to read: host=192.168.253.2@static ... which is the actual IP of the server, and I restart the agent, everything works great. However the agent.properties file is overwritten with the localhost@static value as soon as the agent starts up so the next time I restart the agent I get the 127.0.0.1 SSL errors again. Playing with the server and doing lots of restarts becomes pretty frustrating. So, my question is: What process is rewriting the agent.properties file and where does it get it's values from? If I knew that I could correct the issue at its source. Thanks in advance for any direction on this! Kind regards, Jordan Michaels Vivio Technologies
Re: [SOLVED] How to make permanent changes to agent.properties
Thanks Bobby. That was it. I edited the "host" value in the "Global Settings" of the CloudStack GUI and the value stayed the same after the agent restarted. Really appreciate you pointing me in the right direction my friend. =) -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Boris Stoyanov" To: "users" , "jordan" Sent: Thursday, 11 October, 2018 01:15:57 Subject: Re: How to make permanent changes to agent.properties Hi Jordan, It gets overridden to ‘localhost’ probably because the ‘host’ global setting is set to ‘localhost’. If you’re using just one management it’s safe to change that to 192.168.253.2 and it’ll get updated. In order to overcome the SSL error you could probably need to restart management, but first give it a try without restarting it. Thanks, Bobby. boris.stoya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue > On 10 Oct 2018, at 23:14, Jordan Michaels wrote: > > Hi Folks, > > I'm running a very simple cloudstack setup on a single machine (I'm > attempting to get more familiar with it) and for whatever reason, whenever I > restart cloudstack.agent, the agent.properties file gets rewritten with the > line: > > host=localhost@static > > This results in SSL communication errors in the log: > > > 2018-10-10 10:07:01,565 DEBUG [o.a.c.c.p.RootCACustomTrustManager] > (pool-252-thread-1:null) (logid:) A client/agent attempting connection from > address=127.0.0.1 has presented these certificate(s): > Certificate [1] : > Serial: 348e41b92390b91d > Not Before:Tue Oct 09 21:46:05 EDT 2018 > Not After:Thu Oct 10 09:46:05 EDT 2019 > Signature Algorithm:SHA256withRSA > Version:3 > Subject DN:C=cloudstack, O=cloudstack, OU=cloudstack, CN=nix.viviotech.net > Issuer DN:CN=ca.cloudstack.apache.org > Alternative Names:[[7, fe80:0:0:0:fc00:2eff:fe00:12], [7, > fe80:0:0:0:fc00:fbff:fe00:3], [7, fe80:0:0:0:fc00:22ff:fe00:29], [7, > 192.168.122.1], [7, fe80:0:0:0:fc00:a9ff:fefe:79], [7, > fe80:0:0:0:e8b9:3fff:fe81:524d], [7, fe80:0:0:0:fc00:a9ff:fefe:2a8], [7, > fe80:0:0:0:225:90ff:fed2:15da], [7, 192.168.253.2], [7, > fe80:0:0:0:fc00:4bff:fe00:7], [2, 192.168.253.2]] > Certificate [2] : > Serial: d9fead25f9acaf6a > Not Before:Mon Oct 08 02:17:06 EDT 2018 > Not After:Wed Sep 30 14:17:06 EDT 2048 > Signature Algorithm:SHA256withRSA > Version:3 > Subject DN:CN=ca.cloudstack.apache.org > Issuer DN:CN=ca.cloudstack.apache.org > Alternative Names:null > 2018-10-10 10:07:01,566 ERROR [o.a.c.c.p.RootCACustomTrustManager] > (pool-252-thread-1:null) (logid:) Certificate ownership verification failed > for client: 127.0.0.1 > > > If I change the agent.properties file to read: > > host=192.168.253.2@static > > ... which is the actual IP of the server, and I restart the agent, everything > works great. However the agent.properties file is overwritten with the > localhost@static value as soon as the agent starts up so the next time I > restart the agent I get the 127.0.0.1 SSL errors again. Playing with the > server and doing lots of restarts becomes pretty frustrating. > > So, my question is: What process is rewriting the agent.properties file and > where does it get it's values from? If I knew that I could correct the issue > at its source. > > Thanks in advance for any direction on this! > > Kind regards, > Jordan Michaels > Vivio Technologies
Where to look when your SSVM creation NPE's?
ot sure what else could be wrong or where else to look. Could someone point me in the right direction on where to look to get what's actually failing here? Thank you in advance! Kind regards, Jordan Michaels Vivio Technologies
Re: Where to look when your SSVM creation NPE's?
Hi Si, Thanks so much for the follow-up! > Could you tell us a bit more about your setup? I've got a little lab setup, with a dedicated router, switch, and several 1U's that I can test with. Will eventually set up a little micro-environment with VLAN's and such but for now just trying to get things working - which is turning out to be much more difficult than it sounds. > Hypervisor Type? KVM for now > Network design (basic or advanced)? Basic; using a single 192.168.253.0/24 range for the various networks similar to what's shown here: http://docs.cloudstack.apache.org/en/4.11.1.0/installguide/hypervisor/kvm.html#configuring-the-networking I've got the two bridges set up with the management IP assigned to cloudbr0 and no ip assigned to cloudbr1. > Primary storage type? I've tried NFS and local, though the result is the same regardless. > CloudStack version? 4.11 > OS being used? CentOS 7 More than just getting it working, I'd like to know where to find out what error is actually occurring here. I want to understand the details. I'm guessing the NPE is because the API was expecting to get something back from the storage server and it didn't? Is the command that was sent logged anywhere? What about the result? If the command that was sent to the storage server threw an error, is there a way that I can see what the error was specifically? Thanks so much for your time. I really appreciate it. -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Simon Weller" To: "users" , "jordan" Sent: Thursday, 18 October, 2018 13:14:41 Subject: Re: Where to look when your SSVM creation NPE's? Jordan, Could you tell us a bit more about your setup? Hypervisor Type? Network design (basic or advanced)? Primary storage type? CloudStack version? OS being used? - Si From: Jordan Michaels Sent: Thursday, October 18, 2018 2:26 PM To: users Subject: Where to look when your SSVM creation NPE's? Hi Folks, I've added a host to the CloudStack Management server but now I'm getting NPE's when the Management server tries to create the System VM's: 2018-10-18 06:20:26,052 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (Work-Job-Executor-40:ctx-ac017e0e job-1248/job-1621) (logid:b6f3dd96) Done executing com.cloud.vm.VmWorkStart for job-1621 2018-10-18 06:20:26,054 INFO [o.a.c.f.j.i.AsyncJobMonitor] (Work-Job-Executor-40:ctx-ac017e0e job-1248/job-1621) (logid:b6f3dd96) Remove job-1621 from job monitoring 2018-10-18 06:20:26,073 WARN [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-70aba7ab) (logid:f3c51c51) Exception while trying to start secondary storage vm java.lang.NullPointerException at com.cloud.network.guru.DirectPodBasedNetworkGuru$2.doInTransactionWithoutResult(DirectPodBasedNetworkGuru.java:183) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:40) at com.cloud.network.guru.DirectPodBasedNetworkGuru.getIp(DirectPodBasedNetworkGuru.java:173) at com.cloud.network.guru.DirectPodBasedNetworkGuru.reserve(DirectPodBasedNetworkGuru.java:161) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepareNic(NetworkOrchestrator.java:1594) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1565) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:4930) at sun.reflect.GeneratedMethodAccessor155.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5093) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:581) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at
Re: Where to look when your SSVM creation NPE's?
TBH, I'm not sure. Probably the latest. Whatever is delivered when you add the CloudStack repo. I built this instance ~3-4 days ago. -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Rafael Weingärtner" To: "users" , "jordan" Cc: "Simon Weller" Sent: Friday, 19 October, 2018 02:49:32 Subject: Re: Where to look when your SSVM creation NPE's? 4.11.0.0? -- Rafael Weingärtner
Re: Where to look when your SSVM creation NPE's?
Looking closer at secondary storage, this appears to be the issue. Thank you Boris. I've added both a 'local' NFS share (from when I installed it on the single server, 192.168.253.2) and a remote NFS share (192.168.253.30) as secondary storage. They both show up just fine in the CloudStack GUI and when I mount the remote NFS share to a temp directory (/secondary) on the management server, it shows up just fine, so it doesn't appear to be an issue with NFS: [root@local secondary]# mount -t nfs 192.168.253.30:/mnt/secondary /secondary [root@local secondary]# df -h Filesystem Size Used Avail Use% Mounted on 192.168.253.30:/mnt/secondary 923G 5.7G 917G 1% /secondary Again, I'm not actually trying to use /secondary, I'm just demonstrating that it mounts fine from the management server and that the space is available. However, the CloudStack GUI doesn't show any actual space in secondary storage - despite two servers being configured as secondary storage. Screen shots attached. How would I go about further troubleshooting this issue? Thank you very much for any direction you can offer. -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Boris Stoyanov" To: "users" , "jordan" Cc: "Simon Weller" Sent: Thursday, 18 October, 2018 22:20:06 Subject: Re: Where to look when your SSVM creation NPE's? 2018-10-18 06:20:26,076 INFO [o.a.c.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-70aba7ab) (logid:f3c51c51) Unable to start secondary storage vm for standby capacity, vm id : 346, will recycle it and start a new one 2018-10-18 06:20:26,095 INFO [o.a.c.s.PremiumSecondaryStorageManagerImpl] (secstorage-1:ctx-70aba7ab) (logid:f3c51c51) Primary secondary storage is not even started, wait until next turn Looks like you have an issue with secondary storage, can you check status/add it again and troubleshoot it? Bobby. boris.stoya...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue > On 19 Oct 2018, at 0:23, Jordan Michaels wrote: > > Hi Si, > > Thanks so much for the follow-up! > >> Could you tell us a bit more about your setup? > > I've got a little lab setup, with a dedicated router, switch, and several > 1U's that I can test with. Will eventually set up a little micro-environment > with VLAN's and such but for now just trying to get things working - which is > turning out to be much more difficult than it sounds. > >> Hypervisor Type? > > KVM for now > >> Network design (basic or advanced)? > > Basic; using a single 192.168.253.0/24 range for the various networks similar > to what's shown here: > http://docs.cloudstack.apache.org/en/4.11.1.0/installguide/hypervisor/kvm.html#configuring-the-networking > > I've got the two bridges set up with the management IP assigned to cloudbr0 > and no ip assigned to cloudbr1. > >> Primary storage type? > > I've tried NFS and local, though the result is the same regardless. > >> CloudStack version? > > 4.11 > >> OS being used? > > CentOS 7 > > More than just getting it working, I'd like to know where to find out what > error is actually occurring here. I want to understand the details. > > I'm guessing the NPE is because the API was expecting to get something back > from the storage server and it didn't? Is the command that was sent logged > anywhere? What about the result? If the command that was sent to the storage > server threw an error, is there a way that I can see what the error was > specifically? > > Thanks so much for your time. I really appreciate it. > > -- > Kind regards, > Jordan Michaels > Vivio Technologies > > - Original Message - > From: "Simon Weller" > To: "users" , "jordan" > Sent: Thursday, 18 October, 2018 13:14:41 > Subject: Re: Where to look when your SSVM creation NPE's? > > Jordan, > > > Could you tell us a bit more about your setup? > > Hypervisor Type? Network design (basic or advanced)? Primary storage type? > CloudStack version? OS being used? > > - Si > > From: Jordan Michaels > Sent: Thursday, October 18, 2018 2:26 PM > To: users > Subject: Where to look when your SSVM creation NPE's? > > Hi Folks, > > I've added a host to the CloudStack Management server but now I'm getting > NPE's when the Management server tries to create the System VM's: > > 2018-10-18 06:20:26,052 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] > (Work-Job-Executor-40:ctx-ac017e0e job-1248/job-1621) (logid:b6f3dd96)
Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE 0.00KB (URGENT)
I am encountering this issue in a single-server setup as well. The initial setup worked fine, then I messed with some network settings a bit which caused me to remove the one host, and cannot get the system up and running again because secondary storage shows 0KB. Verified NFS shares are writable, verified firewall ports are open, not sure what else to check or to try. -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Alexandre Bruyere" To: "users" Sent: Wednesday, 24 October, 2018 06:39:43 Subject: Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE 0.00KB (URGENT) Just saw you followed it, and I'm not sure where the problem is, I'll need to study it - I've had no trouble on my part. On Wed, Oct 24, 2018 at 9:34 AM Alexandre Bruyere < bruyere.alexan...@gmail.com> wrote: > For reference, you can use iptables commands in firewall-cmd by using the > --direct option. > > I've made a pull request to update the Quick Installation Guide with an > example of commands you can use to configure the firewall. > > On Wed, Oct 24, 2018 at 8:07 AM Andrija Panic > wrote: > >> I assume a bit late (just a few months :) - but for sake of other list >> members - had exactly the same case, because of FIREWALL on CentOS 7 >> >> - dashboard shows ZERO capacity, since SSVM is NOT functional - because >> agent inside SSVM could not connect to Management Server - because of >> FIREWALL... >> - running ssvm.sh script reported BAD IP address of the Secondary Storage >> inside VM - so make sure the agent is CONNECTED when viewing SSVM and CPVM >> from Infrastructure --> System VMs... >> - also CPVM was not working - again, because agent was not connected to >> mgmt server.. >> >> Firewall can be properly fixed/configured (obviously), or you can try temp >> workaround: >> systemctl disable firewalld >> systemctl stop firewalld >> >> After that, disable Zone, destroy both CPVM and SSVM, Enable Zone, and >> wait >> for SSVM and CPVM to be created and that agent connects (Agent State shows >> UP in GUI) >> >> Cheers >> Andrija >> >> On Fri, 23 Mar 2018 at 17:52, Dag Sonstebo >> wrote: >> >> > Hi Olivier, >> > >> > Can you write to the NFS mount from SSVM? It could be you have it >> mounted >> > OK, but ACLs and/or settings prevent you from actually reading/writing. >> > >> > Also keep in mind the NFS permissions you need to set >> > (rw,async,no_root_squash,no_subtree_check) – some pointers on >> > >> http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.11/management-server/index.html#using-a-separate-nfs-server >> > >> > Regards, >> > Dag Sonstebo >> > Cloud Architect >> > ShapeBlue >> > >> > On 23/03/2018, 16:27, "Olivier GUIN" wrote: >> > >> > Hi, >> > >> > I've a problem with secondary storage, in the dashboard it is >> 0.00KB . >> > >> > In the ssvm, when I launch ssvm.check : This no nfs mount >> directory ! >> > >> > root@s-2-VM:/usr/local/cloud/systemvm# ./ssvm-check.sh >> > >> > First DNS server is 200.13.136.8 >> > PING 200.13.136.8 (200.13.136.8): 56 data bytes >> > 64 bytes from 200.13.136.8: icmp_seq=0 ttl=63 time=2.566 ms >> > 64 bytes from 200.13.136.8: icmp_seq=1 ttl=63 time=0.516 ms >> > --- 200.13.136.8 ping statistics --- >> > 2 packets transmitted, 2 packets received, 0% packet loss >> > round-trip min/avg/max/stddev = 0.516/1.541/2.566/1.025 ms >> > Good: Can ping DNS server >> > >> > Good: DNS resolves cloudstack.apache.org >> > >> > nfs is currently mounted >> > >> > Management server is 172.16.1.5. Checking connectivity. >> > ./ssvm-check.sh: line 121: warning: command substitution: ignored >> null >> > byte in input >> > Good: Can connect to management server port 8250 >> > >> > Good: Java process is running >> > >> > Tests Complete. Look for ERROR or WARNING above. >> > >> > Can you help me to verify ssvm (Apache CloudStack Syste
Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE 0.00KB (URGENT)
Hi Andrija, Maybe my issue is different then. I apologize, as I didn't mean to hijack this thread. It just sounded very similar to the issue I am experiencing. In my case, the SSVM's are never created, because the system seems to not be able to find the storage. I'll keep working on it. Thank you! -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Andrija Panic" To: "users" , "jordan" Sent: Thursday, 25 October, 2018 11:23:23 Subject: Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE 0.00KB (URGENT) Hi Jordan, I' would perhaps still suspect firewall issue - can you destroy SSVM and CPVM (they will be automatically created after few tens of seconds) - SSVM is the one connecting to Secondary Storage and afaik reporting back capacity to management server (what you see in dashboard) I did my tests by doing SSH to inside the SSVM (and CPVM), and did telnet to port 8250 to mgmt IP address to verify communication with mgmt. Also inside SSVM there is the script which you can use to check ssvm health: /usr/local/cloud/systemvm/ssvm-check.sh - it's use to check connections to mgmt server, to internet, dns resolution, if able to access Secondary Storage etc - if this script gives all OK (i.e. no errors) than you are good. If you need help doing ssh to SSVM/CPVM - check this link please: https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting Try please and On Thu, 25 Oct 2018 at 19:59, Jordan Michaels wrote: > I am encountering this issue in a single-server setup as well. The initial > setup worked fine, then I messed with some network settings a bit which > caused me to remove the one host, and cannot get the system up and running > again because secondary storage shows 0KB. Verified NFS shares are > writable, verified firewall ports are open, not sure what else to check or > to try. > > -- > Kind regards, > Jordan Michaels > Vivio Technologies > > - Original Message - > From: "Alexandre Bruyere" > To: "users" > Sent: Wednesday, 24 October, 2018 06:39:43 > Subject: Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE > 0.00KB (URGENT) > > Just saw you followed it, and I'm not sure where the problem is, I'll need > to study it - I've had no trouble on my part. > > On Wed, Oct 24, 2018 at 9:34 AM Alexandre Bruyere < > bruyere.alexan...@gmail.com> wrote: > > > For reference, you can use iptables commands in firewall-cmd by using the > > --direct option. > > > > I've made a pull request to update the Quick Installation Guide with an > > example of commands you can use to configure the firewall. > > > > On Wed, Oct 24, 2018 at 8:07 AM Andrija Panic > > wrote: > > > >> I assume a bit late (just a few months :) - but for sake of other list > >> members - had exactly the same case, because of FIREWALL on CentOS 7 > >> > >> - dashboard shows ZERO capacity, since SSVM is NOT functional - because > >> agent inside SSVM could not connect to Management Server - because of > >> FIREWALL... > >> - running ssvm.sh script reported BAD IP address of the Secondary > Storage > >> inside VM - so make sure the agent is CONNECTED when viewing SSVM and > CPVM > >> from Infrastructure --> System VMs... > >> - also CPVM was not working - again, because agent was not connected to > >> mgmt server.. > >> > >> Firewall can be properly fixed/configured (obviously), or you can try > temp > >> workaround: > >> systemctl disable firewalld > >> systemctl stop firewalld > >> > >> After that, disable Zone, destroy both CPVM and SSVM, Enable Zone, and > >> wait > >> for SSVM and CPVM to be created and that agent connects (Agent State > shows > >> UP in GUI) > >> > >> Cheers > >> Andrija > >> > >> On Fri, 23 Mar 2018 at 17:52, Dag Sonstebo > >> wrote: > >> > >> > Hi Olivier, > >> > > >> > Can you write to the NFS mount from SSVM? It could be you have it > >> mounted > >> > OK, but ACLs and/or settings prevent you from actually > reading/writing. > >> > > >> > Also keep in mind the NFS permissions you need to set > >> > (rw,async,no_root_squash,no_subtree_check) – some pointers on > >> > > >> > http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.11/management-server/index.html#using-a-separate-nfs-server > >> > > >> > Regards, > >> > Dag
Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE 0.00KB (URGENT)
It's all good! I sincerely appreciate any advice you send my way even if it's rushed. ;) Thank you. -- Kind regards, Jordan Michaels Vivio Technologies - Original Message - From: "Andrija Panic" To: "jordan" Cc: "users" Sent: Thursday, 25 October, 2018 15:13:47 Subject: Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE 0.00KB (URGENT) Well, my apologies also - I see now that the original thread stated a normally working SSVM... Seems I was rushing with my answer :) On Thu, 25 Oct 2018 at 23:48, Jordan Michaels wrote: > Hi Andrija, > > Maybe my issue is different then. I apologize, as I didn't mean to hijack > this thread. It just sounded very similar to the issue I am experiencing. > > In my case, the SSVM's are never created, because the system seems to not > be able to find the storage. I'll keep working on it. > > Thank you! > > -- > Kind regards, > Jordan Michaels > Vivio Technologies > > - Original Message - > From: "Andrija Panic" > To: "users" , "jordan" > Sent: Thursday, 25 October, 2018 11:23:23 > Subject: Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY STORAGE > 0.00KB (URGENT) > > Hi Jordan, > I' would perhaps still suspect firewall issue - can you destroy SSVM and > CPVM (they will be automatically created after few tens of seconds) - SSVM > is the one connecting to Secondary Storage and afaik reporting back > capacity to management server (what you see in dashboard) > > I did my tests by doing SSH to inside the SSVM (and CPVM), and did telnet > to port 8250 to mgmt IP address to verify communication with mgmt. Also > inside SSVM there is the script which you can use to check ssvm > health: /usr/local/cloud/systemvm/ssvm-check.sh - it's use to check > connections to mgmt server, to internet, dns resolution, if able to access > Secondary Storage etc - if this script gives all OK (i.e. no errors) > than you are good. > > If you need help doing ssh to SSVM/CPVM - check this link please: > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM%2C+templates%2C+Secondary+storage+troubleshooting > > Try please and > > On Thu, 25 Oct 2018 at 19:59, Jordan Michaels > wrote: > > > I am encountering this issue in a single-server setup as well. The > initial > > setup worked fine, then I messed with some network settings a bit which > > caused me to remove the one host, and cannot get the system up and > running > > again because secondary storage shows 0KB. Verified NFS shares are > > writable, verified firewall ports are open, not sure what else to check > or > > to try. > > > > -- > > Kind regards, > > Jordan Michaels > > Vivio Technologies > > > > - Original Message - > > From: "Alexandre Bruyere" > > To: "users" > > Sent: Wednesday, 24 October, 2018 06:39:43 > > Subject: Re: FRESH install Cloustack 4.11 CentOS7 XEN6.5 SECONDARY > STORAGE > > 0.00KB (URGENT) > > > > Just saw you followed it, and I'm not sure where the problem is, I'll > need > > to study it - I've had no trouble on my part. > > > > On Wed, Oct 24, 2018 at 9:34 AM Alexandre Bruyere < > > bruyere.alexan...@gmail.com> wrote: > > > > > For reference, you can use iptables commands in firewall-cmd by using > the > > > --direct option. > > > > > > I've made a pull request to update the Quick Installation Guide with an > > > example of commands you can use to configure the firewall. > > > > > > On Wed, Oct 24, 2018 at 8:07 AM Andrija Panic > > > > wrote: > > > > > >> I assume a bit late (just a few months :) - but for sake of other > list > > >> members - had exactly the same case, because of FIREWALL on CentOS 7 > > >> > > >> - dashboard shows ZERO capacity, since SSVM is NOT functional - > because > > >> agent inside SSVM could not connect to Management Server - because of > > >> FIREWALL... > > >> - running ssvm.sh script reported BAD IP address of the Secondary > > Storage > > >> inside VM - so make sure the agent is CONNECTED when viewing SSVM and > > CPVM > > >> from Infrastructure --> System VMs... > > >> - also CPVM was not working - again, because agent was not connected > to > > >> mgmt server.. > > >> > > >> Firewall can be properly fixed/configured (obviously), or you can try > > temp > > >> workaround: > > >> systemctl disa
