03-05-2016
Hmmm. Checked all the PHP and MySQL log files and did not find any errors that would be associated with these missing threads.
Let's keep an eye on things, perhaps (hopefully) it was just a fluke errors.
Thanks for everyones help on this.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just inst freeBSD boot installation and it didnt work for(probably my lack of knowledge) reasons but i now have to partitions in freeBSD and i really need them back for windows at the moment. i just cant find them. The bad thing is that i only got this bundled version of windows so i cant really... (2 Replies)
Discussion started by: riwa
2 Replies
2. UNIX for Dummies Questions & Answers
when i am doing the crontab editing i am using the setenv EDITOR /usr/bin/vi
but their was an error i tried to put set EDITOR /usr/bin/vi and it wnet through and i started editing using the command crontab -e but somehow it is slow and displayed something like e300 and i tried to stop because it... (3 Replies)
Discussion started by: afuella
3 Replies
3. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
4. Solaris
Hi all
I have a really strange situation. This morning I ran lpstat -p and it didn't return any results. I ran lpstat -t and the scheduler is running.
How strange, it seems all the printers have disappeared from my server.
Can anyone perhaps explain to me how this is possible? (4 Replies)
Discussion started by: soliberus
4 Replies
5. UNIX Desktop Questions & Answers
I'm doing an assignment for a Unix course at school.
I attempted to rename one of the shell programming questions from home to Q1 by typing:
mv home Q1
It returned a message saying
mv: cannot access home
And now there's no home or Q1 in the directory. Please help! (8 Replies)
Discussion started by: slogged
8 Replies
6. Solaris
Hello all I was configuring a SUN 2540 raid and after a reboot the hba`s is gone.
There is no longer an entry in etc/path_to_inst for them (2 cards).
I tried a reconfigure boot several times but it does not work.
The hba`s is a SUN qlogic 2200 in x4240 server (AMD).
Using solaris 10 update7.... (6 Replies)
Discussion started by: vettec3
6 Replies
7. Solaris
Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out.
exit
rebootxscf
logout
#.
#>
#>
~#
~#
exit
sendbreak
exit
I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies
8. Solaris
Can't find the data in either pool.
bash-3.00# zoneadm -z PPSMzone1 move /zpool/ppsmzone1
cannot create ZFS dataset zpool/ppsmzone1: dataset already exists
Moving across file-systems; copying zonepath /rpool/PPSMzone1...
Cleaning up zonepath /rpool/PPSMzone1...
bash-3.00# zonecfg -z... (1 Reply)
Discussion started by: LittleLebowski
1 Replies
9. Solaris
System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD.
I have been experimenting on the above system, using ldmp2v to create "clones" of my physical systems as LDoms on the server when there was an unscheduled power outage. After the system came back up I had lost my LDoms, although... (7 Replies)
Discussion started by: apmcd47
7 Replies
10. Solaris
I have a problem where I installed several OSes as partitions on one disk. And suddenly I cannot see Solaris 11.3 in the bios boot screen anymore. I have no clue why. Do anyone have a suggestion so I can dig further somewhere?
I first installed Solaris 11.3. Then Windows10 (gaming). Then Linux... (3 Replies)
Discussion started by: kebabbert
3 Replies
LEARN ABOUT DEBIAN
mydumper
MYDUMPER(1) mydumper MYDUMPER(1)
NAME
mydumper - multi-threaded MySQL dumping
SYNOPSIS
mydumper [OPTIONS]
DESCRIPTION
mydumper is a tool used for backing up MySQL database servers much faster than the mysqldump tool distributed with MySQL. It also has the
capability to retrieve the binary logs from the remote server at the same time as the dump itself. The advantages of mydumper are:
o Parallelism (hence, speed) and performance (avoids expensive character set conversion routines, efficient code overall)
o Easier to manage output (separate files for tables, dump metadata, etc, easy to view/parse data)
o Consistency - maintains snapshot across all threads, provides accurate master and slave log positions, etc
o Manageability - supports PCRE for specifying database and tables inclusions and exclusions
OPTIONS
The mydumper tool has several available options:
--help Show help text
--host, -h
Hostname of MySQL server to connect to (default localhost)
--user, -u
MySQL username with the correct privileges to execute the dump
--password, -p
The corresponding password for the MySQL user
--port, -P
The port for the MySQL connection.
Note For localhost TCP connections use 127.0.0.1 for --host.
--socket, -S
The UNIX domain socket file to use for the connection
--database, -B
Database to dump
--table-list, -T
A comma separated list of tables to dump
--threads, -t
The number of threads to use for dumping data, default is 4
Note Other threads are used in mydumper, this option does not control these
--outputdir, -o
Output directory name, default is export-YYYYMMDD-HHMMSS
--statement-size, -s
The maximum size for an insert statement before breaking into a new statement, default 1,000,000 bytes
--rows, -r
Split table into chunks of this many rows, default unlimited
--compress, -c
Compress the output files
--compress-input, -C
Use client protocol compression for connections to the MySQL server
--build-empty-files, -e
Create empty dump files if there is no data to dump
--regex, -x
A regular expression to match against database and table
--ignore-engines, -i
Comma separated list of storage engines to ignore
--no-schemas, -m
Do not dump schemas with the data
--long-query-guard, -l
Timeout for long query execution in seconds, default 60
--kill-long-queries, -k
Kill long running queries instead of aborting the dump
--version, -V
Show the program version and exit
--verbose, -v
The verbosity of messages. 0 = silent, 1 = errors, 2 = warnings, 3 = info. Default is 2.
--binlogs, -b
Get the binlogs from the server as well as the dump files
--daemon, -D
Enable daemon mode
--snapshot-interval, -I
Interval between each dump snapshot (in minutes), requires --daemon, default 60 (minutes)
--logfile, -L
A file to log mydumper output to instead of console output. Useful for daemon mode.
--no-locks, -k
Do not execute the temporary shared read lock.
Warning
This will cause inconsistent backups.
AUTHOR
Andrew Hutchings
COPYRIGHT
2011, Andrew Hutchings
0.5.1 June 09, 2012 MYDUMPER(1)