Jump to content

tsiedsma

Members
  • Posts

    88
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by tsiedsma

  1. Yes, the db is localhost, both blesta and whmcs databases. The MySQL server did not go away, I confirmed the service uptime. PHP is configured with a ridiculously high execution time, memory limit and max input time. MySQL Persistence is enabled and the MySQL Wait timeout is 60 minutes. The import dies before all clients are imported. About 90% are imported. I enabled the system benchmark to see how long the import runs for. I cleared my DB and started again.
  2. Well, here's the results. I don't have anything configured on the server to kill long running processes and PHP's max_execution_time is set to over an hour. This ran for about 10 minutes before stopping. I'll check the logs on the server and see what I can find... The import completed but the following errors ocurred: importClients: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away on line 124 importContacts: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importTaxes: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importCurrencies: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importInvoices: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importTransactions: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importPackages: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importServices: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importSupportDepartments: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importSupportTickets: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 importMisc: SQLSTATE[HY093]: Invalid parameter number: number of bound variables does not match number of tokens on line 124 Edit: I set the mysql wait_timeout to an hour, it was set to 20 minutes. Also changed some cache settings and the max_allowed_packet size. Trying a new import now.
  3. Upgraded to 1.0.3 and am starting a new import after reverting my database. Will report the results shortly (5-10 minutes).
  4. What about my other question? "Do you have a roadmap of features scheduled for next and future releases?"
  5. Please do, I would really like to get this working!
  6. I just ran the importer on my rather large database. It worked this time from localhost instead of over the network. Items in red did not import, items in green were confirmed imported, items in orange cannot be confirmed because the do not apply. Staff (including login passwords) Client Groups Clients (excluding login passwords) Credit Card Payment Accounts Custom Client Fields and Values Client Notes Contacts - Imported as clients, this can be an issue... Tax Rules Currencies Invoices Recurring Invoices Transactions Client Credits Support Departments Support Tickets (excluding attachments) Support Predefined Response Categories Support Predefined Responses Sent Emails The following Settings: Mail Delivery Type SMTP Host, User, Password, Port, and Security Type Invoice Days Before Renewal Invoice Reminder Settings Auto Debit Days Before Due Suspend Services After Due Calendar Events Products (become packages) Registrars (become modules/module rows) Servers (become modules/module rows) Services Domains (become services)
  7. Does the importer import email activity? The table tblemails to be exact.
  8. I was referring to this: http://docs.blesta.com/display/dev/Modules And http://docs.blesta.com/display/user/Logicboxes
  9. Do you have a roadmap of features scheduled for next and future releases? Also, do you have more detailed developer docs regarding provisioning module development? I was looking at the docs as well as the included logicboxes module, I want to extend the functionality of the logic boxes module to included hosting and vps provisioning. I had written one for WHMCS, so i just need to port it over.
  10. I'm considering the switch to Blesta from WHMCS but am curious if the certain features that I may want coded can be purchased instead of submitting as a feature request, waiting for community feedback and the scheduled for a future release. I have not made a list by any means but there are a few things that I would need in place before I could consider the switch. Simple example would be the ability to choose a server location when placing an order. This is something I was able to code into WHMCS using their hooks system and changing the server group based on the selection of a Server Location configurable option for the hosting plan. It works great for me and since I have servers in Europe and the US, my customers need to be able to choose where to have their hosting provisioned. So, is it even an option to pay for custom dev work without having to hire a 3rd party or do it myself?
  11. The database is quite large. I'll try exporting the database and loading it on the Blesta server and seeing if a localhost import is quicker.
  12. I've just installed Blesta to evaluate as a replacement for WHMCS after the string of recent exploits and insight into how horribly coded it is. I'm trying out the importer so I can have real data to play with and I have a couple of items of feedback. 1) It would be nice to import packages that don't exist. I've got a ton and having to create them all before the import is going to be a task in itself. 2) A sort of status of what is going on would be nice. I'm sitting with a spinning mouse cursor for over 5 minutes now and have no idea what it's doing. 3) It eventually timed out, is there a CLI option? It would be nice if it could resume where it left off or something. Other than that, things are looking good. Thanks for the import module, it sure beats a fresh start.
×
×
  • Create New...