~iworx/bin/can now be used to take a master domain, and have it “swap roles” with a pointer domain that is pointing to it. For example, if there is a Siteworx account with domain name “mydomain.com” with a pointer domain called “mydomain.net”, then the domain promoter script will make “mydomain.net” the master domain, and “mydomain.com” the pointer domain.
Ok ive tried several ways to figure this out… Could somebody please provide me with example command? The help options make little sense to me. Maybe im just stupid.
I hope you don’t mind, but I thought I would test this on our sytems, as we have never used it before.
I setup a new domain called primary.url, then set a pointer called pointer.url.
Checked siteworx, and above was set correctly.
I then run the promoter pex, (see details of output below) and checked against the siteworx account, and it had changed as expected.
It would help if you could you provide output details of your failed promoter pex if you find it still does not work.
I hope this helps a little
Many thanks
John
~iworx/bin/domain-promoter.pex --pointer-to-primary --primary
-domain primary.url --pointer-domain pointer.url
Updating InterWorx Domains Table
Changing pointer domain type
Changing primary domain type
Updating parent ids of other child domains
Updating domain quota information
Update Apache Config
Replacing non-escaped domain in vhost file
Replacing escaped domain in vhost file
Renaming primary domain directory
Renaming var directory
Updating public_html symlink
Synchronizing Server Aliases
Update Mail Information
Writing new qmail assign file
Running qmail-newu
Removing old symlink
Making new symlink
Updating mailboxes
Updating aliases, groups, etc
Updating vpopmail dir_control
Updating FTP Configurations
Updating FTP Users
Updating Stats information
Renaming daily stat files
Renaming monthly stat files
Done! primary.url and pointer.url have swapped places![/QUOTE]
Hello,
Perhaps this is a bug I have come across then, can you create a new test account but make the domain in the format of a sub domain so like test.domain.com and then add a pointer to that newdomain.com.
I ask because you have not posted your output of promoter pex and therefore no details to help, or you could set IW to debug, run promoter pex and look for any issues
[SIZE=2]Yes its installed
[/SIZE][SIZE=2]Package interworx-cli-2.0.0-1.iworx.x86_64 already installed and latest version
As before here is what is see when I run the command.
[/SIZE]
[SIZE=2][root@w1 ~]# ~iworx/bin/domain-promoter.pex --pointer-to-primary --primary-domain testdomain.com --pointer-domain pointer.net[/SIZE]
[SIZE=2]The specified pointer domain does not point to the primary domain[/SIZE]
[SIZE=2]
Now I can see on the testdomain.com account it does have a pointer.net pointer domain.
How have you set the pointer domain, as an alias, redirect 301 or 302.
Sorry if I have redirects number wrong, it’s late here so doing it from memory
Also, what is your OS, or distro as some do not understand OS…
Were on latest version centos 6.5 64 bit
I suspect the failure is because the pointer does not exist to the domain, and as a test, if you setup a test domain, called as primary.url, add a pointer called pointer.url, set as alias, does this then work as expected.
If so, I’ll test using how you set the pointer, alias redirect 301 302 and let you know tommorow
I hope that helps but if you need it urgently, I would suggest open a support ticket and reference this post.
How have you set the pointer domain, as an alias, redirect 301 or 302.
Sorry if I have redirects number wrong, it’s late here so doing it from memory
Also, what is your OS, or distro as some do not understand OS…
Were on latest version centos 6.5 64 bit
I suspect the failure is because the pointer does not exist to the domain, and as a test, if you setup a test domain, called as primary.url, add a pointer called pointer.url, set as alias, does this then work as expected.
If so, I’ll test using how you set the pointer, alias redirect 301 302 and let you know tommorow
I hope that helps but if you need it urgently, I would suggest open a support ticket and referencethis post.
Many thanks
John[/QUOTE]
Hello,
The pointer is setup as a 301 redirect. The o/s is CentOs 6.5 64bit. The two domains do exist. I assume I can login straight to run the command or do I need to issue any further commands before it?
Many thanks, and I can confirm pointer domain set to either 301 or 302 do not work when using promoter pex.
As a work around, set the pointer domain to alias, run promoter pex and set the pointer domain back to 301 or 302.
I can only think that when the promoter pex was written, the pointer section did not have redirect 301 or 302, as I believe it was introduced in a later version of IW.
I am sure IW will be reading this post and hopefully will go on the roadmap.