Cannot find cluster mangement page and meet npe error in v0.3.0

[magicsilence]

hi team, I deploy the pulsar-manager with binary package. And i meet some problems when using it.

The first problem is cannot find cluster management in my pulsar-manager (v0.3.0) and the pulsar cluster's version is v2.9.3.

Second, pulsar-manager's backend serive always output exception log: java.lang.NullPointerException: null at org.apache.pulsar.manager.service.impl.BrokerStatsServiceImpl.scheduleCollectStats(BrokerStatsServiceImpl.java:124) ~[pulsar-manager.jar:na] at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source) ~[na:na] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_342] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_342] at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE] at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.0.6.RELEASE.jar:5.0.6.RELEASE] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_342] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_342] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_342] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_342] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_342] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_342] at java.lang.Thread.run(Thread.java:750) [na:1.8.0_342]

How can i fix it ?

Thank you.

[haiboself]

Same issue， the only difference is I deploy 0.3.0 in docker。

[Apurva007]

Same issue. Cannot find the "clusters" in the sidebar.

[dongzhonghua]

enter /management/clusters in the url can find cluster management，will this be fixed in the next version?