NginUS's questions

I have a couple virtualized fileservers running in QEMU/KVM on ProxmoxVE.

The physical host has 4 storage tiers with significant performance variances. They're attached both locally and via NFS.

These will be provided to the fileserver(s) as local disks, abstracted into pools, and handling multiple streams of data for the network. My aim is for this abstraction layer to intelligently pool the tiers.

There's a similar post on the site here: Home-brew automatic tiered storage solutions with Linux? (Memory -> SSD -> HDD -> remote storage) in which the accepted answer was a suggestion to abandon a linux solution for NexentaStor.

I like the idea of running NexentaStor. It almost fits the bill.

NexentaStor provides Hybrid Storage Pools, and I love the idea of checksumming. 16TB without incurring licensing fees is a huge plus as well. After the expense of the hardware, free is about all my budget can handle.

I don't know if zfs pools are adaptive or dynamically allocated based on load, but it becomes irrelevant since NexentaStor doesn't support virtio network or block drivers, which is a must in my environment.

Then I saw a commercial solution called SmartMove: http://www.enigmadata.com/smartmove.html

And it looks like a step in the right direction, but I'm so broke I'd be wasting their time to even ask for a quote, so I'm looking for another option.

I'm after a linux implementation that supports virtio drivers, and I'm at a loss as to which software is up to it.

I ditched shorewall because it seemed overkill for the simple, unchanging ruleset this seems to call for.

I have 2 bastion firewalls in the rack between the host & each ISP.

The host contains an enclosure-bound VM which load-balances the 2 WAN connections and provides routing for multiple networks.

Since it also hosts the bridges, the VM host has an IP on each subnet that's connecting each bastion firewall to their own WAN port on the VM router.

The VM host doesn't need either of these connections other than to be able to provide the router VM access to the physical ports- the VM router provides the host's gateway & DNS.

The goal is to define rules which cause all inbound traffic on eth(n) and vmbr(n) use VM-WAN-IP-foo as a gateway, and all outbound traffic on eth(n) and vmbr(n) use bastion-fw-IP-bar as a gateway.

Also for eth(x) & vmbr(x).

Originally I thought I could do this with:

iptables -A INPUT -i eth(n) -s 0.0.0.0/0 -d 0.0.0.0/0 -j ROUTE --gw foo(n)

iptables -A OUTPUT -o eth(n) -s 0.0.0.0/0 -d 0.0.0.0/0 -j ROUTE --gw bar(n)

and

iptables -A INPUT -i eth(x) -s 0.0.0.0/0 -d 0.0.0.0/0 -j ROUTE --gw foo(x)

iptables -A OUTPUT -o eth(x) -s 0.0.0.0/0 -d 0.0.0.0/0 -j ROUTE --gw bar(x)

But that didn't take, so I must not be understanding correctly what I see in the manpage.

When I asked in the #netfilter IRC room someone mentioned that 'ROUTE' was depreciated, and to use -mangle instead. I would have never guessed that mangling would be needed for something like this.

Am I mistaken that this should be simple & straightforward?

I have a feeling there's an easier way to go about it that I'm just not aware of, maybe someone can enlighten me.

EDIT:

To put it another way, the VM Host is hosting these connection points, but isn't allowed to use them.

It and anything else that might find it's way onto those interfaces has to go around through the VM Router to reach the VM Host.

Here's a before & after drawing of what I mean:

|-------|               |-------|
| ISP-A |<--|           | ISP-B |<--|
|-------|   |           |-------|   |
            |                       |
            V                       V
        |-----------|           |-----------|
        | BASTION-A |<--|       | BASTION-B |<--|
        |-----------|   |       |-----------|   |
                        |                       |
                        |                       |           
                        |                       |
         VM Host        |                       |           
            |           |                       |
            |           |                       |
           \|/          |                       |
            V           |                       |
                        |                       |           
    ||=================\|/=====================\|/==========||
    ||              |---V---|               |---V---|       ||
    ||              |       |<----\   /---->|       |       ||
    ||              |       |      \ /      |       |       ||
    ||              | eth(n)|       V       |eth(x) |       ||
    ||              |       |       |       |       |       ||
    ||              |       |<--|   |   |-->|       |       ||
    ||              |-------|   |   |   |   |-------|       ||
    ||                          |   |   |                   ||
    ||                          |   |   |                   ||
    ||                          |   |   |                   ||
    ||              |-------|   |   |   |   |-------|       ||
    ||              |       |<--|   |   |-->|       |       ||
    ||              |       |       |       |       |       ||
    ||              |vmbr(n)|       |       |vmbr(x)|       ||
    ||              |       |       |       |       |       ||
    ||          |-->|       |<--|   |   |-->|       |<--|   ||
    ||          |   |-------|   |   |   |   |-------|   |   ||
    ||          |               |   |   |               |   ||
    ||          |               |   |   |               |   ||
    ||          |               |   |   |               |   ||
    ||          |               |   |   |               |   ||
    ||          |               |   |   |               |   ||
    ||          |               |   |   |               |   ||
    ||          |              /   / \   \              |   ||
    ||          |             V   V   V   V         |---|   ||
    ||          |           |---------------|       |       ||
    ||          |           |               |       |       ||
    ||          |           |               |       |       ||
    ||          |       |-->|    VM Host    |       |       ||
    ||          |       |   |               |       |       ||
    ||          |       |   |               |       |       ||
    ||          |       |   |---------------|       |       ||
    ||          |       |                           |       ||
    ||          |       |                           |       ||
    ||          V       V                           V       ||
    ||      |-------------------------------------------|   ||
    ||      |  WAN     LAN                         WAN  |   ||
    ||      |                                           |   ||
    ||      |                     VM Router             |   ||
    ||      |                                           |   ||
    ||      |                                           |   ||
    ||      |                                           |   ||
    ||      |  LAN     LAN     LAN     LAN     SAN      |   ||
    ||      |-------------------------------------------|   ||
    ||          ^       ^       ^       ^       ^           ||
    ||          |       |       |       |       |           ||
    ||          |       |       |       |       |           ||
    ||          |       |       |       |       |           ||
    ||          ,       ,       ,       ,       ,           ||
    ||        .*^*,   .*^*,   .*^*,   .*^*,   .*^*,         ||
    ||       (     ) (     ) (     ) (     ) (     )        ||
    ||       ((    ) ((    ) ((    ) ((    ) ((    )        ||
    ||        (  .)   (  .)   (  .)   (  .)   (  .)         ||
    ||         `~      `~      `~      `~      `~           ||
    ||                                                      ||
    ||                                                      ||
    ||======================================================||











|-------|               |-------|
| ISP-A |<--|           | ISP-B |<--|
|-------|   |           |-------|   |
            |                       |
            V                       V
        |-----------|           |-----------|
        | BASTION-A |<--|       | BASTION-B |<--|
        |-----------|   |       |-----------|   |
                        |                       |
                        |                       |           
                        |                       |
         VM Host        |                       |           
            |           |                       |
            |           |                       |
           \|/          |                       |
            V           |                       |
                        |                       |           
    ||=================\|/=====================\|/==========||
    ||              |---V---|               |---V---|       ||
    ||              |       |<----\   /---->|       |       ||
    ||              |       |      \ /      |       |       ||
    ||              | eth(n)|       V       |eth(x) |       ||
    ||              |       |       |       |       |       ||
    ||              |       |<--|   |   |-->|       |       ||
    ||              |-------|   |   |   |   |-------|       ||
    ||                          |   |   |                   ||
    ||                          |   |   |                   ||
    ||                          |   |   |                   ||
    ||              |-------|   |   |   |   |-------|       ||
    ||              |       |<--|   |   |-->|       |       ||
    ||              |       |       |       |       |       ||
    ||              |vmbr(n)|       |       |vmbr(x)|       ||
    ||              |       |       |       |       |       ||
    ||          |-->|       |<--|   |   |-->|       |<--|   ||
    ||          |   |-------|   |   |   |   |-------|   |   ||
    ||          |               |   |   |               |   ||
    ||          |     //============================//  |   ||
    ||          |    //                            //   |   ||
    ||          |   //  IP Tables Says: 'Detour'  //    |   ||
    ||          |  //                            //     |   ||
    ||          | //============================//      |   ||
    ||          |              /   / \   \              |   ||
    ||          |             V   V   V   V         |---|   ||
    ||          |           |---------------|       |       ||
    ||          |           |               |       |       ||
    ||          |           |               |       |       ||
    ||          |       |-->|    VM Host    |       |       ||
    ||          |       |   |               |       |       ||
    ||          |       |   |               |       |       ||
    ||          |       |   |---------------|       |       ||
    ||          |       |                           |       ||
    ||          |       |                           |       ||
    ||          V       V                           V       ||
    ||      |-------------------------------------------|   ||
    ||      |  WAN     LAN                         WAN  |   ||
    ||      |                                           |   ||
    ||      |                     VM Router             |   ||
    ||      |                                           |   ||
    ||      |                                           |   ||
    ||      |                                           |   ||
    ||      |  LAN     LAN     LAN     LAN     SAN      |   ||
    ||      |-------------------------------------------|   ||
    ||          ^       ^       ^       ^       ^           ||
    ||          |       |       |       |       |           ||
    ||          |       |       |       |       |           ||
    ||          |       |       |       |       |           ||
    ||          ,       ,       ,       ,       ,           ||
    ||        .*^*,   .*^*,   .*^*,   .*^*,   .*^*,         ||
    ||       (     ) (     ) (     ) (     ) (     )        ||
    ||       ((    ) ((    ) ((    ) ((    ) ((    )        ||
    ||        (  .)   (  .)   (  .)   (  .)   (  .)         ||
    ||         `~      `~      `~      `~      `~           ||
    ||                                                      ||
    ||                                                      ||
    ||======================================================||

I use nullmailer to forward root's mail to a smarthost.

When mail to root from mdadm reaches my inbox, syslog looks like this:

nullmailer[1502]: Trigger pulled.

nullmailer[1502]: Rescanning queue.

nullmailer[1502]: Starting delivery: protocol: smtp host: sub.domain.com file: 1289568895.4704

nullmailer[4706]: smtp: Succeeded: 250 2.0.0 Ok: queued as 36A595E4384

nullmailer[1502]: Sent file.

nullmailer[1502]: Delivery complete, 0 message(s) remain.

--

When mail to root from smartd fails, syslog looks like this:

smartd[4717]: Executing test of mail to root ...

smartd[4717]: Test of mail to root produced unexpected output (20 bytes) to STDOUT/STDERR: #012sh: mail: not found#012

smartd[4717]: Test of mail to root: failed (32-bit/8-bit exit status: 32512/127)

What's smartd doing differently?

Does anyone know how to resolve these init errors that happen from the Cyberpower powerpanel for linux package?

Ref: http://www.cyberpowersystems.com/products/management-software/ppl.html

-

I tried using nut instead, but it has issues, namely Debian bug 354429 that effectively disables syslog, and thus nut is not an option.

Ref: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354429

Output:

root@host:~# aptitude install foo

The following NEW packages will be installed:

  foo python-central{a}

The following packages are RECOMMENDED but will NOT be installed:

  whois

0 packages upgraded, 2 newly installed, 0 to remove and 1 not upgraded.

Need to get 0 B/144 kB of archives. After unpacking 1,016 kB will be used.

Do you want to continue? [Y/n/?]

Selecting previously deselected package python-central.

(Reading database ... 16630 files and directories currently installed.)

Unpacking python-central (from .../python-central_0.6.16+nmu1_all.deb) ...

Selecting previously deselected package foo.

Unpacking foo (from .../foo_x.x.x-x_all.deb) ...

Processing triggers for man-db ...

Setting up python-central (0.6.16+nmu1) ...

Setting up foo (x.x.x-x) ...

insserv: warning: script 'K99pwrstatd' missing LSB tags and overrides

insserv: warning: script 'pwrstatd' missing LSB tags and overrides

insserv: There is a loop at service pwrstatd if started

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Max recursions depth 99 reached

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service stop-bootlogd and mountnfs if started

insserv:  loop involving service mountnfs at depth 8

insserv:  loop involving service nfs-common at depth 7

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service pwrstatd and mountall if started

insserv:  loop involving service mountall at depth 4

insserv:  loop involving service checkfs at depth 3

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv:  loop involving service mountnfs-bootclean at depth 10

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv:  loop involving service networking at depth 6

insserv: There is a loop between service stop-bootlogd and udev if started

insserv:  loop involving service udev at depth 1

insserv: There is a loop between service stop-bootlogd and checkroot if started

insserv:  loop involving service checkroot at depth 2

insserv:  loop involving service keyboard-setup at depth 1

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop at service stop-bootlogd if started

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv:  loop involving service kbd at depth 12

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service pwrstatd and mountoverflowtmp if started

insserv:  loop involving service mountoverflowtmp at depth 7

insserv:  loop involving service mountall-bootclean at depth 6

insserv:  loop involving service hwclockfirst at depth 2

insserv:  loop involving service hostname at depth 3

insserv:  loop involving service mtab at depth 5

insserv: There is a loop between service stop-bootlogd and ifupdown-clean if started

insserv:  loop involving service ifupdown-clean at depth 5

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service stop-bootlogd and mdadm-raid if started

insserv:  loop involving service mdadm-raid at depth 3

insserv:  loop involving service mountkernfs at depth 1

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd andconfigured to not write apport 
reports therefore on system facility     `$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: exiting now without changing boot order!

update-rc.d: error: insserv rejected the script header

dpkg: error processing foo (--configure):

subprocess installed post-installation script returned error exit status 1

Processing triggers for python-central ...

Errors were encountered while processing:

 foo

E: Sub-process /usr/bin/dpkg returned an error code (1)

A package failed to install.  Trying to recover:

Setting up foo (x.x.x-x) ...

insserv: warning: script 'K99pwrstatd' missing LSB tags and overrides

insserv: warning: script 'pwrstatd' missing LSB tags and overrides

insserv: There is a loop at service pwrstatd if started

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Max recursions depth 99 reached

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service stop-bootlogd and mountnfs if started

insserv:  loop involving service mountnfs at depth 8

insserv:  loop involving service nfs-common at depth 7

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service pwrstatd and mountall if started

insserv:  loop involving service mountall at depth 4

insserv:  loop involving service checkfs at depth 3

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv:  loop involving service mountnfs-bootclean at depth 10

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv:  loop involving service networking at depth 6

insserv: There is a loop between service stop-bootlogd and udev if started

insserv:  loop involving service udev at depth 1

insserv: There is a loop between service stop-bootlogd and checkroot if started

insserv:  loop involving service checkroot at depth 2

insserv:  loop involving service keyboard-setup at depth 1

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop at service stop-bootlogd if started

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv:  loop involving service kbd at depth 12

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service pwrstatd and mountoverflowtmp if started

insserv:  loop involving service mountoverflowtmp at depth 7

insserv:  loop involving service mountall-bootclean at depth 6

insserv:  loop involving service hwclockfirst at depth 2

insserv:  loop involving service hostname at depth 3

insserv:  loop involving service mtab at depth 5

insserv: There is a loop between service stop-bootlogd and ifupdown-clean if started

insserv:  loop involving service ifupdown-clean at depth 5

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: There is a loop between service stop-bootlogd and mdadm-raid if started

insserv:  loop involving service mdadm-raid at depth 3

insserv:  loop involving service mountkernfs at depth 1

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: Starting pwrstatd depends on stop-bootlogd and therefore on system facility 
`$all' which can not be true!

insserv: exiting now without changing boot order!

update-rc.d: error: insserv rejected the script header

dpkg: error processing foo (--configure):

 subprocess installed post-installation script returned error exit status 1

Processing triggers for python-central ...

Errors were encountered while processing:

 foo



root@host:~# dpkg -r powerpanel

(Reading database ... 16715 files and directories currently installed.)

Removing powerpanel ...

Stopping  pwrstatd 1.1.4.

uninstallation accomplish!

Processing triggers for man-db ...

root@host:~# aptitude install foo

The following partially installed packages will be configured:

  foo

No packages will be installed, upgraded, or removed.

0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Need to get 0 B of archives. After unpacking 0 B will be used.

Setting up foo (x.x.x-x) ...

Processing triggers for python-central ...



root@host:~# dpkg -i powerpanel_1.1.4_amd64.deb

Selecting previously deselected package powerpanel.

(Reading database ... 16694 files and directories currently installed.)

Unpacking powerpanel (from powerpanel_1.1.4_amd64.deb) ...

Setting up powerpanel (1.1.4) ...

Starting pwrstatd 1.1.4.

Installation accomplish!



Processing triggers for man-db ...

root@host:~#

I have a Debian Squeeze (2.6.32-5) guest in KVM that has all virtio network interfaces, and their MACs are apparently blacklisted by udev as per /lib/udev/rules.d/75-persistent-net-generator.rules such that /etc/udev/rules.d/70-persistent-net.rules is not generated.

I tried making a /etc/udev/rules.d/010_netinterfaces.rules file to define eth(foo) per MAC(foo), but it was ignored.

So now I'm unable to explicitly define interface names.

Can someone advise as to how the /lib/udev/rules.d/75-persistent-net-generator.rules needs to be edited whitelist these MACs?

I have a netbook with not much power, 1GHz CPU & 1G memory. I'd like to install a headless linux to it, either Debian or TinyCore, both of which use aptitude & dpkg.

I'm not sure which package has a server to run in Debian and a client that can run in Windows to send a USB device on that box over the network to a virtualized Windows environment.

I'm having a problem with a couple 10GB NICs, one in particular in Windows 7 x64 that always thinks the cable is missing. The drivers for the NIC are current, downloaded from Intel- it's settings are defaults, although I did set an IP address once to see if it helped, and it didn't.

The cards I'm using are both the same, hybrid Dell / Intel. Dell Part Numbers T645H, Intel Models 82598.

The cable I'm using between the cards is a Cisco SFP-H10GB-CU3M.

I found this information helpful from Intel.com regarding which SFP+ cables will work with that card: www.intel.com/support/network/adapter/10gbe/afdadualserver/sb/CS-029097.htm

It mentions the cables have to comply with certain specifications to function properly, and according to the product page for the cable I have, they match and should be working.

Cisco cable details: www.cisco.com/en/US/prod/collateral/modules/ps5455/data_sheet_c78-455693.html

I saw this relatively cheap switch on eBay, (Item number: 370424159424) and considered buying that to see if the problem has to do with the cable not being a 'crossover' cable per se.

I'm hesitant to do that since the description mentions it having SFP ports, rather than SFP+ ports, and I'm not sure of the ramifications of mixing these, since I'm early in the learning curve of 10GB.

I'm not certain what to do next, I don't want to have to buy a switch to go between, plus another cable- it seems very expensive just to make a single fast link.

Thanks in advance, your feedback is appreciated.