185 reputation
9
bio website
location
age
visits member for 2 years, 6 months
seen May 18 '13 at 17:37

Nov
12
comment website connection reset on first load
I have updated my original post with default.conf and nginx.conf. The error I get when I I turn debugging on in nginx says that the client prematurely terminated the connection. this results in those 400 bad requests errors also. How might I go about watching it at server level?
Nov
12
comment website connection reset on first load
It is happening in all browsers.
Oct
11
comment Send input to background process
This is a loginserver. I can send commands to shutdown worlds for a game I'm hosting. The commands are interpreted by the loginserver, so they can really be whatever. Shutdown was just an example.
Oct
11
comment Send input to background process
Just text. Commands like 'shutdown 10' where 10 is the number of minutes before it shuts down.. etc. I've also tried echo "shutdown 10" > /procs/pid/fd/0 with no success. The bg/fg works but only in the same ssh session.
Sep
25
comment Game login server
The accounts are the same for the game and the website. The game will have another database for character information that won't need to be accessed from the web server.
Sep
13
comment DNS/Nameserver issue. Can't ping IP or domain
can't ping anything at all, even IP addresses.. under any circumstance :(
Sep
13
comment DNS/Nameserver issue. Can't ping IP or domain
It resolves when I have nameserver 127.0.0.1 in resolv.conf, otherwise, nope. The only thing in /etc/host.conf is 'multi on'.
Sep
13
comment Server tries to resolve domains through itself
How is that possible? I do netstat -an | grep ^udp | grep 53 and have listening on both 127.0.0.1:53 and serverip:53
Sep
13
comment Server tries to resolve domains through itself
Both of them say connection timed out; no servers could be reached
Sep
13
comment Server tries to resolve domains through itself
@ShaneMadden updated question with requested output
Sep
13
comment Server tries to resolve domains through itself
I put part of my named.conf in my question to show that I do have recursion enabled for internal and local resolver
Sep
13
comment Server tries to resolve domains through itself
I've edited with some more information.. though I don't know how to format it.
Sep
13
comment Server tries to resolve domains through itself
The question is why is it doing this? I know this isn't normal behavior. I can resolve domain names to IP addresses but I cannot ping domains or IP addreses. I also get constant servfails in tcpdump although people are able to connect to my site and interact with it as usual.
Jul
21
comment Using port 80 for web server adds weird query string
I've been completely unable to find anything about this COLLCC query string on Google, besides a few Chinese websites that have been affected by the same problem. It(my site) was working without problems earlier today but has since started this behavior at around midnight PST.
Jun
23
comment Can /etc/hosts.deny/allow be overridden?
Sorry about that. If my question is answered within the 7 minute limit I often forget to go back and accept answers.
Jun
12
comment Connection established to google DNS, can't resolve any hosts
updated with packet capture pinging google.com. with dot at the end gives same results
Jun
11
comment ping: unknown host google.com
Yes, I can ping them. It's weird because I've been using google DNS ever since we switched to this server like 2 months ago with no problems. I emailed them and asked about a default DNS server. My host does have a hardware firewall but I can't imagine why it would start happening just now.
Jun
11
comment ping: unknown host google.com
dig and nslookup always fail to connect to host no matter what arguments I use. this is the tcpdump command i used: tcpdump -n not port ssh and not port 4838 and not port 80 and not port 6667 I have stopped iptables, restarted and made sure port 53 was allowed etc. I can ping all IP addresses fine but no domains resolve.
Jun
11
comment ping: unknown host google.com
Here is the output of route -n server_ip 0.0.0.0 255.255.255.0 U 0 0 0 em1 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 em1 0.0.0.0 server_ip 0.0.0.0 UG 0 0 0 em1
Jun
9
comment Apache redirecting requests to port 23
Also there is nothing in apache error log to suggest that a script injection is at fault.. Only errors in there are 404s because of some favicons that i haven't updated.