Hello All,

I' m currently set up a fresh installation of cloucdstack 4.11 on CentOS7/KVM 
server.

All was working good until the systemvm installation...the ssvm is using the 
public ip to contact the nfs instead of the internal ip adresse.
I had this issue before and it was a ip route and/or arp records problem, but 
not this time.

>From ssvm_check script, i got two error

-          NFS not mounted

-          Java process not running

I don't know if the java process error is related to the NFS not mounted.

Here the result  :
First DNS server is  8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=48 time=54.150 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=48 time=45.959 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 45.959/50.055/54.150/4.096 ms
Good: Can ping DNS server
================================================
Good: DNS resolves cloudstack.apache.org
================================================
ERROR: NFS is not currently mounted
Try manually mounting from inside the VM
NFS server is  77.88.44.225
PING 77.88.44.225 (77.88.44.225): 56 data bytes
64 bytes from 77.88.44.225: icmp_seq=0 ttl=64 time=1.132 ms
64 bytes from 77.88.44.225: icmp_seq=1 ttl=64 time=1.123 ms
--- 77.88.44.225 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.123/1.127/1.132/0.000 ms
Good: Can ping nfs server
================================================
Management server is 172.16.22.60. Checking connectivity.
./ssvm-check.sh: line 121: warning: command substitution: ignored null byte in 
input
Good: Can connect to management server port 8250
================================================
ERROR: Java process not running.  Try restarting the SSVM.

>From the /var/log/cloud.log, i've noticed this error :
2018-04-10 10:24:22,062 INFO  [cloud.agent.AgentShell] (main:null) Agent started
2018-04-10 10:24:22,066 INFO  [cloud.agent.AgentShell] (main:null) 
Implementation Version is 4.11.0.0
2018-04-10 10:24:22,067 INFO  [cloud.agent.AgentShell] (main:null) 
agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
2018-04-10 10:24:22,077 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to using properties file for storage
2018-04-10 10:24:22,084 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to the constant time backoff algorithm
2018-04-10 10:24:22,114 INFO  [cloud.utils.LogUtils] (main:null) log4j 
configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
2018-04-10 10:24:22,168 INFO  [cloud.agent.AgentShell] (main:null) Using 
default Java settings for IPv6 preference for agent connection
2018-04-10 10:24:22,323 ERROR [cloud.agent.AgentShell] (main:null) Unable to 
start agent: Resource class not found: 
com.cloud.storage.resource.PremiumSecondaryStorageResource due to: 
java.lang.ClassNotFoundException: 
com.cloud.storage.resource.PremiumSecondaryStorageResource


>From the host, i've created cloudbr0 (mgmt) and cloudbr1 with a bridge/vlan  
>connected to the secondary storage network.
###ifcfg-cloudbr1####
DEVICE=cloudbr1
NM_CONTROLLED=no
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes
DEFROUTE=yes
ZONE=public

###ifcfg-cloudbr1.103####
DEVICE=cloudbr1.103
ONBOOT=yes
TYPE=Bridge
IPADDR=172.16.3.217
NETMASK=255.255.255.0
GATEWAY=172.16.3.254
NM_CONTROLLED=no
BOOTPROTO=static
ZONE=public

###ifcfg-vlan103####
VLAN=yes
TYPE=vlan
DEVICE=vlan103
PHYSDEV=teamTRUNK
VLAN_ID=103
NAME=VLAN103
ONBOOT=yes
BRIDGE=cloudbr1.103

###brctl show result###
bridge name     bridge id               STP enabled     interfaces
brteamTRUNK-500         8000.80c16e791e14       no              teamTRUNK.500
                                                                                
                                         vnet2
                                                                                
                                          vnet5
cloud0                             8000.fe00a9fe0101       no                   
      vnet0
                                                                                
                                        vnet3
cloudbr0                         8000.80c16e791e10       no              
teamMGMT
                                                                                
                                          vnet1
                                                                                
                                         vnet4
cloudbr1                         8000.80c16e791e14       no              
teamTRUNK
                                                                                
                                          vnet6
cloudbr1.103                  8000.80c16e791e14       no              vlan103
virbr0          8000.525400663967       yes             virbr0-nic

>From the host i can ping and attached the NFS.

Im running out of idea, any help would be appreciated.

Thanks a lot !

Best regards,
N.B

Reply via email to