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 <tatay...@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 <ustcweiz...@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 
>> <mailto:alex%3Afounder@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 <tatay...@gmail.com 
>> <mailto:tatay...@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 
>>> > <mailto:cloud%3Arootpass@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 <tatay...@gmail.com 
>>> > <mailto:tatay...@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 
>>> > <mailto:cloud%3Arootpass@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) <g...@apache.org 
>>> >> <mailto:g...@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 
>>> >> <mailto:users@cloudstack.apache.org>.
>>> >> To unsubscribe, please send an email to: 
>>> >> users-unsubscr...@cloudstack.apache.org 
>>> >> <mailto:users-unsubscr...@cloudstack.apache.org>
>>> >> 
>>> > 
>>> 
> 

Reply via email to