Skip to content

Troubleshooting

ch604 edited this page Jun 15, 2020 · 1 revision

Pullsync gives you information about the errors it encountered at the conclusion of a task, through the 'errors of note' body. This can be found at /home/temp/pullsync/errors_of_note.txt for past pullsyncs. Often, a parenthetic command will show you how to output more details from the error. Generally, the recourse for any error is to perform the same action manually.

Installation Failed

Installations for npm, nodejs, tomcat, maldet, memcache, or configserver plugins can all fail mid-initial-sync. The recourse for this is to attempt the installation manually.

Database Issues

At times, databases can fail to dump or import properly. This is usually because of a corrupt database file on the source preventing a full dump, or an incompatibility with the table scheme, usually from a too-large upgrade of mysql (e.g. mysql 4.0 to mariadb 10.1). A dump and import should be attempted manually to see the actual text of the error and at what point or table the import ceases, so that the offending table can be corrected or skipped.

Failed Account, Domain, or Database Restore

The /home/temp/pullsync/missingthings.txt file informs a tech of full cPanel accounts, addon or parked domains, or databases that failed to restore. These should be attempted for migration, park, or creation and mapping manually as needed.

Clone this wiki locally