vladimirpetrov opened a new issue, #6632:
URL: https://github.com/apache/cloudstack/issues/6632
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UPGRADE
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18 nightly build (2022-08-11)
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced zone
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
CentOS 7 management and host OSes
##### SUMMARY
<!-- Explain the problem/feature briefly -->
After upgrading from 4.17, the management service fails
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
1. Change the cloudstack repo in **/etc/yum.repos.d/cloudstack.repo** with
the nighly build repo
2. Execute command 'yum clean all'
3. Execute command 'yum upgrade cloudstack-management cloudstack-common
cloudstack-usage'
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The management server should continue working (no stop/start command has
been issued).
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
The management server process fails:
systemctl status -l cloudstack-management
● cloudstack-management.service - CloudStack Management Server
Loaded: loaded (/usr/lib/systemd/system/cloudstack-management.service;
disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since чт 2022-08-11 12:36:04 UTC;
56min ago
Main PID: 17142 (code=exited, status=143)
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 java[17142]: WARN
[c.c.u.d.GlobalLock] (SpringContextShutdownHook:null) (logid:) Unmatched Global
lock secstorage.scan.lock reference usage detected, check your code!
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 java[17142]: WARN
[c.c.u.d.GlobalLock] (SpringContextShutdownHook:null) (logid:) Unmatched Global
lock secStorageVm.alloc reference usage detected, check your code!
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 java[17142]: INFO
[c.c.c.ConsoleProxyManagerImpl] (SpringContextShutdownHook:null) (logid:) Stop
console proxy manager
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 java[17142]: WARN
[c.c.u.d.GlobalLock] (SpringContextShutdownHook:null) (logid:) Unmatched Global
lock consoleproxy.scan.lock reference usage detected, check your code!
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 java[17142]: WARN
[c.c.u.d.GlobalLock] (SpringContextShutdownHook:null) (logid:) Unmatched Global
lock consoleproxy.alloc reference usage detected, check your code!
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 java[17142]: INFO
[o.a.c.s.NfsMountManager] (SpringContextShutdownHook:null) (logid:) Clean up
mounted NFS mount points used in current session.
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 systemd[1]:
cloudstack-management.service: main process exited, code=exited, status=143/n/a
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 systemd[1]: Stopped
CloudStack Management Server.
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 systemd[1]: Unit
cloudstack-management.service entered failed state.
авг 11 12:36:04 ref-trl-3507-v-M7-vladimir-petrov-mgmt1 systemd[1]:
cloudstack-management.service failed.
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
