UPDATE - Because of the infrastructure changes from the acquisition, there was an IP address conflict. Once that was identified, the behavior stopped, as traffic could consistently be routed to the correct location. Thank you all for your help.
I have a Virtualized Centos 6.2 FINAL server. The intent of the machine is to run Jenkins on Tomcat for automated builds. As my company was acquired, the network infrastructure changed and so some of the configuration was changed as well. I can go into the history more if needed, but for now, I'll focus on my actual symptoms.
- The machine, if attempted to be interacted with via network over ssh or http, does not respond typically.
- The machine, if logged into directly, will interact with machines. However, it seems to take a bit to finally start conversing. That is, when I run a traceroute from the vm to my local machine, it takes a few iterations. Same with ping - it can take up to 6 iterations before the packets begin to make it through.
- Once the machine is conversing with other machines, outside contact is achievable. I can ssh to it, and the Jenkins application will respond over http.
- The communication will eventually cease however and return to the initial first state where outside contact is not possible, until I directly interact with the machine to cause it to communicate with the outside world (2).
I'm at a bit of a loss to understand what to look into from a diagnostic perspective. As I said earlier, there was some history here. The machine originally had one network adapter with an ip address assigned via DHCP. Then one additional network adapter was added, and the ip address was assigned statically. Now there is only one network adapter with the ip address assigned statically.
I've looked at other threads out on the Internet that talk about various commands that can help diagnose, but I'm not sure how to read them.
I imagine this isn't enough information to make a diagnosis (though would be grateful if it was!) so I will appreciate further reading materials, steps to take, or clarifying questions.
Thanks so much for your time.