Loading Profile...
Replacing third host with a new one makes apache buggy...
I'm using VHX 2.0.6 with MAMP 1.8.2 and Snow Leopard. I have no license so I'm limited to three hosts. Now I removed a host and replaced it with a new one but then Apache shuts down and in Test Configuration I get a port 9002 conflict. Apache won't restart until I remove the new host. I can add the old host back and Apache is OK but the new host is the problem.
Is this because I have no license (planning to buy one in the next couple of days) or another bug...
when I enable Network Share in VHX the old AND the new host (although it is removed from VHX) is visible in BonjourFoxy
EDIT:
did some thourough testing.
The problem occurs when I add a third host AND enable Network Share, then Apache shuts down. If I don't enable Network Share then everything is fine, although the removed host still appears in BonjourFoxy
any help appreciated
grtz
Greg
Is this because I have no license (planning to buy one in the next couple of days) or another bug...
when I enable Network Share in VHX the old AND the new host (although it is removed from VHX) is visible in BonjourFoxy
EDIT:
did some thourough testing.
The problem occurs when I add a third host AND enable Network Share, then Apache shuts down. If I don't enable Network Share then everything is fine, although the removed host still appears in BonjourFoxy
any help appreciated
grtz
Greg
I’m troubled
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?It sounds like one of the extra hosts VHX creates to enable network sharing got stuck "on". Definitely a bug. I'll check into the problem tonight and try and get a fix out soon.
-
Inappropriate?Maybe a conflict between the two files "hosts" and "httpd-vhosts.conf" in "Library/Application Support/VirtualHostX" and those in "/etc/..." or where they normally reside.
or
maybe a bad update from VHX 1.0 to VHX 2.0 (did that yesterday).
I also removed XAMPP and replaced it with MAMP -
Inappropriate?Tyler, have you found a solution?
BTW, I just paid for a license ;) -
Inappropriate?another update:
Tyler, I'm now fully licensed with VHX 2.0 and added my extra hosts. They all work fine WITH Network Share EXCEPT for my third host.
Originally I had it pointing to MAMP's localhost folder (htdocs) but I changed it to another xxxxx.dev site. So the conflict is with port 9002
My Test Configuration report:
[Thu Sep 24 14:17:47 2009] [warn] _default_ VirtualHost overlap on port 9002, the first has precedence
Syntax OK
I hope this helps in some way...
keep on the good work ;)
Greg -
Inappropriate?Tyler,
I found the problem but not the cause....
the problem was a double entry in etc/apache2/extra/httpd-vhosts.conf
twice an entry on port 9002 as the Test Configuration clearly stated.
So I opened that file in Terminal and edited the entries.
Now I can enable Network Share on that host and Apache doesn't shutdown anymore.
Why that entry wasn't properly deleted when I deleted the host in VHX, I don't know but now I'm a happy camper ....
grtz
Greg
I’m happy
-
Inappropriate?Had another "issue" yesterday.
Added a new host in VHX and my httpd-vhosts.conf (the one in etc/apache2/extra) was messed up again. My first entry on port 9000 was partially deleted.
Can someone explain me what the use of "hosts" and" httpd-vhosts.conf" in both "etc/..." and "application support/vitualhostx" is -
Inappropriate?The files in "Application Support/VirtualHostX" are just temporary files that VHX uses. They have no effect on your system.
EMPLOYEE
