When I go to add a secondary/pointer domain, after I click submit my my browsers page goes blank. I’ve checked various logs and I don’t see anything out of the ordinary.
What information do you guys need to better help me solve this issue?
Hi Phobos -
Sounds like there’s an error that is causing the process to exit. Turning on debugging should present a more useful error message, but not always. We’ve greatly improved error handling for the next release because of issues like this!
Anyway, to turn debugging on, you’ll need to edit the iworx.ini file, which is in /home/interworx/iworx.ini
As root, open it up and look for debug=“0” and change it to debug=“1”
Then try it again and see what it says.
Or, you can just log a support ticket with us, and we can have a look to clear things up for you!
I’ve enabled debug, heres what I got.
[SIZE=2] [B]InterWorx Error Report[/B] [/SIZE] [SIZE=2] [B]DETAIL:[/B] [/SIZE] [SIZE=2] [B]FILE:[/B] /usr/local/interworx/include/siteworx/Domain.php
----- ASSERTION FAILED BEGIN -----
ASSERTION FAILED: /usr/local/interworx/include/siteworx/Domain.php (89):
----- ASSERTION FAILED END -----
[/SIZE] [SIZE=2] [B]STACK TRACE:[/B] [/SIZE] [SIZE=2]
----- DEBUG STACKTRACE BEGIN -----
/usr/local/interworx/include/IWorxDebug.php debug_printstacktrace (266)
/usr/local/interworx/include/IWorxDebug.php debug_die (193)
/usr/local/interworx/include/IWorxDebug.php debug_assert (69)
0 iworx_debug_assert (0)
/usr/local/interworx/include/siteworx/Domain.php assert (89)
/usr/local/interworx/include/siteworx/Domain.php _populate (74)
/usr/local/interworx/include/dns/Zone.php domain (510)
/usr/local/interworx/include/siteworx/SiteWorx.php toassocarray (649)
/usr/local/interworx/siteworx/html/domains.php addslavedomain (515)
/usr/local/interworx/siteworx/html/domains.php domains_slave_add (482)
/usr/local/interworx/siteworx/html/domains.php domains_slave (98)
/usr/local/interworx/siteworx/html/domains.php domains (78)
/usr/local/interworx/siteworx/html/domains.php _il_exec (2)
----- DEBUG STACKTRACE END -----[/SIZE]
Yep, I’d suggest logging a bug - the support guys can fix this up for you.
Is there any possible way you could walk me through what I’m supposed to be doing here and I’ll take care of it myself?
Unfortunately, the error message isn’t specific enough to help remotely. It indicates that the domain is empty in the DNS Zone, which may mean that your DNS templates are set up improperly - but that’s tough to tell without actually looking at them.
I shot over a support ticket.
For the record, I believe the problem here was that the DNS Zones for the primary domain had been deleted, and that was causing the problem.
Even if DNS is hosted off the server, leaving the DNS Zones there is not a problem.