tatay188 opened a new issue, #10408: URL: https://github.com/apache/cloudstack/issues/10408
### problem I was trying to Install the 4.20.0.0 as Standalone and not as an Upgrade from 4.19.x.x and UI every attempt provides 503 and logs stop even with DEBUG Enabled. Running on a minimum Ubuntu 22.04 ### versions The versions of ACS, hypervisors, storage, network etc.. ACS 4.20.0.0 HYP: KVM STOR: CEPH, EMC Unity NETWORK: Pure L3. ### The steps to reproduce the bug 1. There is a long e-mail trail with Wei ZHOU. [(https://lists.apache.org/thread/1fzkjcfvo5vymdhlpgwl5n7m3nxwoxkd)] Scenario Two Management servers with Separate DB. ALl Ubuntu 22.04 Minimum Install MGMT-SEVER-1 Uninstalled 4.20.0.0 getting 503 in the UI. Purged and cleaned 1 ) LOaded the repositories to 4.19 2 ) Installed 4.19.1.3 Succesfully 2.1)UI fails providing 503, The UI works if I don't use -m and -k options 3) Reinstalled Successfully without the -m -k options 3.1) UI Works on 4.19.1.3 4) Upgraded to 4.20.0.0 4.1) UI Works on 4.20.0.0 MGMT-SEVER-2 Installed a fresh standalone 4.20.0.0 - No upgrade on the second server 1) All db was successfully installed without the -m -k and without the --deploy-as options. NOTE: every time it installs without errors with the options -m -k but the UI does not work, same problem observed on 4.19.x.x 2) UI throws 503 on the second server 3) What I found so far, I did not check everything: On MGMT-SERVER-1 SERVER `/etc/cloudstack/management# ls -al total 100 drwxr-xr-x 2 root root 4096 Feb 15 21:38 . drwxr-xr-x 5 root root 4096 Feb 14 13:36 .. -rw-r--r-- 1 root root 19996 Nov 28 05:00 config.json -rw-r----- 1 root cloud 4824 Feb 15 21:00 db.properties -rw-r----- 1 root root 4800 Feb 14 00:20 db.properties.OMAR -rw-r--r-- 1 root root 22806 Nov 28 04:55 ehcache.xml -rw-r--r-- 1 root root 981 Nov 28 04:55 environment.properties -rw-r--r-- 1 root root 931 Nov 28 04:55 java.security.ciphers -rw-r--r-- 1 root root 8 Feb 15 21:00 key -rw-r--r-- 1 root root 5338 Nov 28 04:55 log4j-cloud.xml **lrwxrwxrwx 1 root root 42 Feb 13 01:37 log4j.xml -> /etc/cloudstack/management/log4j-cloud.xml`** lrwxrwxrwx 1 root root 42 Feb 14 01:37 log4j2.xml -> /etc/cloudstack/management/log4j-cloud.xml` On MGMT-SERVER-2 SERVER `/etc/cloudstack/management# ls -al total 100 drwxr-xr-x 2 root root 4096 Feb 15 21:38 . drwxr-xr-x 5 root root 4096 Feb 14 13:36 .. -rw-r--r-- 1 root root 19996 Nov 28 05:00 config.json -rw-r----- 1 root cloud 4824 Feb 15 21:00 db.properties -rw-r----- 1 root root 4800 Feb 14 00:20 db.properties. -rw-r--r-- 1 root root 22806 Nov 28 04:55 ehcache.xml -rw-r--r-- 1 root root 981 Nov 28 04:55 environment.properties -rw-r--r-- 1 root root 931 Nov 28 04:55 java.security.ciphers -rw-r--r-- 1 root root 8 Feb 15 21:00 key -rw-r--r-- 1 root root 5338 Nov 28 04:55 log4j-cloud.xml lrwxrwxrwx 1 root root 42 Feb 14 13:36 log4j2.xml -> /etc/cloudstack/management/log4j-cloud.xml On the 4.20.0.1 the link log4j.xml is missing, Then I try on the MGMT-SERVER-2 /etc/cloudstack/management directory ln -s /etc/cloudstack/management/log4j-cloud.xml log4j.xml restarted the Management server and works!!!, even If I never installed the 4.19.x.x on the second MGMT-SERVER-2 ... ### What to do about it? Work around for the stand alone: /etc/cloudstack/management directory ln -s /etc/cloudstack/management/log4j-cloud.xml log4j.xml Expected to work as Standalone. not as Upgrade, or Indicate a PATH to the new release. if is not intended as an Standalone. -- 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: commits-unsubscr...@cloudstack.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
