The Web UI is finally up, 2 hours after I restarted the Management Server. Is
this an explainable behaviour? I will look at the logs around the time.
Regards,
Antoine
> On Oct 18, 2022, at 4:24 PM, Wei ZHOU <ustcweiz...@gmail.com> wrote:
>
> It would be good to upload the management server log since last start.
>
> -Wei
>
> On Tuesday, 18 October 2022, Antoine Boucher <antoi...@haltondc.com> wrote:
>
>> Hello,
>>
>> I have been working on saml configurarion for the past few days, while
>> refining our setup we have restarted our management server a dozen of times
>> but this time the UI is not up but logs are showing that the management
>> server is up.
>>
>> Netstats shows no applications listening on port 8080,8250 or 9090, no UI
>> or cloud monkey access
>>
>> Logs indicates that the Mangement server is up and running, here are the
>> only error that I see ( I skipped the INFO and WARN messages)
>>
>>
>>
>> 2022-10-18 12:31:09,169 ERROR [c.c.c.ClusterManagerImpl] (main:null)
>> (logid:) Unable to ping management server at 10.101.2.40:9090 due to
>> ConnectException
>>
>> 2022-10-18 12:31:09,317 WARN [c.c.s.d.DownloadMonitorImpl] (main:null)
>> (logid:) Only realhostip.com ssl cert is supported, ignoring self-signed
>> and other certs
>>
>> 2022-10-18 12:31:10,753 ERROR [c.c.u.PropertiesUtil] (main:null) (logid:)
>> Unable to find properties file: commands.properties
>>
>> Then a few of these related to snapshot schedule
>> 2022-10-18 12:31:17,106 WARN [c.c.u.d.T.Transaction] (main:null) (logid:)
>> txn: Commit called when it is not a transaction: -SnapshotSchedulerImpl.
>> scheduleNextSnapshotJob:396-SnapshotSchedulerImpl.start:466-
>> CloudStackExtendedLifeCycle$1.with:74-CloudStackExtendedLifeCycle.
>> with:153-CloudStackExtendedLifeCycle.startBeans:71-
>> CloudStackExtendedLifeCycleStart.run:46-DefaultModuleDefinitionSet$1.
>> with:104-DefaultModuleDefinitionSet.withModule:244-
>> DefaultModuleDefinitionSet.withModule:249-DefaultModuleDefinitionSet.
>> withModule:249-DefaultModuleDefinitionSet.withModule:232-
>> DefaultModuleDefinitionSet.startContexts:96
>>
>>
>> 2022-10-18 12:31:20,039 WARN [c.c.a.AlertManagerImpl]
>> (Cluster-Notification-1:ctx-b9523ef9) (logid:54f42903) alertType=[14]
>> dataCenterId=[0] podId=[0] clusterId=[null] message=[Management server node
>> 10.101.2.40 is up].
>>
>> 2022-10-18 12:31:20,061 WARN [c.c.c.ClusterManagerImpl]
>> (Cluster-Notification-1:ctx-b9523ef9) (logid:54f42903) Notifying
>> management server join event took 23 ms
>>
>> 2022-10-18 12:31:20,354 WARN [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-8:null) (logid:) Throwing away a request because it
>> came through as the first command on a connect: Seq 0-18565: { Cmd ,
>> MgmtId: -1, via: 0, Ver: v1, Flags: 11, [{"com.cloud.agent.api.
>> PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_
>> hostVmStateReport":{},"_gatewayAccessible":"true","_
>> vnetAccessible":"true","hostType":"Routing","hostId":"0","wait":"0","
>> bypassHostMaintenance":"false"}}] }
>>
>>
>> 2022-10-18 12:31:20,371 WARN [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-2:null) (logid:) Throwing away a request because it
>> came through as the first command on a connect: Seq 0-18570: { Cmd ,
>> MgmtId: -1, via: 0, Ver: v1, Flags: 11, [{"com.cloud.agent.api.
>> PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_
>> hostVmStateReport":{},"_gatewayAccessible":"true","_
>> vnetAccessible":"true","hostType":"Routing","hostId":"0","wait":"0","
>> bypassHostMaintenance":"false"}}] }
>>
>> 2022-10-18 12:31:20,381 WARN [c.c.a.m.AgentManagerImpl]
>> (AgentManager-Handler-11:null) (logid:) Throwing away a request because it
>> came through as the first command on a connect: Seq 0-18579: { Cmd ,
>> MgmtId: -1, via: 0, Ver: v1, Flags: 11, [{"com.cloud.agent.api.
>> PingRoutingWithNwGroupsCommand":{"newGroupStates":{},"_
>> hostVmStateReport":{},"_gatewayAccessible":"true","_
>> vnetAccessible":"true","hostType":"Routing","hostId":"0","wait":"0","
>> bypassHostMaintenance":"false"}}] }
>>
>>
>>
>>
>> Our management server in on Centos 7.9, the mysql is up a running,
>> sytemctl status is showing no issues including cloudstack-management up and
>> running without issues.
>>
>> No firewalls or selinux, we rebooted and restarted a number of times but
>> still not access, stops is showing minimum activities.
>>
>> Has anyone had this situation happened? I will keep digging...
>>
>> Regards,
>> Antoine
>>
>>
>>
