A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Write for DigitalOcean You get paid, we donate to tech non-profits.
DigitalOcean Meetups Find and meet other developers in your city.
Hacktoberfest Contribute to Open Source
I have send a ticket over 3,5 hours ago and still no reply?
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
DigitalOcean does not charge enough to justify a support SLA, it’s best effort, up to 48 hours.
ticket id: 490358
ok thats a long time....
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
I have two identical droplets - both 2 GB / 2 CPUs / 40 GB Disk, nyc3. Both set up with WordPress/Ubuntu 14.04. The first is a production web server that has been up for 6 months or so. The second is a new test server. I have a 9MB (zipped) phpMyAdmin export of a MySQL table with ~2 million records. I can import this into the first server in about 3 minutes. On the second server the import causes a timeout after ~4,000 records. I set the phpMyAdmin timeout to 0, and the import has been running for at least an hour so far. What would make these two servers act so differently?
It seems there's a nasty MySQL zero day flaw that needs to be fixed on all servers running MySQL 5.7.13 and below, including MariaDB and PerconaDB: http://seclists.org/oss-sec/2016/q3/481 Does anyone know how to apply the patch to fix this vulnerability ? A quick D.O tutorial would be pretty handy.
I have an issue after I upgrade MYSQL from 5.5 to 5.6 cause I want security update. I using Vesta CP on my droplet to hold 3 Wordpress websites. My droplet: Ubuntu 14.04.4 x32 Memory 512 MB Disk 20 GB ``` 2016-10-06 15:49:07 5080 [Note] Plugin 'FEDERATED' is disabled. 2016-10-06 15:49:07 5080 [ERROR] Function 'innodb' already exists 2016-10-06 15:49:07 5080 [Warning] Couldn't load plugin named 'innodb' with soname 'ha_innodb.so'. 2016-10-06 15:49:07 5080 [ERROR] Function 'federated' already exists 2016-10-06 15:49:07 5080 [Warning] Couldn't load plugin named 'federated' with soname 'ha_federated.so'. 2016-10-06 15:49:07 5080 [ERROR] Function 'blackhole' already exists 2016-10-06 15:49:07 5080 [Warning] Couldn't load plugin named 'blackhole' with soname 'ha_blackhole.so'. 2016-10-06 15:49:07 5080 [ERROR] Function 'archive' already exists 2016-10-06 15:49:07 5080 [Warning] Couldn't load plugin named 'archive' with soname 'ha_archive.so'. 2016-10-06 15:49:07 5080 [Note] InnoDB: Using atomics to ref count buffer pool pages 2016-10-06 15:49:07 5080 [Note] InnoDB: The InnoDB memory heap is disabled 2016-10-06 15:49:07 5080 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-10-06 15:49:07 5080 [Note] InnoDB: Memory barrier is not used 2016-10-06 15:49:07 5080 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-10-06 15:49:07 5080 [Note] InnoDB: Using Linux native AIO 2016-10-06 15:49:07 5080 [Note] InnoDB: Not using CPU crc32 instructions 2016-10-06 15:49:07 5080 [Note] InnoDB: Initializing buffer pool, size = 20.0M 2016-10-06 15:49:07 5080 [Note] InnoDB: Completed initialization of buffer pool 2016-10-06 15:49:07 5080 [Note] InnoDB: Highest supported file format is Barracuda. 2016-10-06 15:49:07 5080 [Note] InnoDB: The log sequence numbers 114578589 and 114578589 in ibdata files do not match the log sequence number 115317197 in the ib_logfiles! 2016-10-06 15:49:07 5080 [Note] InnoDB: Database was not shutdown normally! 2016-10-06 15:49:07 5080 [Note] InnoDB: Starting crash recovery. 2016-10-06 15:49:07 5080 [Note] InnoDB: Reading tablespace information from the .ibd files... 2016-10-06 15:49:07 5080 [Note] InnoDB: Restoring possible half-written data pages 2016-10-06 15:49:07 5080 [Note] InnoDB: from the doublewrite buffer... 2016-10-06 15:49:07 5080 [Note] InnoDB: 128 rollback segment(s) are active. 2016-10-06 15:49:07 5080 [Note] InnoDB: Waiting for purge to start 2016-10-06 15:49:08 5080 [Note] InnoDB: 5.6.33 started; log sequence number 115317197 2016-10-06 15:49:08 5080 [Note] Server hostname (bind-address): '*'; port: 3306 2016-10-06 15:49:08 5080 [Note] IPv6 is available. 2016-10-06 15:49:08 5080 [Note] - '::' resolves to '::'; 2016-10-06 15:49:08 5080 [Note] Server socket created on IP: '::'. 2016-10-06 15:49:08 5080 [Note] Event Scheduler: Loaded 0 events 2016-10-06 15:49:08 5080 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.33-0ubuntu0.14.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) ``` How I should do to fix this issue ? It happen many times after the server do cron job to backup. Thanks :)
I am trying to connect to my database server with an application that will connect through an ODBC connection. To set up the ODBC connection I need to use SSL. How do I set that up?
