Open Source

newsyslog: can’t notify daemon, pid 2090: No such process

I keep getting this message in my email, daily, at midnight UTC: newsyslog: can’t notify daemon, pid 2090: No such process This is generated by this entry: $ grep hp http /etc/newsyslog.conf /var/log/httpd-*.log 640 28 * $D5 BG /var/run/httpd.pid 30 This rolls over the log files for me. The message has been the same every day: pid 2090. However, there is no process with that ID: $ ps auwx | grep 2090 $ […]

newsyslog: can’t notify daemon, pid 2090: No such process Read More »

zfs send taking a while…

That ZFS send from yesterday, is taking more than 24 hours. Current status: in @ 53.7 MB/s, out @ 53.7 MB/s, 3892 GB total, buffer 100% full That’s about 4TB out nearly 13TB: $ zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT storage 12.7T 12.0T 739G 94% 1.00x ONLINE – Based on that progress, my prediction for completion is Thursday morning. On a related note, my pool needs to be upgraded:

zfs send taking a while… Read More »

zfs send from old file server

Earlier today, I started a zfs send | zfs receive between the old file server and the new file server. It won’t finish until early morning tomorrow. [root@kraken ~]# zfs send storage/compressed/bacula@2013.07.22:06:33 | mbuffer | ssh -t dan@10.5.0.20 ‘zfs receive system/usr/local/bacula/FromKraken’ Pseudo-terminal will not be allocated because stdin is not a terminal. in @ 54.9 MB/s, out @ 54.9 MB/s, 47.6 GB total, buffer 100% full Why mbuffer? Because it shows me some

zfs send from old file server Read More »

raidz2: 10 disks – half and half

Following up on last weeks comparison of 10 disks vs 8 disks on raidz2, it was suggested by Marie Helene that I try more HDD on the m/b. I’m here to report just that. I’ve put 5 HDD on the SUPERMICRO MBD-X8SIL-O Micro ATX Server m/b and five on the LSI SATA/SAS 9211-8i 6Gb/s. Here are the pg_restore times: 18m28.511s 18m32.359s 18m30.077s An average of 18m 30s. This is the slowest of all

raidz2: 10 disks – half and half Read More »

raidz2: 10 disks vs 8 disks

Yesterday, I mentioned I wanted to compare raidz2 when using 10 disks versus using 8 disks. Along the way, I noticed that my ZFS-setup script needed a change to cope with mixed devices. Once I got past that hurdle, I started adding packages and setting up the system for some very simple tests. The test My test of preference is loading a database, and then dumping it. Each pg_restore was done into a

raidz2: 10 disks vs 8 disks Read More »

Problem with disk numbering in my ZFS creation script

THe last system I set up with ZFS, I used a script. Today, when trying a system with different device types, I encountered a limitation of that script. I need to fix it. In the above script, NUM takes on the value of what digits appear in the string of I. Given that DISKS contains both ada0 and da0, two disks will get the same value for $I. That’s a problem. I need

Problem with disk numbering in my ZFS creation script Read More »

ZFS: raidz2 with 8 or 10 disks?

The traditional thoughts on ZFS are to have arrays which are a power-of-2 when it comes to number of disks. That means 2, 4, 8, etc. But for raidz1, that would be 3, 5, 9. For my choice of raidz2, it would be 4, 6, and 10. In the system I’m building up now, I have an 8-port LSI SATA/SAS 9211-8i 6Gb/s card. I can add two more HDD by attaching them to

ZFS: raidz2 with 8 or 10 disks? Read More »

Gateway getting old; File server getting full

My gateway is dying. My file server is getting full. Over the past few weeks, I’ve been dealing with aging infrastructure. My development server started acting up and was showing signs of age. This aging desktop box contained 80GB HDD, which means it’s probably 6 or 7 years old. That’s getting on in age. It’s been replaced by a much gruntier server. After completeing that work, I have to consider my gateway, which

Gateway getting old; File server getting full Read More »

Compiling bacula client gives link errors

I was trying to recompile sysutils/bacula-client on a FreeBSD 8.4 jail when I encountered some perplexing link errors. It took me a while to figure it out, but with the help of some IRC conversation, we figured it out. I started off by deleting the old (quite old) port: bacula-client-5.0.3 Then I recompiled: cd /usr/ports/sysutils/bacula-client && make install clean The errors in question are: I tried recompiling a few ports, such as gettext.

Compiling bacula client gives link errors Read More »

FATAL: could not create shared memory segment: Function not implemented

I recently upgraded a jail server from FreeBSD 8.2 to FreeBSD 8.4. This stopped various jails from starting their own instances of PostgreSQL. The messages in the logs were: Jul 9 14:48:48 building postgres[40785]: [2-1] FATAL: could not create shared memory segment: Function not implemented Jul 9 14:48:48 building postgres[40785]: [2-2] DETAIL: Failed system call was shmget(key=5432001, size=12099584, 03600). In my jails, I was seeing: $ sysctl security.jail.sysvipc_allowed security.jail.sysvipc_allowed: 0 Looking at my

FATAL: could not create shared memory segment: Function not implemented Read More »

Scroll to Top