You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Chi vediamo <ta...@gmail.com> on 2025/02/11 00:06:16 UTC
I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Is a fresh Install
I have the same issue with 4.20, with Mysql 8.0
My DB is in a separate server,
I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
I follow the basic install with a separate DB. which completed as successful.
cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
Mysql user name:cloud [ OK ]
Mysql user password:****** [ OK ]
Mysql server ip:10.23.23.23 [ OK ]
Mysql server port:3306 [ OK ]
Using specified cluster management server node IP 10.23.23.21 [ OK ]
Checking Cloud database files ... [ OK ]
Checking local machine hostname ... [ OK ]
Checking SELinux setup ... [ OK ]
Preparing /etc/cloudstack/management/db.properties [ OK ]
Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
Processing encryption ... [ OK ]
Finalizing setup ... [ OK ]
CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
All firewalls are down for now.
my tail log is very simple:
tail -f /var/log/cloudstack/management/management-server.log
2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
Tata Y.
> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org> wrote:
>
>
> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>
> Hello team,
>
> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>
> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>
> Type of installation is single node management server with nfs and db on same host.
>
> Java version:
> ```
> openjdk 11.0.19 2023-04-18
> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
> ```
> MySql version:
> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>
> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
> `mysql -u cloud -p cloud -h localhost`
>
> and the grants
> ```
> mysql> show grants;
> +----------------------------------------------------------------+
> | Grants for cloud@localhost |
> +----------------------------------------------------------------+
> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
> +----------------------------------------------------------------+
> ```
> This is part of my db.properties
> ```
> # management server clustering parameters, change cluster.node.IP to the machine IP address
> # in which the management server is running
> cluster.node.IP=127.0.0.1
> cluster.servlet.port=9090
> region.id=1
>
> # CloudStack database settings
> db.cloud.username=cloud
> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
> db.cloud.host=localhost
> db.cloud.driver=jdbc:mysql
> db.cloud.port=3306
> db.cloud.name=cloud
> ```
>
> And this is output of command for service status
> ```
> systemctl status cloudstack-management
> cloudstack-management.service - CloudStack Management Server
> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
> Main PID: 5358 (java)
> ```
> which shows some errors (i guess) in the second part
> ```
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
> ```
>
> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>
> Netstat output
> ```
> netstat -tulpn | grep 8080
> tcp6 0 0 :::8080 :::* LISTEN 5358/java
> ```
>
> You can find attached my log
> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>
> There is a single sql exception about creating a table that already exists.
> ```
> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
> ```
>
> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>
> How can I resolve?
>
> Thank you for any help.
>
> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>
> ----
> This is an automatically sent email for users@cloudstack.apache.org.
> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Same server Install
I should get my apache.org <http://apache.org/> e-mail as Collaborator tester :)
1) I changed the DB.properties to match the local server
2) cloudstack-setup-databases cloud:rootpass@10.23.23.21 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
FAILED 503 error same logs I dont get any additional logs.
3) cloudstack-setup-databases cloud:rootpass@10.23.23.21 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
FAILED 503 error same logs I dont get any additional logs.
Mysql user name:cloud [ OK ]
Mysql user password:****** [ OK ]
Mysql server ip:10.23.23.21 [ OK ]
Mysql server port:3306 [ OK ]
Mysql root user name:root [ OK ]
Mysql root user password:****** [ OK ]
Using specified cluster management server node IP 10.23.23.21 [ OK ]
Checking Cloud database files ... [ OK ]
Checking local machine hostname ... [ OK ]
Checking SELinux setup ... [ OK ]
Preparing /etc/cloudstack/management/db.properties [ OK ]
Applying /usr/share/cloudstack-management/setup/create-database.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/create-database-premium.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
Processing encryption ... [ OK ]
Finalizing setup ... [ OK ]
CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
root@csmgmtatl201:/var/log/mysql# cd /var/log/cloudstack/management
root@csmgmtatl201:/var/log/cloudstack/management# systemctl stop cloudstack-management
root@csmgmtatl201:/var/log/cloudstack/management# systemctl start cloudstack-management
root@csmgmtatl201:/var/log/cloudstack/management# systemctl status cloudstack-management
● cloudstack-management.service - CloudStack Management Server
Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2025-02-13 15:05:18 UTC; 10s ago
Main PID: 643223 (java)
Tasks: 107 (limit: 629145)
Memory: 461.1M
CPU: 18.950s
CGroup: /system.slice/cloudstack-management.service
└─643223 /usr/bin/java -Djava.security.properties=/etc/cloudstack/management/java.security.ciphers -Djava.awt.headless=true -Xmx2G -XX:+UseParallelGC -XX:MaxGCPauseMillis=500 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDump>
Feb 13 15:05:18 csmgmtatl201 systemd[1]: Started CloudStack Management Server.
Thank you
Tata Y.
> On Feb 13, 2025, at 9:25 AM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> Any Ideas ?
>
> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>
> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>
>
>
> Tata Y.
>
>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>>
>> Hello Wei,
>>
>> I just did what you requested, without the -r 1
>>
>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>
>> same results.
>> http://10.23.23.21:8080/client/
>> HTTP ERROR 503 Service Unavailable
>>
>> URI: /client/
>> STATUS: 503
>> MESSAGE: Service Unavailable
>> SERVLET: -
>>
>> The same exact logs as before, there is no additional information in the logs.
>>
>> Tata Y.
>>
>>
>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>>
>>> strange
>>>
>>> Can you set up database without `-r 1` ?
>>>
>>> -Wei
>>>
>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>
>>>> I tryed, same result 503
>>>>
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Hello Wei,
>>>>>>
>>>>>> Interestingly I got same errors:
>>>>>>
>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>> 3) I run the command as follows, without the default keys
>>>>>>
>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>
>>>>>> 4) start the management server
>>>>>>
>>>>>> 5) cheking the logs
>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>
>>>>>>
>>>>>> I Even reinstalled the management server.
>>>>>>
>>>>>>
>>>>>> management-server.log
>>>>>>
>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>
>>>>>> management-server.err
>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>
>>>>>>
>>>>>> management-server.out
>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>> ... 25 more
>>>>>>
>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>
>>>>>> any tips are welcome.
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>
>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>
>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Wei
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> Hello Wei
>>>>>>>>
>>>>>>>> Additionally, I have the management error:
>>>>>>>>
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>
>>>>>>>> I am using the JAVA 17
>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>
>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>
>>>>>>>> thank you
>>>>>>>>
>>>>>>>> Tata Y
>>>>>>>>
>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hello Wei,
>>>>>>>>>
>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>
>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>
>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>
>>>>>>>>> -- Create the cloud user
>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>
>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>
>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>
>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>
>>>>>>>>> Tata Y.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>
>>>>>>>>>> normally I use a command like
>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Wei
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>
>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>
>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>
>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>
>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>
>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>
>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>> ... 25 more
>>>>>>>>>>>
>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>
>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>> >
>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>> >
>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>> >
>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>> >
>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>> >
>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>> >
>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>> >
>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>> >
>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>> >
>>>>>>>>>>> > Tata Y.
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>> >>
>>>>>>>>>>> >> Hello team,
>>>>>>>>>>> >>
>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>> >>
>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>> >>
>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>> >>
>>>>>>>>>>> >> Java version:
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> MySql version:
>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>> >>
>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>> >>
>>>>>>>>>>> >> and the grants
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>> >>
>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>> >>
>>>>>>>>>>> >> Netstat output
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>> >>
>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>> >>
>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>> >>
>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>> >>
>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>> >>
>>>>>>>>>>> >> ----
>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>> >>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
Any Ideas ?
Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
Tata Y.
> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> I just did what you requested, without the -r 1
>
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>
> same results.
> http://10.23.23.21:8080/client/
> HTTP ERROR 503 Service Unavailable
>
> URI: /client/
> STATUS: 503
> MESSAGE: Service Unavailable
> SERVLET: -
>
> The same exact logs as before, there is no additional information in the logs.
>
> Tata Y.
>
>
>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> strange
>>
>> Can you set up database without `-r 1` ?
>>
>> -Wei
>>
>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>> it automatically redirects to http://10.23.23.21:8080/client
>>>
>>> I tryed, same result 503
>>>
>>>
>>> Tata Y.
>>>
>>>
>>>
>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Can you try http://10.23.23.21:8080/client ?
>>>>
>>>>
>>>>
>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> Hello Wei,
>>>>>
>>>>> Interestingly I got same errors:
>>>>>
>>>>> 1) I drop the databases cloud and cloud_usage
>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>> 3) I run the command as follows, without the default keys
>>>>>
>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> 4) start the management server
>>>>>
>>>>> 5) cheking the logs
>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>
>>>>>
>>>>> I Even reinstalled the management server.
>>>>>
>>>>>
>>>>> management-server.log
>>>>>
>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>
>>>>> management-server.err
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>
>>>>>
>>>>> management-server.out
>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>
>>>>> any tips are welcome.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The error logs can be ignored. The java version is good.
>>>>>>
>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>
>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>
>>>>>>
>>>>>> Kind regards,
>>>>>> Wei
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Hello Wei
>>>>>>>
>>>>>>> Additionally, I have the management error:
>>>>>>>
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>
>>>>>>> I am using the JAVA 17
>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>
>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>
>>>>>>> thank you
>>>>>>>
>>>>>>> Tata Y
>>>>>>>
>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hello Wei,
>>>>>>>>
>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>
>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>
>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>
>>>>>>>> -- Create the cloud user
>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>
>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>
>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>
>>>>>>>>
>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>
>>>>>>>>> normally I use a command like
>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Wei
>>>>>>>>>
>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>
>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>> the database contains the tables.
>>>>>>>>>>
>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>
>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>
>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Is a fresh Install
>>>>>>>>>> >
>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>> >
>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>> >
>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>> >
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>> >
>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>> >
>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>> >
>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> >
>>>>>>>>>> > Tata Y.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>> >>
>>>>>>>>>> >> Hello team,
>>>>>>>>>> >>
>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>> >>
>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>> >>
>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>> >>
>>>>>>>>>> >> Java version:
>>>>>>>>>> >> ```
>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>> >> ```
>>>>>>>>>> >> MySql version:
>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>> >>
>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>> >>
>>>>>>>>>> >> and the grants
>>>>>>>>>> >> ```
>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> ```
>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>> >> ```
>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>> >>
>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>> >> ```
>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>> >> ```
>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>> >> ```
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>> >>
>>>>>>>>>> >> Netstat output
>>>>>>>>>> >> ```
>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> You can find attached my log
>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>> >>
>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>> >> ```
>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>> >>
>>>>>>>>>> >> How can I resolve?
>>>>>>>>>> >>
>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>> >>
>>>>>>>>>> >> ----
>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>> >>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Wei,
What additional info do you need from my environment. ?
Should my syslog be listening to the port 4560 to get more logs?
my environment.properties:
paths.script=/usr/share/cloudstack-common
mount.parent=/var/lib/cloudstack/mnt
cloud-stack-components-specification=components-nonoss.xml
my server.properties:
context.path=/client
# The HTTP port to be used by the management server
http.enable=true
http.port=8080
# Max inactivity time in minutes for the session
session.timeout=30
# Max allowed API request payload/content size in bytes
request.content.size=1048576
# Options to configure and enable HTTPS on the management server
#
# For the management server to pick up these configuration settings, the configured
# keystore file should exist and be readable by the management server.
https.enable=true
https.port=8443
# The keystore and manager passwords are assumed to be same.
https.keystore=/etc/cloudstack/management/cloud.jks
# If you want to encrypt the password itself, follow the steps mentioned at:
http://docs.cloudstack.apache.org/en/latest/adminguide/management.html?highlight=jasypt#changing-the-database-password
https.keystore.password=vmops.com
# If an encrypted password is used, specify the encryption type. Valid types: file, web, env (set environment variable CLOUD_SECRET_KEY)
# password.encryption.type=none
# The path to webapp directory
webapp.dir=/usr/share/cloudstack-management/webapp
# The path to access log file
access.log=/var/log/cloudstack/management/access.log
my DB.properties:
cluster.node.IP=10.23.23.21
cluster.servlet.port=9090
region.id=1
# CloudStack database settings
db.cloud.username=cloud
db.cloud.password=ENC(+xxxxx)
db.cloud.host=10.23.23.23
db.cloud.driver=jdbc:mysql
db.cloud.port=3306
db.cloud.name=cloud
# Connection URI to the database "cloud". When this property is set, only the following properties will be used along with it: db.cloud.maxActive, db.cloud.maxIdle, db.cloud.maxWait, db.cloud.username, db.cloud.password, db.cloud.driver, db.cloud.validationQuery, db.cloud.isolation.level. Other properties will be ignored.
db.cloud.uri=
# CloudStack database tuning parameters
db.cloud.connectionPoolLib=hikaricp
db.cloud.maxActive=7000
db.cloud.maxIdle=30
db.cloud.maxWait=600000
db.cloud.minIdleConnections=5
db.cloud.connectionTimeout=30000
db.cloud.keepAliveTime=600000
db.cloud.validationQuery=/* ping */ SELECT 1
db.cloud.testOnBorrow=true
db.cloud.testWhileIdle=true
db.cloud.timeBetweenEvictionRunsMillis=40000
db.cloud.minEvictableIdleTimeMillis=240000
db.cloud.poolPreparedStatements=false
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC
# CloudStack database SSL settings
db.cloud.useSSL=false
db.cloud.keyStore=
db.cloud.keyStorePassword=
db.cloud.trustStore=
db.cloud.trustStorePassword=
# Encryption Settings
db.cloud.encryption.type=file
db.cloud.encrypt.secret=ENC(XXXXX)
db.cloud.encryptor.version=V2
# usage database settings
db.usage.username=cloud
db.usage.password=ENC(XXXXX)
db.usage.host=10.23.23.23
db.usage.driver=jdbc:mysql
db.usage.port=3306
db.usage.name=cloud_usage
# Connection URI to the database "usage". When this property is set, only the following properties will be used along with it: db.usage.maxActive, db.cloud.maxIdle, db.cloud.maxWait, db.usage.username, db.usage.password, db.usage.driver, db.usage.validationQuery, db.usage.isolation.level. Other properties will be ignored.
db.usage.uri=
# usage database tuning parameters
db.usage.connectionPoolLib=hikaricp
db.usage.maxActive=5000
db.usage.maxIdle=30
db.usage.maxWait=600000
db.usage.minIdleConnections=5
db.usage.connectionTimeout=30000
db.usage.keepAliveTime=600000
db.usage.url.params=serverTimezone=UTC
# Simulator database settings
db.simulator.username=clouddemo
db.simulator.password=XXXX
db.simulator.host=10.23.23.23
db.simulator.driver=jdbc:mysql
db.simulator.port=3306
db.simulator.name=simulator
db.simulator.connectionPoolLib=hikaricp
db.simulator.maxActive=0
db.simulator.maxIdle=30
db.simulator.maxWait=600000
db.simulator.minIdleConnections=5
db.simulator.connectionTimeout=30000
db.simulator.keepAliveTime=600000
db.simulator.autoReconnect=true
# Connection URI to the database "simulator". When this property is set, only the following properties will be used along with it: db.simulator.host, db.simulator.port, db.simulator.name, db.simulator.autoReconnect. Other properties will be ignored.
db.simulator.uri=
# High Availability And Cluster Properties
db.ha.enabled=true
db.ha.loadBalanceStrategy=com.cloud.utils.db.StaticStrategy
# cloud stack Database
db.cloud.replicas=10.23.23.24
db.cloud.autoReconnect=true
db.cloud.failOverReadOnly=true
db.cloud.reconnectAtTxEnd=true
db.cloud.autoReconnectForPools=true
db.cloud.secondsBeforeRetrySource=60
db.cloud.queriesBeforeRetrySource=50
db.cloud.initialTimeout=60
#usage Database
db.usage.replicas=10.23.23.24
db.usage.autoReconnect=true
db.usage.failOverReadOnly=true
db.usage.reconnectAtTxEnd=true
db.usage.autoReconnectForPools=true
db.usage.secondsBeforeRetrySource=60
db.usage.queriesBeforeRetrySource=50
I did enable debug mode in everything:
No additional info
Thank you
Tata Y.
> On Feb 13, 2025, at 11:17 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi Chi,
>
> Either 4.20 or 4.19 has been installed in many productions. Both are production ready.
>
> I think it is caused by a configuration with your server or database. However your env is a black box to me.
>
> I run the same command as you (without deploy-as) , here is the output
>
> ===========
>
>
> # cloudstack-setup-databases cloud:rootpass@10.23.23.21 <ma...@10.23.23.21> -m iknow -k somekey -i 10.23.23.21
> Mysql user name:cloud [ OK ]
> Mysql user password:****** [ OK ]
> Mysql server ip:10.23.23.21 [ OK ]
> Mysql server port:3306 [ OK ]
> Using specified cluster management server node IP 10.23.23.21 [ OK ]
> Checking Cloud database files ... [ OK ]
> Checking local machine hostname ... [ OK ]
> Checking SELinux setup ... [ OK ]
> Preparing /etc/cloudstack/management/db.properties [ OK ]
> No mysql root user specified, will not create Cloud DB schema
> Processing encryption ... [ OK ]
> Finalizing setup ... [ OK ]
>
> CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>
> # systemctl restart cloudstack-management
>
> # tail -f /var/log/cloudstack/management/management-server.log
>
> 2025-02-13T16:12:53,115 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
> 2025-02-13T16:12:53,120 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
> 2025-02-13T16:12:53,124 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=false, https.port=8443, context.path=/client
> 2025-02-13T16:13:01,752 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
> 2025-02-13T16:13:01,753 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
> 2025-02-13T16:13:01,870 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
> 2025-02-13T16:13:01,871 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Calling to initialize for class com.cloud.utils.crypt.EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,055 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Initialized with all possible encryptors
> 2025-02-13T16:13:02,068 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) CloudStack will encrypt and decrypt values using encryptor : AeadBase64Encryptor for class EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,139 INFO [c.c.u.LogUtils] (main:[]) (logid:) log4j configuration found at /etc/cloudstack/management/log4j-cloud.xml
> 2025-02-13T16:13:02,143 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loaded module context [bootstrap] in 387 ms
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: bootstrap
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: system
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: core
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: allocator
>
>
> ===========
>
>
> Please note,
>
> If you use 4.19, please set default java version to 4.11
> If you use 4.20, please set default java version to 4.17
>
>
>
> -Wei
>
>
> On Thu, Feb 13, 2025 at 3:24 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Wei,
>>
>> Then 4.20 is not production ready !
>>
>> There are nothing on the logs so far to indicate a problem with the DB.
>>
>> Was this tested before for production, or was just throw to the community to be tested?
>>
>> Thank you
>>
>> Tata Y.
>>
>>
>>> On Feb 13, 2025, at 8:48 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Can you test with a local database ?
>>>
>>> -Wei
>>>
>>> On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> And Yes,
>>>>
>>>> I Did isntalled using a single Managemenent server with a Single Database, Nothing works so far. Still get the 503.
>>>>
>>>> As I mentioned before I did try any obvious possibility. I did not try removing the -m -k options just because that should work and nothing points to that may be the problem, as the DB are created on the remote DB.
>>>>
>>>> Thank you
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>>> On Feb 13, 2025, at 8:03 AM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hello Wei,
>>>>>
>>>>> Any Ideas ?
>>>>>
>>>>> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>>>>>
>>>>> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>>>>>
>>>>>
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hello Wei,
>>>>>>
>>>>>> I just did what you requested, without the -r 1
>>>>>>
>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>>>>>
>>>>>> same results.
>>>>>> http://10.23.23.21:8080/client/
>>>>>> HTTP ERROR 503 Service Unavailable
>>>>>>
>>>>>> URI: /client/
>>>>>> STATUS: 503
>>>>>> MESSAGE: Service Unavailable
>>>>>> SERVLET: -
>>>>>>
>>>>>> The same exact logs as before, there is no additional information in the logs.
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>
>>>>>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> strange
>>>>>>>
>>>>>>> Can you set up database without `-r 1` ?
>>>>>>>
>>>>>>> -Wei
>>>>>>>
>>>>>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>>>>>
>>>>>>>> I tryed, same result 503
>>>>>>>>
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Hello Wei,
>>>>>>>>>>
>>>>>>>>>> Interestingly I got same errors:
>>>>>>>>>>
>>>>>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>>>>>> 3) I run the command as follows, without the default keys
>>>>>>>>>>
>>>>>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> 4) start the management server
>>>>>>>>>>
>>>>>>>>>> 5) cheking the logs
>>>>>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I Even reinstalled the management server.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.log
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>
>>>>>>>>>> management-server.err
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.out
>>>>>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> any tips are welcome.
>>>>>>>>>>
>>>>>>>>>> Thank you
>>>>>>>>>>
>>>>>>>>>> Tata Y.
>>>>>>>>>>
>>>>>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>>>>>
>>>>>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>>>>>
>>>>>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Kind regards,
>>>>>>>>>>> Wei
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>> Hello Wei
>>>>>>>>>>>>
>>>>>>>>>>>> Additionally, I have the management error:
>>>>>>>>>>>>
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>>
>>>>>>>>>>>> I am using the JAVA 17
>>>>>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>>>>>
>>>>>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>>>>>
>>>>>>>>>>>> thank you
>>>>>>>>>>>>
>>>>>>>>>>>> Tata Y
>>>>>>>>>>>>
>>>>>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello Wei,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>>>>>
>>>>>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud user
>>>>>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>>>>>
>>>>>>>>>>>>> Tata Y.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> normally I use a command like
>>>>>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Wei
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>>>>>> ... 25 more
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Tata Y.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Hello team,
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Java version:
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> MySql version:
>>>>>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> and the grants
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Netstat output
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> ----
>>>>>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Wei,
What additional info do you need from my environment. ?
Should my syslog be listening to the port 4560 to get more logs?
my environment.properties:
paths.script=/usr/share/cloudstack-common
mount.parent=/var/lib/cloudstack/mnt
cloud-stack-components-specification=components-nonoss.xml
my server.properties:
context.path=/client
# The HTTP port to be used by the management server
http.enable=true
http.port=8080
# Max inactivity time in minutes for the session
session.timeout=30
# Max allowed API request payload/content size in bytes
request.content.size=1048576
# Options to configure and enable HTTPS on the management server
#
# For the management server to pick up these configuration settings, the configured
# keystore file should exist and be readable by the management server.
https.enable=true
https.port=8443
# The keystore and manager passwords are assumed to be same.
https.keystore=/etc/cloudstack/management/cloud.jks
# If you want to encrypt the password itself, follow the steps mentioned at:
http <http://docs.cloudstack.apache.org/en/latest/adminguide/management.html?highlight=jasypt#changing-the-database-password>: <http://docs.cloudstack.apache.org/en/latest/adminguide/management.html?highlight=jasypt#changing-the-database-password>//docs.cloudstack.apache.org/en/latest/adminguide/management.html?highlight=jasypt#changing-the-database-password <http://docs.cloudstack.apache.org/en/latest/adminguide/management.html?highlight=jasypt#changing-the-database-password>
https.keystore.password=vmops.com <http://vmops.com/>
# If an encrypted password is used, specify the encryption type. Valid types: file, web, env (set environment variable CLOUD_SECRET_KEY)
# password.encryption.type=none
# The path to webapp directory
webapp.dir=/usr/share/cloudstack-management/webapp
# The path to access log file
access.log=/var/log/cloudstack/management/access.log
my DB.properties:
cluster.node.IP=10.23.23.21
cluster.servlet.port=9090
region.id <http://region.id/>=1
# CloudStack database settings
db.cloud.username=cloud
db.cloud.password=ENC(+xxxxx)
db.cloud.host=10.23.23.23
db.cloud.driver=jdbc:mysql
db.cloud.port=3306
db.cloud.name=cloud
# Connection URI to the database "cloud". When this property is set, only the following properties will be used along with it: db.cloud.maxActive, db.cloud.maxIdle, db.cloud.maxWait, db.cloud.username, db.cloud.password, db.cloud.driver, db.cloud.validationQuery, db.cloud.isolation.level. Other properties will be ignored.
db.cloud.uri=
# CloudStack database tuning parameters
db.cloud.connectionPoolLib=hikaricp
db.cloud.maxActive=7000
db.cloud.maxIdle=30
db.cloud.maxWait=600000
db.cloud.minIdleConnections=5
db.cloud.connectionTimeout=30000
db.cloud.keepAliveTime=600000
db.cloud.validationQuery=/* ping */ SELECT 1
db.cloud.testOnBorrow=true
db.cloud.testWhileIdle=true
db.cloud.timeBetweenEvictionRunsMillis=40000
db.cloud.minEvictableIdleTimeMillis=240000
db.cloud.poolPreparedStatements=false
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC
# CloudStack database SSL settings
db.cloud.useSSL=false
db.cloud.keyStore=
db.cloud.keyStorePassword=
db.cloud.trustStore=
db.cloud.trustStorePassword=
# Encryption Settings
db.cloud.encryption.type=file
db.cloud.encrypt.secret=ENC(XXXXX)
db.cloud.encryptor.version=V2
# usage database settings
db.usage.username=cloud
db.usage.password=ENC(XXXXX)
db.usage.host=10.23.23.23
db.usage.driver=jdbc:mysql
db.usage.port=3306
db.usage.name=cloud_usage
# Connection URI to the database "usage". When this property is set, only the following properties will be used along with it: db.usage.maxActive, db.cloud.maxIdle, db.cloud.maxWait, db.usage.username, db.usage.password, db.usage.driver, db.usage.validationQuery, db.usage.isolation.level. Other properties will be ignored.
db.usage.uri=
# usage database tuning parameters
db.usage.connectionPoolLib=hikaricp
db.usage.maxActive=5000
db.usage.maxIdle=30
db.usage.maxWait=600000
db.usage.minIdleConnections=5
db.usage.connectionTimeout=30000
db.usage.keepAliveTime=600000
db.usage.url.params=serverTimezone=UTC
# Simulator database settings
db.simulator.username=clouddemo
db.simulator.password=XXXX
db.simulator.host=10.23.23.23
db.simulator.driver=jdbc:mysql
db.simulator.port=3306
db.simulator.name=simulator
db.simulator.connectionPoolLib=hikaricp
db.simulator.maxActive=0
db.simulator.maxIdle=30
db.simulator.maxWait=600000
db.simulator.minIdleConnections=5
db.simulator.connectionTimeout=30000
db.simulator.keepAliveTime=600000
db.simulator.autoReconnect=true
# Connection URI to the database "simulator". When this property is set, only the following properties will be used along with it: db.simulator.host, db.simulator.port, db.simulator.name, db.simulator.autoReconnect. Other properties will be ignored.
db.simulator.uri=
# High Availability And Cluster Properties
db.ha.enabled=true
db.ha.loadBalanceStrategy=com.cloud.utils.db.StaticStrategy
# cloud stack Database
db.cloud.replicas=10.23.23.24
db.cloud.autoReconnect=true
db.cloud.failOverReadOnly=true
db.cloud.reconnectAtTxEnd=true
db.cloud.autoReconnectForPools=true
db.cloud.secondsBeforeRetrySource=60
db.cloud.queriesBeforeRetrySource=50
db.cloud.initialTimeout=60
#usage Database
db.usage.replicas=10.23.23.24
db.usage.autoReconnect=true
db.usage.failOverReadOnly=true
db.usage.reconnectAtTxEnd=true
db.usage.autoReconnectForPools=true
db.usage.secondsBeforeRetrySource=60
db.usage.queriesBeforeRetrySource=50
I did enable debug mode in everything:
No additional info
Thank you
Tata Y.
> On Feb 13, 2025, at 11:17 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi Chi,
>
> Either 4.20 or 4.19 has been installed in many productions. Both are production ready.
>
> I think it is caused by a configuration with your server or database. However your env is a black box to me.
>
> I run the same command as you (without deploy-as) , here is the output
>
> ===========
>
>
> # cloudstack-setup-databases cloud:rootpass@10.23.23.21 <ma...@10.23.23.21> -m iknow -k somekey -i 10.23.23.21
> Mysql user name:cloud [ OK ]
> Mysql user password:****** [ OK ]
> Mysql server ip:10.23.23.21 [ OK ]
> Mysql server port:3306 [ OK ]
> Using specified cluster management server node IP 10.23.23.21 [ OK ]
> Checking Cloud database files ... [ OK ]
> Checking local machine hostname ... [ OK ]
> Checking SELinux setup ... [ OK ]
> Preparing /etc/cloudstack/management/db.properties [ OK ]
> No mysql root user specified, will not create Cloud DB schema
> Processing encryption ... [ OK ]
> Finalizing setup ... [ OK ]
>
> CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>
> # systemctl restart cloudstack-management
>
> # tail -f /var/log/cloudstack/management/management-server.log
>
> 2025-02-13T16:12:53,115 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
> 2025-02-13T16:12:53,120 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
> 2025-02-13T16:12:53,124 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=false, https.port=8443, context.path=/client
> 2025-02-13T16:13:01,752 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
> 2025-02-13T16:13:01,753 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
> 2025-02-13T16:13:01,870 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
> 2025-02-13T16:13:01,871 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Calling to initialize for class com.cloud.utils.crypt.EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,055 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Initialized with all possible encryptors
> 2025-02-13T16:13:02,068 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) CloudStack will encrypt and decrypt values using encryptor : AeadBase64Encryptor for class EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,139 INFO [c.c.u.LogUtils] (main:[]) (logid:) log4j configuration found at /etc/cloudstack/management/log4j-cloud.xml
> 2025-02-13T16:13:02,143 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loaded module context [bootstrap] in 387 ms
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: bootstrap
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: system
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: core
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: allocator
>
>
> ===========
>
>
> Please note,
>
> If you use 4.19, please set default java version to 4.11
> If you use 4.20, please set default java version to 4.17
>
>
>
> -Wei
>
>
> On Thu, Feb 13, 2025 at 3:24 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Wei,
>>
>> Then 4.20 is not production ready !
>>
>> There are nothing on the logs so far to indicate a problem with the DB.
>>
>> Was this tested before for production, or was just throw to the community to be tested?
>>
>> Thank you
>>
>> Tata Y.
>>
>>
>>> On Feb 13, 2025, at 8:48 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Can you test with a local database ?
>>>
>>> -Wei
>>>
>>> On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> And Yes,
>>>>
>>>> I Did isntalled using a single Managemenent server with a Single Database, Nothing works so far. Still get the 503.
>>>>
>>>> As I mentioned before I did try any obvious possibility. I did not try removing the -m -k options just because that should work and nothing points to that may be the problem, as the DB are created on the remote DB.
>>>>
>>>> Thank you
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>>> On Feb 13, 2025, at 8:03 AM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hello Wei,
>>>>>
>>>>> Any Ideas ?
>>>>>
>>>>> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>>>>>
>>>>> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>>>>>
>>>>>
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hello Wei,
>>>>>>
>>>>>> I just did what you requested, without the -r 1
>>>>>>
>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>>>>>
>>>>>> same results.
>>>>>> http://10.23.23.21:8080/client/
>>>>>> HTTP ERROR 503 Service Unavailable
>>>>>>
>>>>>> URI: /client/
>>>>>> STATUS: 503
>>>>>> MESSAGE: Service Unavailable
>>>>>> SERVLET: -
>>>>>>
>>>>>> The same exact logs as before, there is no additional information in the logs.
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>
>>>>>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> strange
>>>>>>>
>>>>>>> Can you set up database without `-r 1` ?
>>>>>>>
>>>>>>> -Wei
>>>>>>>
>>>>>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>>>>>
>>>>>>>> I tryed, same result 503
>>>>>>>>
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Hello Wei,
>>>>>>>>>>
>>>>>>>>>> Interestingly I got same errors:
>>>>>>>>>>
>>>>>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>>>>>> 3) I run the command as follows, without the default keys
>>>>>>>>>>
>>>>>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> 4) start the management server
>>>>>>>>>>
>>>>>>>>>> 5) cheking the logs
>>>>>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I Even reinstalled the management server.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.log
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>
>>>>>>>>>> management-server.err
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.out
>>>>>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> any tips are welcome.
>>>>>>>>>>
>>>>>>>>>> Thank you
>>>>>>>>>>
>>>>>>>>>> Tata Y.
>>>>>>>>>>
>>>>>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>>>>>
>>>>>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>>>>>
>>>>>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Kind regards,
>>>>>>>>>>> Wei
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>> Hello Wei
>>>>>>>>>>>>
>>>>>>>>>>>> Additionally, I have the management error:
>>>>>>>>>>>>
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>>
>>>>>>>>>>>> I am using the JAVA 17
>>>>>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>>>>>
>>>>>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>>>>>
>>>>>>>>>>>> thank you
>>>>>>>>>>>>
>>>>>>>>>>>> Tata Y
>>>>>>>>>>>>
>>>>>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello Wei,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>>>>>
>>>>>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud user
>>>>>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>>>>>
>>>>>>>>>>>>> Tata Y.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> normally I use a command like
>>>>>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Wei
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>>>>>> ... 25 more
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Tata Y.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Hello team,
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Java version:
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> MySql version:
>>>>>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> and the grants
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Netstat output
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> ----
>>>>>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Wei,
What additional info do you need from my environment. ?
Should my syslog be listening to the port 4560 to get more logs?
my environment.properties:
paths.script=/usr/share/cloudstack-common
mount.parent=/var/lib/cloudstack/mnt
cloud-stack-components-specification=components-nonoss.xml
my server.properties:
context.path=/client
# The HTTP port to be used by the management server
http.enable=true
http.port=8080
# Max inactivity time in minutes for the session
session.timeout=30
# Max allowed API request payload/content size in bytes
request.content.size=1048576
# Options to configure and enable HTTPS on the management server
#
# For the management server to pick up these configuration settings, the configured
# keystore file should exist and be readable by the management server.
https.enable=true
https.port=8443
# The keystore and manager passwords are assumed to be same.
https.keystore=/etc/cloudstack/management/cloud.jks
# If you want to encrypt the password itself, follow the steps mentioned at:
http://docs.cloudstack.apache.org/en/latest/adminguide/management.html?highlight=jasypt#changing-the-database-password
https.keystore.password=vmops.com
# If an encrypted password is used, specify the encryption type. Valid types: file, web, env (set environment variable CLOUD_SECRET_KEY)
# password.encryption.type=none
# The path to webapp directory
webapp.dir=/usr/share/cloudstack-management/webapp
# The path to access log file
access.log=/var/log/cloudstack/management/access.log
my DB.properties:
cluster.node.IP=10.23.23.21
cluster.servlet.port=9090
region.id=1
# CloudStack database settings
db.cloud.username=cloud
db.cloud.password=ENC(+xxxxx)
db.cloud.host=10.23.23.23
db.cloud.driver=jdbc:mysql
db.cloud.port=3306
db.cloud.name=cloud
# Connection URI to the database "cloud". When this property is set, only the following properties will be used along with it: db.cloud.maxActive, db.cloud.maxIdle, db.cloud.maxWait, db.cloud.username, db.cloud.password, db.cloud.driver, db.cloud.validationQuery, db.cloud.isolation.level. Other properties will be ignored.
db.cloud.uri=
# CloudStack database tuning parameters
db.cloud.connectionPoolLib=hikaricp
db.cloud.maxActive=7000
db.cloud.maxIdle=30
db.cloud.maxWait=600000
db.cloud.minIdleConnections=5
db.cloud.connectionTimeout=30000
db.cloud.keepAliveTime=600000
db.cloud.validationQuery=/* ping */ SELECT 1
db.cloud.testOnBorrow=true
db.cloud.testWhileIdle=true
db.cloud.timeBetweenEvictionRunsMillis=40000
db.cloud.minEvictableIdleTimeMillis=240000
db.cloud.poolPreparedStatements=false
db.cloud.url.params=prepStmtCacheSize=517&cachePrepStmts=true&sessionVariables=sql_mode='STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION'&serverTimezone=UTC
# CloudStack database SSL settings
db.cloud.useSSL=false
db.cloud.keyStore=
db.cloud.keyStorePassword=
db.cloud.trustStore=
db.cloud.trustStorePassword=
# Encryption Settings
db.cloud.encryption.type=file
db.cloud.encrypt.secret=ENC(XXXXX)
db.cloud.encryptor.version=V2
# usage database settings
db.usage.username=cloud
db.usage.password=ENC(XXXXX)
db.usage.host=10.23.23.23
db.usage.driver=jdbc:mysql
db.usage.port=3306
db.usage.name=cloud_usage
# Connection URI to the database "usage". When this property is set, only the following properties will be used along with it: db.usage.maxActive, db.cloud.maxIdle, db.cloud.maxWait, db.usage.username, db.usage.password, db.usage.driver, db.usage.validationQuery, db.usage.isolation.level. Other properties will be ignored.
db.usage.uri=
# usage database tuning parameters
db.usage.connectionPoolLib=hikaricp
db.usage.maxActive=5000
db.usage.maxIdle=30
db.usage.maxWait=600000
db.usage.minIdleConnections=5
db.usage.connectionTimeout=30000
db.usage.keepAliveTime=600000
db.usage.url.params=serverTimezone=UTC
# Simulator database settings
db.simulator.username=clouddemo
db.simulator.password=XXXX
db.simulator.host=10.23.23.23
db.simulator.driver=jdbc:mysql
db.simulator.port=3306
db.simulator.name=simulator
db.simulator.connectionPoolLib=hikaricp
db.simulator.maxActive=0
db.simulator.maxIdle=30
db.simulator.maxWait=600000
db.simulator.minIdleConnections=5
db.simulator.connectionTimeout=30000
db.simulator.keepAliveTime=600000
db.simulator.autoReconnect=true
# Connection URI to the database "simulator". When this property is set, only the following properties will be used along with it: db.simulator.host, db.simulator.port, db.simulator.name, db.simulator.autoReconnect. Other properties will be ignored.
db.simulator.uri=
# High Availability And Cluster Properties
db.ha.enabled=true
db.ha.loadBalanceStrategy=com.cloud.utils.db.StaticStrategy
# cloud stack Database
db.cloud.replicas=10.23.23.24
db.cloud.autoReconnect=true
db.cloud.failOverReadOnly=true
db.cloud.reconnectAtTxEnd=true
db.cloud.autoReconnectForPools=true
db.cloud.secondsBeforeRetrySource=60
db.cloud.queriesBeforeRetrySource=50
db.cloud.initialTimeout=60
#usage Database
db.usage.replicas=10.23.23.24
db.usage.autoReconnect=true
db.usage.failOverReadOnly=true
db.usage.reconnectAtTxEnd=true
db.usage.autoReconnectForPools=true
db.usage.secondsBeforeRetrySource=60
db.usage.queriesBeforeRetrySource=50
I did enable debug mode in everything:
No additional info
Thank you
Tata Y.
> On Feb 13, 2025, at 11:17 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi Chi,
>
> Either 4.20 or 4.19 has been installed in many productions. Both are production ready.
>
> I think it is caused by a configuration with your server or database. However your env is a black box to me.
>
> I run the same command as you (without deploy-as) , here is the output
>
> ===========
>
>
> # cloudstack-setup-databases cloud:rootpass@10.23.23.21 <ma...@10.23.23.21> -m iknow -k somekey -i 10.23.23.21
> Mysql user name:cloud [ OK ]
> Mysql user password:****** [ OK ]
> Mysql server ip:10.23.23.21 [ OK ]
> Mysql server port:3306 [ OK ]
> Using specified cluster management server node IP 10.23.23.21 [ OK ]
> Checking Cloud database files ... [ OK ]
> Checking local machine hostname ... [ OK ]
> Checking SELinux setup ... [ OK ]
> Preparing /etc/cloudstack/management/db.properties [ OK ]
> No mysql root user specified, will not create Cloud DB schema
> Processing encryption ... [ OK ]
> Finalizing setup ... [ OK ]
>
> CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>
> # systemctl restart cloudstack-management
>
> # tail -f /var/log/cloudstack/management/management-server.log
>
> 2025-02-13T16:12:53,115 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
> 2025-02-13T16:12:53,120 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
> 2025-02-13T16:12:53,124 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=false, https.port=8443, context.path=/client
> 2025-02-13T16:13:01,752 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
> 2025-02-13T16:13:01,753 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
> 2025-02-13T16:13:01,870 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
> 2025-02-13T16:13:01,871 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Calling to initialize for class com.cloud.utils.crypt.EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,055 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Initialized with all possible encryptors
> 2025-02-13T16:13:02,068 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) CloudStack will encrypt and decrypt values using encryptor : AeadBase64Encryptor for class EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,139 INFO [c.c.u.LogUtils] (main:[]) (logid:) log4j configuration found at /etc/cloudstack/management/log4j-cloud.xml
> 2025-02-13T16:13:02,143 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loaded module context [bootstrap] in 387 ms
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: bootstrap
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: system
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: core
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: allocator
>
>
> ===========
>
>
> Please note,
>
> If you use 4.19, please set default java version to 4.11
> If you use 4.20, please set default java version to 4.17
>
>
>
> -Wei
>
>
> On Thu, Feb 13, 2025 at 3:24 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Wei,
>>
>> Then 4.20 is not production ready !
>>
>> There are nothing on the logs so far to indicate a problem with the DB.
>>
>> Was this tested before for production, or was just throw to the community to be tested?
>>
>> Thank you
>>
>> Tata Y.
>>
>>
>>> On Feb 13, 2025, at 8:48 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Can you test with a local database ?
>>>
>>> -Wei
>>>
>>> On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> And Yes,
>>>>
>>>> I Did isntalled using a single Managemenent server with a Single Database, Nothing works so far. Still get the 503.
>>>>
>>>> As I mentioned before I did try any obvious possibility. I did not try removing the -m -k options just because that should work and nothing points to that may be the problem, as the DB are created on the remote DB.
>>>>
>>>> Thank you
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>>> On Feb 13, 2025, at 8:03 AM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hello Wei,
>>>>>
>>>>> Any Ideas ?
>>>>>
>>>>> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>>>>>
>>>>> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>>>>>
>>>>>
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hello Wei,
>>>>>>
>>>>>> I just did what you requested, without the -r 1
>>>>>>
>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>>>>>
>>>>>> same results.
>>>>>> http://10.23.23.21:8080/client/
>>>>>> HTTP ERROR 503 Service Unavailable
>>>>>>
>>>>>> URI: /client/
>>>>>> STATUS: 503
>>>>>> MESSAGE: Service Unavailable
>>>>>> SERVLET: -
>>>>>>
>>>>>> The same exact logs as before, there is no additional information in the logs.
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>
>>>>>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> strange
>>>>>>>
>>>>>>> Can you set up database without `-r 1` ?
>>>>>>>
>>>>>>> -Wei
>>>>>>>
>>>>>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>>>>>
>>>>>>>> I tryed, same result 503
>>>>>>>>
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Hello Wei,
>>>>>>>>>>
>>>>>>>>>> Interestingly I got same errors:
>>>>>>>>>>
>>>>>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>>>>>> 3) I run the command as follows, without the default keys
>>>>>>>>>>
>>>>>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> 4) start the management server
>>>>>>>>>>
>>>>>>>>>> 5) cheking the logs
>>>>>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I Even reinstalled the management server.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.log
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>
>>>>>>>>>> management-server.err
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.out
>>>>>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> any tips are welcome.
>>>>>>>>>>
>>>>>>>>>> Thank you
>>>>>>>>>>
>>>>>>>>>> Tata Y.
>>>>>>>>>>
>>>>>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>>>>>
>>>>>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>>>>>
>>>>>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Kind regards,
>>>>>>>>>>> Wei
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>> Hello Wei
>>>>>>>>>>>>
>>>>>>>>>>>> Additionally, I have the management error:
>>>>>>>>>>>>
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>>
>>>>>>>>>>>> I am using the JAVA 17
>>>>>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>>>>>
>>>>>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>>>>>
>>>>>>>>>>>> thank you
>>>>>>>>>>>>
>>>>>>>>>>>> Tata Y
>>>>>>>>>>>>
>>>>>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello Wei,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>>>>>
>>>>>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud user
>>>>>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>>>>>
>>>>>>>>>>>>> Tata Y.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> normally I use a command like
>>>>>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Wei
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>>>>>> ... 25 more
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Tata Y.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Hello team,
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Java version:
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> MySql version:
>>>>>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> and the grants
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Netstat output
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> ----
>>>>>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>
Solved a BUG workaround - Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
I think I found the issue
I compeltely remove the 4.20.0.0
I installed in One server the 4.19.1.3
To me will work if you Upgrade from 4.19.x.x to 4.20.0.0 or have previouslinstalled the 4.19.x.x, but not on a clean install directly to 4.20.0.0.
Here is what I found:
root@csmgmtatl201:/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 14 01:37 log4j.xml -> /etc/cloudstack/management/log4j-cloud.xml
Worked!!
Upgraded to 4.20.0.0 worked.
SECOND SERVER:
On the second server I went directly to 4.20.0.0 again and Failed
I keep digging and found a difference between both servers:
root@csmgmtatl201:/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 14 13:36 log4j2.xml -> /etc/cloudstack/management/log4j-cloud.xml
On the 4.20.0.1 the link log4j.xml is missing
I see a difference. It worth to give a try.
I created the symlink on the second server where I never have had installed the 4.19.x.x
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 server.
Now you tell me if this should happen.
Hope this helps.
ALso if you are kind, can you tell me if I use a UBUNTU 22.04 minimal server what other dependencies should I have ?
Thank you
Tata Y.
> On Feb 13, 2025, at 11:17 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi Chi,
>
> Either 4.20 or 4.19 has been installed in many productions. Both are production ready.
>
> I think it is caused by a configuration with your server or database. However your env is a black box to me.
>
> I run the same command as you (without deploy-as) , here is the output
>
> ===========
>
>
> # cloudstack-setup-databases cloud:rootpass@10.23.23.21 <ma...@10.23.23.21> -m iknow -k somekey -i 10.23.23.21
> Mysql user name:cloud [ OK ]
> Mysql user password:****** [ OK ]
> Mysql server ip:10.23.23.21 [ OK ]
> Mysql server port:3306 [ OK ]
> Using specified cluster management server node IP 10.23.23.21 [ OK ]
> Checking Cloud database files ... [ OK ]
> Checking local machine hostname ... [ OK ]
> Checking SELinux setup ... [ OK ]
> Preparing /etc/cloudstack/management/db.properties [ OK ]
> No mysql root user specified, will not create Cloud DB schema
> Processing encryption ... [ OK ]
> Finalizing setup ... [ OK ]
>
> CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>
> # systemctl restart cloudstack-management
>
> # tail -f /var/log/cloudstack/management/management-server.log
>
> 2025-02-13T16:12:53,115 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
> 2025-02-13T16:12:53,120 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
> 2025-02-13T16:12:53,124 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=false, https.port=8443, context.path=/client
> 2025-02-13T16:13:01,752 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
> 2025-02-13T16:13:01,753 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
> 2025-02-13T16:13:01,870 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
> 2025-02-13T16:13:01,871 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Calling to initialize for class com.cloud.utils.crypt.EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,055 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) Initialized with all possible encryptors
> 2025-02-13T16:13:02,068 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[]) (logid:) CloudStack will encrypt and decrypt values using encryptor : AeadBase64Encryptor for class EncryptionSecretKeyChecker
> 2025-02-13T16:13:02,139 INFO [c.c.u.LogUtils] (main:[]) (logid:) log4j configuration found at /etc/cloudstack/management/log4j-cloud.xml
> 2025-02-13T16:13:02,143 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loaded module context [bootstrap] in 387 ms
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: bootstrap
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: system
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: core
> 2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Module Hierarchy: allocator
>
>
> ===========
>
>
> Please note,
>
> If you use 4.19, please set default java version to 4.11
> If you use 4.20, please set default java version to 4.17
>
>
>
> -Wei
>
>
> On Thu, Feb 13, 2025 at 3:24 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Wei,
>>
>> Then 4.20 is not production ready !
>>
>> There are nothing on the logs so far to indicate a problem with the DB.
>>
>> Was this tested before for production, or was just throw to the community to be tested?
>>
>> Thank you
>>
>> Tata Y.
>>
>>
>>> On Feb 13, 2025, at 8:48 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Can you test with a local database ?
>>>
>>> -Wei
>>>
>>> On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> And Yes,
>>>>
>>>> I Did isntalled using a single Managemenent server with a Single Database, Nothing works so far. Still get the 503.
>>>>
>>>> As I mentioned before I did try any obvious possibility. I did not try removing the -m -k options just because that should work and nothing points to that may be the problem, as the DB are created on the remote DB.
>>>>
>>>> Thank you
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>>> On Feb 13, 2025, at 8:03 AM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hello Wei,
>>>>>
>>>>> Any Ideas ?
>>>>>
>>>>> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>>>>>
>>>>> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>>>>>
>>>>>
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hello Wei,
>>>>>>
>>>>>> I just did what you requested, without the -r 1
>>>>>>
>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>>>>>
>>>>>> same results.
>>>>>> http://10.23.23.21:8080/client/
>>>>>> HTTP ERROR 503 Service Unavailable
>>>>>>
>>>>>> URI: /client/
>>>>>> STATUS: 503
>>>>>> MESSAGE: Service Unavailable
>>>>>> SERVLET: -
>>>>>>
>>>>>> The same exact logs as before, there is no additional information in the logs.
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>
>>>>>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> strange
>>>>>>>
>>>>>>> Can you set up database without `-r 1` ?
>>>>>>>
>>>>>>> -Wei
>>>>>>>
>>>>>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>>>>>
>>>>>>>> I tryed, same result 503
>>>>>>>>
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Hello Wei,
>>>>>>>>>>
>>>>>>>>>> Interestingly I got same errors:
>>>>>>>>>>
>>>>>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>>>>>> 3) I run the command as follows, without the default keys
>>>>>>>>>>
>>>>>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> 4) start the management server
>>>>>>>>>>
>>>>>>>>>> 5) cheking the logs
>>>>>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I Even reinstalled the management server.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.log
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>
>>>>>>>>>> management-server.err
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> management-server.out
>>>>>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> any tips are welcome.
>>>>>>>>>>
>>>>>>>>>> Thank you
>>>>>>>>>>
>>>>>>>>>> Tata Y.
>>>>>>>>>>
>>>>>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>>>>>
>>>>>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>>>>>
>>>>>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Kind regards,
>>>>>>>>>>> Wei
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>> Hello Wei
>>>>>>>>>>>>
>>>>>>>>>>>> Additionally, I have the management error:
>>>>>>>>>>>>
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>>>
>>>>>>>>>>>> I am using the JAVA 17
>>>>>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>>>>>
>>>>>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>>>>>
>>>>>>>>>>>> thank you
>>>>>>>>>>>>
>>>>>>>>>>>> Tata Y
>>>>>>>>>>>>
>>>>>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hello Wei,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>>>>>
>>>>>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Create the cloud user
>>>>>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>>>>>
>>>>>>>>>>>>> Tata Y.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> normally I use a command like
>>>>>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -Wei
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>>>>>> ... 25 more
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> > Tata Y.
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Hello team,
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Java version:
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> MySql version:
>>>>>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> and the grants
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Netstat output
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >> ----
>>>>>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>>>>>> >>
>>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
Hi Chi,
Either 4.20 or 4.19 has been installed in many productions. Both are
production ready.
I think it is caused by a configuration with your server or database.
However your env is a black box to me.
I run the same command as you (without deploy-as) , here is the output
===========
# cloudstack-setup-databases cloud:rootpass@10.23.23.21 -m iknow -k somekey
-i 10.23.23.21
Mysql user name:cloud
[ OK ]
Mysql user password:******
[ OK ]
Mysql server ip:10.23.23.21
[ OK ]
Mysql server port:3306
[ OK ]
Using specified cluster management server node IP 10.23.23.21
[ OK ]
Checking Cloud database files ...
[ OK ]
Checking local machine hostname ...
[ OK ]
Checking SELinux setup ...
[ OK ]
Preparing /etc/cloudstack/management/db.properties
[ OK ]
No mysql root user specified, will not create Cloud DB schema
Processing encryption ...
[ OK ]
Finalizing setup ...
[ OK ]
CloudStack has successfully initialized database, you can check your
database configuration in /etc/cloudstack/management/db.properties
# systemctl restart cloudstack-management
# tail -f /var/log/cloudstack/management/management-server.log
2025-02-13T16:12:53,115 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
Server configuration file found:
/etc/cloudstack/management/server.properties
2025-02-13T16:12:53,120 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
(main:[]) (logid:) Encryption Type: null
2025-02-13T16:12:53,124 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
Initializing server daemon on null, with http.enable=true, http.port=8080,
https.enable=false, https.port=8443, context.path=/client
2025-02-13T16:13:01,752 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Loading module context [bootstrap] from URL
[jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
2025-02-13T16:13:01,753 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Loading module context [bootstrap] from URL
[jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.1.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
2025-02-13T16:13:01,870 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
(main:[]) (logid:) Encryption Type: file
2025-02-13T16:13:01,871 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[])
(logid:) Calling to initialize for class
com.cloud.utils.crypt.EncryptionSecretKeyChecker
2025-02-13T16:13:02,055 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[])
(logid:) Initialized with all possible encryptors
2025-02-13T16:13:02,068 DEBUG [c.c.u.c.CloudStackEncryptor] (main:[])
(logid:) CloudStack will encrypt and decrypt values using encryptor :
AeadBase64Encryptor for class EncryptionSecretKeyChecker
2025-02-13T16:13:02,139 INFO [c.c.u.LogUtils] (main:[]) (logid:) log4j
configuration found at /etc/cloudstack/management/log4j-cloud.xml
2025-02-13T16:13:02,143 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Loaded module context [bootstrap] in 387 ms
2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Module Hierarchy: bootstrap
2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Module Hierarchy: system
2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Module Hierarchy: core
2025-02-13T16:13:02,145 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:[]) (logid:) Module Hierarchy: allocator
===========
Please note,
If you use 4.19, please set default java version to 4.11
If you use 4.20, please set default java version to 4.17
-Wei
On Thu, Feb 13, 2025 at 3:24 PM Chi vediamo <ta...@gmail.com> wrote:
> Wei,
>
> Then 4.20 is not production ready !
>
> There are nothing on the logs so far to indicate a problem with the DB.
>
> Was this tested before for production, or was just throw to the community
> to be tested?
>
> Thank you
>
> Tata Y.
>
>
> On Feb 13, 2025, at 8:48 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Can you test with a local database ?
>
> -Wei
>
> On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <ta...@gmail.com> wrote:
>
>> And Yes,
>>
>> I Did isntalled using a single Managemenent server with a Single
>> Database, Nothing works so far. Still get the 503.
>>
>> As I mentioned before I did try any obvious possibility. I did not try
>> removing the -m -k options just because that should work and nothing points
>> to that may be the problem, as the DB are created on the remote DB.
>>
>> Thank you
>>
>> Tata Y.
>>
>>
>>
>> On Feb 13, 2025, at 8:03 AM, Chi vediamo <ta...@gmail.com> wrote:
>>
>> Hello Wei,
>>
>> Any Ideas ?
>>
>> Just to add more context this is a fresh preproduction Install with 2
>> management servers and 2 DB servers in HA.
>>
>> Something I noticed many scripts appear to be for Upgrading to 4.20,
>> maybe I am wrong, SHould I use 4.20 directly ?
>>
>>
>>
>> Tata Y.
>>
>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>>
>> Hello Wei,
>>
>> I just did what you requested, without the -r 1
>>
>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --deploy-as=root:somepass
>> -m iknow -k somekey -i 10.23.23.21
>>
>> same results.
>> http://10.23.23.21:8080/client/
>> HTTP ERROR 503 Service Unavailable
>> URI: /client/
>> STATUS: 503
>> MESSAGE: Service Unavailable
>> SERVLET: -
>>
>> The same exact logs as before, there is no additional information in the
>> logs.
>>
>> Tata Y.
>>
>>
>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> strange
>>
>> Can you set up database without `-r 1` ?
>>
>> -Wei
>>
>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <ta...@gmail.com> wrote:
>>
>>> it automatically redirects to http://10.23.23.21:8080/client
>>>
>>> I tryed, same result 503
>>>
>>>
>>> Tata Y.
>>>
>>>
>>>
>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>>
>>> Can you try http://10.23.23.21:8080/client ?
>>>
>>>
>>>
>>> On Wednesday, February 12, 2025, Chi vediamo <ta...@gmail.com> wrote:
>>>
>>>> Hello Wei,
>>>>
>>>> Interestingly I got same errors:
>>>>
>>>> 1) I drop the databases cloud and cloud_usage
>>>> 2) stop the management server systemctl start cloudstack-management
>>>> 3) I run the command as follows, without the default keys
>>>>
>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --deploy-as=root:somepass
>>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>
>>>> 4) start the management server
>>>>
>>>> 5) cheking the logs
>>>> 6) Still getting 503 http://10.23.23.21:8080 same for the
>>>> http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>
>>>>
>>>> I Even reinstalled the management server.
>>>>
>>>>
>>>> management-server.log
>>>>
>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>>> Server configuration file found:
>>>> /etc/cloudstack/management/server.properties
>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>> (main:[]) (logid:) Encryption Type: null
>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>>> Initializing server daemon on null, with http.enable=true, http.port=8080,
>>>> https.enable=true, https.port=8443, context.path=/client
>>>> 2025-02-12 10:25:27,017 INFO
>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>> module context [bootstrap] from URL
>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>> 2025-02-12 10:25:27,017 INFO
>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>> module context [bootstrap] from URL
>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>> (main:[]) (logid:) Encryption Type: file
>>>>
>>>> management-server.err
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>> further details.
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>> further details.
>>>>
>>>>
>>>> management-server.out
>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager
>>>> (TCP:localhost:4560) caught exception and will continue: java.io.IOException:
>>>> Unable to create socket for localhost at port 4560 using ip address
>>>> 127.0.0.1 and port 4560
>>>> at org.apache.logging.log4j.core.net
>>>> .TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>> at org.apache.logging.log4j.core.net
>>>> .TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>> at org.apache.logging.log4j.core.net
>>>> .TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>> at
>>>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>> at
>>>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>> at org.apache.logging.log4j.core.net
>>>> .TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>> at
>>>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>> at
>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>> at
>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>> at
>>>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>> at
>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>> at
>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>> at
>>>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>> at
>>>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>> at
>>>> org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>> at
>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>> Caused by: java.net.ConnectException: Connection refused
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>>>> Method)
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>> .connect(Net.java:579)
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>> .connect(Net.java:568)
>>>> at java.base/sun.nio.ch
>>>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>>>> at java.base/java.net
>>>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>> at org.apache.logging.log4j.core.net
>>>> .TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>> at org.apache.logging.log4j.core.net
>>>> .TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>> ... 25 more
>>>>
>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter
>>>> that matches element properties
>>>>
>>>> any tips are welcome.
>>>>
>>>> Thank you
>>>>
>>>> Tata Y.
>>>>
>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <us...@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> The error logs can be ignored. The java version is good.
>>>>
>>>> Can you run the command (with deploy-as) to set up cloudstack
>>>> databases, and then restart cloudstack-management service ?
>>>>
>>>> You can get more logs
>>>> in /var/log/cloudstack/management/management-server.log
>>>>
>>>>
>>>> Kind regards,
>>>> Wei
>>>>
>>>>
>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <ta...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Wei
>>>>>
>>>>> Additionally, I have the management error:
>>>>>
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>>> further details.
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>>> further details.
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>>> further details.
>>>>>
>>>>> I am using the JAVA 17
>>>>> openjdk version "17.0.13" 2024-10-15
>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed
>>>>> mode, sharing)
>>>>>
>>>>> The management server is just a minimal server with syslog and the
>>>>> management 4.20 installation.
>>>>>
>>>>> thank you
>>>>>
>>>>> Tata Y
>>>>>
>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <ta...@gmail.com> wrote:
>>>>>
>>>>> Hello Wei,
>>>>>
>>>>> I use the manual page
>>>>> https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>
>>>>> and about 3/4 of the web page you sill find this instructions to do
>>>>> not have to pass thw root password on it
>>>>>
>>>>>
>>>>>
>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>
>>>>>
>>>>> - In dbpassword, specify the password to be assigned to the cloud
>>>>> user. You can choose to provide no password.
>>>>> - In deploy-as, specify the username and password of the user
>>>>> deploying the database. In the following command, it is assumed the root
>>>>> user is deploying the database and creating the cloud user.
>>>>> -
>>>>>
>>>>> (Optional) There is an option to bypass the creating of the
>>>>> databases, user and granting permissions to the user. This is useful if you
>>>>> don’t want to expose your root credentials but still want the database to
>>>>> be prepared for first start up. These skipped steps will have had to be
>>>>> done manually prior to executing this script.
>>>>>
>>>>> *This behaviour can be invoked by passing the –schema-only flag*.
>>>>> This flag conflicts with the –deploy-as flag so the two cannot be used
>>>>> together. To set up the databases and user manually before executing the
>>>>> script with the flag, these commands can be executed:
>>>>>
>>>>>
>>>>> I did created the Databases and provided the grants as the manual
>>>>> states.
>>>>>
>>>>>
>>>>> -- Create the cloud and cloud_usage databasesCREATE DATABASE `cloud`;CREATE DATABASE `cloud_usage`;
>>>>> -- Create the cloud userCREATE USER cloud@`localhost` identified by '<password>';CREATE USER cloud@`%` identified by '<password>';
>>>>> -- Grant all privileges to the cloud user on the databasesGRANT ALL ON cloud.* to cloud@`localhost`;GRANT ALL ON cloud.* to cloud@`%`;
>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>> -- Grant process list privilege for all other databasesGRANT process ON *.* TO cloud@`localhost`;GRANT process ON *.* TO cloud@`%`;
>>>>>
>>>>> - (Optional) For encryption_type, use file or web to indicate the
>>>>> technique used to pass in the database encryption password. Default: file.
>>>>> See About Password and Key Encryption
>>>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>>>> .
>>>>> - (Optional) For management_server_key, substitute the default key
>>>>> that is used to encrypt confidential parameters in the CloudStack
>>>>> properties file. Default: password. It is highly recommended that you
>>>>> replace this with a more secure value. See About Password and Key
>>>>> Encryption
>>>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>>>> .
>>>>> - (Optional) For database_key, substitute the default key that is
>>>>> used to encrypt confidential parameters in the CloudStack database.
>>>>> Default: password. It is highly recommended that you replace this with a
>>>>> more secure value. See About Password and Key Encryption
>>>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>>>> .
>>>>>
>>>>>
>>>>>
>>>>> I got the When this script is finished, you should see a message like
>>>>> “Successfully initialized the database.”
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>
>>>>>
>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I think there might be an issue with the command you executed.
>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>
>>>>> normally I use a command like
>>>>> cloudstack-setup-databases alex:founder@1.2.3.4
>>>>> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>
>>>>>
>>>>> -Wei
>>>>>
>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <ta...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Please help, as I am lost,
>>>>>>
>>>>>> I read everything i can find about, even reinstalling, I create the
>>>>>> DB and installed with the command shown below:
>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23
>>>>>> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>
>>>>>> db server 10.23.23.23 cluster
>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>> the database contains the tables.
>>>>>>
>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>> OS Ubuntu 22.04.5
>>>>>>
>>>>>>
>>>>>> And I still got the 503 error.
>>>>>>
>>>>>> I don't see any table with data, but the tables were populated, and
>>>>>> again there are no errors on the Mysql server side.
>>>>>>
>>>>>>
>>>>>>
>>>>>> the management server
>>>>>> /var/log/cloudstack/management/management-server.out
>>>>>>
>>>>>> shows only this reapeated times.
>>>>>>
>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager
>>>>>> (TCP:localhost:4560) caught exception and will continue:
>>>>>> java.io.IOException: Unable to create socket for localhost at port 4560
>>>>>> using ip address 127.0.0.1 and port 4560
>>>>>> at
>>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>> at
>>>>>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>> at
>>>>>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>> at
>>>>>> org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>> at
>>>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>>>>>> Method)
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>>>> .connect(Net.java:579)
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>>>> .connect(Net.java:568)
>>>>>> at java.base/sun.nio.ch
>>>>>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>> at java.base/java.net
>>>>>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>> at
>>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>> ... 25 more
>>>>>>
>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no
>>>>>> parameter that matches element properties
>>>>>>
>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com>
>>>>>> wrote:
>>>>>> >
>>>>>> > Is a fresh Install
>>>>>> >
>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>> >
>>>>>> > My DB is in a separate server,
>>>>>> >
>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which
>>>>>> is missing !!
>>>>>> >
>>>>>> >
>>>>>> >
>>>>>> > I follow the basic install with a separate DB. which completed as
>>>>>> successful.
>>>>>> >
>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23
>>>>>> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>> > Mysql user name:cloud
>>>>>> [ OK ]
>>>>>> > Mysql user password:******
>>>>>> [ OK ]
>>>>>> > Mysql server ip:10.23.23.23
>>>>>> [ OK ]
>>>>>> > Mysql server port:3306
>>>>>> [ OK ]
>>>>>> > Using specified cluster management server node IP 10.23.23.21
>>>>>> [ OK ]
>>>>>> > Checking Cloud database files ...
>>>>>> [ OK ]
>>>>>> > Checking local machine hostname ...
>>>>>> [ OK ]
>>>>>> > Checking SELinux setup ...
>>>>>> [ OK ]
>>>>>> > Preparing /etc/cloudstack/management/db.properties
>>>>>> [ OK ]
>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql
>>>>>> [ OK ]
>>>>>> > Applying
>>>>>> /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK
>>>>>> ]
>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql
>>>>>> [ OK ]
>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql
>>>>>> [ OK ]
>>>>>> > Processing encryption ...
>>>>>> [ OK ]
>>>>>> > Finalizing setup ...
>>>>>> [ OK ]
>>>>>> >
>>>>>> > CloudStack has successfully initialized database, you can check
>>>>>> your database configuration in /etc/cloudstack/management/db.properties
>>>>>> >
>>>>>> > All firewalls are down for now.
>>>>>> >
>>>>>> >
>>>>>> > my tail log is very simple:
>>>>>> >
>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>>>> (main:[]) (logid:) Encryption Type: file
>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[])
>>>>>> (logid:) Server configuration file found:
>>>>>> /etc/cloudstack/management/server.properties
>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>>>> (main:[]) (logid:) Encryption Type: null
>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[])
>>>>>> (logid:) Initializing server daemon on null, with http.enable=true,
>>>>>> http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>> > 2025-02-10 23:41:33,784 INFO
>>>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>>>> module context [bootstrap] from URL
>>>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>> > 2025-02-10 23:41:33,784 INFO
>>>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>>>> module context [bootstrap] from URL
>>>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>>>> (main:[]) (logid:) Encryption Type: file
>>>>>> >
>>>>>> > Tata Y.
>>>>>> >
>>>>>> >
>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org>
>>>>>> wrote:
>>>>>> >>
>>>>>> >>
>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack
>>>>>> UI after installation
>>>>>> >>
>>>>>> >> Hello team,
>>>>>> >>
>>>>>> >> I've took interest in CloudStack a few days ago and tried to
>>>>>> install it. I've got success but now I have a problem accessing the client
>>>>>> UI in my browser.
>>>>>> >>
>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is
>>>>>> 4.20.0.0. I've followed the steps at
>>>>>> https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>> >>
>>>>>> >> Type of installation is single node management server with nfs and
>>>>>> db on same host.
>>>>>> >>
>>>>>> >> Java version:
>>>>>> >> ```
>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>> >> OpenJDK Runtime Environment (build
>>>>>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>> >> OpenJDK 64-Bit Server VM (build
>>>>>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>> >> ```
>>>>>> >> MySql version:
>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using
>>>>>> EditLine wrapper`
>>>>>> >>
>>>>>> >> Database is configure and I have all grants for cloud user. I can
>>>>>> access the database at localhost with no problem with command
>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>> >>
>>>>>> >> and the grants
>>>>>> >> ```
>>>>>> >> mysql> show grants;
>>>>>> >> +----------------------------------------------------------------+
>>>>>> >> | Grants for cloud@localhost |
>>>>>> >> +----------------------------------------------------------------+
>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>> >> +----------------------------------------------------------------+
>>>>>> >> ```
>>>>>> >> This is part of my db.properties
>>>>>> >> ```
>>>>>> >> # management server clustering parameters, change cluster.node.IP
>>>>>> to the machine IP address
>>>>>> >> # in which the management server is running
>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>> >> cluster.servlet.port=9090
>>>>>> >> region.id=1
>>>>>> >>
>>>>>> >> # CloudStack database settings
>>>>>> >> db.cloud.username=cloud
>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>> >> db.cloud.host=localhost
>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>> >> db.cloud.port=3306
>>>>>> >> db.cloud.name=cloud
>>>>>> >> ```
>>>>>> >>
>>>>>> >> And this is output of command for service status
>>>>>> >> ```
>>>>>> >> systemctl status cloudstack-management
>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>> >> Loaded: loaded
>>>>>> (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset:
>>>>>> enabled)
>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET;
>>>>>> 40min ago
>>>>>> >> Main PID: 5358 (java)
>>>>>> >> ```
>>>>>> >> which shows some errors (i guess) in the second part
>>>>>> >> ```
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>> >> ```
>>>>>> >>
>>>>>> >> As of now I cannot access the http://localhost:8080/client/
>>>>>> address as it shows http 503.
>>>>>> >>
>>>>>> >> Netstat output
>>>>>> >> ```
>>>>>> >> netstat -tulpn | grep 8080
>>>>>> >> tcp6 0 0 :::8080 :::*
>>>>>> LISTEN 5358/java
>>>>>> >> ```
>>>>>> >>
>>>>>> >> You can find attached my log
>>>>>> >> [log.txt](
>>>>>> https://github.com/user-attachments/files/18550118/log.txt)
>>>>>> >>
>>>>>> >> There is a single sql exception about creating a table that
>>>>>> already exists.
>>>>>> >> ```
>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker]
>>>>>> (main:[]) (logid:) Unable to execute upgrade script
>>>>>> java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker]
>>>>>> (main:[]) (logid:) Unable to upgrade the database
>>>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
>>>>>> script
>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers'
>>>>>> already exists
>>>>>> >> ```
>>>>>> >>
>>>>>> >> But relevant part of log seems linked to Bean Definition. There
>>>>>> are many errors (under DEBUG/WARN) like this for different modules.
>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:)
>>>>>> Failed to start module [storage-volume-flasharray] due to: [Error creating
>>>>>> bean with name
>>>>>> 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0'
>>>>>> defined in URL
>>>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]:
>>>>>> Cannot resolve reference to bean 'DefaultConfigResources' while setting
>>>>>> bean property 'locations'; nested exception is
>>>>>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
>>>>>> named 'DefaultConfigResources' available]`
>>>>>> >>
>>>>>> >> How can I resolve?
>>>>>> >>
>>>>>> >> Thank you for any help.
>>>>>> >>
>>>>>> >> GitHub link:
>>>>>> https://github.com/apache/cloudstack/discussions/10276
>>>>>> >>
>>>>>> >> ----
>>>>>> >> This is an automatically sent email for
>>>>>> users@cloudstack.apache.org.
>>>>>> >> To unsubscribe, please send an email to:
>>>>>> users-unsubscribe@cloudstack.apache.org
>>>>>> >>
>>>>>> >
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Wei,
Then 4.20 is not production ready !
There are nothing on the logs so far to indicate a problem with the DB.
Was this tested before for production, or was just throw to the community to be tested?
Thank you
Tata Y.
> On Feb 13, 2025, at 8:48 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Can you test with a local database ?
>
> -Wei
>
> On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> And Yes,
>>
>> I Did isntalled using a single Managemenent server with a Single Database, Nothing works so far. Still get the 503.
>>
>> As I mentioned before I did try any obvious possibility. I did not try removing the -m -k options just because that should work and nothing points to that may be the problem, as the DB are created on the remote DB.
>>
>> Thank you
>>
>> Tata Y.
>>
>>
>>
>>> On Feb 13, 2025, at 8:03 AM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hello Wei,
>>>
>>> Any Ideas ?
>>>
>>> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>>>
>>> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>>>
>>>
>>>
>>> Tata Y.
>>>
>>>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hello Wei,
>>>>
>>>> I just did what you requested, without the -r 1
>>>>
>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>>>
>>>> same results.
>>>> http://10.23.23.21:8080/client/
>>>> HTTP ERROR 503 Service Unavailable
>>>>
>>>> URI: /client/
>>>> STATUS: 503
>>>> MESSAGE: Service Unavailable
>>>> SERVLET: -
>>>>
>>>> The same exact logs as before, there is no additional information in the logs.
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> strange
>>>>>
>>>>> Can you set up database without `-r 1` ?
>>>>>
>>>>> -Wei
>>>>>
>>>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>>>
>>>>>> I tryed, same result 503
>>>>>>
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> Hello Wei,
>>>>>>>>
>>>>>>>> Interestingly I got same errors:
>>>>>>>>
>>>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>>>> 3) I run the command as follows, without the default keys
>>>>>>>>
>>>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>
>>>>>>>> 4) start the management server
>>>>>>>>
>>>>>>>> 5) cheking the logs
>>>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>>>
>>>>>>>>
>>>>>>>> I Even reinstalled the management server.
>>>>>>>>
>>>>>>>>
>>>>>>>> management-server.log
>>>>>>>>
>>>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>
>>>>>>>> management-server.err
>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>
>>>>>>>>
>>>>>>>> management-server.out
>>>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>> ... 25 more
>>>>>>>>
>>>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>
>>>>>>>> any tips are welcome.
>>>>>>>>
>>>>>>>> Thank you
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>>>
>>>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>>>
>>>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Kind regards,
>>>>>>>>> Wei
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Hello Wei
>>>>>>>>>>
>>>>>>>>>> Additionally, I have the management error:
>>>>>>>>>>
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>>>
>>>>>>>>>> I am using the JAVA 17
>>>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>>>
>>>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>>>
>>>>>>>>>> thank you
>>>>>>>>>>
>>>>>>>>>> Tata Y
>>>>>>>>>>
>>>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hello Wei,
>>>>>>>>>>>
>>>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>>>
>>>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>>>
>>>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>>>
>>>>>>>>>>> -- Create the cloud user
>>>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>>>
>>>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>>>
>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>>>
>>>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>>>
>>>>>>>>>>> Tata Y.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>>>
>>>>>>>>>>>> normally I use a command like
>>>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> -Wei
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>>
>>>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>>>
>>>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>>>
>>>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>>>> ... 25 more
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>>>
>>>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > Tata Y.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Hello team,
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Java version:
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> MySql version:
>>>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> and the grants
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Netstat output
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>>>> >> ```
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> ----
>>>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
Can you test with a local database ?
-Wei
On Thu, Feb 13, 2025 at 2:44 PM Chi vediamo <ta...@gmail.com> wrote:
> And Yes,
>
> I Did isntalled using a single Managemenent server with a Single Database,
> Nothing works so far. Still get the 503.
>
> As I mentioned before I did try any obvious possibility. I did not try
> removing the -m -k options just because that should work and nothing points
> to that may be the problem, as the DB are created on the remote DB.
>
> Thank you
>
> Tata Y.
>
>
>
> On Feb 13, 2025, at 8:03 AM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> Any Ideas ?
>
> Just to add more context this is a fresh preproduction Install with 2
> management servers and 2 DB servers in HA.
>
> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe
> I am wrong, SHould I use 4.20 directly ?
>
>
>
> Tata Y.
>
> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> I just did what you requested, without the -r 1
>
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --deploy-as=root:somepass
> -m iknow -k somekey -i 10.23.23.21
>
> same results.
> http://10.23.23.21:8080/client/
> HTTP ERROR 503 Service Unavailable
> URI: /client/
> STATUS: 503
> MESSAGE: Service Unavailable
> SERVLET: -
>
> The same exact logs as before, there is no additional information in the
> logs.
>
> Tata Y.
>
>
> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>
> strange
>
> Can you set up database without `-r 1` ?
>
> -Wei
>
> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <ta...@gmail.com> wrote:
>
>> it automatically redirects to http://10.23.23.21:8080/client
>>
>> I tryed, same result 503
>>
>>
>> Tata Y.
>>
>>
>>
>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> Can you try http://10.23.23.21:8080/client ?
>>
>>
>>
>> On Wednesday, February 12, 2025, Chi vediamo <ta...@gmail.com> wrote:
>>
>>> Hello Wei,
>>>
>>> Interestingly I got same errors:
>>>
>>> 1) I drop the databases cloud and cloud_usage
>>> 2) stop the management server systemctl start cloudstack-management
>>> 3) I run the command as follows, without the default keys
>>>
>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --deploy-as=root:somepass
>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>
>>> 4) start the management server
>>>
>>> 5) cheking the logs
>>> 6) Still getting 503 http://10.23.23.21:8080 same for the
>>> http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>
>>>
>>> I Even reinstalled the management server.
>>>
>>>
>>> management-server.log
>>>
>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>> Server configuration file found:
>>> /etc/cloudstack/management/server.properties
>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>> (main:[]) (logid:) Encryption Type: null
>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>> Initializing server daemon on null, with http.enable=true, http.port=8080,
>>> https.enable=true, https.port=8443, context.path=/client
>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
>>> (main:[]) (logid:) Loading module context [bootstrap] from URL
>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
>>> (main:[]) (logid:) Loading module context [bootstrap] from URL
>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>> (main:[]) (logid:) Encryption Type: file
>>>
>>> management-server.err
>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>> further details.
>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>> further details.
>>>
>>>
>>> management-server.out
>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560)
>>> caught exception and will continue: java.io.IOException: Unable to
>>> create socket for localhost at port 4560 using ip address 127.0.0.1 and
>>> port 4560
>>> at org.apache.logging.log4j.core.net
>>> .TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>> at org.apache.logging.log4j.core.net
>>> .TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>> at org.apache.logging.log4j.core.net
>>> .TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>> at
>>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>> at
>>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>> at org.apache.logging.log4j.core.net
>>> .TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>> at
>>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>> at
>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>> at
>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>> at
>>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>> at
>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>> at
>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>> at
>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>> at
>>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>> at
>>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>> at
>>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>> at
>>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>> at
>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>> at
>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>> at
>>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>> at
>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>> at
>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>> at
>>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>> at
>>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>> at
>>> org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>> Caused by: java.net.ConnectException: Connection refused
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>>> Method)
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>> .connect(Net.java:579)
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>> .connect(Net.java:568)
>>> at java.base/sun.nio.ch
>>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>>> at java.base/java.net
>>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>> at org.apache.logging.log4j.core.net
>>> .TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>> at org.apache.logging.log4j.core.net
>>> .TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>> ... 25 more
>>>
>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter
>>> that matches element properties
>>>
>>> any tips are welcome.
>>>
>>> Thank you
>>>
>>> Tata Y.
>>>
>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <us...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> The error logs can be ignored. The java version is good.
>>>
>>> Can you run the command (with deploy-as) to set up cloudstack databases,
>>> and then restart cloudstack-management service ?
>>>
>>> You can get more logs
>>> in /var/log/cloudstack/management/management-server.log
>>>
>>>
>>> Kind regards,
>>> Wei
>>>
>>>
>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <ta...@gmail.com> wrote:
>>>
>>>> Hello Wei
>>>>
>>>> Additionally, I have the management error:
>>>>
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>> further details.
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>> further details.
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>>> further details.
>>>>
>>>> I am using the JAVA 17
>>>> openjdk version "17.0.13" 2024-10-15
>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed
>>>> mode, sharing)
>>>>
>>>> The management server is just a minimal server with syslog and the
>>>> management 4.20 installation.
>>>>
>>>> thank you
>>>>
>>>> Tata Y
>>>>
>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <ta...@gmail.com> wrote:
>>>>
>>>> Hello Wei,
>>>>
>>>> I use the manual page
>>>> https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>
>>>> and about 3/4 of the web page you sill find this instructions to do not
>>>> have to pass thw root password on it
>>>>
>>>>
>>>>
>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>
>>>>
>>>> - In dbpassword, specify the password to be assigned to the cloud
>>>> user. You can choose to provide no password.
>>>> - In deploy-as, specify the username and password of the user
>>>> deploying the database. In the following command, it is assumed the root
>>>> user is deploying the database and creating the cloud user.
>>>> -
>>>>
>>>> (Optional) There is an option to bypass the creating of the
>>>> databases, user and granting permissions to the user. This is useful if you
>>>> don’t want to expose your root credentials but still want the database to
>>>> be prepared for first start up. These skipped steps will have had to be
>>>> done manually prior to executing this script.
>>>>
>>>> *This behaviour can be invoked by passing the –schema-only flag*.
>>>> This flag conflicts with the –deploy-as flag so the two cannot be used
>>>> together. To set up the databases and user manually before executing the
>>>> script with the flag, these commands can be executed:
>>>>
>>>>
>>>> I did created the Databases and provided the grants as the manual
>>>> states.
>>>>
>>>>
>>>> -- Create the cloud and cloud_usage databasesCREATE DATABASE `cloud`;CREATE DATABASE `cloud_usage`;
>>>> -- Create the cloud userCREATE USER cloud@`localhost` identified by '<password>';CREATE USER cloud@`%` identified by '<password>';
>>>> -- Grant all privileges to the cloud user on the databasesGRANT ALL ON cloud.* to cloud@`localhost`;GRANT ALL ON cloud.* to cloud@`%`;
>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>> -- Grant process list privilege for all other databasesGRANT process ON *.* TO cloud@`localhost`;GRANT process ON *.* TO cloud@`%`;
>>>>
>>>> - (Optional) For encryption_type, use file or web to indicate the
>>>> technique used to pass in the database encryption password. Default: file.
>>>> See About Password and Key Encryption
>>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>>> .
>>>> - (Optional) For management_server_key, substitute the default key
>>>> that is used to encrypt confidential parameters in the CloudStack
>>>> properties file. Default: password. It is highly recommended that you
>>>> replace this with a more secure value. See About Password and Key
>>>> Encryption
>>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>>> .
>>>> - (Optional) For database_key, substitute the default key that is
>>>> used to encrypt confidential parameters in the CloudStack database.
>>>> Default: password. It is highly recommended that you replace this with a
>>>> more secure value. See About Password and Key Encryption
>>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>>> .
>>>>
>>>>
>>>>
>>>> I got the When this script is finished, you should see a message like
>>>> “Successfully initialized the database.”
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I think there might be an issue with the command you executed.
>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>
>>>> normally I use a command like
>>>> cloudstack-setup-databases alex:founder@1.2.3.4
>>>> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>
>>>>
>>>> -Wei
>>>>
>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <ta...@gmail.com> wrote:
>>>>
>>>>> Please help, as I am lost,
>>>>>
>>>>> I read everything i can find about, even reinstalling, I create the DB
>>>>> and installed with the command shown below:
>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only
>>>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> db server 10.23.23.23 cluster
>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>> the database contains the tables.
>>>>>
>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>> OS Ubuntu 22.04.5
>>>>>
>>>>>
>>>>> And I still got the 503 error.
>>>>>
>>>>> I don't see any table with data, but the tables were populated, and
>>>>> again there are no errors on the Mysql server side.
>>>>>
>>>>>
>>>>>
>>>>> the management server
>>>>> /var/log/cloudstack/management/management-server.out
>>>>>
>>>>> shows only this reapeated times.
>>>>>
>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager
>>>>> (TCP:localhost:4560) caught exception and will continue:
>>>>> java.io.IOException: Unable to create socket for localhost at port 4560
>>>>> using ip address 127.0.0.1 and port 4560
>>>>> at
>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at
>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at
>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at
>>>>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at
>>>>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at
>>>>> org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at
>>>>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at
>>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at
>>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at
>>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at
>>>>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at
>>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at
>>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at
>>>>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at
>>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at
>>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at
>>>>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at
>>>>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at
>>>>> org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at
>>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>>>>> Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>>> .connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>>> .connect(Net.java:568)
>>>>> at java.base/sun.nio.ch
>>>>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net
>>>>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>> at
>>>>> org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at
>>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no
>>>>> parameter that matches element properties
>>>>>
>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com> wrote:
>>>>> >
>>>>> > Is a fresh Install
>>>>> >
>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>> >
>>>>> > My DB is in a separate server,
>>>>> >
>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which
>>>>> is missing !!
>>>>> >
>>>>> >
>>>>> >
>>>>> > I follow the basic install with a separate DB. which completed as
>>>>> successful.
>>>>> >
>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only
>>>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>> > Mysql user name:cloud
>>>>> [ OK ]
>>>>> > Mysql user password:******
>>>>> [ OK ]
>>>>> > Mysql server ip:10.23.23.23
>>>>> [ OK ]
>>>>> > Mysql server port:3306
>>>>> [ OK ]
>>>>> > Using specified cluster management server node IP 10.23.23.21
>>>>> [ OK ]
>>>>> > Checking Cloud database files ...
>>>>> [ OK ]
>>>>> > Checking local machine hostname ...
>>>>> [ OK ]
>>>>> > Checking SELinux setup ...
>>>>> [ OK ]
>>>>> > Preparing /etc/cloudstack/management/db.properties
>>>>> [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql
>>>>> [ OK ]
>>>>> > Applying
>>>>> /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK
>>>>> ]
>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql
>>>>> [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql
>>>>> [ OK ]
>>>>> > Processing encryption ...
>>>>> [ OK ]
>>>>> > Finalizing setup ...
>>>>> [ OK ]
>>>>> >
>>>>> > CloudStack has successfully initialized database, you can check your
>>>>> database configuration in /etc/cloudstack/management/db.properties
>>>>> >
>>>>> > All firewalls are down for now.
>>>>> >
>>>>> >
>>>>> > my tail log is very simple:
>>>>> >
>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>>> (main:[]) (logid:) Encryption Type: file
>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[])
>>>>> (logid:) Server configuration file found:
>>>>> /etc/cloudstack/management/server.properties
>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>>> (main:[]) (logid:) Encryption Type: null
>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[])
>>>>> (logid:) Initializing server daemon on null, with http.enable=true,
>>>>> http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> > 2025-02-10 23:41:33,784 INFO
>>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>>> module context [bootstrap] from URL
>>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> > 2025-02-10 23:41:33,784 INFO
>>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>>> module context [bootstrap] from URL
>>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>>> (main:[]) (logid:) Encryption Type: file
>>>>> >
>>>>> > Tata Y.
>>>>> >
>>>>> >
>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org>
>>>>> wrote:
>>>>> >>
>>>>> >>
>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack
>>>>> UI after installation
>>>>> >>
>>>>> >> Hello team,
>>>>> >>
>>>>> >> I've took interest in CloudStack a few days ago and tried to
>>>>> install it. I've got success but now I have a problem accessing the client
>>>>> UI in my browser.
>>>>> >>
>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is
>>>>> 4.20.0.0. I've followed the steps at
>>>>> https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>> >>
>>>>> >> Type of installation is single node management server with nfs and
>>>>> db on same host.
>>>>> >>
>>>>> >> Java version:
>>>>> >> ```
>>>>> >> openjdk 11.0.19 2023-04-18
>>>>> >> OpenJDK Runtime Environment (build
>>>>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>> >> OpenJDK 64-Bit Server VM (build
>>>>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>> >> ```
>>>>> >> MySql version:
>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using
>>>>> EditLine wrapper`
>>>>> >>
>>>>> >> Database is configure and I have all grants for cloud user. I can
>>>>> access the database at localhost with no problem with command
>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>> >>
>>>>> >> and the grants
>>>>> >> ```
>>>>> >> mysql> show grants;
>>>>> >> +----------------------------------------------------------------+
>>>>> >> | Grants for cloud@localhost |
>>>>> >> +----------------------------------------------------------------+
>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>> >> +----------------------------------------------------------------+
>>>>> >> ```
>>>>> >> This is part of my db.properties
>>>>> >> ```
>>>>> >> # management server clustering parameters, change cluster.node.IP
>>>>> to the machine IP address
>>>>> >> # in which the management server is running
>>>>> >> cluster.node.IP=127.0.0.1
>>>>> >> cluster.servlet.port=9090
>>>>> >> region.id=1
>>>>> >>
>>>>> >> # CloudStack database settings
>>>>> >> db.cloud.username=cloud
>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>> >> db.cloud.host=localhost
>>>>> >> db.cloud.driver=jdbc:mysql
>>>>> >> db.cloud.port=3306
>>>>> >> db.cloud.name=cloud
>>>>> >> ```
>>>>> >>
>>>>> >> And this is output of command for service status
>>>>> >> ```
>>>>> >> systemctl status cloudstack-management
>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>> >> Loaded: loaded
>>>>> (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset:
>>>>> enabled)
>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min
>>>>> ago
>>>>> >> Main PID: 5358 (java)
>>>>> >> ```
>>>>> >> which shows some errors (i guess) in the second part
>>>>> >> ```
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>> >> ```
>>>>> >>
>>>>> >> As of now I cannot access the http://localhost:8080/client/
>>>>> address as it shows http 503.
>>>>> >>
>>>>> >> Netstat output
>>>>> >> ```
>>>>> >> netstat -tulpn | grep 8080
>>>>> >> tcp6 0 0 :::8080 :::*
>>>>> LISTEN 5358/java
>>>>> >> ```
>>>>> >>
>>>>> >> You can find attached my log
>>>>> >> [log.txt](
>>>>> https://github.com/user-attachments/files/18550118/log.txt)
>>>>> >>
>>>>> >> There is a single sql exception about creating a table that already
>>>>> exists.
>>>>> >> ```
>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker]
>>>>> (main:[]) (logid:) Unable to execute upgrade script
>>>>> java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker]
>>>>> (main:[]) (logid:) Unable to upgrade the database
>>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
>>>>> script
>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers'
>>>>> already exists
>>>>> >> ```
>>>>> >>
>>>>> >> But relevant part of log seems linked to Bean Definition. There are
>>>>> many errors (under DEBUG/WARN) like this for different modules.
>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:)
>>>>> Failed to start module [storage-volume-flasharray] due to: [Error creating
>>>>> bean with name
>>>>> 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0'
>>>>> defined in URL
>>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]:
>>>>> Cannot resolve reference to bean 'DefaultConfigResources' while setting
>>>>> bean property 'locations'; nested exception is
>>>>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
>>>>> named 'DefaultConfigResources' available]`
>>>>> >>
>>>>> >> How can I resolve?
>>>>> >>
>>>>> >> Thank you for any help.
>>>>> >>
>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>> >>
>>>>> >> ----
>>>>> >> This is an automatically sent email for users@cloudstack.apache.org
>>>>> .
>>>>> >> To unsubscribe, please send an email to:
>>>>> users-unsubscribe@cloudstack.apache.org
>>>>> >>
>>>>> >
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
And Yes,
I Did isntalled using a single Managemenent server with a Single Database, Nothing works so far. Still get the 503.
As I mentioned before I did try any obvious possibility. I did not try removing the -m -k options just because that should work and nothing points to that may be the problem, as the DB are created on the remote DB.
Thank you
Tata Y.
> On Feb 13, 2025, at 8:03 AM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> Any Ideas ?
>
> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>
> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
>
>
>
> Tata Y.
>
>> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>>
>> Hello Wei,
>>
>> I just did what you requested, without the -r 1
>>
>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>>
>> same results.
>> http://10.23.23.21:8080/client/
>> HTTP ERROR 503 Service Unavailable
>>
>> URI: /client/
>> STATUS: 503
>> MESSAGE: Service Unavailable
>> SERVLET: -
>>
>> The same exact logs as before, there is no additional information in the logs.
>>
>> Tata Y.
>>
>>
>>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>>
>>> strange
>>>
>>> Can you set up database without `-r 1` ?
>>>
>>> -Wei
>>>
>>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> it automatically redirects to http://10.23.23.21:8080/client
>>>>
>>>> I tryed, same result 503
>>>>
>>>>
>>>> Tata Y.
>>>>
>>>>
>>>>
>>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Can you try http://10.23.23.21:8080/client ?
>>>>>
>>>>>
>>>>>
>>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Hello Wei,
>>>>>>
>>>>>> Interestingly I got same errors:
>>>>>>
>>>>>> 1) I drop the databases cloud and cloud_usage
>>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>>> 3) I run the command as follows, without the default keys
>>>>>>
>>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>
>>>>>> 4) start the management server
>>>>>>
>>>>>> 5) cheking the logs
>>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>>
>>>>>>
>>>>>> I Even reinstalled the management server.
>>>>>>
>>>>>>
>>>>>> management-server.log
>>>>>>
>>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>
>>>>>> management-server.err
>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>
>>>>>>
>>>>>> management-server.out
>>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>> ... 25 more
>>>>>>
>>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>
>>>>>> any tips are welcome.
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> Tata Y.
>>>>>>
>>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> The error logs can be ignored. The java version is good.
>>>>>>>
>>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>>
>>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>>
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Wei
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>> Hello Wei
>>>>>>>>
>>>>>>>> Additionally, I have the management error:
>>>>>>>>
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>>
>>>>>>>> I am using the JAVA 17
>>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>>
>>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>>
>>>>>>>> thank you
>>>>>>>>
>>>>>>>> Tata Y
>>>>>>>>
>>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hello Wei,
>>>>>>>>>
>>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>>
>>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>>
>>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>>
>>>>>>>>> -- Create the cloud user
>>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>>
>>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>>
>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>>
>>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>>
>>>>>>>>> Tata Y.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>>
>>>>>>>>>> normally I use a command like
>>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Wei
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>>
>>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>>
>>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>>> the database contains the tables.
>>>>>>>>>>>
>>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>>
>>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>>
>>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>>
>>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>>> ... 25 more
>>>>>>>>>>>
>>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>>
>>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>>> >
>>>>>>>>>>> > Is a fresh Install
>>>>>>>>>>> >
>>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>>> >
>>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>>> >
>>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>>> >
>>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>>> >
>>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>>> >
>>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>>> >
>>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>>> >
>>>>>>>>>>> > Tata Y.
>>>>>>>>>>> >
>>>>>>>>>>> >
>>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>>> >>
>>>>>>>>>>> >>
>>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>>> >>
>>>>>>>>>>> >> Hello team,
>>>>>>>>>>> >>
>>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>>> >>
>>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>>> >>
>>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>>> >>
>>>>>>>>>>> >> Java version:
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> MySql version:
>>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>>> >>
>>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>>> >>
>>>>>>>>>>> >> and the grants
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>>> >>
>>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>>> >>
>>>>>>>>>>> >> Netstat output
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> You can find attached my log
>>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>>> >>
>>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>>> >> ```
>>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>>> >> ```
>>>>>>>>>>> >>
>>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>>> >>
>>>>>>>>>>> >> How can I resolve?
>>>>>>>>>>> >>
>>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>>> >>
>>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>>> >>
>>>>>>>>>>> >> ----
>>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>>> >>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
Any Ideas ?
Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly ?
Tata Y.
> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> I just did what you requested, without the -r 1
>
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>
> same results.
> http://10.23.23.21:8080/client/
> HTTP ERROR 503 Service Unavailable
>
> URI: /client/
> STATUS: 503
> MESSAGE: Service Unavailable
> SERVLET: -
>
> The same exact logs as before, there is no additional information in the logs.
>
> Tata Y.
>
>
>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> strange
>>
>> Can you set up database without `-r 1` ?
>>
>> -Wei
>>
>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>> it automatically redirects to http://10.23.23.21:8080/client
>>>
>>> I tryed, same result 503
>>>
>>>
>>> Tata Y.
>>>
>>>
>>>
>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Can you try http://10.23.23.21:8080/client ?
>>>>
>>>>
>>>>
>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> Hello Wei,
>>>>>
>>>>> Interestingly I got same errors:
>>>>>
>>>>> 1) I drop the databases cloud and cloud_usage
>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>> 3) I run the command as follows, without the default keys
>>>>>
>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> 4) start the management server
>>>>>
>>>>> 5) cheking the logs
>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>
>>>>>
>>>>> I Even reinstalled the management server.
>>>>>
>>>>>
>>>>> management-server.log
>>>>>
>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>
>>>>> management-server.err
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>
>>>>>
>>>>> management-server.out
>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>
>>>>> any tips are welcome.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The error logs can be ignored. The java version is good.
>>>>>>
>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>
>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>
>>>>>>
>>>>>> Kind regards,
>>>>>> Wei
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Hello Wei
>>>>>>>
>>>>>>> Additionally, I have the management error:
>>>>>>>
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>
>>>>>>> I am using the JAVA 17
>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>
>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>
>>>>>>> thank you
>>>>>>>
>>>>>>> Tata Y
>>>>>>>
>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hello Wei,
>>>>>>>>
>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>
>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>
>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>
>>>>>>>> -- Create the cloud user
>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>
>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>
>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>
>>>>>>>>
>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>
>>>>>>>>> normally I use a command like
>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Wei
>>>>>>>>>
>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>
>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>> the database contains the tables.
>>>>>>>>>>
>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>
>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>
>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Is a fresh Install
>>>>>>>>>> >
>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>> >
>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>> >
>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>> >
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>> >
>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>> >
>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>> >
>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> >
>>>>>>>>>> > Tata Y.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>> >>
>>>>>>>>>> >> Hello team,
>>>>>>>>>> >>
>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>> >>
>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>> >>
>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>> >>
>>>>>>>>>> >> Java version:
>>>>>>>>>> >> ```
>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>> >> ```
>>>>>>>>>> >> MySql version:
>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>> >>
>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>> >>
>>>>>>>>>> >> and the grants
>>>>>>>>>> >> ```
>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> ```
>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>> >> ```
>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>> >>
>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>> >> ```
>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>> >> ```
>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>> >> ```
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>> >>
>>>>>>>>>> >> Netstat output
>>>>>>>>>> >> ```
>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> You can find attached my log
>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>> >>
>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>> >> ```
>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>> >>
>>>>>>>>>> >> How can I resolve?
>>>>>>>>>> >>
>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>> >>
>>>>>>>>>> >> ----
>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>> >>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei
I did run every obvious option you may suggest.
Even on a single server with a single separated DB, Still Nothing.
I stop the management server and restarted.
Reinstalled the Management server. same result.
I stop the management server and restarted. i confirm is running.
but still 503.
Thank you
Tata Y.
> On Feb 13, 2025, at 7:48 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi,
>
> Did you run the command and start cloudstack-management service on both management servers ?
> Try with 1 management server, and set up another one when the 1st is ready (do not use deploy-as on 2nd).
>
>
> -Wei
>
>
>
> On Thu, Feb 13, 2025 at 1:39 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Hello Wei,
>>
>> Any Ideas ?
>>
>> Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
>>
>> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly or should I install first the 4.19.X ?
>>
>>
>>
>> Tata Y.
>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
Hi,
Did you run the command and start cloudstack-management service on both
management servers ?
Try with 1 management server, and set up another one when the 1st is ready
(do not use deploy-as on 2nd).
-Wei
On Thu, Feb 13, 2025 at 1:39 PM Chi vediamo <ta...@gmail.com> wrote:
> Hello Wei,
>
> Any Ideas ?
>
> Just to add more context this is a fresh preproduction Install with 2
> management servers and 2 DB servers in HA.
>
> Something I noticed many scripts appear to be for Upgrading to 4.20, maybe
> I am wrong, SHould I use 4.20 directly or should I install first the 4.19.X
> ?
>
>
>
> Tata Y.
>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
Any Ideas ?
Just to add more context this is a fresh preproduction Install with 2 management servers and 2 DB servers in HA.
Something I noticed many scripts appear to be for Upgrading to 4.20, maybe I am wrong, SHould I use 4.20 directly or should I install first the 4.19.X ?
Tata Y.
> On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> I just did what you requested, without the -r 1
>
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
>
> same results.
> http://10.23.23.21:8080/client/
> HTTP ERROR 503 Service Unavailable
>
> URI: /client/
> STATUS: 503
> MESSAGE: Service Unavailable
> SERVLET: -
>
> The same exact logs as before, there is no additional information in the logs.
>
> Tata Y.
>
>
>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> strange
>>
>> Can you set up database without `-r 1` ?
>>
>> -Wei
>>
>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>> it automatically redirects to http://10.23.23.21:8080/client
>>>
>>> I tryed, same result 503
>>>
>>>
>>> Tata Y.
>>>
>>>
>>>
>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Can you try http://10.23.23.21:8080/client ?
>>>>
>>>>
>>>>
>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> Hello Wei,
>>>>>
>>>>> Interestingly I got same errors:
>>>>>
>>>>> 1) I drop the databases cloud and cloud_usage
>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>> 3) I run the command as follows, without the default keys
>>>>>
>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> 4) start the management server
>>>>>
>>>>> 5) cheking the logs
>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>
>>>>>
>>>>> I Even reinstalled the management server.
>>>>>
>>>>>
>>>>> management-server.log
>>>>>
>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>
>>>>> management-server.err
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>
>>>>>
>>>>> management-server.out
>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>
>>>>> any tips are welcome.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The error logs can be ignored. The java version is good.
>>>>>>
>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>
>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>
>>>>>>
>>>>>> Kind regards,
>>>>>> Wei
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Hello Wei
>>>>>>>
>>>>>>> Additionally, I have the management error:
>>>>>>>
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>
>>>>>>> I am using the JAVA 17
>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>
>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>
>>>>>>> thank you
>>>>>>>
>>>>>>> Tata Y
>>>>>>>
>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hello Wei,
>>>>>>>>
>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>
>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>
>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>
>>>>>>>> -- Create the cloud user
>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>
>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>
>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>
>>>>>>>>
>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>
>>>>>>>>> normally I use a command like
>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Wei
>>>>>>>>>
>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>
>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>> the database contains the tables.
>>>>>>>>>>
>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>
>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>
>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Is a fresh Install
>>>>>>>>>> >
>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>> >
>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>> >
>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>> >
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>> >
>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>> >
>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>> >
>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> >
>>>>>>>>>> > Tata Y.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>> >>
>>>>>>>>>> >> Hello team,
>>>>>>>>>> >>
>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>> >>
>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>> >>
>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>> >>
>>>>>>>>>> >> Java version:
>>>>>>>>>> >> ```
>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>> >> ```
>>>>>>>>>> >> MySql version:
>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>> >>
>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>> >>
>>>>>>>>>> >> and the grants
>>>>>>>>>> >> ```
>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> ```
>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>> >> ```
>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>> >>
>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>> >> ```
>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>> >> ```
>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>> >> ```
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>> >>
>>>>>>>>>> >> Netstat output
>>>>>>>>>> >> ```
>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> You can find attached my log
>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>> >>
>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>> >> ```
>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>> >>
>>>>>>>>>> >> How can I resolve?
>>>>>>>>>> >>
>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>> >>
>>>>>>>>>> >> ----
>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>> >>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
On Feb 12, 2025, at 5:21 PM, Chi vediamo <ta...@gmail.com> wrote:
Hello Wei,
I just did what you requested, without the -r 1
cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
same results.
http://10.23.23.21:8080/client/
HTTP ERROR 503 Service Unavailable
> URI: /client/
> STATUS: 503
> MESSAGE: Service Unavailable
> SERVLET: -
>
> The same exact logs as before, there is no additional information in the logs.
>
> Tata Y.
>
>
>> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> strange
>>
>> Can you set up database without `-r 1` ?
>>
>> -Wei
>>
>> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>> it automatically redirects to http://10.23.23.21:8080/client
>>>
>>> I tryed, same result 503
>>>
>>>
>>> Tata Y.
>>>
>>>
>>>
>>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Can you try http://10.23.23.21:8080/client ?
>>>>
>>>>
>>>>
>>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> Hello Wei,
>>>>>
>>>>> Interestingly I got same errors:
>>>>>
>>>>> 1) I drop the databases cloud and cloud_usage
>>>>> 2) stop the management server systemctl start cloudstack-management
>>>>> 3) I run the command as follows, without the default keys
>>>>>
>>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> 4) start the management server
>>>>>
>>>>> 5) cheking the logs
>>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>>
>>>>>
>>>>> I Even reinstalled the management server.
>>>>>
>>>>>
>>>>> management-server.log
>>>>>
>>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>
>>>>> management-server.err
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>
>>>>>
>>>>> management-server.out
>>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>
>>>>> any tips are welcome.
>>>>>
>>>>> Thank you
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> The error logs can be ignored. The java version is good.
>>>>>>
>>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>>
>>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>>
>>>>>>
>>>>>> Kind regards,
>>>>>> Wei
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Hello Wei
>>>>>>>
>>>>>>> Additionally, I have the management error:
>>>>>>>
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>>
>>>>>>> I am using the JAVA 17
>>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>>
>>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>>
>>>>>>> thank you
>>>>>>>
>>>>>>> Tata Y
>>>>>>>
>>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hello Wei,
>>>>>>>>
>>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>>
>>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>>
>>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>>> CREATE DATABASE `cloud`;
>>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>>
>>>>>>>> -- Create the cloud user
>>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>>
>>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>>
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>>
>>>>>>>> -- Grant process list privilege for all other databases
>>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>>
>>>>>>>>
>>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>>
>>>>>>>> Tata Y.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>>
>>>>>>>>> normally I use a command like
>>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Wei
>>>>>>>>>
>>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> Please help, as I am lost,
>>>>>>>>>>
>>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>>
>>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>>> the database contains the tables.
>>>>>>>>>>
>>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> And I still got the 503 error.
>>>>>>>>>>
>>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>>
>>>>>>>>>> shows only this reapeated times.
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>>> ... 25 more
>>>>>>>>>>
>>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>>
>>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Is a fresh Install
>>>>>>>>>> >
>>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>>> >
>>>>>>>>>> > My DB is in a separate server,
>>>>>>>>>> >
>>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>>> >
>>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>>> >
>>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>>> >
>>>>>>>>>> > All firewalls are down for now.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > my tail log is very simple:
>>>>>>>>>> >
>>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>>> >
>>>>>>>>>> > Tata Y.
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>>> >>
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>>> >>
>>>>>>>>>> >> Hello team,
>>>>>>>>>> >>
>>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>>> >>
>>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>>> >>
>>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>>> >>
>>>>>>>>>> >> Java version:
>>>>>>>>>> >> ```
>>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>>> >> ```
>>>>>>>>>> >> MySql version:
>>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>>> >>
>>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>>> >>
>>>>>>>>>> >> and the grants
>>>>>>>>>> >> ```
>>>>>>>>>> >> mysql> show grants;
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>>> >> ```
>>>>>>>>>> >> This is part of my db.properties
>>>>>>>>>> >> ```
>>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>>> >> # in which the management server is running
>>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>>> >>
>>>>>>>>>> >> # CloudStack database settings
>>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> And this is output of command for service status
>>>>>>>>>> >> ```
>>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>>> >> ```
>>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>>> >> ```
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>>> >>
>>>>>>>>>> >> Netstat output
>>>>>>>>>> >> ```
>>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> You can find attached my log
>>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>>> >>
>>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>>> >> ```
>>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>>> >> ```
>>>>>>>>>> >>
>>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>>> >>
>>>>>>>>>> >> How can I resolve?
>>>>>>>>>> >>
>>>>>>>>>> >> Thank you for any help.
>>>>>>>>>> >>
>>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>>> >>
>>>>>>>>>> >> ----
>>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>>> >>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
I just did what you requested, without the -r 1
cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21
same results.
http://10.23.23.21:8080/client/
HTTP ERROR 503 Service Unavailable
URI: /client/
STATUS: 503
MESSAGE: Service Unavailable
SERVLET: -
The same exact logs as before, there is no additional information in the logs.
Tata Y.
> On Feb 12, 2025, at 3:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>
> strange
>
> Can you set up database without `-r 1` ?
>
> -Wei
>
> On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> it automatically redirects to http://10.23.23.21:8080/client
>>
>> I tryed, same result 503
>>
>>
>> Tata Y.
>>
>>
>>
>>> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Can you try http://10.23.23.21:8080/client ?
>>>
>>>
>>>
>>> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> Hello Wei,
>>>>
>>>> Interestingly I got same errors:
>>>>
>>>> 1) I drop the databases cloud and cloud_usage
>>>> 2) stop the management server systemctl start cloudstack-management
>>>> 3) I run the command as follows, without the default keys
>>>>
>>>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>
>>>> 4) start the management server
>>>>
>>>> 5) cheking the logs
>>>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>>>
>>>>
>>>> I Even reinstalled the management server.
>>>>
>>>>
>>>> management-server.log
>>>>
>>>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>
>>>> management-server.err
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>
>>>>
>>>> management-server.out
>>>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>> ... 25 more
>>>>
>>>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>>>
>>>> any tips are welcome.
>>>>
>>>> Thank you
>>>>
>>>> Tata Y.
>>>>
>>>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> The error logs can be ignored. The java version is good.
>>>>>
>>>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>>>
>>>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>>>
>>>>>
>>>>> Kind regards,
>>>>> Wei
>>>>>
>>>>>
>>>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>> Hello Wei
>>>>>>
>>>>>> Additionally, I have the management error:
>>>>>>
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>>>
>>>>>> I am using the JAVA 17
>>>>>> openjdk version "17.0.13" 2024-10-15
>>>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>>>
>>>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>>>
>>>>>> thank you
>>>>>>
>>>>>> Tata Y
>>>>>>
>>>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>
>>>>>>> Hello Wei,
>>>>>>>
>>>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>>>
>>>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>>>
>>>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -- Create the cloud and cloud_usage databases
>>>>>>> CREATE DATABASE `cloud`;
>>>>>>> CREATE DATABASE `cloud_usage`;
>>>>>>>
>>>>>>> -- Create the cloud user
>>>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>>>
>>>>>>> -- Grant all privileges to the cloud user on the databases
>>>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>>>
>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>>>
>>>>>>> -- Grant process list privilege for all other databases
>>>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>>>
>>>>>>>
>>>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>>>
>>>>>>> Tata Y.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I think there might be an issue with the command you executed.
>>>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>>>
>>>>>>>> normally I use a command like
>>>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>>>
>>>>>>>>
>>>>>>>> -Wei
>>>>>>>>
>>>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>> Please help, as I am lost,
>>>>>>>>>
>>>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>>
>>>>>>>>> db server 10.23.23.23 cluster
>>>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>>>> the database contains the tables.
>>>>>>>>>
>>>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>>>> OS Ubuntu 22.04.5
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> And I still got the 503 error.
>>>>>>>>>
>>>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>>>
>>>>>>>>> shows only this reapeated times.
>>>>>>>>>
>>>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>>>> ... 25 more
>>>>>>>>>
>>>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>>>
>>>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>>>> >
>>>>>>>>> > Is a fresh Install
>>>>>>>>> >
>>>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>>>> >
>>>>>>>>> > My DB is in a separate server,
>>>>>>>>> >
>>>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>>>> >
>>>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>>>> > Processing encryption ... [ OK ]
>>>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>>>> >
>>>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>>>> >
>>>>>>>>> > All firewalls are down for now.
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> > my tail log is very simple:
>>>>>>>>> >
>>>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>>>> >
>>>>>>>>> > Tata Y.
>>>>>>>>> >
>>>>>>>>> >
>>>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>>>> >>
>>>>>>>>> >> Hello team,
>>>>>>>>> >>
>>>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>>>> >>
>>>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>>>> >>
>>>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>>>> >>
>>>>>>>>> >> Java version:
>>>>>>>>> >> ```
>>>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>>>> >> ```
>>>>>>>>> >> MySql version:
>>>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>>>> >>
>>>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>>>> >>
>>>>>>>>> >> and the grants
>>>>>>>>> >> ```
>>>>>>>>> >> mysql> show grants;
>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>> >> | Grants for cloud@localhost |
>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>>>> >> +----------------------------------------------------------------+
>>>>>>>>> >> ```
>>>>>>>>> >> This is part of my db.properties
>>>>>>>>> >> ```
>>>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>>>> >> # in which the management server is running
>>>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>>>> >> cluster.servlet.port=9090
>>>>>>>>> >> region.id <http://region.id/>=1
>>>>>>>>> >>
>>>>>>>>> >> # CloudStack database settings
>>>>>>>>> >> db.cloud.username=cloud
>>>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>>>> >> db.cloud.host=localhost
>>>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>>>> >> db.cloud.port=3306
>>>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>>>> >> ```
>>>>>>>>> >>
>>>>>>>>> >> And this is output of command for service status
>>>>>>>>> >> ```
>>>>>>>>> >> systemctl status cloudstack-management
>>>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>>>> >> Main PID: 5358 (java)
>>>>>>>>> >> ```
>>>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>>>> >> ```
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>>>> >> ```
>>>>>>>>> >>
>>>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>>>> >>
>>>>>>>>> >> Netstat output
>>>>>>>>> >> ```
>>>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>>>> >> ```
>>>>>>>>> >>
>>>>>>>>> >> You can find attached my log
>>>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>>>> >>
>>>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>>>> >> ```
>>>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>>>> >> ```
>>>>>>>>> >>
>>>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>>>> >>
>>>>>>>>> >> How can I resolve?
>>>>>>>>> >>
>>>>>>>>> >> Thank you for any help.
>>>>>>>>> >>
>>>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>>>> >>
>>>>>>>>> >> ----
>>>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>>>> >>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
strange
Can you set up database without `-r 1` ?
-Wei
On Wed, Feb 12, 2025 at 8:58 PM Chi vediamo <ta...@gmail.com> wrote:
> it automatically redirects to http://10.23.23.21:8080/client
>
> I tryed, same result 503
>
>
> Tata Y.
>
>
>
> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>
> Can you try http://10.23.23.21:8080/client ?
>
>
>
> On Wednesday, February 12, 2025, Chi vediamo <ta...@gmail.com> wrote:
>
>> Hello Wei,
>>
>> Interestingly I got same errors:
>>
>> 1) I drop the databases cloud and cloud_usage
>> 2) stop the management server systemctl start cloudstack-management
>> 3) I run the command as follows, without the default keys
>>
>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --deploy-as=root:somepass
>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>
>> 4) start the management server
>>
>> 5) cheking the logs
>> 6) Still getting 503 http://10.23.23.21:8080 same for the
>> http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>
>>
>> I Even reinstalled the management server.
>>
>>
>> management-server.log
>>
>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>> Server configuration file found:
>> /etc/cloudstack/management/server.properties
>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>> (main:[]) (logid:) Encryption Type: null
>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>> Initializing server daemon on null, with http.enable=true, http.port=8080,
>> https.enable=true, https.port=8443, context.path=/client
>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
>> (main:[]) (logid:) Loading module context [bootstrap] from URL
>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
>> (main:[]) (logid:) Loading module context [bootstrap] from URL
>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>> (main:[]) (logid:) Encryption Type: file
>>
>> management-server.err
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>> further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>> further details.
>>
>>
>> management-server.out
>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560)
>> caught exception and will continue: java.io.IOException: Unable to
>> create socket for localhost at port 4560 using ip address 127.0.0.1 and
>> port 4560
>> at org.apache.logging.log4j.core.net
>> .TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>> at org.apache.logging.log4j.core.net
>> .TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>> at org.apache.logging.log4j.core.net
>> .TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>> at
>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>> at
>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>> at org.apache.logging.log4j.core.net
>> .TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>> at
>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>> at
>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>> at
>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>> at
>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>> at
>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>> at
>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>> at
>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>> at
>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>> at
>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>> at
>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>> at
>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>> at
>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>> Caused by: java.net.ConnectException: Connection refused
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>> Method)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>> .connect(Net.java:579)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>> .connect(Net.java:568)
>> at java.base/sun.nio.ch
>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>> at java.base/java.net
>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>> at java.base/java.net.Socket.connect(Socket.java:633)
>> at org.apache.logging.log4j.core.net
>> .TcpSocketManager.createSocket(TcpSocketManager.java:409)
>> at org.apache.logging.log4j.core.net
>> .TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>> ... 25 more
>>
>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter
>> that matches element properties
>>
>> any tips are welcome.
>>
>> Thank you
>>
>> Tata Y.
>>
>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> Hi,
>>
>> The error logs can be ignored. The java version is good.
>>
>> Can you run the command (with deploy-as) to set up cloudstack databases,
>> and then restart cloudstack-management service ?
>>
>> You can get more logs
>> in /var/log/cloudstack/management/management-server.log
>>
>>
>> Kind regards,
>> Wei
>>
>>
>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <ta...@gmail.com> wrote:
>>
>>> Hello Wei
>>>
>>> Additionally, I have the management error:
>>>
>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>> further details.
>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>> further details.
>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>>> further details.
>>>
>>> I am using the JAVA 17
>>> openjdk version "17.0.13" 2024-10-15
>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed
>>> mode, sharing)
>>>
>>> The management server is just a minimal server with syslog and the
>>> management 4.20 installation.
>>>
>>> thank you
>>>
>>> Tata Y
>>>
>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <ta...@gmail.com> wrote:
>>>
>>> Hello Wei,
>>>
>>> I use the manual page
>>> https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>
>>> and about 3/4 of the web page you sill find this instructions to do not
>>> have to pass thw root password on it
>>>
>>>
>>>
>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>
>>>
>>> - In dbpassword, specify the password to be assigned to the cloud
>>> user. You can choose to provide no password.
>>> - In deploy-as, specify the username and password of the user
>>> deploying the database. In the following command, it is assumed the root
>>> user is deploying the database and creating the cloud user.
>>> -
>>>
>>> (Optional) There is an option to bypass the creating of the
>>> databases, user and granting permissions to the user. This is useful if you
>>> don’t want to expose your root credentials but still want the database to
>>> be prepared for first start up. These skipped steps will have had to be
>>> done manually prior to executing this script.
>>>
>>> *This behaviour can be invoked by passing the –schema-only flag*.
>>> This flag conflicts with the –deploy-as flag so the two cannot be used
>>> together. To set up the databases and user manually before executing the
>>> script with the flag, these commands can be executed:
>>>
>>>
>>> I did created the Databases and provided the grants as the manual
>>> states.
>>>
>>>
>>> -- Create the cloud and cloud_usage databasesCREATE DATABASE `cloud`;CREATE DATABASE `cloud_usage`;
>>> -- Create the cloud userCREATE USER cloud@`localhost` identified by '<password>';CREATE USER cloud@`%` identified by '<password>';
>>> -- Grant all privileges to the cloud user on the databasesGRANT ALL ON cloud.* to cloud@`localhost`;GRANT ALL ON cloud.* to cloud@`%`;
>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;GRANT ALL ON cloud_usage.* to cloud@`%`;
>>> -- Grant process list privilege for all other databasesGRANT process ON *.* TO cloud@`localhost`;GRANT process ON *.* TO cloud@`%`;
>>>
>>> - (Optional) For encryption_type, use file or web to indicate the
>>> technique used to pass in the database encryption password. Default: file.
>>> See About Password and Key Encryption
>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>> .
>>> - (Optional) For management_server_key, substitute the default key
>>> that is used to encrypt confidential parameters in the CloudStack
>>> properties file. Default: password. It is highly recommended that you
>>> replace this with a more secure value. See About Password and Key
>>> Encryption
>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>> .
>>> - (Optional) For database_key, substitute the default key that is
>>> used to encrypt confidential parameters in the CloudStack database.
>>> Default: password. It is highly recommended that you replace this with a
>>> more secure value. See About Password and Key Encryption
>>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>>> .
>>>
>>>
>>>
>>> I got the When this script is finished, you should see a message like
>>> “Successfully initialized the database.”
>>>
>>> Tata Y.
>>>
>>>
>>>
>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> I think there might be an issue with the command you executed.
>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>
>>> normally I use a command like
>>> cloudstack-setup-databases alex:founder@1.2.3.4
>>> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>
>>>
>>> -Wei
>>>
>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <ta...@gmail.com> wrote:
>>>
>>>> Please help, as I am lost,
>>>>
>>>> I read everything i can find about, even reinstalling, I create the DB
>>>> and installed with the command shown below:
>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only
>>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>
>>>> db server 10.23.23.23 cluster
>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>> the database contains the tables.
>>>>
>>>> No connection errors to the DB. Mysql 8.0.40
>>>> OS Ubuntu 22.04.5
>>>>
>>>>
>>>> And I still got the 503 error.
>>>>
>>>> I don't see any table with data, but the tables were populated, and
>>>> again there are no errors on the Mysql server side.
>>>>
>>>>
>>>>
>>>> the management server
>>>> /var/log/cloudstack/management/management-server.out
>>>>
>>>> shows only this reapeated times.
>>>>
>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager
>>>> (TCP:localhost:4560) caught exception and will continue:
>>>> java.io.IOException: Unable to create socket for localhost at port 4560
>>>> using ip address 127.0.0.1 and port 4560
>>>> at
>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>> at
>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>> at
>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>> at
>>>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>> at
>>>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>> at
>>>> org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>> at
>>>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>> at
>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>> at
>>>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>> at
>>>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>> at
>>>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>> at
>>>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>> at
>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>> at
>>>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>> at
>>>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>> at
>>>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>> at
>>>> org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>> at
>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>> Caused by: java.net.ConnectException: Connection refused
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>>>> Method)
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>> .connect(Net.java:579)
>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>>>> .connect(Net.java:568)
>>>> at java.base/sun.nio.ch
>>>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>>>> at java.base/java.net
>>>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>> at
>>>> org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>> at
>>>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>> ... 25 more
>>>>
>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter
>>>> that matches element properties
>>>>
>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com> wrote:
>>>> >
>>>> > Is a fresh Install
>>>> >
>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>> >
>>>> > My DB is in a separate server,
>>>> >
>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is
>>>> missing !!
>>>> >
>>>> >
>>>> >
>>>> > I follow the basic install with a separate DB. which completed as
>>>> successful.
>>>> >
>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only
>>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>> > Mysql user name:cloud
>>>> [ OK ]
>>>> > Mysql user password:******
>>>> [ OK ]
>>>> > Mysql server ip:10.23.23.23
>>>> [ OK ]
>>>> > Mysql server port:3306
>>>> [ OK ]
>>>> > Using specified cluster management server node IP 10.23.23.21
>>>> [ OK ]
>>>> > Checking Cloud database files ...
>>>> [ OK ]
>>>> > Checking local machine hostname ...
>>>> [ OK ]
>>>> > Checking SELinux setup ...
>>>> [ OK ]
>>>> > Preparing /etc/cloudstack/management/db.properties
>>>> [ OK ]
>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql
>>>> [ OK ]
>>>> > Applying
>>>> /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK
>>>> ]
>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql
>>>> [ OK ]
>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql
>>>> [ OK ]
>>>> > Processing encryption ...
>>>> [ OK ]
>>>> > Finalizing setup ...
>>>> [ OK ]
>>>> >
>>>> > CloudStack has successfully initialized database, you can check your
>>>> database configuration in /etc/cloudstack/management/db.properties
>>>> >
>>>> > All firewalls are down for now.
>>>> >
>>>> >
>>>> > my tail log is very simple:
>>>> >
>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>> (main:[]) (logid:) Encryption Type: file
>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>>> Server configuration file found:
>>>> /etc/cloudstack/management/server.properties
>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>> (main:[]) (logid:) Encryption Type: null
>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>>> Initializing server daemon on null, with http.enable=true, http.port=8080,
>>>> https.enable=true, https.port=8443, context.path=/client
>>>> > 2025-02-10 23:41:33,784 INFO
>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>> module context [bootstrap] from URL
>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>> > 2025-02-10 23:41:33,784 INFO
>>>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>>>> module context [bootstrap] from URL
>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>>> (main:[]) (logid:) Encryption Type: file
>>>> >
>>>> > Tata Y.
>>>> >
>>>> >
>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org>
>>>> wrote:
>>>> >>
>>>> >>
>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack
>>>> UI after installation
>>>> >>
>>>> >> Hello team,
>>>> >>
>>>> >> I've took interest in CloudStack a few days ago and tried to install
>>>> it. I've got success but now I have a problem accessing the client UI in my
>>>> browser.
>>>> >>
>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is
>>>> 4.20.0.0. I've followed the steps at
>>>> https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>> >>
>>>> >> Type of installation is single node management server with nfs and
>>>> db on same host.
>>>> >>
>>>> >> Java version:
>>>> >> ```
>>>> >> openjdk 11.0.19 2023-04-18
>>>> >> OpenJDK Runtime Environment (build
>>>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>> >> OpenJDK 64-Bit Server VM (build
>>>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>> >> ```
>>>> >> MySql version:
>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine
>>>> wrapper`
>>>> >>
>>>> >> Database is configure and I have all grants for cloud user. I can
>>>> access the database at localhost with no problem with command
>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>> >>
>>>> >> and the grants
>>>> >> ```
>>>> >> mysql> show grants;
>>>> >> +----------------------------------------------------------------+
>>>> >> | Grants for cloud@localhost |
>>>> >> +----------------------------------------------------------------+
>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>> >> +----------------------------------------------------------------+
>>>> >> ```
>>>> >> This is part of my db.properties
>>>> >> ```
>>>> >> # management server clustering parameters, change cluster.node.IP to
>>>> the machine IP address
>>>> >> # in which the management server is running
>>>> >> cluster.node.IP=127.0.0.1
>>>> >> cluster.servlet.port=9090
>>>> >> region.id=1
>>>> >>
>>>> >> # CloudStack database settings
>>>> >> db.cloud.username=cloud
>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>> >> db.cloud.host=localhost
>>>> >> db.cloud.driver=jdbc:mysql
>>>> >> db.cloud.port=3306
>>>> >> db.cloud.name=cloud
>>>> >> ```
>>>> >>
>>>> >> And this is output of command for service status
>>>> >> ```
>>>> >> systemctl status cloudstack-management
>>>> >> cloudstack-management.service - CloudStack Management Server
>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
>>>> enabled; vendor preset: enabled)
>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min
>>>> ago
>>>> >> Main PID: 5358 (java)
>>>> >> ```
>>>> >> which shows some errors (i guess) in the second part
>>>> >> ```
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.server.Server.start(Server.java:423)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>> >> gen 26 13:20:21 mypc java[5358]: at
>>>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>> >> ```
>>>> >>
>>>> >> As of now I cannot access the http://localhost:8080/client/ address
>>>> as it shows http 503.
>>>> >>
>>>> >> Netstat output
>>>> >> ```
>>>> >> netstat -tulpn | grep 8080
>>>> >> tcp6 0 0 :::8080 :::*
>>>> LISTEN 5358/java
>>>> >> ```
>>>> >>
>>>> >> You can find attached my log
>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt
>>>> )
>>>> >>
>>>> >> There is a single sql exception about creating a table that already
>>>> exists.
>>>> >> ```
>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker]
>>>> (main:[]) (logid:) Unable to execute upgrade script
>>>> java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker]
>>>> (main:[]) (logid:) Unable to upgrade the database
>>>> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
>>>> script
>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers'
>>>> already exists
>>>> >> ```
>>>> >>
>>>> >> But relevant part of log seems linked to Bean Definition. There are
>>>> many errors (under DEBUG/WARN) like this for different modules.
>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:)
>>>> Failed to start module [storage-volume-flasharray] due to: [Error creating
>>>> bean with name
>>>> 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0'
>>>> defined in URL
>>>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]:
>>>> Cannot resolve reference to bean 'DefaultConfigResources' while setting
>>>> bean property 'locations'; nested exception is
>>>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
>>>> named 'DefaultConfigResources' available]`
>>>> >>
>>>> >> How can I resolve?
>>>> >>
>>>> >> Thank you for any help.
>>>> >>
>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>> >>
>>>> >> ----
>>>> >> This is an automatically sent email for users@cloudstack.apache.org.
>>>> >> To unsubscribe, please send an email to:
>>>> users-unsubscribe@cloudstack.apache.org
>>>> >>
>>>> >
>>>>
>>>>
>>>
>>>
>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
it automatically redirects to http://10.23.23.21:8080/client
I tryed, same result 503
Tata Y.
> On Feb 12, 2025, at 2:22 PM, Wei ZHOU <us...@gmail.com> wrote:
>
> Can you try http://10.23.23.21:8080/client ?
>
>
>
> On Wednesday, February 12, 2025, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Hello Wei,
>>
>> Interestingly I got same errors:
>>
>> 1) I drop the databases cloud and cloud_usage
>> 2) stop the management server systemctl start cloudstack-management
>> 3) I run the command as follows, without the default keys
>>
>> cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
>>
>> 4) start the management server
>>
>> 5) cheking the logs
>> 6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
>>
>>
>> I Even reinstalled the management server.
>>
>>
>> management-server.log
>>
>> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>
>> management-server.err
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>
>>
>> management-server.out
>> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>> Caused by: java.net <http://java.net/>.ConnectException: Connection refused
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>> at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>> at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>> ... 25 more
>>
>> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
>>
>> any tips are welcome.
>>
>> Thank you
>>
>> Tata Y.
>>
>>> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi,
>>>
>>> The error logs can be ignored. The java version is good.
>>>
>>> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>>>
>>> You can get more logs in /var/log/cloudstack/management/management-server.log
>>>
>>>
>>> Kind regards,
>>> Wei
>>>
>>>
>>> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>> Hello Wei
>>>>
>>>> Additionally, I have the management error:
>>>>
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>>>
>>>> I am using the JAVA 17
>>>> openjdk version "17.0.13" 2024-10-15
>>>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>>>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>>>
>>>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>>>
>>>> thank you
>>>>
>>>> Tata Y
>>>>
>>>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hello Wei,
>>>>>
>>>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>>>
>>>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>>>
>>>>>
>>>>>
>>>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>>>
>>>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>>>
>>>>>
>>>>>
>>>>> I did created the Databases and provided the grants as the manual states.
>>>>>
>>>>>
>>>>>
>>>>> -- Create the cloud and cloud_usage databases
>>>>> CREATE DATABASE `cloud`;
>>>>> CREATE DATABASE `cloud_usage`;
>>>>>
>>>>> -- Create the cloud user
>>>>> CREATE USER cloud@`localhost` identified by '<password>';
>>>>> CREATE USER cloud@`%` identified by '<password>';
>>>>>
>>>>> -- Grant all privileges to the cloud user on the databases
>>>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>>>
>>>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>>>
>>>>> -- Grant process list privilege for all other databases
>>>>> GRANT process ON *.* TO cloud@`localhost`;
>>>>> GRANT process ON *.* TO cloud@`%`;
>>>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>>>
>>>>>
>>>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>>>
>>>>> Tata Y.
>>>>>
>>>>>
>>>>>
>>>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I think there might be an issue with the command you executed.
>>>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>>>
>>>>>> normally I use a command like
>>>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>>>
>>>>>>
>>>>>> -Wei
>>>>>>
>>>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> Please help, as I am lost,
>>>>>>>
>>>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>>
>>>>>>> db server 10.23.23.23 cluster
>>>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>>>> the database contains the tables.
>>>>>>>
>>>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>>>> OS Ubuntu 22.04.5
>>>>>>>
>>>>>>>
>>>>>>> And I still got the 503 error.
>>>>>>>
>>>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>>>
>>>>>>> shows only this reapeated times.
>>>>>>>
>>>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>>>> ... 25 more
>>>>>>>
>>>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>>>
>>>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>>>> >
>>>>>>> > Is a fresh Install
>>>>>>> >
>>>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>>>> >
>>>>>>> > My DB is in a separate server,
>>>>>>> >
>>>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>>>> >
>>>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>>> > Mysql user name:cloud [ OK ]
>>>>>>> > Mysql user password:****** [ OK ]
>>>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>>>> > Mysql server port:3306 [ OK ]
>>>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>>>> > Checking Cloud database files ... [ OK ]
>>>>>>> > Checking local machine hostname ... [ OK ]
>>>>>>> > Checking SELinux setup ... [ OK ]
>>>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>>>> > Processing encryption ... [ OK ]
>>>>>>> > Finalizing setup ... [ OK ]
>>>>>>> >
>>>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>>>> >
>>>>>>> > All firewalls are down for now.
>>>>>>> >
>>>>>>> >
>>>>>>> > my tail log is very simple:
>>>>>>> >
>>>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>>>> >
>>>>>>> > Tata Y.
>>>>>>> >
>>>>>>> >
>>>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>>>> >>
>>>>>>> >> Hello team,
>>>>>>> >>
>>>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>>>> >>
>>>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>>>> >>
>>>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>>>> >>
>>>>>>> >> Java version:
>>>>>>> >> ```
>>>>>>> >> openjdk 11.0.19 2023-04-18
>>>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>>>> >> ```
>>>>>>> >> MySql version:
>>>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>>>> >>
>>>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>>>> >>
>>>>>>> >> and the grants
>>>>>>> >> ```
>>>>>>> >> mysql> show grants;
>>>>>>> >> +----------------------------------------------------------------+
>>>>>>> >> | Grants for cloud@localhost |
>>>>>>> >> +----------------------------------------------------------------+
>>>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>>>> >> +----------------------------------------------------------------+
>>>>>>> >> ```
>>>>>>> >> This is part of my db.properties
>>>>>>> >> ```
>>>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>>>> >> # in which the management server is running
>>>>>>> >> cluster.node.IP=127.0.0.1
>>>>>>> >> cluster.servlet.port=9090
>>>>>>> >> region.id <http://region.id/>=1
>>>>>>> >>
>>>>>>> >> # CloudStack database settings
>>>>>>> >> db.cloud.username=cloud
>>>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>>>> >> db.cloud.host=localhost
>>>>>>> >> db.cloud.driver=jdbc:mysql
>>>>>>> >> db.cloud.port=3306
>>>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>>>> >> ```
>>>>>>> >>
>>>>>>> >> And this is output of command for service status
>>>>>>> >> ```
>>>>>>> >> systemctl status cloudstack-management
>>>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>>>> >> Main PID: 5358 (java)
>>>>>>> >> ```
>>>>>>> >> which shows some errors (i guess) in the second part
>>>>>>> >> ```
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>>>> >> ```
>>>>>>> >>
>>>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>>>> >>
>>>>>>> >> Netstat output
>>>>>>> >> ```
>>>>>>> >> netstat -tulpn | grep 8080
>>>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>>>> >> ```
>>>>>>> >>
>>>>>>> >> You can find attached my log
>>>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>>>> >>
>>>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>>>> >> ```
>>>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>>>> >> ```
>>>>>>> >>
>>>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>>>> >>
>>>>>>> >> How can I resolve?
>>>>>>> >>
>>>>>>> >> Thank you for any help.
>>>>>>> >>
>>>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>>>> >>
>>>>>>> >> ----
>>>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>>>> >>
>>>>>>> >
>>>>>>>
>>>>>
>>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
Can you try http://10.23.23.21:8080/client ?
On Wednesday, February 12, 2025, Chi vediamo <ta...@gmail.com> wrote:
> Hello Wei,
>
> Interestingly I got same errors:
>
> 1) I drop the databases cloud and cloud_usage
> 2) stop the management server systemctl start cloudstack-management
> 3) I run the command as follows, without the default keys
>
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --deploy-as=root:somepass
> -m iknow -k somekey -i 10.23.23.21 -r 1
>
> 4) start the management server
>
> 5) cheking the logs
> 6) Still getting 503 http://10.23.23.21:8080 same for the
> http://10.23.23.22:8080 <http://10.23.23.21:8080>
>
>
>
> I Even reinstalled the management server.
>
>
>
> management-server.log
>
>
> 2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
> Server configuration file found: /etc/cloudstack/management/
> server.properties
>
> 2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
> (main:[]) (logid:) Encryption Type: null
>
> 2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
> Initializing server daemon on null, with http.enable=true, http.port=8080,
> https.enable=true, https.port=8443, context.path=/client
>
> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:[]) (logid:) Loading module context [bootstrap] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/
> spring-bootstrap-context.xml]
>
> 2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:[]) (logid:) Loading module context [bootstrap] from URL
> [jar:file:/usr/share/cloudstack-management/lib/
> cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/
> spring-bootstrap-context-inheritable.xml]
>
> 2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
> (main:[]) (logid:) Encryption Type: file
>
>
> management-server.err
>
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>
> SLF4J: Defaulting to no-operation (NOP) logger implementation
>
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
>
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>
> SLF4J: Defaulting to no-operation (NOP) logger implementation
>
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
>
>
>
> management-server.out
>
> 2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560)
> caught exception and will continue: java.io.IOException: Unable to create
> socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>
> at org.apache.logging.log4j.core.net.TcpSocketManager$
> TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>
> at org.apache.logging.log4j.core.net.TcpSocketManager$
> TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>
> at org.apache.logging.log4j.core.net.TcpSocketManager$
> TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>
> at org.apache.logging.log4j.core.appender.AbstractManager.
> getManager(AbstractManager.java:144)
>
> at org.apache.logging.log4j.core.appender.OutputStreamManager.
> getManager(OutputStreamManager.java:100)
>
> at org.apache.logging.log4j.core.net.TcpSocketManager.
> getSocketManager(TcpSocketManager.java:202)
>
> at org.apache.logging.log4j.core.appender.SocketAppender.
> createSocketManager(SocketAppender.java:497)
>
> at org.apache.logging.log4j.core.appender.SyslogAppender$
> Builder.build(SyslogAppender.java:151)
>
> at org.apache.logging.log4j.core.appender.SyslogAppender$
> Builder.build(SyslogAppender.java:50)
>
> at org.apache.logging.log4j.core.config.plugins.util.
> PluginBuilder.build(PluginBuilder.java:124)
>
> at org.apache.logging.log4j.core.config.AbstractConfiguration.
> createPluginObject(AbstractConfiguration.java:1138)
>
> at org.apache.logging.log4j.core.config.AbstractConfiguration.
> createConfiguration(AbstractConfiguration.java:1063)
>
> at org.apache.logging.log4j.core.config.AbstractConfiguration.
> createConfiguration(AbstractConfiguration.java:1055)
>
> at org.apache.logging.log4j.core.config.AbstractConfiguration.
> doConfigure(AbstractConfiguration.java:664)
>
> at org.apache.logging.log4j.core.config.AbstractConfiguration.
> initialize(AbstractConfiguration.java:258)
>
> at org.apache.logging.log4j.core.config.AbstractConfiguration.
> start(AbstractConfiguration.java:304)
>
> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(
> LoggerContext.java:621)
>
> at org.apache.logging.log4j.core.LoggerContext.reconfigure(
> LoggerContext.java:694)
>
> at org.apache.logging.log4j.core.LoggerContext.reconfigure(
> LoggerContext.java:711)
>
> at org.apache.logging.log4j.core.LoggerContext.start(
> LoggerContext.java:253)
>
> at org.apache.logging.log4j.core.impl.Log4jContextFactory.
> getContext(Log4jContextFactory.java:155)
>
> at org.apache.logging.log4j.core.impl.Log4jContextFactory.
> getContext(Log4jContextFactory.java:47)
>
> at org.apache.logging.log4j.LogManager.getContext(
> LogManager.java:196)
>
> at org.apache.logging.log4j.LogManager.getLogger(
> LogManager.java:599)
>
> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>
> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>
> Caused by: java.net.ConnectException: Connection refused
>
> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
> Method)
>
> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.
> connect(Net.java:579)
>
> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.
> connect(Net.java:568)
>
> at java.base/sun.nio.ch.NioSocketImpl.connect(
> NioSocketImpl.java:593)
>
> at java.base/java.net.SocksSocketImpl.connect(
> SocksSocketImpl.java:327)
>
> at java.base/java.net.Socket.connect(Socket.java:633)
>
> at org.apache.logging.log4j.core.net.TcpSocketManager.
> createSocket(TcpSocketManager.java:409)
>
> at org.apache.logging.log4j.core.net.TcpSocketManager$
> TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>
> ... 25 more
>
>
> 2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter
> that matches element properties
>
>
> any tips are welcome.
>
>
> Thank you
>
>
> Tata Y.
>
> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi,
>
> The error logs can be ignored. The java version is good.
>
> Can you run the command (with deploy-as) to set up cloudstack databases,
> and then restart cloudstack-management service ?
>
> You can get more logs in /var/log/cloudstack/management/management-server.
> log
>
>
> Kind regards,
> Wei
>
>
> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <ta...@gmail.com> wrote:
>
>> Hello Wei
>>
>> Additionally, I have the management error:
>>
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>> further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>> further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
>> further details.
>>
>> I am using the JAVA 17
>> openjdk version "17.0.13" 2024-10-15
>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed
>> mode, sharing)
>>
>> The management server is just a minimal server with syslog and the
>> management 4.20 installation.
>>
>> thank you
>>
>> Tata Y
>>
>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <ta...@gmail.com> wrote:
>>
>> Hello Wei,
>>
>> I use the manual page https://docs.cloudstack.apache.org/en/latest/
>> installguide/management-server/index.html#install-the-database-server
>>
>> and about 3/4 of the web page you sill find this instructions to do not
>> have to pass thw root password on it
>>
>>
>>
>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>
>>
>> - In dbpassword, specify the password to be assigned to the cloud
>> user. You can choose to provide no password.
>> - In deploy-as, specify the username and password of the user
>> deploying the database. In the following command, it is assumed the root
>> user is deploying the database and creating the cloud user.
>> -
>>
>> (Optional) There is an option to bypass the creating of the
>> databases, user and granting permissions to the user. This is useful if you
>> don’t want to expose your root credentials but still want the database to
>> be prepared for first start up. These skipped steps will have had to be
>> done manually prior to executing this script.
>>
>> *This behaviour can be invoked by passing the –schema-only flag*.
>> This flag conflicts with the –deploy-as flag so the two cannot be used
>> together. To set up the databases and user manually before executing the
>> script with the flag, these commands can be executed:
>>
>>
>> I did created the Databases and provided the grants as the manual
>> states.
>>
>>
>> -- Create the cloud and cloud_usage databasesCREATE DATABASE `cloud`;CREATE DATABASE `cloud_usage`;
>> -- Create the cloud userCREATE USER cloud@`localhost` identified by '<password>';CREATE USER cloud@`%` identified by '<password>';
>> -- Grant all privileges to the cloud user on the databasesGRANT ALL ON cloud.* to cloud@`localhost`;GRANT ALL ON cloud.* to cloud@`%`;
>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;GRANT ALL ON cloud_usage.* to cloud@`%`;
>> -- Grant process list privilege for all other databasesGRANT process ON *.* TO cloud@`localhost`;GRANT process ON *.* TO cloud@`%`;
>>
>> - (Optional) For encryption_type, use file or web to indicate the
>> technique used to pass in the database encryption password. Default: file.
>> See About Password and Key Encryption
>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>> .
>> - (Optional) For management_server_key, substitute the default key
>> that is used to encrypt confidential parameters in the CloudStack
>> properties file. Default: password. It is highly recommended that you
>> replace this with a more secure value. See About Password and Key
>> Encryption
>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>> .
>> - (Optional) For database_key, substitute the default key that is
>> used to encrypt confidential parameters in the CloudStack database.
>> Default: password. It is highly recommended that you replace this with a
>> more secure value. See About Password and Key Encryption
>> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
>> .
>>
>>
>>
>> I got the When this script is finished, you should see a message like
>> “Successfully initialized the database.”
>>
>> Tata Y.
>>
>>
>>
>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> Hi,
>>
>> I think there might be an issue with the command you executed.
>> maybe refer to "cloudstack-setup-databases -h" for help
>>
>> normally I use a command like
>> cloudstack-setup-databases alex:founder@1.2.3.4
>> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>
>>
>> -Wei
>>
>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <ta...@gmail.com> wrote:
>>
>>> Please help, as I am lost,
>>>
>>> I read everything i can find about, even reinstalling, I create the DB
>>> and installed with the command shown below:
>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only
>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>>
>>> db server 10.23.23.23 cluster
>>> management server 10.23.23.21 and secondary 10.23.23.22
>>> the database contains the tables.
>>>
>>> No connection errors to the DB. Mysql 8.0.40
>>> OS Ubuntu 22.04.5
>>>
>>>
>>> And I still got the 503 error.
>>>
>>> I don't see any table with data, but the tables were populated, and
>>> again there are no errors on the Mysql server side.
>>>
>>>
>>>
>>> the management server /var/log/cloudstack/management/management-server.
>>> out
>>>
>>> shows only this reapeated times.
>>>
>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560)
>>> caught exception and will continue: java.io.IOException: Unable to create
>>> socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$
>>> TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$
>>> TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$
>>> TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>> at org.apache.logging.log4j.core.appender.AbstractManager.
>>> getManager(AbstractManager.java:144)
>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.
>>> getManager(OutputStreamManager.java:100)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager.
>>> getSocketManager(TcpSocketManager.java:202)
>>> at org.apache.logging.log4j.core.appender.SocketAppender.
>>> createSocketManager(SocketAppender.java:497)
>>> at org.apache.logging.log4j.core.appender.SyslogAppender$
>>> Builder.build(SyslogAppender.java:151)
>>> at org.apache.logging.log4j.core.appender.SyslogAppender$
>>> Builder.build(SyslogAppender.java:50)
>>> at org.apache.logging.log4j.core.config.plugins.util.
>>> PluginBuilder.build(PluginBuilder.java:124)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.
>>> createPluginObject(AbstractConfiguration.java:1138)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.
>>> createConfiguration(AbstractConfiguration.java:1063)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.
>>> createConfiguration(AbstractConfiguration.java:1055)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.
>>> doConfigure(AbstractConfiguration.java:664)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.
>>> initialize(AbstractConfiguration.java:258)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.
>>> start(AbstractConfiguration.java:304)
>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(
>>> LoggerContext.java:621)
>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(
>>> LoggerContext.java:694)
>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(
>>> LoggerContext.java:711)
>>> at org.apache.logging.log4j.core.LoggerContext.start(
>>> LoggerContext.java:253)
>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.
>>> getContext(Log4jContextFactory.java:155)
>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.
>>> getContext(Log4jContextFactory.java:47)
>>> at org.apache.logging.log4j.LogManager.getContext(
>>> LogManager.java:196)
>>> at org.apache.logging.log4j.LogManager.getLogger(
>>> LogManager.java:599)
>>> at org.apache.cloudstack.ServerDaemon.<init>(
>>> ServerDaemon.java:65)
>>> at org.apache.cloudstack.ServerDaemon.main(
>>> ServerDaemon.java:110)
>>> Caused by: java.net.ConnectException: Connection refused
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>>> Method)
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.
>>> connect(Net.java:579)
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.
>>> connect(Net.java:568)
>>> at java.base/sun.nio.ch.NioSocketImpl.connect(
>>> NioSocketImpl.java:593)
>>> at java.base/java.net.SocksSocketImpl.connect(
>>> SocksSocketImpl.java:327)
>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager.
>>> createSocket(TcpSocketManager.java:409)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$
>>> TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>> ... 25 more
>>>
>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter
>>> that matches element properties
>>>
>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com> wrote:
>>> >
>>> > Is a fresh Install
>>> >
>>> > I have the same issue with 4.20, with Mysql 8.0
>>> >
>>> > My DB is in a separate server,
>>> >
>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is
>>> missing !!
>>> >
>>> >
>>> >
>>> > I follow the basic install with a separate DB. which completed as
>>> successful.
>>> >
>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only
>>> -m iknow -k somekey -i 10.23.23.21 -r 1
>>> > Mysql user name:cloud
>>> [ OK ]
>>> > Mysql user password:******
>>> [ OK ]
>>> > Mysql server ip:10.23.23.23
>>> [ OK ]
>>> > Mysql server port:3306
>>> [ OK ]
>>> > Using specified cluster management server node IP 10.23.23.21
>>> [ OK ]
>>> > Checking Cloud database files ...
>>> [ OK ]
>>> > Checking local machine hostname ...
>>> [ OK ]
>>> > Checking SELinux setup ...
>>> [ OK ]
>>> > Preparing /etc/cloudstack/management/db.properties
>>> [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql
>>> [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql
>>> [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql
>>> [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/templates.sql
>>> [ OK ]
>>> > Processing encryption ...
>>> [ OK ]
>>> > Finalizing setup ...
>>> [ OK ]
>>> >
>>> > CloudStack has successfully initialized database, you can check your
>>> database configuration in /etc/cloudstack/management/db.properties
>>> >
>>> > All firewalls are down for now.
>>> >
>>> >
>>> > my tail log is very simple:
>>> >
>>> > tail -f /var/log/cloudstack/management/management-server.log
>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>> (main:[]) (logid:) Encryption Type: file
>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>> Server configuration file found: /etc/cloudstack/management/
>>> server.properties
>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>> (main:[]) (logid:) Encryption Type: null
>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>>> Initializing server daemon on null, with http.enable=true, http.port=8080,
>>> https.enable=true, https.port=8443, context.path=/client
>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
>>> (main:[]) (logid:) Loading module context [bootstrap] from URL
>>> [jar:file:/usr/share/cloudstack-management/lib/
>>> cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/
>>> spring-bootstrap-context.xml]
>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
>>> (main:[]) (logid:) Loading module context [bootstrap] from URL
>>> [jar:file:/usr/share/cloudstack-management/lib/
>>> cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/
>>> spring-bootstrap-context-inheritable.xml]
>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>>> (main:[]) (logid:) Encryption Type: file
>>> >
>>> > Tata Y.
>>> >
>>> >
>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org>
>>> wrote:
>>> >>
>>> >>
>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI
>>> after installation
>>> >>
>>> >> Hello team,
>>> >>
>>> >> I've took interest in CloudStack a few days ago and tried to install
>>> it. I've got success but now I have a problem accessing the client UI in my
>>> browser.
>>> >>
>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is
>>> 4.20.0.0. I've followed the steps at https://docs.cloudstack.
>>> apache.org/en/4.20.0.0/installguide/management-server/index.html
>>> >>
>>> >> Type of installation is single node management server with nfs and db
>>> on same host.
>>> >>
>>> >> Java version:
>>> >> ```
>>> >> openjdk 11.0.19 2023-04-18
>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-
>>> 0ubuntu118.04.1)
>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1,
>>> mixed mode, sharing)
>>> >> ```
>>> >> MySql version:
>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine
>>> wrapper`
>>> >>
>>> >> Database is configure and I have all grants for cloud user. I can
>>> access the database at localhost with no problem with command
>>> >> `mysql -u cloud -p cloud -h localhost`
>>> >>
>>> >> and the grants
>>> >> ```
>>> >> mysql> show grants;
>>> >> +----------------------------------------------------------------+
>>> >> | Grants for cloud@localhost |
>>> >> +----------------------------------------------------------------+
>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>> >> +----------------------------------------------------------------+
>>> >> ```
>>> >> This is part of my db.properties
>>> >> ```
>>> >> # management server clustering parameters, change cluster.node.IP to
>>> the machine IP address
>>> >> # in which the management server is running
>>> >> cluster.node.IP=127.0.0.1
>>> >> cluster.servlet.port=9090
>>> >> region.id=1
>>> >>
>>> >> # CloudStack database settings
>>> >> db.cloud.username=cloud
>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>> >> db.cloud.host=localhost
>>> >> db.cloud.driver=jdbc:mysql
>>> >> db.cloud.port=3306
>>> >> db.cloud.name=cloud
>>> >> ```
>>> >>
>>> >> And this is output of command for service status
>>> >> ```
>>> >> systemctl status cloudstack-management
>>> >> cloudstack-management.service - CloudStack Management Server
>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
>>> enabled; vendor preset: enabled)
>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min
>>> ago
>>> >> Main PID: 5358 (java)
>>> >> ```
>>> >> which shows some errors (i guess) in the second part
>>> >> ```
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.
>>> handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.
>>> component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.
>>> component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.
>>> Server.start(Server.java:423)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.
>>> component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.
>>> handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.
>>> Server.doStart(Server.java:387)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.
>>> component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.
>>> ServerDaemon.start(ServerDaemon.java:199)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.
>>> ServerDaemon.main(ServerDaemon.java:112)
>>> >> ```
>>> >>
>>> >> As of now I cannot access the http://localhost:8080/client/ address
>>> as it shows http 503.
>>> >>
>>> >> Netstat output
>>> >> ```
>>> >> netstat -tulpn | grep 8080
>>> >> tcp6 0 0 :::8080 :::*
>>> LISTEN 5358/java
>>> >> ```
>>> >>
>>> >> You can find attached my log
>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>> >>
>>> >> There is a single sql exception about creating a table that already
>>> exists.
>>> >> ```
>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker]
>>> (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException:
>>> Table 'nsx_providers' already exists
>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker]
>>> (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException:
>>> Unable to execute upgrade script
>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers'
>>> already exists
>>> >> ```
>>> >>
>>> >> But relevant part of log seems linked to Bean Definition. There are
>>> many errors (under DEBUG/WARN) like this for different modules.
>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:)
>>> Failed to start module [storage-volume-flasharray] due to: [Error creating
>>> bean with name 'org.springframework.beans.factory.config.
>>> PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/
>>> cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-
>>> INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]:
>>> Cannot resolve reference to bean 'DefaultConfigResources' while setting
>>> bean property 'locations'; nested exception is org.springframework.beans.
>>> factory.NoSuchBeanDefinitionException: No bean named
>>> 'DefaultConfigResources' available]`
>>> >>
>>> >> How can I resolve?
>>> >>
>>> >> Thank you for any help.
>>> >>
>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>> >>
>>> >> ----
>>> >> This is an automatically sent email for users@cloudstack.apache.org.
>>> >> To unsubscribe, please send an email to:
>>> users-unsubscribe@cloudstack.apache.org
>>> >>
>>> >
>>>
>>>
>>
>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
Interestingly I got same errors:
1) I drop the databases cloud and cloud_usage
2) stop the management server systemctl start cloudstack-management
3) I run the command as follows, without the default keys
cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
4) start the management server
5) cheking the logs
6) Still getting 503 http://10.23.23.21:8080 <http://10.23.23.21:8080/> same for the http://10.23.23.22:8080 <http://10.23.23.21:8080/>
I Even reinstalled the management server.
management-server.log
2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
management-server.err
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
management-server.out
2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io <http://java.io/>.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
Caused by: java.net <http://java.net/>.ConnectException: Connection refused
at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net <http://java.net/>.Socket.connect(Socket.java:633)
at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager.createSocket(TcpSocketManager.java:409)
at org.apache.logging.log4j.core.net <http://apache.logging.log4j.core.net/>.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
... 25 more
2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
any tips are welcome.
Thank you
Tata Y.
> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi,
>
> The error logs can be ignored. The java version is good.
>
> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>
> You can get more logs in /var/log/cloudstack/management/management-server.log
>
>
> Kind regards,
> Wei
>
>
> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Hello Wei
>>
>> Additionally, I have the management error:
>>
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>
>> I am using the JAVA 17
>> openjdk version "17.0.13" 2024-10-15
>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>
>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>
>> thank you
>>
>> Tata Y
>>
>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hello Wei,
>>>
>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>
>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>
>>>
>>>
>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>
>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>
>>>
>>>
>>> I did created the Databases and provided the grants as the manual states.
>>>
>>>
>>>
>>> -- Create the cloud and cloud_usage databases
>>> CREATE DATABASE `cloud`;
>>> CREATE DATABASE `cloud_usage`;
>>>
>>> -- Create the cloud user
>>> CREATE USER cloud@`localhost` identified by '<password>';
>>> CREATE USER cloud@`%` identified by '<password>';
>>>
>>> -- Grant all privileges to the cloud user on the databases
>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>
>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>
>>> -- Grant process list privilege for all other databases
>>> GRANT process ON *.* TO cloud@`localhost`;
>>> GRANT process ON *.* TO cloud@`%`;
>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>
>>>
>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>
>>> Tata Y.
>>>
>>>
>>>
>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I think there might be an issue with the command you executed.
>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>
>>>> normally I use a command like
>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>
>>>>
>>>> -Wei
>>>>
>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> Please help, as I am lost,
>>>>>
>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> db server 10.23.23.23 cluster
>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>> the database contains the tables.
>>>>>
>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>> OS Ubuntu 22.04.5
>>>>>
>>>>>
>>>>> And I still got the 503 error.
>>>>>
>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>
>>>>>
>>>>>
>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>
>>>>> shows only this reapeated times.
>>>>>
>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>
>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> >
>>>>> > Is a fresh Install
>>>>> >
>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>> >
>>>>> > My DB is in a separate server,
>>>>> >
>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>> >
>>>>> >
>>>>> >
>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>> >
>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>> > Mysql user name:cloud [ OK ]
>>>>> > Mysql user password:****** [ OK ]
>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>> > Mysql server port:3306 [ OK ]
>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>> > Checking Cloud database files ... [ OK ]
>>>>> > Checking local machine hostname ... [ OK ]
>>>>> > Checking SELinux setup ... [ OK ]
>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>> > Processing encryption ... [ OK ]
>>>>> > Finalizing setup ... [ OK ]
>>>>> >
>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>> >
>>>>> > All firewalls are down for now.
>>>>> >
>>>>> >
>>>>> > my tail log is very simple:
>>>>> >
>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>> >
>>>>> > Tata Y.
>>>>> >
>>>>> >
>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>> >>
>>>>> >>
>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>> >>
>>>>> >> Hello team,
>>>>> >>
>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>> >>
>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>> >>
>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>> >>
>>>>> >> Java version:
>>>>> >> ```
>>>>> >> openjdk 11.0.19 2023-04-18
>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>> >> ```
>>>>> >> MySql version:
>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>> >>
>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>> >>
>>>>> >> and the grants
>>>>> >> ```
>>>>> >> mysql> show grants;
>>>>> >> +----------------------------------------------------------------+
>>>>> >> | Grants for cloud@localhost |
>>>>> >> +----------------------------------------------------------------+
>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>> >> +----------------------------------------------------------------+
>>>>> >> ```
>>>>> >> This is part of my db.properties
>>>>> >> ```
>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>> >> # in which the management server is running
>>>>> >> cluster.node.IP=127.0.0.1
>>>>> >> cluster.servlet.port=9090
>>>>> >> region.id <http://region.id/>=1
>>>>> >>
>>>>> >> # CloudStack database settings
>>>>> >> db.cloud.username=cloud
>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>> >> db.cloud.host=localhost
>>>>> >> db.cloud.driver=jdbc:mysql
>>>>> >> db.cloud.port=3306
>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>> >> ```
>>>>> >>
>>>>> >> And this is output of command for service status
>>>>> >> ```
>>>>> >> systemctl status cloudstack-management
>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>> >> Main PID: 5358 (java)
>>>>> >> ```
>>>>> >> which shows some errors (i guess) in the second part
>>>>> >> ```
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>> >> ```
>>>>> >>
>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>> >>
>>>>> >> Netstat output
>>>>> >> ```
>>>>> >> netstat -tulpn | grep 8080
>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>> >> ```
>>>>> >>
>>>>> >> You can find attached my log
>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>> >>
>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>> >> ```
>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>> >> ```
>>>>> >>
>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>> >>
>>>>> >> How can I resolve?
>>>>> >>
>>>>> >> Thank you for any help.
>>>>> >>
>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>> >>
>>>>> >> ----
>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>> >>
>>>>> >
>>>>>
>>>
>>
Still 503 Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
Interestingly I got same errors:
1) I drop the databases cloud and cloud_usage
2) stop the management server systemctl start cloudstack-management
3) I run the command as follows, without the default keys
cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --deploy-as=root:somepass -m iknow -k somekey -i 10.23.23.21 -r 1
4) start the management server
5) cheking the logs
management-server.log
2025-02-12 10:25:17,901 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
2025-02-12 10:25:17,911 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
2025-02-12 10:25:17,914 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
2025-02-12 10:25:27,017 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
2025-02-12 10:25:27,099 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
management-server.err
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
management-server.out
2025-02-12 10:25:17,775 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
Caused by: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:579)
at java.base/sun.nio.ch.Net.connect(Net.java:568)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:593)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
... 25 more
2025-02-12 10:25:17,792 main ERROR appenders Appenders has no parameter that matches element properties
any tips are welcome.
Thank you
Tata Y.
> On Feb 12, 2025, at 2:31 AM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi,
>
> The error logs can be ignored. The java version is good.
>
> Can you run the command (with deploy-as) to set up cloudstack databases, and then restart cloudstack-management service ?
>
> You can get more logs in /var/log/cloudstack/management/management-server.log
>
>
> Kind regards,
> Wei
>
>
> On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Hello Wei
>>
>> Additionally, I have the management error:
>>
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
>>
>> I am using the JAVA 17
>> openjdk version "17.0.13" 2024-10-15
>> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
>> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
>>
>> The management server is just a minimal server with syslog and the management 4.20 installation.
>>
>> thank you
>>
>> Tata Y
>>
>>> On Feb 11, 2025, at 3:55 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hello Wei,
>>>
>>> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>>>
>>> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>>>
>>>
>>>
>>> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>>> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
>>> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
>>> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>>>
>>> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>>>
>>>
>>>
>>> I did created the Databases and provided the grants as the manual states.
>>>
>>>
>>>
>>> -- Create the cloud and cloud_usage databases
>>> CREATE DATABASE `cloud`;
>>> CREATE DATABASE `cloud_usage`;
>>>
>>> -- Create the cloud user
>>> CREATE USER cloud@`localhost` identified by '<password>';
>>> CREATE USER cloud@`%` identified by '<password>';
>>>
>>> -- Grant all privileges to the cloud user on the databases
>>> GRANT ALL ON cloud.* to cloud@`localhost`;
>>> GRANT ALL ON cloud.* to cloud@`%`;
>>>
>>> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
>>> GRANT ALL ON cloud_usage.* to cloud@`%`;
>>>
>>> -- Grant process list privilege for all other databases
>>> GRANT process ON *.* TO cloud@`localhost`;
>>> GRANT process ON *.* TO cloud@`%`;
>>> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>>>
>>>
>>> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>>>
>>> Tata Y.
>>>
>>>
>>>
>>>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <ustcweizhou@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I think there might be an issue with the command you executed.
>>>> maybe refer to "cloudstack-setup-databases -h" for help
>>>>
>>>> normally I use a command like
>>>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>>>
>>>>
>>>> -Wei
>>>>
>>>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> Please help, as I am lost,
>>>>>
>>>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>>
>>>>> db server 10.23.23.23 cluster
>>>>> management server 10.23.23.21 and secondary 10.23.23.22
>>>>> the database contains the tables.
>>>>>
>>>>> No connection errors to the DB. Mysql 8.0.40
>>>>> OS Ubuntu 22.04.5
>>>>>
>>>>>
>>>>> And I still got the 503 error.
>>>>>
>>>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>>>
>>>>>
>>>>>
>>>>> the management server /var/log/cloudstack/management/management-server.out
>>>>>
>>>>> shows only this reapeated times.
>>>>>
>>>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>>>> Caused by: java.net.ConnectException: Connection refused
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>>>> ... 25 more
>>>>>
>>>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>>>
>>>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>>>> >
>>>>> > Is a fresh Install
>>>>> >
>>>>> > I have the same issue with 4.20, with Mysql 8.0
>>>>> >
>>>>> > My DB is in a separate server,
>>>>> >
>>>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>>>> >
>>>>> >
>>>>> >
>>>>> > I follow the basic install with a separate DB. which completed as successful.
>>>>> >
>>>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>>> > Mysql user name:cloud [ OK ]
>>>>> > Mysql user password:****** [ OK ]
>>>>> > Mysql server ip:10.23.23.23 [ OK ]
>>>>> > Mysql server port:3306 [ OK ]
>>>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>>>> > Checking Cloud database files ... [ OK ]
>>>>> > Checking local machine hostname ... [ OK ]
>>>>> > Checking SELinux setup ... [ OK ]
>>>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>>>> > Processing encryption ... [ OK ]
>>>>> > Finalizing setup ... [ OK ]
>>>>> >
>>>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>>>> >
>>>>> > All firewalls are down for now.
>>>>> >
>>>>> >
>>>>> > my tail log is very simple:
>>>>> >
>>>>> > tail -f /var/log/cloudstack/management/management-server.log
>>>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>>>> >
>>>>> > Tata Y.
>>>>> >
>>>>> >
>>>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>>>> >>
>>>>> >>
>>>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>>>> >>
>>>>> >> Hello team,
>>>>> >>
>>>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>>>> >>
>>>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>>>> >>
>>>>> >> Type of installation is single node management server with nfs and db on same host.
>>>>> >>
>>>>> >> Java version:
>>>>> >> ```
>>>>> >> openjdk 11.0.19 2023-04-18
>>>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>>>> >> ```
>>>>> >> MySql version:
>>>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>>>> >>
>>>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>>>> >> `mysql -u cloud -p cloud -h localhost`
>>>>> >>
>>>>> >> and the grants
>>>>> >> ```
>>>>> >> mysql> show grants;
>>>>> >> +----------------------------------------------------------------+
>>>>> >> | Grants for cloud@localhost |
>>>>> >> +----------------------------------------------------------------+
>>>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>>>> >> +----------------------------------------------------------------+
>>>>> >> ```
>>>>> >> This is part of my db.properties
>>>>> >> ```
>>>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>>>> >> # in which the management server is running
>>>>> >> cluster.node.IP=127.0.0.1
>>>>> >> cluster.servlet.port=9090
>>>>> >> region.id <http://region.id/>=1
>>>>> >>
>>>>> >> # CloudStack database settings
>>>>> >> db.cloud.username=cloud
>>>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>>>> >> db.cloud.host=localhost
>>>>> >> db.cloud.driver=jdbc:mysql
>>>>> >> db.cloud.port=3306
>>>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>>>> >> ```
>>>>> >>
>>>>> >> And this is output of command for service status
>>>>> >> ```
>>>>> >> systemctl status cloudstack-management
>>>>> >> cloudstack-management.service - CloudStack Management Server
>>>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>>>> >> Main PID: 5358 (java)
>>>>> >> ```
>>>>> >> which shows some errors (i guess) in the second part
>>>>> >> ```
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>>>> >> ```
>>>>> >>
>>>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>>>> >>
>>>>> >> Netstat output
>>>>> >> ```
>>>>> >> netstat -tulpn | grep 8080
>>>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>>>> >> ```
>>>>> >>
>>>>> >> You can find attached my log
>>>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>>>> >>
>>>>> >> There is a single sql exception about creating a table that already exists.
>>>>> >> ```
>>>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>>>> >> ```
>>>>> >>
>>>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>>>> >>
>>>>> >> How can I resolve?
>>>>> >>
>>>>> >> Thank you for any help.
>>>>> >>
>>>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>>>> >>
>>>>> >> ----
>>>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>>>> >>
>>>>> >
>>>>>
>>>
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
Hi,
The error logs can be ignored. The java version is good.
Can you run the command (with deploy-as) to set up cloudstack databases,
and then restart cloudstack-management service ?
You can get more logs
in /var/log/cloudstack/management/management-server.log
Kind regards,
Wei
On Tue, Feb 11, 2025 at 11:11 PM Chi vediamo <ta...@gmail.com> wrote:
> Hello Wei
>
> Additionally, I have the management error:
>
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
>
> I am using the JAVA 17
> openjdk version "17.0.13" 2024-10-15
> OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
> OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed
> mode, sharing)
>
> The management server is just a minimal server with syslog and the
> management 4.20 installation.
>
> thank you
>
> Tata Y
>
> On Feb 11, 2025, at 3:55 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> I use the manual page
> https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>
> and about 3/4 of the web page you sill find this instructions to do not
> have to pass thw root password on it
>
>
>
> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
>
>
> - In dbpassword, specify the password to be assigned to the cloud
> user. You can choose to provide no password.
> - In deploy-as, specify the username and password of the user
> deploying the database. In the following command, it is assumed the root
> user is deploying the database and creating the cloud user.
> -
>
> (Optional) There is an option to bypass the creating of the databases,
> user and granting permissions to the user. This is useful if you don’t want
> to expose your root credentials but still want the database to be prepared
> for first start up. These skipped steps will have had to be done manually
> prior to executing this script.
>
> *This behaviour can be invoked by passing the –schema-only flag*.
> This flag conflicts with the –deploy-as flag so the two cannot be used
> together. To set up the databases and user manually before executing the
> script with the flag, these commands can be executed:
>
>
> I did created the Databases and provided the grants as the manual
> states.
>
>
> -- Create the cloud and cloud_usage databasesCREATE DATABASE `cloud`;CREATE DATABASE `cloud_usage`;
> -- Create the cloud userCREATE USER cloud@`localhost` identified by '<password>';CREATE USER cloud@`%` identified by '<password>';
> -- Grant all privileges to the cloud user on the databasesGRANT ALL ON cloud.* to cloud@`localhost`;GRANT ALL ON cloud.* to cloud@`%`;
> GRANT ALL ON cloud_usage.* to cloud@`localhost`;GRANT ALL ON cloud_usage.* to cloud@`%`;
> -- Grant process list privilege for all other databasesGRANT process ON *.* TO cloud@`localhost`;GRANT process ON *.* TO cloud@`%`;
>
> - (Optional) For encryption_type, use file or web to indicate the
> technique used to pass in the database encryption password. Default: file.
> See About Password and Key Encryption
> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
> .
> - (Optional) For management_server_key, substitute the default key
> that is used to encrypt confidential parameters in the CloudStack
> properties file. Default: password. It is highly recommended that you
> replace this with a more secure value. See About Password and Key
> Encryption
> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
> .
> - (Optional) For database_key, substitute the default key that is used
> to encrypt confidential parameters in the CloudStack database. Default:
> password. It is highly recommended that you replace this with a more secure
> value. See About Password and Key Encryption
> <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>
> .
>
>
>
> I got the When this script is finished, you should see a message like
> “Successfully initialized the database.”
>
> Tata Y.
>
>
>
> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi,
>
> I think there might be an issue with the command you executed.
> maybe refer to "cloudstack-setup-databases -h" for help
>
> normally I use a command like
> cloudstack-setup-databases alex:founder@1.2.3.4 --deploy-as=root:nonsense
> -e file -m password -k dbpassword -i 10.20.30.40
>
>
> -Wei
>
> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <ta...@gmail.com> wrote:
>
>> Please help, as I am lost,
>>
>> I read everything i can find about, even reinstalling, I create the DB
>> and installed with the command shown below:
>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m
>> iknow -k somekey -i 10.23.23.21 -r 1
>>
>> db server 10.23.23.23 cluster
>> management server 10.23.23.21 and secondary 10.23.23.22
>> the database contains the tables.
>>
>> No connection errors to the DB. Mysql 8.0.40
>> OS Ubuntu 22.04.5
>>
>>
>> And I still got the 503 error.
>>
>> I don't see any table with data, but the tables were populated, and again
>> there are no errors on the Mysql server side.
>>
>>
>>
>> the management server /var/log/cloudstack/management/management-server.out
>>
>> shows only this reapeated times.
>>
>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560)
>> caught exception and will continue: java.io.IOException: Unable to create
>> socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>> at
>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>> at
>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>> at
>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>> at
>> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>> at
>> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>> at
>> org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>> at
>> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>> at
>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>> at
>> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>> at
>> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>> at
>> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>> at
>> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>> at
>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>> at
>> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>> at
>> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>> at
>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>> at
>> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>> at
>> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>> at
>> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>> Caused by: java.net.ConnectException: Connection refused
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native
>> Method)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>> .connect(Net.java:579)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>
>> .connect(Net.java:568)
>> at java.base/sun.nio.ch
>> .NioSocketImpl.connect(NioSocketImpl.java:593)
>> at java.base/java.net
>> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
>> at java.base/java.net.Socket.connect(Socket.java:633)
>> at
>> org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>> at
>> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>> ... 25 more
>>
>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter
>> that matches element properties
>>
>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com> wrote:
>> >
>> > Is a fresh Install
>> >
>> > I have the same issue with 4.20, with Mysql 8.0
>> >
>> > My DB is in a separate server,
>> >
>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is
>> missing !!
>> >
>> >
>> >
>> > I follow the basic install with a separate DB. which completed as
>> successful.
>> >
>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m
>> iknow -k somekey -i 10.23.23.21 -r 1
>> > Mysql user name:cloud
>> [ OK ]
>> > Mysql user password:******
>> [ OK ]
>> > Mysql server ip:10.23.23.23
>> [ OK ]
>> > Mysql server port:3306
>> [ OK ]
>> > Using specified cluster management server node IP 10.23.23.21
>> [ OK ]
>> > Checking Cloud database files ...
>> [ OK ]
>> > Checking local machine hostname ...
>> [ OK ]
>> > Checking SELinux setup ...
>> [ OK ]
>> > Preparing /etc/cloudstack/management/db.properties
>> [ OK ]
>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql
>> [ OK ]
>> > Applying
>> /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK
>> ]
>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql
>> [ OK ]
>> > Applying /usr/share/cloudstack-management/setup/templates.sql
>> [ OK ]
>> > Processing encryption ...
>> [ OK ]
>> > Finalizing setup ...
>> [ OK ]
>> >
>> > CloudStack has successfully initialized database, you can check your
>> database configuration in /etc/cloudstack/management/db.properties
>> >
>> > All firewalls are down for now.
>> >
>> >
>> > my tail log is very simple:
>> >
>> > tail -f /var/log/cloudstack/management/management-server.log
>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>> (main:[]) (logid:) Encryption Type: file
>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>> Server configuration file found:
>> /etc/cloudstack/management/server.properties
>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>> (main:[]) (logid:) Encryption Type: null
>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
>> Initializing server daemon on null, with http.enable=true, http.port=8080,
>> https.enable=true, https.port=8443, context.path=/client
>> > 2025-02-10 23:41:33,784 INFO
>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>> module context [bootstrap] from URL
>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>> > 2025-02-10 23:41:33,784 INFO
>> [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading
>> module context [bootstrap] from URL
>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
>> (main:[]) (logid:) Encryption Type: file
>> >
>> > Tata Y.
>> >
>> >
>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org>
>> wrote:
>> >>
>> >>
>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI
>> after installation
>> >>
>> >> Hello team,
>> >>
>> >> I've took interest in CloudStack a few days ago and tried to install
>> it. I've got success but now I have a problem accessing the client UI in my
>> browser.
>> >>
>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is
>> 4.20.0.0. I've followed the steps at
>> https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>> >>
>> >> Type of installation is single node management server with nfs and db
>> on same host.
>> >>
>> >> Java version:
>> >> ```
>> >> openjdk 11.0.19 2023-04-18
>> >> OpenJDK Runtime Environment (build
>> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1,
>> mixed mode, sharing)
>> >> ```
>> >> MySql version:
>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine
>> wrapper`
>> >>
>> >> Database is configure and I have all grants for cloud user. I can
>> access the database at localhost with no problem with command
>> >> `mysql -u cloud -p cloud -h localhost`
>> >>
>> >> and the grants
>> >> ```
>> >> mysql> show grants;
>> >> +----------------------------------------------------------------+
>> >> | Grants for cloud@localhost |
>> >> +----------------------------------------------------------------+
>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>> >> +----------------------------------------------------------------+
>> >> ```
>> >> This is part of my db.properties
>> >> ```
>> >> # management server clustering parameters, change cluster.node.IP to
>> the machine IP address
>> >> # in which the management server is running
>> >> cluster.node.IP=127.0.0.1
>> >> cluster.servlet.port=9090
>> >> region.id=1
>> >>
>> >> # CloudStack database settings
>> >> db.cloud.username=cloud
>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>> >> db.cloud.host=localhost
>> >> db.cloud.driver=jdbc:mysql
>> >> db.cloud.port=3306
>> >> db.cloud.name=cloud
>> >> ```
>> >>
>> >> And this is output of command for service status
>> >> ```
>> >> systemctl status cloudstack-management
>> >> cloudstack-management.service - CloudStack Management Server
>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
>> enabled; vendor preset: enabled)
>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>> >> Main PID: 5358 (java)
>> >> ```
>> >> which shows some errors (i guess) in the second part
>> >> ```
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.server.Server.start(Server.java:423)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.server.Server.doStart(Server.java:387)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>> >> gen 26 13:20:21 mypc java[5358]: at
>> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>> >> ```
>> >>
>> >> As of now I cannot access the http://localhost:8080/client/ address
>> as it shows http 503.
>> >>
>> >> Netstat output
>> >> ```
>> >> netstat -tulpn | grep 8080
>> >> tcp6 0 0 :::8080 :::*
>> LISTEN 5358/java
>> >> ```
>> >>
>> >> You can find attached my log
>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>> >>
>> >> There is a single sql exception about creating a table that already
>> exists.
>> >> ```
>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[])
>> (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException:
>> Table 'nsx_providers' already exists
>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[])
>> (logid:) Unable to upgrade the database
>> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
>> script
>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers'
>> already exists
>> >> ```
>> >>
>> >> But relevant part of log seems linked to Bean Definition. There are
>> many errors (under DEBUG/WARN) like this for different modules.
>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed
>> to start module [storage-volume-flasharray] due to: [Error creating bean
>> with name
>> 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0'
>> defined in URL
>> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]:
>> Cannot resolve reference to bean 'DefaultConfigResources' while setting
>> bean property 'locations'; nested exception is
>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
>> named 'DefaultConfigResources' available]`
>> >>
>> >> How can I resolve?
>> >>
>> >> Thank you for any help.
>> >>
>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>> >>
>> >> ----
>> >> This is an automatically sent email for users@cloudstack.apache.org.
>> >> To unsubscribe, please send an email to:
>> users-unsubscribe@cloudstack.apache.org
>> >>
>> >
>>
>>
>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei
Additionally, I have the management error:
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
I am using the JAVA 17
openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment (build 17.0.13+11-Ubuntu-2ubuntu122.04)
OpenJDK 64-Bit Server VM (build 17.0.13+11-Ubuntu-2ubuntu122.04, mixed mode, sharing)
The management server is just a minimal server with syslog and the management 4.20 installation.
thank you
Tata Y
> On Feb 11, 2025, at 3:55 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Hello Wei,
>
> I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
>
> and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
>
>
>
> cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
> In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
> In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
> (Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
>
> This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
>
>
>
> I did created the Databases and provided the grants as the manual states.
>
>
>
> -- Create the cloud and cloud_usage databases
> CREATE DATABASE `cloud`;
> CREATE DATABASE `cloud_usage`;
>
> -- Create the cloud user
> CREATE USER cloud@`localhost` identified by '<password>';
> CREATE USER cloud@`%` identified by '<password>';
>
> -- Grant all privileges to the cloud user on the databases
> GRANT ALL ON cloud.* to cloud@`localhost`;
> GRANT ALL ON cloud.* to cloud@`%`;
>
> GRANT ALL ON cloud_usage.* to cloud@`localhost`;
> GRANT ALL ON cloud_usage.* to cloud@`%`;
>
> -- Grant process list privilege for all other databases
> GRANT process ON *.* TO cloud@`localhost`;
> GRANT process ON *.* TO cloud@`%`;
> (Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
> (Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
> (Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
>
>
> I got the When this script is finished, you should see a message like “Successfully initialized the database.”
>
> Tata Y.
>
>
>
>> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>>
>> Hi,
>>
>> I think there might be an issue with the command you executed.
>> maybe refer to "cloudstack-setup-databases -h" for help
>>
>> normally I use a command like
>> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>>
>>
>> -Wei
>>
>> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>> Please help, as I am lost,
>>>
>>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>>
>>> db server 10.23.23.23 cluster
>>> management server 10.23.23.21 and secondary 10.23.23.22
>>> the database contains the tables.
>>>
>>> No connection errors to the DB. Mysql 8.0.40
>>> OS Ubuntu 22.04.5
>>>
>>>
>>> And I still got the 503 error.
>>>
>>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>>
>>>
>>>
>>> the management server /var/log/cloudstack/management/management-server.out
>>>
>>> shows only this reapeated times.
>>>
>>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>>> Caused by: java.net.ConnectException: Connection refused
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>>> at java.base/java.net.Socket.connect(Socket.java:633)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>>> ... 25 more
>>>
>>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>>
>>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>>> >
>>> > Is a fresh Install
>>> >
>>> > I have the same issue with 4.20, with Mysql 8.0
>>> >
>>> > My DB is in a separate server,
>>> >
>>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>>> >
>>> >
>>> >
>>> > I follow the basic install with a separate DB. which completed as successful.
>>> >
>>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>> > Mysql user name:cloud [ OK ]
>>> > Mysql user password:****** [ OK ]
>>> > Mysql server ip:10.23.23.23 [ OK ]
>>> > Mysql server port:3306 [ OK ]
>>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>>> > Checking Cloud database files ... [ OK ]
>>> > Checking local machine hostname ... [ OK ]
>>> > Checking SELinux setup ... [ OK ]
>>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>>> > Processing encryption ... [ OK ]
>>> > Finalizing setup ... [ OK ]
>>> >
>>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>>> >
>>> > All firewalls are down for now.
>>> >
>>> >
>>> > my tail log is very simple:
>>> >
>>> > tail -f /var/log/cloudstack/management/management-server.log
>>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>>> >
>>> > Tata Y.
>>> >
>>> >
>>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>>> >>
>>> >>
>>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>> >>
>>> >> Hello team,
>>> >>
>>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>> >>
>>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>> >>
>>> >> Type of installation is single node management server with nfs and db on same host.
>>> >>
>>> >> Java version:
>>> >> ```
>>> >> openjdk 11.0.19 2023-04-18
>>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>>> >> ```
>>> >> MySql version:
>>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>> >>
>>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>>> >> `mysql -u cloud -p cloud -h localhost`
>>> >>
>>> >> and the grants
>>> >> ```
>>> >> mysql> show grants;
>>> >> +----------------------------------------------------------------+
>>> >> | Grants for cloud@localhost |
>>> >> +----------------------------------------------------------------+
>>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>>> >> +----------------------------------------------------------------+
>>> >> ```
>>> >> This is part of my db.properties
>>> >> ```
>>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>>> >> # in which the management server is running
>>> >> cluster.node.IP=127.0.0.1
>>> >> cluster.servlet.port=9090
>>> >> region.id <http://region.id/>=1
>>> >>
>>> >> # CloudStack database settings
>>> >> db.cloud.username=cloud
>>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>>> >> db.cloud.host=localhost
>>> >> db.cloud.driver=jdbc:mysql
>>> >> db.cloud.port=3306
>>> >> db.cloud.name <http://db.cloud.name/>=cloud
>>> >> ```
>>> >>
>>> >> And this is output of command for service status
>>> >> ```
>>> >> systemctl status cloudstack-management
>>> >> cloudstack-management.service - CloudStack Management Server
>>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>>> >> Main PID: 5358 (java)
>>> >> ```
>>> >> which shows some errors (i guess) in the second part
>>> >> ```
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>>> >> ```
>>> >>
>>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>> >>
>>> >> Netstat output
>>> >> ```
>>> >> netstat -tulpn | grep 8080
>>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>>> >> ```
>>> >>
>>> >> You can find attached my log
>>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>> >>
>>> >> There is a single sql exception about creating a table that already exists.
>>> >> ```
>>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>>> >> ```
>>> >>
>>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>> >>
>>> >> How can I resolve?
>>> >>
>>> >> Thank you for any help.
>>> >>
>>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>> >>
>>> >> ----
>>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>>> >>
>>> >
>>>
>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Hello Wei,
I use the manual page https://docs.cloudstack.apache.org/en/latest/installguide/management-server/index.html#install-the-database-server
and about 3/4 of the web page you sill find this instructions to do not have to pass thw root password on it
cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> [ --deploy-as=root:<password> | --schema-only ]-e <encryption_type> -m <management_server_key> -k <database_key> -i <management_server_ip>
In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password.
In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user.
(Optional) There is an option to bypass the creating of the databases, user and granting permissions to the user. This is useful if you don’t want to expose your root credentials but still want the database to be prepared for first start up. These skipped steps will have had to be done manually prior to executing this script.
This behaviour can be invoked by passing the –schema-only flag. This flag conflicts with the –deploy-as flag so the two cannot be used together. To set up the databases and user manually before executing the script with the flag, these commands can be executed:
I did created the Databases and provided the grants as the manual states.
-- Create the cloud and cloud_usage databases
CREATE DATABASE `cloud`;
CREATE DATABASE `cloud_usage`;
-- Create the cloud user
CREATE USER cloud@`localhost` identified by '<password>';
CREATE USER cloud@`%` identified by '<password>';
-- Grant all privileges to the cloud user on the databases
GRANT ALL ON cloud.* to cloud@`localhost`;
GRANT ALL ON cloud.* to cloud@`%`;
GRANT ALL ON cloud_usage.* to cloud@`localhost`;
GRANT ALL ON cloud_usage.* to cloud@`%`;
-- Grant process list privilege for all other databases
GRANT process ON *.* TO cloud@`localhost`;
GRANT process ON *.* TO cloud@`%`;
(Optional) For encryption_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
(Optional) For management_server_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
(Optional) For database_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption <https://docs.cloudstack.apache.org/en/latest/installguide/encryption.html#about-password-key-encryption>.
I got the When this script is finished, you should see a message like “Successfully initialized the database.”
Tata Y.
> On Feb 11, 2025, at 2:56 PM, Wei ZHOU <us...@gmail.com> wrote:
>
> Hi,
>
> I think there might be an issue with the command you executed.
> maybe refer to "cloudstack-setup-databases -h" for help
>
> normally I use a command like
> cloudstack-setup-databases alex:founder@1.2.3.4 <ma...@1.2.3.4> --deploy-as=root:nonsense -e file -m password -k dbpassword -i 10.20.30.40
>
>
> -Wei
>
> On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> Please help, as I am lost,
>>
>> I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>>
>> db server 10.23.23.23 cluster
>> management server 10.23.23.21 and secondary 10.23.23.22
>> the database contains the tables.
>>
>> No connection errors to the DB. Mysql 8.0.40
>> OS Ubuntu 22.04.5
>>
>>
>> And I still got the 503 error.
>>
>> I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
>>
>>
>>
>> the management server /var/log/cloudstack/management/management-server.out
>>
>> shows only this reapeated times.
>>
>> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
>> at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
>> at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
>> at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
>> at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
>> at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
>> at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
>> at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
>> at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
>> at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
>> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
>> at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
>> at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
>> at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
>> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
>> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
>> Caused by: java.net.ConnectException: Connection refused
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect0(Native Method)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:579)
>> at java.base/sun.nio.ch.Net <http://sun.nio.ch.net/>.connect(Net.java:568)
>> at java.base/sun.nio.ch <http://sun.nio.ch/>.NioSocketImpl.connect(NioSocketImpl.java:593)
>> at java.base/java.net <http://java.net/>.SocksSocketImpl.connect(SocksSocketImpl.java:327)
>> at java.base/java.net.Socket.connect(Socket.java:633)
>> at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
>> at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
>> ... 25 more
>>
>> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
>>
>> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <tatay188@gmail.com <ma...@gmail.com>> wrote:
>> >
>> > Is a fresh Install
>> >
>> > I have the same issue with 4.20, with Mysql 8.0
>> >
>> > My DB is in a separate server,
>> >
>> > I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>> >
>> >
>> >
>> > I follow the basic install with a separate DB. which completed as successful.
>> >
>> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 <ma...@10.23.23.23> --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
>> > Mysql user name:cloud [ OK ]
>> > Mysql user password:****** [ OK ]
>> > Mysql server ip:10.23.23.23 [ OK ]
>> > Mysql server port:3306 [ OK ]
>> > Using specified cluster management server node IP 10.23.23.21 [ OK ]
>> > Checking Cloud database files ... [ OK ]
>> > Checking local machine hostname ... [ OK ]
>> > Checking SELinux setup ... [ OK ]
>> > Preparing /etc/cloudstack/management/db.properties [ OK ]
>> > Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
>> > Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
>> > Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
>> > Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
>> > Processing encryption ... [ OK ]
>> > Finalizing setup ... [ OK ]
>> >
>> > CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>> >
>> > All firewalls are down for now.
>> >
>> >
>> > my tail log is very simple:
>> >
>> > tail -f /var/log/cloudstack/management/management-server.log
>> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
>> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
>> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
>> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
>> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>> >
>> > Tata Y.
>> >
>> >
>> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <git@apache.org <ma...@apache.org>> wrote:
>> >>
>> >>
>> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>> >>
>> >> Hello team,
>> >>
>> >> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>> >>
>> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>> >>
>> >> Type of installation is single node management server with nfs and db on same host.
>> >>
>> >> Java version:
>> >> ```
>> >> openjdk 11.0.19 2023-04-18
>> >> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>> >> ```
>> >> MySql version:
>> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>> >>
>> >> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>> >> `mysql -u cloud -p cloud -h localhost`
>> >>
>> >> and the grants
>> >> ```
>> >> mysql> show grants;
>> >> +----------------------------------------------------------------+
>> >> | Grants for cloud@localhost |
>> >> +----------------------------------------------------------------+
>> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>> >> +----------------------------------------------------------------+
>> >> ```
>> >> This is part of my db.properties
>> >> ```
>> >> # management server clustering parameters, change cluster.node.IP to the machine IP address
>> >> # in which the management server is running
>> >> cluster.node.IP=127.0.0.1
>> >> cluster.servlet.port=9090
>> >> region.id <http://region.id/>=1
>> >>
>> >> # CloudStack database settings
>> >> db.cloud.username=cloud
>> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>> >> db.cloud.host=localhost
>> >> db.cloud.driver=jdbc:mysql
>> >> db.cloud.port=3306
>> >> db.cloud.name <http://db.cloud.name/>=cloud
>> >> ```
>> >>
>> >> And this is output of command for service status
>> >> ```
>> >> systemctl status cloudstack-management
>> >> cloudstack-management.service - CloudStack Management Server
>> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>> >> Main PID: 5358 (java)
>> >> ```
>> >> which shows some errors (i guess) in the second part
>> >> ```
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>> >> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>> >> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>> >> ```
>> >>
>> >> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>> >>
>> >> Netstat output
>> >> ```
>> >> netstat -tulpn | grep 8080
>> >> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>> >> ```
>> >>
>> >> You can find attached my log
>> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>> >>
>> >> There is a single sql exception about creating a table that already exists.
>> >> ```
>> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>> >> ```
>> >>
>> >> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>> >>
>> >> How can I resolve?
>> >>
>> >> Thank you for any help.
>> >>
>> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>> >>
>> >> ----
>> >> This is an automatically sent email for users@cloudstack.apache.org <ma...@cloudstack.apache.org>.
>> >> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org <ma...@cloudstack.apache.org>
>> >>
>> >
>>
Re: Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Wei ZHOU <us...@gmail.com>.
Hi,
I think there might be an issue with the command you executed.
maybe refer to "cloudstack-setup-databases -h" for help
normally I use a command like
cloudstack-setup-databases alex:founder@1.2.3.4 --deploy-as=root:nonsense
-e file -m password -k dbpassword -i 10.20.30.40
-Wei
On Tue, Feb 11, 2025 at 5:15 PM Chi vediamo <ta...@gmail.com> wrote:
> Please help, as I am lost,
>
> I read everything i can find about, even reinstalling, I create the DB and
> installed with the command shown below:
> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m
> iknow -k somekey -i 10.23.23.21 -r 1
>
> db server 10.23.23.23 cluster
> management server 10.23.23.21 and secondary 10.23.23.22
> the database contains the tables.
>
> No connection errors to the DB. Mysql 8.0.40
> OS Ubuntu 22.04.5
>
>
> And I still got the 503 error.
>
> I don't see any table with data, but the tables were populated, and again
> there are no errors on the Mysql server side.
>
>
>
> the management server /var/log/cloudstack/management/management-server.out
>
> shows only this reapeated times.
>
> 2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560)
> caught exception and will continue: java.io.IOException: Unable to create
> socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
> at
> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
> at
> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
> at
> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
> at
> org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
> at
> org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
> at
> org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
> at
> org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
> at
> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
> at
> org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
> at
> org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
> at
> org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
> at
> org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
> at
> org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
> at
> org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
> at
> org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
> at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
> at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
> Caused by: java.net.ConnectException: Connection refused
> at java.base/sun.nio.ch.Net.connect0(Native Method)
> at java.base/sun.nio.ch.Net.connect(Net.java:579)
> at java.base/sun.nio.ch.Net.connect(Net.java:568)
> at java.base/sun.nio.ch
> .NioSocketImpl.connect(NioSocketImpl.java:593)
> at java.base/java.net
> .SocksSocketImpl.connect(SocksSocketImpl.java:327)
> at java.base/java.net.Socket.connect(Socket.java:633)
> at
> org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
> at
> org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
> ... 25 more
>
> 2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter
> that matches element properties
>
> > On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com> wrote:
> >
> > Is a fresh Install
> >
> > I have the same issue with 4.20, with Mysql 8.0
> >
> > My DB is in a separate server,
> >
> > I try to find the "spring-bootstrap-context-inheritable.xml" which is
> missing !!
> >
> >
> >
> > I follow the basic install with a separate DB. which completed as
> successful.
> >
> > cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m
> iknow -k somekey -i 10.23.23.21 -r 1
> > Mysql user name:cloud
> [ OK ]
> > Mysql user password:******
> [ OK ]
> > Mysql server ip:10.23.23.23
> [ OK ]
> > Mysql server port:3306
> [ OK ]
> > Using specified cluster management server node IP 10.23.23.21
> [ OK ]
> > Checking Cloud database files ...
> [ OK ]
> > Checking local machine hostname ...
> [ OK ]
> > Checking SELinux setup ...
> [ OK ]
> > Preparing /etc/cloudstack/management/db.properties
> [ OK ]
> > Applying /usr/share/cloudstack-management/setup/create-schema.sql
> [ OK ]
> > Applying
> /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK
> ]
> > Applying /usr/share/cloudstack-management/setup/server-setup.sql
> [ OK ]
> > Applying /usr/share/cloudstack-management/setup/templates.sql
> [ OK ]
> > Processing encryption ...
> [ OK ]
> > Finalizing setup ...
> [ OK ]
> >
> > CloudStack has successfully initialized database, you can check your
> database configuration in /etc/cloudstack/management/db.properties
> >
> > All firewalls are down for now.
> >
> >
> > my tail log is very simple:
> >
> > tail -f /var/log/cloudstack/management/management-server.log
> > 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
> (main:[]) (logid:) Encryption Type: file
> > 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
> Server configuration file found:
> /etc/cloudstack/management/server.properties
> > 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
> (main:[]) (logid:) Encryption Type: null
> > 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:)
> Initializing server daemon on null, with http.enable=true, http.port=8080,
> https.enable=true, https.port=8443, context.path=/client
> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:[]) (logid:) Loading module context [bootstrap] from URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
> > 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
> (main:[]) (logid:) Loading module context [bootstrap] from URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
> > 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
> (main:[]) (logid:) Encryption Type: file
> >
> > Tata Y.
> >
> >
> >> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org>
> wrote:
> >>
> >>
> >> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI
> after installation
> >>
> >> Hello team,
> >>
> >> I've took interest in CloudStack a few days ago and tried to install
> it. I've got success but now I have a problem accessing the client UI in my
> browser.
> >>
> >> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is
> 4.20.0.0. I've followed the steps at
> https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
> >>
> >> Type of installation is single node management server with nfs and db
> on same host.
> >>
> >> Java version:
> >> ```
> >> openjdk 11.0.19 2023-04-18
> >> OpenJDK Runtime Environment (build
> 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
> >> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1,
> mixed mode, sharing)
> >> ```
> >> MySql version:
> >> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine
> wrapper`
> >>
> >> Database is configure and I have all grants for cloud user. I can
> access the database at localhost with no problem with command
> >> `mysql -u cloud -p cloud -h localhost`
> >>
> >> and the grants
> >> ```
> >> mysql> show grants;
> >> +----------------------------------------------------------------+
> >> | Grants for cloud@localhost |
> >> +----------------------------------------------------------------+
> >> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
> >> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
> >> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
> >> +----------------------------------------------------------------+
> >> ```
> >> This is part of my db.properties
> >> ```
> >> # management server clustering parameters, change cluster.node.IP to
> the machine IP address
> >> # in which the management server is running
> >> cluster.node.IP=127.0.0.1
> >> cluster.servlet.port=9090
> >> region.id=1
> >>
> >> # CloudStack database settings
> >> db.cloud.username=cloud
> >> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
> >> db.cloud.host=localhost
> >> db.cloud.driver=jdbc:mysql
> >> db.cloud.port=3306
> >> db.cloud.name=cloud
> >> ```
> >>
> >> And this is output of command for service status
> >> ```
> >> systemctl status cloudstack-management
> >> cloudstack-management.service - CloudStack Management Server
> >> Loaded: loaded (/lib/systemd/system/cloudstack-management.service;
> enabled; vendor preset: enabled)
> >> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
> >> Main PID: 5358 (java)
> >> ```
> >> which shows some errors (i guess) in the second part
> >> ```
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.server.Server.start(Server.java:423)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.server.Server.doStart(Server.java:387)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
> >> gen 26 13:20:21 mypc java[5358]: at
> org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
> >> ```
> >>
> >> As of now I cannot access the http://localhost:8080/client/ address as
> it shows http 503.
> >>
> >> Netstat output
> >> ```
> >> netstat -tulpn | grep 8080
> >> tcp6 0 0 :::8080 :::*
> LISTEN 5358/java
> >> ```
> >>
> >> You can find attached my log
> >> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
> >>
> >> There is a single sql exception about creating a table that already
> exists.
> >> ```
> >> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[])
> (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException:
> Table 'nsx_providers' already exists
> >> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[])
> (logid:) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade
> script
> >> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers'
> already exists
> >> ```
> >>
> >> But relevant part of log seems linked to Bean Definition. There are
> many errors (under DEBUG/WARN) like this for different modules.
> >> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed
> to start module [storage-volume-flasharray] due to: [Error creating bean
> with name
> 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0'
> defined in URL
> [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]:
> Cannot resolve reference to bean 'DefaultConfigResources' while setting
> bean property 'locations'; nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean
> named 'DefaultConfigResources' available]`
> >>
> >> How can I resolve?
> >>
> >> Thank you for any help.
> >>
> >> GitHub link: https://github.com/apache/cloudstack/discussions/10276
> >>
> >> ----
> >> This is an automatically sent email for users@cloudstack.apache.org.
> >> To unsubscribe, please send an email to:
> users-unsubscribe@cloudstack.apache.org
> >>
> >
>
>
Please help. port 4560 ! Re: I have the same Issue 4.20 Re: [D] Error accessing Cloudstack UI after installation [cloudstack]
Posted by Chi vediamo <ta...@gmail.com>.
Please help, as I am lost,
I read everything i can find about, even reinstalling, I create the DB and installed with the command shown below:
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
db server 10.23.23.23 cluster
management server 10.23.23.21 and secondary 10.23.23.22
the database contains the tables.
No connection errors to the DB. Mysql 8.0.40
OS Ubuntu 22.04.5
And I still got the 503 error.
I don't see any table with data, but the tables were populated, and again there are no errors on the Mysql server side.
the management server /var/log/cloudstack/management/management-server.out
shows only this reapeated times.
2025-02-11 15:48:54,030 main ERROR TcpSocketManager (TCP:localhost:4560) caught exception and will continue: java.io.IOException: Unable to create socket for localhost at port 4560 using ip address 127.0.0.1 and port 4560
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:509)
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:478)
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createManager(TcpSocketManager.java:459)
at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:144)
at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100)
at org.apache.logging.log4j.core.net.TcpSocketManager.getSocketManager(TcpSocketManager.java:202)
at org.apache.logging.log4j.core.appender.SocketAppender.createSocketManager(SocketAppender.java:497)
at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:151)
at org.apache.logging.log4j.core.appender.SyslogAppender$Builder.build(SyslogAppender.java:50)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:124)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1138)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1063)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1055)
at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:664)
at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:258)
at org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:304)
at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:621)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:694)
at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:711)
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:253)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:155)
at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:47)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:196)
at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:599)
at org.apache.cloudstack.ServerDaemon.<init>(ServerDaemon.java:65)
at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:110)
Caused by: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:579)
at java.base/sun.nio.ch.Net.connect(Net.java:568)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:593)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at org.apache.logging.log4j.core.net.TcpSocketManager.createSocket(TcpSocketManager.java:409)
at org.apache.logging.log4j.core.net.TcpSocketManager$TcpSocketManagerFactory.createSocket(TcpSocketManager.java:504)
... 25 more
2025-02-11 15:48:54,042 main ERROR appenders Appenders has no parameter that matches element properties
> On Feb 10, 2025, at 7:06 PM, Chi vediamo <ta...@gmail.com> wrote:
>
> Is a fresh Install
>
> I have the same issue with 4.20, with Mysql 8.0
>
> My DB is in a separate server,
>
> I try to find the "spring-bootstrap-context-inheritable.xml" which is missing !!
>
>
>
> I follow the basic install with a separate DB. which completed as successful.
>
> cloudstack-setup-databases cloud:rootpass@10.23.23.23 --schema-only -m iknow -k somekey -i 10.23.23.21 -r 1
> Mysql user name:cloud [ OK ]
> Mysql user password:****** [ OK ]
> Mysql server ip:10.23.23.23 [ OK ]
> Mysql server port:3306 [ OK ]
> Using specified cluster management server node IP 10.23.23.21 [ OK ]
> Checking Cloud database files ... [ OK ]
> Checking local machine hostname ... [ OK ]
> Checking SELinux setup ... [ OK ]
> Preparing /etc/cloudstack/management/db.properties [ OK ]
> Applying /usr/share/cloudstack-management/setup/create-schema.sql [ OK ]
> Applying /usr/share/cloudstack-management/setup/create-schema-premium.sql [ OK ]
> Applying /usr/share/cloudstack-management/setup/server-setup.sql [ OK ]
> Applying /usr/share/cloudstack-management/setup/templates.sql [ OK ]
> Processing encryption ... [ OK ]
> Finalizing setup ... [ OK ]
>
> CloudStack has successfully initialized database, you can check your database configuration in /etc/cloudstack/management/db.properties
>
> All firewalls are down for now.
>
>
> my tail log is very simple:
>
> tail -f /var/log/cloudstack/management/management-server.log
> 2025-02-10 23:00:35,420 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
> 2025-02-10 23:41:24,440 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Server configuration file found: /etc/cloudstack/management/server.properties
> 2025-02-10 23:41:24,446 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: null
> 2025-02-10 23:41:24,449 INFO [o.a.c.ServerDaemon] (main:[]) (logid:) Initializing server daemon on null, with http.enable=true, http.port=8080, https.enable=true, https.port=8443, context.path=/client
> 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
> 2025-02-10 23:41:33,784 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Loading module context [bootstrap] from URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
> 2025-02-10 23:41:33,868 DEBUG [c.c.u.c.EncryptionSecretKeyChecker] (main:[]) (logid:) Encryption Type: file
>
> Tata Y.
>
>
>> On Jan 27, 2025, at 3:35 AM, ManuFe (via GitHub) <gi...@apache.org> wrote:
>>
>>
>> GitHub user ManuFe closed a discussion: Error accessing Cloudstack UI after installation
>>
>> Hello team,
>>
>> I've took interest in CloudStack a few days ago and tried to install it. I've got success but now I have a problem accessing the client UI in my browser.
>>
>> My system for test is Ubuntu 18.04.6 LTS and CloudStack Relase is 4.20.0.0. I've followed the steps at https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/management-server/index.html
>>
>> Type of installation is single node management server with nfs and db on same host.
>>
>> Java version:
>> ```
>> openjdk 11.0.19 2023-04-18
>> OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1)
>> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, mixed mode, sharing)
>> ```
>> MySql version:
>> `mysql Ver 14.14 Distrib 5.7.42, for Linux (x86_64) using EditLine wrapper`
>>
>> Database is configure and I have all grants for cloud user. I can access the database at localhost with no problem with command
>> `mysql -u cloud -p cloud -h localhost`
>>
>> and the grants
>> ```
>> mysql> show grants;
>> +----------------------------------------------------------------+
>> | Grants for cloud@localhost |
>> +----------------------------------------------------------------+
>> | GRANT PROCESS ON *.* TO 'cloud'@'localhost' |
>> | GRANT ALL PRIVILEGES ON `cloud`.* TO 'cloud'@'localhost' |
>> | GRANT ALL PRIVILEGES ON `cloud_usage`.* TO 'cloud'@'localhost' |
>> +----------------------------------------------------------------+
>> ```
>> This is part of my db.properties
>> ```
>> # management server clustering parameters, change cluster.node.IP to the machine IP address
>> # in which the management server is running
>> cluster.node.IP=127.0.0.1
>> cluster.servlet.port=9090
>> region.id=1
>>
>> # CloudStack database settings
>> db.cloud.username=cloud
>> db.cloud.password=ENC(nV8er4pYAlcF8Fw/UK56Z7AL9CYPkPIwyKP6IsHbhFLM)
>> db.cloud.host=localhost
>> db.cloud.driver=jdbc:mysql
>> db.cloud.port=3306
>> db.cloud.name=cloud
>> ```
>>
>> And this is output of command for service status
>> ```
>> systemctl status cloudstack-management
>> cloudstack-management.service - CloudStack Management Server
>> Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled; vendor preset: enabled)
>> Active: active (running) since Sun 2025-01-26 13:20:11 CET; 40min ago
>> Main PID: 5358 (java)
>> ```
>> which shows some errors (i guess) in the second part
>> ```
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.start(Server.java:423)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.server.Server.doStart(Server.java:387)
>> gen 26 13:20:21 mypc java[5358]: at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
>> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.start(ServerDaemon.java:199)
>> gen 26 13:20:21 mypc java[5358]: at org.apache.cloudstack.ServerDaemon.main(ServerDaemon.java:112)
>> ```
>>
>> As of now I cannot access the http://localhost:8080/client/ address as it shows http 503.
>>
>> Netstat output
>> ```
>> netstat -tulpn | grep 8080
>> tcp6 0 0 :::8080 :::* LISTEN 5358/java
>> ```
>>
>> You can find attached my log
>> [log.txt](https://github.com/user-attachments/files/18550118/log.txt)
>>
>> There is a single sql exception about creating a table that already exists.
>> ```
>> 2025-01-26 11:00:34,007 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to execute upgrade script java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>> 2025-01-26 11:00:34,008 ERROR [c.c.u.DatabaseUpgradeChecker] (main:[]) (logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: Unable to execute upgrade script
>> Caused by: java.sql.SQLSyntaxErrorException: Table 'nsx_providers' already exists
>> ```
>>
>> But relevant part of log seems linked to Bean Definition. There are many errors (under DEBUG/WARN) like this for different modules.
>> `[o.a.c.s.m.m.i.DefaultModuleDefinitionSet] (main:[]) (logid:) Failed to start module [storage-volume-flasharray] due to: [Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.20.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean property 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available]`
>>
>> How can I resolve?
>>
>> Thank you for any help.
>>
>> GitHub link: https://github.com/apache/cloudstack/discussions/10276
>>
>> ----
>> This is an automatically sent email for users@cloudstack.apache.org.
>> To unsubscribe, please send an email to: users-unsubscribe@cloudstack.apache.org
>>
>