Problem with Database Export: BUG REPORT

So if you trust the database tools within Dolphin you will end up loosing 90% of your users from the profile table.

this is occurring with a LAMP install

The workaround is to use other methods such as phpmyadmin or line commands from within mysql.

Do you mean the members weren't included in the MySQL dump? If so, it sounds like an issue with the PHP configuration being too low for Dolphin to dump the database properly, especially if there's a large amount of data. Make sure there's a high enough value for memory_limit and max_execution_time.

But you're right that the best method is to use phpMyAdmin. Really, using the database tools are not recommended. I would like to see them replaced with a nice little script like Adminer.

memory_limit 128M

ill bump up the execution time and see if it makes a diff...

very small database for testing with only about 50 members.

when importing the database the problem lies with the field of "status"

max_execution_time is far too low for Dolphin. The minimum recommended value for it is 300. Please up it and try again, and increase as needed. But again, it's really better to use phpMyAdmin. You should up max_execution_time to 300 anyway, however for Dolphin's sake.

 
Yea, it should be higher. 300 is about what i have mine set for.

I also have run with various memory limit settings, and dolphin runs best at 512M or higher. Any lower you will run into out of memory problems from time to time. 128M is just dolphins min requirement. But i call that the bare minimum and not really enough.

Note: Some providers of shared services don't allow memory to be boosted to 512M.

But seriously. I don't trust the built in database tools either, and never have. I use phpMyAdmin for everything.

If you have a large database to import, I recommend bigdump.php; do a search.  However, before doing your export, read the guide as bigdump needs exports to be done in a certain way (using phpMyAdmin or others) or it won't do the import.

max_execution_time = 60

worked for years for me on other scripts... with

max_execution_time = 300 

how easy is it for someone to overwhelm a server?  (even at 60) ...  

------------------------

off topic: the other problem that i am having is creating the *_m.jpg, *_ri.jpg, *_rt.jpg and *_t.jpg files. with 27000 base profile images this will result in 135,000 files in ONE directory, and at the moment i can not move them around on a windows or a mac machine.  Dolphin seems to place all images into one folder in the current version.  Is anyone successfully running a site of this size?

Dolphin is not other scripts. Dolphin is not your simple CMS.

how easy is it for someone to overwhelm a server?
I have run at 300 for as long as i have been running dolphin. Over 7 years now. Never seen it happen.

Dolphin seems to place all images into one folder in the current version
Dolphin has done that with all versions for years now. I am sure dealing with them by hand was not something boonex even thought of. Under normal operation you don't need to touch the photo files. So it's normally not a issue.

I know of one site with over 74000 base photos. I am sure there are other much bigger ones. Modern versions of linux which most servers run can handle over 4 billion files in one folder if running ext4 file system.

The default file system for CentOS 7 is XFS

True, however most providers most likely will not use it. It has some limitations that are used by many service providers. XFS does not support quotas, and the file system cannot be shrunk which is useful in virtual environments.

But XFS most likely would remain default on dedicated servers. Most hosting providers don't yet offer CentOS 7. So XFS will not be very common for at least another year or so.