It has been explained many times over the internet, so I won’t cover that. One thing you have to pay attention to is, if you run snmptt as a daemon, be sure that it has the right to write to Nagios FIFO. On my Debian system, I had to run snmptt as nagios user. Then, when you convert the MIBs to snmptt.conf file format, sometimes it will fail because the MIB is not RFC compliant. Most of the times, object definitions contain underscores (_) or dots (.) . Just sed them. ...
After a few hours spent trying to find why Ubuntu 12.04 would not download a preseed file while netbooting, I stumbled upon this bug https://bugs.launchpad.net/ubuntu/+source/casper/+bug/923219 . I needed to add “IPAPPEND 2” after the APPEND directive in the pxelinux config file. Great.
Just as a reference for future needs. To resize a zvol exported as an iSCSI LUN to a Windows OS, you need to change the zvol size, then change the “iSCSI backend” the LUN changed size and then do a disk rescan on your Windows initiator. Commands are: zfs set volsize=1T tank/volume sbdadm modify-lu -s 1T <GUID of the volume> Then on Windows, go to Server manager, choose Storage, right click on Disk management and select rescan. You should see some allocated space on the disk. Source: https://www.growse.com/news/comments/growing-an-ntfs-iscsi-volume-that-s-hosted-on-zfs/ ...
After a few weeks using FreeNAS 8.3.1, I noticed I could not create new volumes because the pool was out of space. The problem was that I should have had enough space, by a long shot. In fact, one of my “block” volumes was taking space more than twice it’s size. I had other volumes that seemed unaffected (or less affected), the only difference was that the problematic volume had volblocksize=8k set . ...
Update: I just saw that since April 25th, SQL Server 2012 and Windows Server 2012 are supported by VMware vCenter 5.1U1 . All information is available here : http://blogs.vmware.com/vsphere/2013/04/vmware-vcenter-server-5-1-update-1-released.html Original November 21th 2012: While it is working with the SSO service, vCenter and vCloud Director, it just doesn’t work with Update Manager service. Well, at least with the SQL Server native client v11. Then Update Manager service just doesn’t start and throws an unhelpful 1067 Error. ...
So, here’s a short checklist of what to do right after I install FreeNAS 8.3 (not necessarily in order). configure link aggregation (LACP seems to work with 2 switches, failover or other algorithms don’t) change admin and root password enable ssh with root password when LAN is secure configure SMART tests (monthly long test) configure general settings (timezone, syslog, email server) create zpools with lzjb compress, atime off and no deduplication create zfs datasets and volumes and inherit options active directory synchronization iSCSI targets and stuff SMART checks enable SNMP
I’ve just got my hands on a new server to store backups and archived files before being sent offsite, and it wouldn’t boot off my USB key. Even after many dd, dd with skip and FreeNAS installations, I was getting a “GPT table corrupt” message. Finally, the fix was easy enough: boot FreeNAS installation CD and choose Shell instead of Install type gpart show, it listed my device and that GPT table was corrupt type gpart destroy -F <thedevice> return to the menu choose Install when it’s finished, go back to the shell type gpart show again to check that it’s not corrupt anymore reboot enjoy your FreeNAS That’s it. ...
Last week, I saw an huge “spam” outbreak on my MX servers. Instead of ~200k rejected SMTP connections, I had ~3M connections and it was rising. This caused some minor issues with the frequent log parsing as the log file quickly grew. To reduce the log file size and also the DNS requests number, I decided to use fail2ban to drop the connections before they got to Exim. This is rather easy, just create/append /etc/fail2ban/jail.local with the following: ...
If you use Varnish with an Apache server and analyze Apache log files (with AWstats or something else), you probably saw all requests were coming from 127.0.0.1 (or the IP address Varnish is on). You’ve probably forgotten to change the LogFormat you use. Fortunately, Varnish adds an header on its request to Apache with the remote IP address in it. Just replace “%h” with “%{X-Forwarded-For}i” in the LogFormat and reload your server. ...
I needed to install some incoming mail servers (MX servers) to filter emails before delivering them to customers servers. So the need is to accept mails for a fixed list of domains, check for viruses and spams, then route them to customers servers for delivery. The distribution is Debian 6, the mailserver is Exim. The antivirus check is done by ClamAV and the antispam with Spamassassin + Pyzor + Razor + DCC + DNSBL. I get the list of domains from the f*cking OSS/BSS/whatever software. ...