bendrop Posted August 31, 2018 Share Posted August 31, 2018 Just wondered if this has happened to anyone else? Since I upgraded to 7.6.1 - the Domain Sync task isn't running anymore? It's not even triggered (nothing in the logs). All settings in Automation settings are correct (Checked, Every 4 hours) - but nothing. I'm guessing no, but has something changed I need to know about in the 7.6.1 release? 0 Quote Link to comment Share on other sites More sharing options...
bear Posted September 1, 2018 Share Posted September 1, 2018 Not just you. Automation status on mine shows this: Domain Expiry Synchronisation 0 Completed There's loads of domains in the system. Should that not show it's done at least some of those? 0 Quote Link to comment Share on other sites More sharing options...
mbrando Posted September 1, 2018 Share Posted September 1, 2018 Hello, I'm having the same issue. I've opened a ticket about this. 7.6.x seems to be a buggy release. There was also an issue with name servers not displaying for domains in the domain view. - Mike 0 Quote Link to comment Share on other sites More sharing options...
NoDoze Posted September 2, 2018 Share Posted September 2, 2018 Same issue going on here. Hopefully they'll fix the bug soon! 0 Quote Link to comment Share on other sites More sharing options...
mbrando Posted September 2, 2018 Share Posted September 2, 2018 Hello, So far WHMCS support has replied to say the cronjob in v7.6 has been moved to be part of the normal cronrun: https://docs.whmcs.com/Crons Quote Can you ensure you have your normal cron executing every 5 minutes and it is completing fully? Anyone know how to confirm the cron is completing fully? I do have my cron set to */5 for every 5 minutes. Mine still does not work. - Mike 0 Quote Link to comment Share on other sites More sharing options...
xyzulu Posted September 3, 2018 Share Posted September 3, 2018 (edited) I'm seeing the same.. please keep this thread updated when you hear from WHMCS Edited September 3, 2018 by xyzulu 0 Quote Link to comment Share on other sites More sharing options...
WHMCS ChrisD Posted September 3, 2018 Share Posted September 3, 2018 Hi all, The domainsync cron is now part of the standard cron, what would be a huge help in troubleshooting this is having you go into Setup > General Settings > Other and enable Display Errors & Log errors. Once done please log into your server terminal window and force your full cron to run using the command php -q /home/username/crons/cron.php -F all -vvv This will force the cron to run with an extendated output, check this output at the point that the expiry runs for any errors and let us know in this thread this will better help us guide you with the issue. 0 Quote Link to comment Share on other sites More sharing options...
bendrop Posted September 3, 2018 Author Share Posted September 3, 2018 If I run it with the force all command, domain sync runs fine. However, running as the standard cron (and the daily) it never triggers. 0 Quote Link to comment Share on other sites More sharing options...
xyzulu Posted September 3, 2018 Share Posted September 3, 2018 (edited) 22 minutes ago, bendrop said: If I run it with the force all command, domain sync runs fine. However, running as the standard cron (and the daily) it never triggers. Same result here. @WHMCS ChrisD I do have an open bug report about this (as do others apparently). If you test this yourself I am sure you will be able to replicate the behaviour we are ALL seeing. Edited September 3, 2018 by xyzulu Grammar 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Technical Analyst II WHMCS Alex Posted September 3, 2018 WHMCS Technical Analyst II Share Posted September 3, 2018 Hello, I can confirm that we are aware of this behavouir in version 7.6 and have case CORE-12679 open with our development team in order to have this reviewed further. In the meantime, I would advise creating a separate cron job to execute both the -DomainExpirySync --DomainTransferSync tasks at the frequency you require, for example, to run them every 4 hours, you would use this cron: 0 */4 * * * php -q /path/to/crons/cron.php do --DomainExpirySync --DomainTransferSync Simply replace /path/to/crons with the actual path to your crons directory. I am sorry for any and all inconvenience caused. 1 Quote Link to comment Share on other sites More sharing options...
bear Posted September 3, 2018 Share Posted September 3, 2018 Same result here, and I'd added that into my own thread. Force it, I get the email and it updates without error. Enabling errors shows nothing obvious going wrong, it's just not firing. Thanks for the temp fix, Alex. 0 Quote Link to comment Share on other sites More sharing options...
bendrop Posted September 3, 2018 Author Share Posted September 3, 2018 @WHMCS Alex - Temp fix works for me too, thanks! 0 Quote Link to comment Share on other sites More sharing options...
bear Posted September 3, 2018 Share Posted September 3, 2018 (edited) Hmm, something amiss. Using the call provided, and instead of every 4 hours (I'd changed that to 2), it's running once per minute. Check what yours is doing, I'd suggest. Oh, of course. First entry is "every minute". You need to put a time in that. * */2 * * * php -q /path/to/cron.php do --DomainExpirySync --DomainTransferSync Edited September 3, 2018 by bear 0 Quote Link to comment Share on other sites More sharing options...
bear Posted September 3, 2018 Share Posted September 3, 2018 Hmm, I edited that code block to show the proper entry, and it's missing. Included below. Also, the automation status page still shows expiration status updated as 0. Maybe that's just looking at ones it's changed the date on? 0 */2 * * * php -q /path/to/cron.php do --DomainExpirySync --DomainTransferSync 0 Quote Link to comment Share on other sites More sharing options...
mbrando Posted September 3, 2018 Share Posted September 3, 2018 Hello, I have the same result here. Domain sync does not run with regular cron. It does run with forced cron all and if run as php -q /path/to/cron.php do --DomainExpirySync --DomainTransferSync - Mike 0 Quote Link to comment Share on other sites More sharing options...
bear Posted September 3, 2018 Share Posted September 3, 2018 (edited) It would also appear the domain cron email is hard coded to use UK date format. That should be using the system setting, no? Edited September 3, 2018 by bear 0 Quote Link to comment Share on other sites More sharing options...
shadowtek Posted September 3, 2018 Share Posted September 3, 2018 Thx for this temp fix Alex 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Support Manager Featured Comment WHMCS John Posted September 4, 2018 WHMCS Support Manager Featured Comment Share Posted September 4, 2018 Hi all, A hotfix has been published for this case. It can be downloaded from here: Thanks for your reports. 3 Quote Link to comment Share on other sites More sharing options...
bear Posted September 4, 2018 Share Posted September 4, 2018 The dates on those two files are both July 31. Before I replace the original download files, is that right? Build Date: 27 Aug 2018 < full download that isn't working Build Date: 27 Jul 2018 < hot fix just downloaded 0 Quote Link to comment Share on other sites More sharing options...
redit Posted September 4, 2018 Share Posted September 4, 2018 Looks like the HOT fix is just a roll back to what was working 0 Quote Link to comment Share on other sites More sharing options...
mbrando Posted September 4, 2018 Share Posted September 4, 2018 Hello, Yes, 7.6.0 it was working and broke with 7.6.1 0 Quote Link to comment Share on other sites More sharing options...
mbrando Posted September 4, 2018 Share Posted September 4, 2018 Hello, I applied the hotfix and it appears to be working. 0 Quote Link to comment Share on other sites More sharing options...
bear Posted September 8, 2018 Share Posted September 8, 2018 (edited) Anyone noticed the date format on the email is UK (dd/mm/yyyy), even if the system is set to use US (mm/dd/yyyy)? Edited September 8, 2018 by bear 0 Quote Link to comment Share on other sites More sharing options...
mbrando Posted September 8, 2018 Share Posted September 8, 2018 Hello, Yes. Mine displays dd/mm/yyyy and I'm set for US Quote Domain Synchronisation Cron Report for 07-09-2018 11:00:02 0 Quote Link to comment Share on other sites More sharing options...
Nona Posted October 31, 2018 Share Posted October 31, 2018 php5 -q /home/xxxxxxx/htdocs/crons/cron.php do --DomainExpirySync --DomainTransferSync [Symfony\Component\Console\Exception\RuntimeException] The "--DomainTransferSync" option does not exist. do [--email-report [EMAIL-REPORT]] [--AddLateFees] [--AffiliateCommissions] [--AffiliateReports] [--AutoClientStatusSync] [--AutoTerminations] [--CancellationRequests] [--CheckForWhmcsUpdate] [--CloseInactiveTickets] [--CreateInvoices] [--CreditCardExpiryNotices] [--CurrencyUpdateExchangeRates] [--CurrencyUpdateProductPricing] [--DomainRenewalNotices] [--EmailMarketer] [--FixedTermTerminations] [--InvoiceReminders] [--OverageBilling] [--ProcessCreditCardPayments] [--AutoSuspensions] [--TicketEscalations] [--UpdateDomainExpiryStatus] [--UpdateServerUsage] [--RunJobsQueue] [--DataRetentionPruning] [--DomainExpirySync] [--DomainTransferSync] [--DatabaseBackup] 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Posted by WHMCS John,
Reputation Points
Go to this post
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.