MattBianco's questions

In a shell script, we currently call /usr/sbin/pcs status cluster and then grep -qE for 'Current DC:.*partition with quorum' to find out if the cluster is fine.

I would like to know if there is a quicker way, because pcs status cluster makes it query all nodes for their PCSD status, which takes time, about a second and a half, and I want to do this check before doing certain operations which are to be done quite often.

Would pcs status nodes both and counting the number of online nodes be equally good for deciding if the cluster is functioning without issues?

This takes ~2 seconds: pcs status cluster 2>&1 | grep -qE 'Current DC:.*partition with quorum'

This takes ~0.2 seconds: pcs status nodes both | grep -cE 'Online: [a-z]+ [a-z]+ [a-z]+'

(The cluster has 5 nodes, hence the three node names in the regular expression).

EDIT:

This takes ~0.02 seconds: corosync-quorumtool 2>&1 | grep -q -E '^Quorate:.*Yes$'

Thank you Matt Kereczman!

I would like to have a reverse proxy (apache httpd with mod_proxy) in front of an IIS hosting a SOAP Web Service.

The problem I'm facing is that the SOAP clients ask the web server for the details about the web service by downloading the WSDL from the endpoint. This WSDL is generated by the web service and it contains the URLs to the web service that the client should use. The problem is that when the web service is behind the proxy, the generated URLs contain the wrong, private, address.

the IIS web service is located at http://internal.host.com/Dirname/Service.asmx and it can be called with GET or POST.

The WSDL is retrieved with GET with WSDL as the query string:

http://internal.host.com/Dirname/Service.asmx?WSDL

The reverse proxy presents the web service as:

https://proxy.host.com/VirtualDir/Service.asmx

And my problem is that the contents of the dynamically generated WSDL contains the internal URLs (that the proxy connects to).

I would like to avoid hacking/recompiling the web service itself, so when I was thinking of alternative solutions, I wondered this;

Could I make httpd on the proxy server somehow intercept the call to the ?WSDL document and serve static content instead, and still forward other queries (including GET parameters) to the internal IIS server?

The relevant httpd config currently looks like this:

ProxyPass "/VirtualDir/"  "http://internal.host.com/Dirname/"

And I was thinking that perhaps RewriteCond and RewriteRule could be used in some clever way to catch only the requests to the /.../Service.asmx?WSDL and serve a static local document instead, and forward "the rest" to the IIS, but I don't really know how to do that correctly without breaking anything else.

The reverse proxy is used for other services as well, under other virtual "directories".

I'm running two pacemaker clusters on the corosync stack on CentOS 7 with all packages up to date with the distro release/updates packages.

Both clusters shows no cluster name with the command pcs status: Like this:

Cluster name:
Last updated: Mon Nov  3 09:55:58 2014
Last change: Fri Oct 31 11:09:22 2014 via cibadmin on beaker
Stack: corosync
Current DC: scooter (2) - partition with quorum
Version: 1.1.10-32.el7_0.1-368c726
5 Nodes configured
21 Resources configured

There is a cluster_name: entry in the totem section of /etc/corosync/corosync.conf, but I can't find anything related to the cluster name in the pacemaker CIB.

The clusters were created with pcs cluster setup --name clustername node1 node2 node3 node4 node5 (with clustername being the intended name of the cluster).

The /etc/corosync/corosync.conf is world-readable, as well as the directories above it.

The login page of IBM's web interface to its document archive software "Content Manager OnDemand" doesn't load on Internet Explorer 11.

The web application is built on the dojo framework.

What could be the cause of this?

I have an AIX 6.1 volume group called arscachevg. It is a few terabytes big and consists of 15 physical volumes. When I try to extend it with a new physical volume, I get this error:

0516-008 extendvg: LVM system call returned an unknown
    error code (-267).
0516-050 extendvg: Not enough descriptor area space left in this volume
    group. Either try adding a smaller PV or use another volume group.
0516-792 extendvg: Unable to extend volume group.

I always thought that scalable VGs had no practical limitations!

Some info from lsvg on the volume group:

PP SIZE:            256 megabyte(s)
MAX PVs:            1024
TOTAL PPs:          13185 (3375360 megabytes)
FREE PPs:           570 (145920 megabytes)
USED PPs:           12615 (3229440 megabytes)
QUORUM:             8 (Enabled)
MAX LVs:            256
LVs:                11
OPEN LVs:           11
TOTAL PVs:          15
ACTIVE PVs:         15
MAX PPs per VG:     262144
LTG size (Dynamic): 256 kilobyte(s)

Anyone that can explain why this fails? The new disk is 350 GB.

I even tried chvg -t2 arscachevg, but it is not a valid command on a scalable VG:

0516-1781 chvg: The t option is not valid for volume groups of the Scalable Volume Group type.
0516-732 chvg: Unable to change volume group arscachevg.

Very grateful if there are any AIX-LVM gurus out there that can shed some light on this. Thanks!

I have an IPv4 setup of postfix on RHEL6 with SElinux in enforcing mode. All my attempts at incorporating opendkim fails miserably unless I leave enforcing mode.

The errors I get when SElinux is enforcing:

Jan 25 09:57:25 <mail.warning> katniss postfix/cleanup[16571]: warning: cannot receive milters via service cleanup socket socket
Jan 25 09:57:25 <mail.crit> katniss postfix/cleanup[16571]: fatal: cleanup_milter_receive: milter receive failed
Jan 25 09:57:26 <mail.warning> katniss postfix/smtpd[16567]: warning: cannot send milters to service public/cleanup socket
Jan 25 09:57:26 <mail.warning> katniss postfix/master[16559]: warning: process /usr/libexec/postfix/cleanup pid 16571 exit status 1
Jan 25 09:57:26 <mail.warning> katniss postfix/master[16559]: warning: /usr/libexec/postfix/cleanup: bad command startup -- throttling

What I've done recently:

setenforce permissive

(sending mail works)

setenforce enforcing

(sending mail fails with cleanup errors above)

egrep -e 'postfix|opendkim|cleanup' /var/log/audit/audit.log | audit2allow -m postfixMine > postfixMine.te
checkmodule -M -m -o postfixMine.mod postfixMine.te 
semodule_package -m postfixMine.mod -o postfixMine.pp
semodule -i postfixMine.pp

(sending mail still fails with the same errors from cleanup above)

So, everything works as expected with permissive SElinux setting, and fails with enforcing setting.

in postfix main.cf:

smtpd_milters           = inet:127.0.0.1:8891
non_smtpd_milters       = $smtpd_milters
milter_default_action   = accept
milter_protocol         = 2

some info:

# netstat -napl | grep 8891
tcp        0      0 127.0.0.1:8891              0.0.0.0:*                   LISTEN      16464/opendkim      

# ps -ef|grep opendkim
opendkim 16463     1  0 09:56 ?        00:00:00 /usr/local/sbin/opendkim -x /etc/opendkim.conf -P /var/run/opendkim/opendkim.pid
opendkim 16464 16463  0 09:56 ?        00:00:00 /usr/local/sbin/opendkim -x /etc/opendkim.conf -P /var/run/opendkim/opendkim.pid

# ls -lZ /usr/libexec/postfix/cleanup
-rwxr-xr-x. root root system_u:object_r:postfix_cleanup_exec_t:SystemLow /usr/libexec/postfix/cleanup

Before I begin pulling my hair off, can someone point me in the right direction, please? There must be something very simple I'm overlooking.

I know the purpose of SElinux, but I haven't found any tutorials that seem to be on "my level", (short and informative) :-) so I'm still a n00b when it comes to SElinux. Very willing to learn.

Disabling SElinux is not the way I learn.