Hi, Everything is in the title. Resync clientdb config Does not recreate users Does not recreate database Does not grant user to database While looking thru the queue web_database_user task are not visible The are created within the sys_datalog table but with server_id = 0 and apparently not displayed du such Surprisingly sys_datalog entry are created in 'OK' state ... isn't it pending that should be? Regards
Resync updates users and databases, it does not create them. Thats exactly how it should work. database users are not bound to a server, thats why they use ID 0. The column you refer to i not used at all,so it can contain any value.
What do you mean by update user? Point is I had to restore system from backup due server crash. Resync does the job for everything but db user and database. Also appart from digging thru the code, is there any wsdl or comprehensive list of /remote schema ?
The purpose of the remote function is to write changes that ahs been done in the ispconfig database manualy to disk. so it is a update tool, not a tool to create something that you deleted or that was missing for another reason. It might be that you can recreate some parts of the config when you deleted it with the resync tool, but thtas not guaranteed as it is not made for that. A restore from backup should also contain to restore the mysql "mysql" database and especially the website users in the passwd, shadow and group files. Hen you use the resync tool before you restored the system users, then the new users in passwd might have different ID's from the ones in your backup so that the permissions of the restored websites will be wrong. See documentation in /remote_client folder of the tar.gz. Beside that, you can get detailed information on the available fields of the $params array by looking at the ispconfig database. the $params key fields match the database column names.
Exactly what I expected by recovering the dbispconfig database and hit resync. Now I'm lost. Doesn't this part contradict the first part? And what "resync dbuser and databases" mean in such context... Ok not that usefull specially when in multi-server or other scenario when "server" change, mysql user allowed server need to fits the new server I addressed my need by a couple of sql statement to recreate DB and USER ... However ;-) Appart from those misunderstanding of mine ... Good job, your panel rocks
No, not at all. Do you understand that there is a differnce between inserting and updating something? You can only update something that exists already. What you tried is to update a non existing mysql user and non existing mysql database and the result in mysql is that nothing happens, as mysql can not update a user or database that is not existing.
I do understand the difference... So resync user will solely resync mysql password with the ispconfig stored one And resync database change the default charset Correct?
A resync can change all values of a existing item that can be changed trough the ispconfig interface, but it will not create that item if it does not exist. Like I explained above, the resync might create some items, but these items have not bnescessarily the same parameters like uid's then the original items as e.g. Linux uses the next free uid when you create a user.
Understand ... I guess Thank you Any plan/roadmap/wish to have some export/import for migrating an ispconfig ? I'll be glad to propose something I it is your will
We developed already a import tool that supports importing of ISPConfig 2, ISPConfig 3, Plesk and Confixx into a ISPConfig 3 System. The tool will be available in a few weeks.
