execute switch-controller diagnose-connection yoursn
If not ntp issue, it's DHCP issue.
How to fix:
Go to Wifi & Switch Controller -> Fortilink Interface -> enable DHCP and save
execute switch-controller diagnose-connection yoursn
If not ntp issue, it's DHCP issue.
How to fix:
Go to Wifi & Switch Controller -> Fortilink Interface -> enable DHCP and save
In angluar.json, please add the following line.
{
...,
"scripts":
[ "node_modules/echarts/dist/echarts.min.js",
...
],
...
}
| Generator | Description |
| increment | It generates identifiers of type long, short or int that are unique only when no other process is inserting data into the same table. It should not the used in the clustered environment. |
| identity | It supports identity columns in DB2, MySQL, MS SQL Server, Sybase and HypersonicSQL. The returned identifier is of type long, short or int. |
| sequence | The sequence generator uses a sequence in DB2, PostgreSQL, Oracle, SAP DB, McKoi or a generator in Interbase. The returned identifier is of type long, short or int |
| hilo | The hilo generator uses a hi/lo algorithm to efficiently generate identifiers of type long, short or int, given a table and column (by default hibernate_unique_key and next_hi respectively) as a source of hi values. The hi/lo algorithm generates identifiers that are unique only for a particular database. Do not use this generator with connections enlisted with JTA or with a user-supplied connection. |
| seqhilo | The seqhilo generator uses a hi/lo algorithm to efficiently generate identifiers of type long, short or int, given a named database sequence. |
| uuid | The uuid generator uses a 128-bit UUID algorithm to generate identifiers of type string, unique within a network (the IP address is used). The UUID is encoded as a string of hexadecimal digits of length 32. |
| guid | It uses a database-generated GUID string on MS SQL Server and MySQL. |
| native | It picks identity, sequence or hilo depending upon the capabilities of the underlying database. |
| assigned | lets the application to assign an identifier to the object before save() is called. This is the default strategy if no <generator> element is specified. |
| select | retrieves a primary key assigned by a database trigger by selecting the row by some unique key and retrieving the primary key value. |
| foreign | uses the identifier of another associated object. Usually used in conjunction with a <one-to-one> primary key association. |
ssh -i your_pem_file.pem ubuntu@your-instance-public-dns sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get remove --purge openjdk*
sudo apt-get install oracle-java-7-installer
java -version
wget -O openfire.tar.gz http://www.igniterealtime.org/downloads/download-landing.jsp?file=openfire/openfire_3_8_1.tar.gz
Change the version to the latest stable available. Then untar and move like so: tar -xzvf openfire.tar.gz
mv openfire/ /opt
/etc/hosts and add a line to let the server know what’s its name is. Hosts file should look like: 127.0.0.1 localhost
127.0.1.1 ubuntu
127.0.0.1 chat.yourdomain.com
/your_openfire_directory/bin and running ./openfire start/etc/hosts file a while ago./your_openfire_directory/plugins/hazelcast/classes/hazelcast-cache-config.xml. Find the <network> tag and we should configure it like so:...
<port auto-increment="true">5701</port>
<join>
<multicast enabled="false" />
<tcp-ip enabled="true">
<hostname>private-ip-address-of-this-machine:5701</hostname>
</tcp-ip>
<aws enabled="false"/>
</join>
<interfaces enabled="true">
<interface>private-ip-address-of-this-machine</interface>
</interfaces>
...
The private IP address of your machine can be found on your Amazon EC2 Console on the instance details under Private IPs./your_openfire_dir/bin and doing ./openfire stop and ./openfire start Visit your Openfire Admin Console and enable clustering. You should be able to join a cluster with one node running. Neat./your_openfire_directory/plugins/hazelcast/classes/hazelcast-cache-config.xml. The config should now look like:...
<port auto-increment="true">5701</port>
<join>
<multicast enabled="false" />
<tcp-ip enabled="true">
<hostname>private-ip-of-the-other-machine:5701</hostname>
<hostname>private-ip-address-of-this-machine:5701</hostname>
</tcp-ip>
<aws enabled="false"/>
</join>
<interfaces enabled="true">
<interface>private-ip-address-of-this-machine</interface>
</interfaces>
...
Make sure the IP addresses for the machine is correct.<hostname> line on the file with the IP address of the new instance we just created.sudo /etc/init.d/mysql stopNow Copy the existing data directory (default located in /var/lib/mysql) using the following command
sudo cp -R -p /var/lib/mysql /path/to/new/datadirAll you need are the data files, so delete the others with the command
sudo rm /path/to/new/datadirNote:- You will get a message about not being able to delete some directories, but that's what you want.
gksu gedit /etc/mysql/my.cnfLook for the entry for "datadir", and change the path (which should be "/var/lib/mysql") to the new data directory.
sudo gedit /etc/apparmor.d/usr.sbin.mysqldCopy the lines beginning with "/var/lib/mysql", comment out the originals with hash marks ("#"), and paste the lines below the originals.
sudo /etc/init.d/apparmor reloadRestart MySQL with the command
sudo /etc/init.d/mysql restartNow MySQL should start with no errors, and your data will be stored in the new data directory location.