Jump to content


Level 2 Member
  • Content count

  • Joined

  • Last visited

  • Days Won


Chris74 last won the day on February 17 2014

Chris74 had the most liked content!

Community Reputation

28 Excellent

About Chris74

  • Rank
    Level 2 Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Chris74

    Nominet module now requires TLS 1.2

    Does anyone know if it's ok to upload the 7.6 Nominet module to a 7.5 installation? I'm not ready to update to 7.6 yet and I missed the notifications about the TLS 1.2 requirement. Edit... That appears to have worked so far.
  2. Chris74

    PHP Errors...

    Thanks for your input Brian. All addons were 7.5 compatible (or advertised as working with version 6+). I've disabled and removed all addons that are non essential. Yesterday the cron job sending the server load soaring was happening every time it ran. Server load was in the 20's (high CPU) - and the cron was taking 17 minutes, so I removed all addons that were triggered during cron. There was one, "WHMCS cleaner" that I suspected was a problem - and so far, having removed that (and others) overnight it seems the regular crons are now running within about 30 seconds. The daily cron takes longer than five minutes, so I've adjusted the frequency to every ten mins. I'm still randomly getting that PHP error. Last instance of it was at around 2am. Having looked into the terminations issue - it seems any and all cancellation requests are being ignored by the cron since we updated to 7.5.1. Normal terminations are working fine - i.e those that are past the renewal date. I think this can only be a bug. I'm looking at three separate issues here I think. So far I reckon issue 1 is resolved, after getting rid of the addons.
  3. Chris74

    PHP Errors...

    Assuming the -all flag will run the "daily" tasks, the output didn't provide much insight... 0/24 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0% < 1 sec/< 1 sec 79.5 MiB 2/24 [▓▓░░░░░░░░░░░░░░░░░░░░░░░░░░] 8% < 1 sec/< 1 sec 79.5 MiB 4/24 [▓▓▓▓░░░░░░░░░░░░░░░░░░░░░░░░] 16% < 1 sec/< 1 sec 79.5 MiB 6/24 [▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░░░] 25% 9 secs/36 secs 83.5 MiB 8/24 [▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░] 33% 9 secs/27 secs 83.5 MiB 10/24 [▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░] 41% 9 secs/22 secs 83.5 MiB 12/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░] 50% 10 secs/20 secs 84.2 MiB 14/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░] 58% 10 secs/17 secs 84.2 MiB 16/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░] 66% 10 secs/15 secs 84.2 MiB 18/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░] 75% 31 secs/41 secs 84.8 MiB 20/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░] 83% 33 secs/40 secs 85.0 MiB 22/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░] 91% 35 secs/38 secs 95.8 MiB 24/24 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100% 43 secs/43 secs 94.5 MiB 0/4 [░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0% < 1 sec/< 1 sec 100.0 MiB 1/4 [▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░░░] 25% < 1 sec/< 1 sec 100.0 MiB 2/4 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░] 50% < 1 sec/< 1 sec 100.0 MiB 3/4 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░░] 75% 2 secs/3 secs 100.0 MiB 4/4 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100% 2 secs/2 secs 100.0 MiB I output to a text file and it just contained this... WHMCS Automation Task Utility: all ================================== Daily Cron Automation Mode Queuing Tasks ------------- Force run any tasks: ignore "in progress" and "is due" Task queues ready Executing Application Queue --------------------------- Currency Exchange Rates Product Pricing Updates Invoices Late Fees Credit Card Charges Invoice & Overdue Reminders Domain Renewal Notices Cancellation Requests Overdue Suspensions Overdue Terminations Fixed Term Terminations Inactive Tickets Delayed Affiliate Commissions Affiliate Reports Email Marketer Rules Credit Card Expiry Notices Server Usage Stats Overage Billing Charges Client Status Update Domain Expiry Ticket Escalation Rules Data Retention Pruning Run Jobs Queue WHMCS Updates Sending Daily Cron Digest email Executing System Queue ---------------------- [OK] Completed It doesn't really help troubleshoot the issues I'm having. The main problem I'm experiencing is with cancellations not processing. I have hosting plans that are set to immediate cancel that are not being terminated and hosting plans that are set to end of term that have gone past the end of term and are not terminating. The activity log shows no attempt to cancel these services. The services are suspending correctly and the suspension is being reported correctly - but not the termination. This doesn't seem to happen to all of them. Everything has been fine until the 7.5 update. I think I'm getting two different issues mixed up here. The original PHP errors seem to be related to Stripe, which is not impacting on the cancellations. The cron jobs getting stuck and there being multiple instances seems to have stopped happening, but the PHP errors are still there and the issue with services not terminating is still happening. I think both issues are simply bugs introduced in 7.5
  4. Chris74

    PHP Errors...

    Any ideas on these?... I'm having a problem with the daily cron job seemingly getting stuck and sending server load soaring. I think the crons are overlapping. One has been running for over 20 minutes and server load is now in double figures. I notice six instances of cron.php are now running. This has only started happening since the upgrade to 7.5.
  5. I think it will probably just about work ok. Not tested it fully yet. Shame they haven't included any LVE limit options. It turns out despite the instructions saying you have to set the initial pricing to zero, it does seem to work with pricing added - so setting the "base" limits to free and having a starting price suits my needs. It does seem to work ok in the cart. Not got around to testing the provisioning yet. Like most things in WHMCS, its very basic and unrefined. They seem to develop the bare minimum of each module that they can get away with - then rarely bother to add any improvements. I honestly don't know why anyone hasn't come up with a better solution yet.
  6. Thanks Brian, always appreciate your input. I was of the impression that this addon was quite new. No idea why I thought that. I'll persist with it for a while and see what happens. Cheers.
  7. It also says " Configure any of the limits on the Module Settings tab that you don't want to offer as options on the order form ". I've read that sentence a few times and it doesn't seem to make sense. I have to presume it means that I should enter values in the "Advanced Mode" only for resources that I specifically do not want to be configurable? i.e If I enter values in Disk Space for example, no matter what configurable options I set up - those will not be configurable - and the value from the "Advanced Mode" will override it. The documentation doesn't mention advanced mode, but as that's the only option that allows values to be set up for the product, I guess that is what it is referring to. What I'd like to do is set a base price for the product, and the base limit of a resource - let's say 5GB of space included in the price - and then allow the client to choose if they want to purchase more at the time of ordering, or later. I have a terrible feeling, none of the basics have been covered here at all. It looks a bit s**t. It's possible, with trial and error, I might get it to do what I want. If the documentation was a bit more clear and more thorough it would help a lot. I think the instructions for this were perhaps written a few versions ago - and not updated.
  8. Thanks for the speedy reply Brian. It was actually a dropdown menu because I'd already selected my server group (why wouldn't I?) and at that point, it loads in packages from the servers and presents them as a list rather than allowing anything to be typed in. Thanks to your reply, If I de-select the server group, I can now enter "custom" - then re-select my server group afterwords. It's a just a very sloppy form. Another example of lazy and thoughtless coding in WHMCS. This is already causing a headache because I (stupidly) thought I'd be able to start with a base configuration and price - then allow the client to choose additional resources when ordering. It seems I now have to set the product to a zero cost, so they must build it entirely from scratch. Makes this a tad more complicated when calculating the pricing. I now have to make the combination of resources all add up to the minimum price I wanted to charge, rather than setting a base price and pricing additional resources on top. It's very poorly designed. But I've come to expect that really.
  9. I'm just posting this in the hope that someone else has had this issue and it's just a simple solution. I purchased the configurable package addon and I'm working through the instructions here... https://docs.whmcs.com/Configurable_Package_Addon ...which are very straightforward, however I'm stuck. It says... So I did this but there is no "Custom" option available in the "Package Name" field. Any ideas?
  10. It seems changing the cron frequency hasn't resolved the problem of cancellation requests not being processed - certainly not for any outstanding "immediate" ones. I've needed to run these manually. I'll keep an eye on it and see what happens with any new ones that come in.
  11. Ahh - just noticed that at some point the required frequency of the cron seems to have changed. Until now we've had it running once a day, but it seems there is now a need to run this every 5 minutes - with scheduled tasks running at the specified time.Interestingly, the documentation still says to run the cron once a day... https://docs.whmcs.com/Automation_Settings But when you drill down to this one it explains that since 7.0, the cron should be run every 5 minutes... https://docs.whmcs.com/Crons I must not have read the release notes thoroughly enough! Strangely everything was working ok on 7.4 with the cron running once a day.
  12. It seems since we updated to WHMCS 7.5 recently, any customers with cancellation requests for any products (in our case cpanel hosting accounts) are not being cancelled when the cron job runs. In fact, it looks like no cancellations are being processed at all by the cron. We've checked the activity log and there is an entry every day "Automated Task: Starting Cancellation Requests" but then it just skips to "Automated Task: Starting Overdue Suspensions" and ignores any pending cancellation requests completely. Everything was working fine before the move to 7.5 Anyone else experiencing this?
  13. Chris74

    GDPR and domain contact data?

    That's good to know. Thanks Brian. I was concerned that registrant data was held within the WHMCS database and could remain there until removed. I'll probably just find an addon to hide expired domains from the end user anyway - just to stop them nagging.
  14. Chris74

    GDPR and domain contact data?

    I'm just wondering what the implications are of keeping expired domains, which have associated contact data, after they have expired. We have a customer who demands that we delete his old domains because they contain registrant data that he doesn't want stored in our system. I wonder if someone could clarify exactly what is stored in the domain's database entry - does it include contact info - or is that simply associated with the contacts they have added in their account? I guess what I'm trying to establish is whether or not we have an obligation now under GDPR to delete the contact data held for a particular domain, once that domain has expired. I would suggest if that contact data is held within the same database record as the domain itself, the domain should be deleted once it has been expired for a certain period. If the personal data is not held along with the database, surely then it is simply up to the customer to delete the "contact" or sub account they added for use with the domain. I'd like to clarify this. I think it is quite important to make a distinction, because there is no way in WHMCS to delete domains once they have been expired for a certain period of time, which means it is holding on to data longer than is necessary and thus, possibly not GDPR compliant.
  15. Chris74

    MySQL query to bulk cancel a product.

    Thanks for your reply. It wasn't the query as much as a confirmation of the correct fields. Brian came to my rescue and confirmed what I thought. UPDATE tblhosting SET domainstatus = 'Cancelled' WHERE packageid = 16; Worked perfectly. Strange that they chose "domainstatus" as a field name for products.

Important Information

By using this site, you agree to our Terms of Use & Guidelines