I'm using rsyslog to forward syslog entries from a pile of servers to Loggly
The configuration looks something like this:
# Config for loggly upload
*.* @@logs.loggly.com:12345
This works, but because it's forwarding, any log entries which occur when there isn't an internet connection never make it to loggly.
Is there anyway I can configure rsyslog to "hold" log entries until an internet connection is established, and then send them? Or is there another tool I should be using for this?
To manage the configuration of a server, I keep some configuration flies (located in /etc) under version control (in the home folder) and then symlink to them from their /etc locations:
/etc/someprog/c.conf -> /home/ubuntu/etc-config/someprog/c.conf
Is this a reasonable approach? Any potential downsides?
I have a server running Ubuntu 11.04, deployed in the field. When someone is debugging the server, they plug eth1 in, but the rest of the time, nothing is plugged into eth1. The syslog is full of DHCPDISCOVER requests from dhclient trying to find a connection. Is there any way I can configure dhclient to only run DHCPDISCOVER a fixed number of times?
Syslog entries every:
Nov 2 07:58:32 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
Nov 2 07:58:35 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Nov 2 07:58:39 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
Nov 2 07:58:47 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
Nov 2 07:59:02 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
Nov 2 07:59:15 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
Nov 2 07:59:29 sensor-2bb8 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Nov 2 07:59:33 sensor-2bb8 dhclient: No DHCPOFFERS received.
Nov 2 07:59:33 sensor-2bb8 dhclient: No working leases in persistent database - sleeping.
Contents of /etc/network/interfaces:
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth1
iface eth1 inet dhcp
I have a ubuntu server that I suspect failed due to overheating. I'm doing a post-mortem and I'm not exactly sure what to look for to confirm my hunch.
Any thoughts on what logged information would indicate a failure from overheating?