After editing files in my development environment and saving them to my guest OS (CentOS), the Guest delivers a cached version of the edited files (.css or .js).
At first I thought this was a local browser caching issue, but I've deleted, disabled, incinerated, etc every local cache in all 4 browsers and in the laptop (non-host) hard drive.
In addition, I tested using a machine (that has never accessed the guest) and the guest still delivered the unedited files.
I've then disabled all caching modules in Apache - I'm pretty sure (but not positive - and open to any suggestions) Apache is not the culprit.
Either my guest or my host is caching files somehow/somewhere and I can't figure out how or where.
This has been a very frustrating 48 hours - any help would be greatly appreciated.
Background:
VirtualBox v 4.0.12
Guest: CentOS 5.5/LAMP (Being used as a local development server) Internal IP 192.168.12.62
Host: Windows Server 2008 (Network Config: Bridged) Internal IP 192.168.12.42
Development files are stored on the Host and shared with the Guest via "Shared Folders"
Application development is done on a third machine (laptop) connected to the host via mapped network drive. Internal IP 192.168.12.32
I've configured Apache with numerous virtual IP's 192.168.12.150-180
Please let me know if I've left anything out.
This forum post confirms the problem. Here's the bug report. Vboxsf doesn't play nicely with sendfile. The Apache workaround, as previously mentioned:
EnableSendFile Off
For the curious, here's the SendFile docs.
Related
I have an older dedicated PC running on my home network as a webserver. Trying to retire it by replacing it with a VM on a brand new workstation Santa brought me. Simple home hobbyist network consists of router, 10Gb switch and of course computing devices off of that.
The new machine is running Windows11 Pro, and via Hyper-V I have a CentOS 7 VM. I've configured the firewall to enable http service (and port 80) being accessible from outside my network. I'm running httpd. From behind my router/switch I can access the web server with no problem, from the host machine and other machines on my network). Alas - I'm unable to access this web server remotely/externally - even after turning of the VM's firewall and ensuring port forwarding was properly pointing to IP:80 from my router. I have been scouring the web/forums/etc. for days now - nothing I've tried seems to work.
Also, I was careful in ensuring the Hyper-V settings for a virtual switch are pointing to my actual hardware NIC and set accordingly as found here and other forums (see attached image for details).
From all the "experimentations" I've tried - it's seems like the port is just not being forwarded from my router properly. So it's really pointing towards my router at this point. BUT - I can and have configured real hardware before (over decades) with no problem. Since I'm NEWB to Hyper-V and VM's - I'm worried some setting may not be correct.
Thus - reaching out to anyone with similar experience who's solved this problem. Thanks in advance.
Here's a graphic in which I captured some of the many things I've tried to no avail.
settings, etc.
I have reinstalled wamp server and my project is running very fast than before. All that different is there is no tmp file in tmp folder (which was of 34GB!!)
Apache maintains website access and error logs that can grow in size very quickly. PHP also has similar logs (if enabled via configuration).
C:\WampDeveloper\Logs
C:\WampDeveloper\Temp
Once Apache log files grow in size to above several 100 MB, performance issues can arise.
Also the Temp folder holds lots of session and temporary data files that don’t get properly cleaned up, which causes it’s own issues.
To speed up Read this WAMP is Running Very Slow, This will have this points
Windows Hosts file
IPv6
Firewall and Anti-Virus software
Power Plan
Local Issues
YOUR BROWSER
Clear Your WAMP Log Files
Apache
MySQL
etc...
Ok, I have a quick question to ask all the veteran Wamp users on this board.
At work, we are currently working on a web application. We are trying to use Wamp to design everything, but we have a problem. All the computers right now have wamp installed to the default location (C:/wamp).
Our problem is, we all want to have access to the same MySQL database so we can edit it at the same time. Right now, only one person can edit it at a time to prevent losing the work of someone else.
When done, we just dump the mySQL folder onto a network drive so whoever wants to edit it next can take it and use it.
This isn't very time efficient, so we're wondering if its possible to install Wamp directly to a network drive in some way. We tried doing it just now but we can't get Wamp to start services.
So any type of advice will be helpful
i think these two thing would help you :
1: install wamp in only one system then in apache configuration file listen to his lan ip in order to others can access it in this way you have just one database server
2: as you've installed wamp to all systems choose one system's database as main and in mysql configuration define a new server wich server's ip is that system's lan ip
then users instead of using localhost for connecting to mysql will use that ip
I am migrating my vCenter Server 5.5 to a new server (databases have already been moved to a new SQL server and all is OK on existing vCenter Server 5.5 implementation). When I begin the simple install process on the new vCenter Server host the Single Sign-On component presents me with an IP address of 10.10.10.117 as the ip address of the FQDN file01.xxxxxxxxx.com. This is the iSCSI interface address. I need it to use the 10.1.1.17 ip address that is the address of the production NIC that the ESXi 5.5 hosts will be communicating with. I have already changed the binding order of the NIC cards and flushed the DNS cache. I also added file01.xxxxxxxx.com with the proper IP address to the hosts file and also file01 to the hosts file. Still, during the install, 10.10.10.117 is discovered. Thanks in advance! Babak C.
Just to get a quick clarification...are you freshly installing vCenter 5.5? Or are you migrating an existing vCenter server to a new host and using the update utility to upgrade? I am assuming you are doing a fresh install based on your details about the SQL server and SSO. Here is my suggestion, in case it is a fresh install.
We had a similar problem with 5.5 on a new install where the IP address that was discovered during the actual vCenter Server install was that of the public facing NIC which we never use for management traffic (it's for internet access on the vC server, for update manager, etc.)
The strange thing is that there had NEVER been an entry in ANY of our DNS servers for that interface. So, after looking into it a little bit, I started thinking the IP that was returned during install was not a DNS result at all. Rather, it was (most likely) simply gathered from the interfaces on the Server based on binding order (e.g. which NIC has the default gateway.)
In order to save having to uninstall and clean up a major mess if the install completed wrong, we stopped and got in touch with VMware support. They suggested we clear all of the temporary files both in the standard "temporary" folder on windows as well as under /ApplicationData/vmware/xxx, where 'xxx' would be whatever product is giving you trouble and HAS NOT been FULLY INSTALLED* (e.g. you started the install and noticed the incorrect IP, so you terminated the installer and there is metadata and cached files remaining from the partially run install).
Basically, what we had to do, was clear the temporary files and then make sure the NIC Binding Priority was correct (so you should check in Network Adapters|(press-alt)|Advanced Settings. Make sure the correct binding is checked (e.g. if you don't use IPv6 on the private network, clear it) and make sure that the Windows Network is at the top of the priority list on the second pane of the advanced settings. This helps tremendously with SSO by making sure the Windows Network stack is the first queried when you are signing in and SSO must submit a kerberos ticket to the AD DC for validation.
It is possible, that once you delete the partial install files and temporary files and fix the network settings (probably be a good idea to reboot as well), the next time you run the installer you might have success.
I will try to check this post later to see if it helped you at all... or it I just succeeded in making your life even more difficult (which I certainly hope not!) :)
One more thing...prior to initializing the installer, open up a PS session, perform ipconfig /flushdns and then ping the hostname of your vCenter server in order to get it in the DNS cache. You should also perform the following:
nslookup
NS>{your vcenter server IP address}
/* make sure the resulting hostname is correct..this ensures your PTRs and rDNS is working correctly. vCenter HEAVILY relies on accurate reverse DNS configuration...then do the following lookup for forward DNS */
NS>{your vcenter server FQDN}
Hope it helps. Best of luck my friend!
SIETEC
I am a GIS tech trying to get migrate to Geoserver, unfortunately I am not very savvy on web hosting.
I installed the Windows version 2.3.1.
I was able to build by map and access it through localhost:8080\geoserver\www\
I take that to mean that the jetty server it working.
I understand that I should be able to replace my local IP address where "localhost" is and be able to access it from another computer via Http.
I can't figure out the next step. I have found great tutorials on every part of geoserver process except this. And the user guide does not get into this either.
My set up: Cable Modem > Router > PC with Geoserver
What I have tried: Setting up a virtual server on my router. I have tried changing by router to inbound port 8080 to private port 8080
I also tried 80 to 8080
and 80 to 80
I also tried windows firewall exception. and turning off windows firewall.
I read about using appache tomcat but I have not installed it because it seems that jetty is working (at least as a local host) and I don't want to put another program on 8080. And to my understanding it can work stand alone but I really honestly don't know no.
I am must be missing some vital piece of information on how to do this. I am hoping it is just so basic that it wasn't worth mentioning on tutorials.
Thanks
Karin
This would be a GeoServer configuration question, but since its deployed in jetty the solution is likely in the underlying jetty configuration. That being said it is a guess on my part (the jetty side of things) how they set up this distribution, but if you find a jetty.xml file, perhaps under an /etc directory then you should be able to edit that file and set a proper host in the configuration.
Seriously though, this has to be a pretty common GeoServer question so I bet they have some documentation floating around for setting this properly in their software distribution.
http://docs.geoserver.org/latest/en/user/webadmin/basics.html
That seems to indicate it might be dependent on your container configuration, in which case look through how ever they are configuring jetty for a Host setting that is likely hardcoded to 'localhost'