Summary of problems encountered in server configuration of openfire

1.jdk,nginx,tomcat, database, have been installed and configured, services have been up, background login, has been reported that users do not exist, excluding network reasons (firewalls), and log writing failure (no manual creation of log directories on the new server), still not work, and later found that the database case-sensitive did not close.
character-set-server=utf8mb4 // Incidentally add database Emoji expression support
loose-default-character-set = utf8mb4
lower_case_table_names=1
max_connections=1000

After configuring the above items, restart the database, login in the background, and succeed.


2. After installing openfire successfully, you can login to the openfire background normally with the default configuration, but when you specify the connection address to the data used by the project, you always report the root password incorrectly. I thought that the password was the password specified in the process of installing openfire and specifying the external database. The password set here is correct indeed.
Best of all, after comparing all the data in the open fire database ofproperty table and the data in the ofproperty table after configuration on the server, we find that the database connection address specified after the attribute name is jdbcProvider.connection String, followed by the user name and password, both of which are R. Oot,

The password on the server is not root. Modify the value, restart openfire, enter the background, login successfully, and find that the user table has been successfully assigned to the project user table.


3. Commands used for openfire reinstallation:
[root@localhost logs]# service openfire stop 
Shutting down openfire:                                    [  OK  ]
[root@localhost logs]# Rpm-qa | grep openfire // View openfire installed on the server
openfire-4.1.3-1.x86_64
[root@localhost logs]# Rpm-ql | grep openfire // Details
rpm: no arguments given for query
[root@localhost logs]# Rpm-e openfire-4.1.3-1.x86_64//uninstall
Shutting down openfire: kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
warning: /opt/openfire/resources/security/keystore saved as /opt/openfire/resources/security/keystore.rpmsave
warning: /opt/openfire/conf/security.xml saved as /opt/openfire/conf/security.xml.rpmsave
warning: /opt/openfire/conf/openfire.xml saved as /opt/openfire/conf/openfire.xml.rpmsave
[root@localhost logs]# Rm-rfv/opt/openfire///Delete file directory
removed `/opt/openfire/logs/error.log'
removed `/opt/openfire/logs/debug.log'
removed `/opt/openfire/logs/info.log.1'
removed `/opt/openfire/logs/nohup.out'
removed `/opt/openfire/logs/all.log'
removed `/opt/openfire/logs/all.log.1'
removed `/opt/openfire/logs/info.log'
removed `/opt/openfire/logs/warn.log'
removed directory: `/opt/openfire/logs'
[root@localhost opt]# init 6//Server Restart
[root@localhost opt]# 
Connection closed by foreign host.
[root@localhost ~]# Rpm-ivh openfire-4.1.3-1.x86_64.rpm//installation
Preparing...                ########################################### [100%]
   1:openfire               ########################################### [100%]
mysql> create database openfire ;
Query OK, 1 row affected (0.00 sec)
mysql> source /data/crmoa_sql/openfire_init.sql // Create a database and execute initialization scripts
   
[root@localhost ~]# service openfire start // start the openfire service, openfire has been automatically registered as a system service after the installation is completed
Starting openfire: 

Tags: Database RPM xml MySQL

Posted on Wed, 17 Jul 2019 17:38:42 -0700 by digitallookout