Michael Plautz's questions

On a server running Windows Server 2012 R2 Datacenter, I have installed MS SQL Server 2014, using a very typical installation. On a Windows 7 client, I have installed SQL Server Management Studio 2016. I am able to connect to my SQL Server (as a Database Engine) just fine using SSMS. However, when I try to use SSMS to connect to Integration Services on the exact same server host, like so:

I get this error:

I do not believe I have SQL Server 2005 Integration Services installed since I did an out-of-the-box SQL Server 2014 installation, and I would expect (hope, at least) that the Integration Services matched.

However, I am able to deploy SSIS packages just fine and run them using SSMS from the Integration Services Catalog. I only run into issues when trying to log in directly to Integration Services or access the SSIS Package Store.

The version of SQL Server is 12.0.4459.0 (this is also the version of my Integration Services service, MsDtsSrvr.exe).

How do I resolve this?

I am used to being able to use the system-config-lvm utility in RedHat Linux (I was using RHEL 5) to resize the LVM while the system was running. To be clear, I did this while running on the disk I was using for the system I was using and there were no errors or issues. When doing this, I was told that the volumes would have to be unmounted then mounted back when done. This worked when I did it.

I tried doing this in CentOS 6.5 with system-config-lvm. I first tried to resize the /home partition to be smaller so I could grow the /root partition. I sized it down, clicked apply, I was informed that it would have to be unmounted first, I clicked OK, and I was told it couldn't be unmounted because the device was busy. This is already different behavior than RHEL, and I understand that LV's are intended to have the ability to be resized while in use. Well some degree of searching online said that this was not actually the case, and it is not possible (to unmount the volume while in use) and recommended to use a live CD and perform the operation with the file system not yet mounted. This is what I did. I took a CentOS 6.5 Live CD, ran system-config-lvm to resize the LVs (basically swap the size of the / (root) and /home volumes), it was successful, then I rebooted.

When I rebooted, the boot was interrupted by file system errors that were detected. I decided to undo my logical volume resize back to their original sizes (which required booting back into the Live CD and repeating the LVM process), rebooted and still errors. The errors resided only with the /home volume, because the / (root) volume was totally intact. To try and rescue, I tried doing fsck -y and that didn't quite work, and it's okay because this whole file system was a clone of a VM to begin with. I don't mind losing the data.

But what I'm after is, why did this happen? Or better yet, what is the correct way to do this? Ideally of course without creating file system errors. Could this ever be the result of sizing a volume to be too small than contents of the volume (I believe I checked and this was not the case, but I cannot be totally sure)? I see this server fault post that recommends using resize2fs. Is that the correct way to do it, and not system-config-lvm?

I am using CentOS 6. I found a great article on how to install and configure OpenLDAP on CentOS 6, and I found some other great documentation here on how to configure LDAP to work on Apache HTTPD (I am using 2.2, which comes with CentOS 6). Unfortunately, what both articles do not necessarily specify is how to connect the two together. The second article I mentioned is great for an Apache walk through assuming you already have a good understanding of LDAP syntax, and the first article I mentioned is great assuming you already have in mind a way to test it. It seems like you have to be an expert at one or the other for either walk through to get you completely set up.

So let's assume that I configured my LDAP credentials according to the CentOS OpenLDAP walk-through article. I have added the following folks:

acme.ldif

dn: dc=acme,dc=com
objectClass: dcObject
objectClass: organization
dc: acme
o : acme

users.ldif

dn: ou=Users,dc=acme,dc=com
objectClass: organizationalUnit
ou: Users

bob.ldif

dn: cn=Bob Jones,ou=Users,dc=acme,dc=com
cn: Bob Jones
sn: Jones
objectClass: inetOrgPerson
userPassword: p@ssw0rd
uid: bjones

engineering.ldif

dn: cn=Engineering,ou=Users,dc=acme,dc=com
cn: Engineering
objectClass: groupOfNames
member: cn=Bob Jones,ou=Users,dc=acme,dc=com

addUserToGroup.ldif

dn: cn=Engineering,ou=Users,dc=acme,dc=com
changetype: modify
add: member
member: cn=Al Smith,ou=Users,dc=acme,dc=com

al.ldif

dn: cn=Al Smith,ou=Users,dc=acme,dc=com
cn: Al Smith
sn: Smith
objectClass: inetOrgPerson
userPassword: 12345
uid: asmith

I downloaded LDAPExplorer Tool 2 from SourceForge and successfully connected to this LDAP directory and explored it, and it looks just like the LDIF files suggest.

The following is from my httpd.conf file for Apache HTTPD:

<Directory /var/www/html/authpage>
    AuthType Basic
    AuthName "Enter valid user name"
    AuthLDAPURL ldap://magneto.acme.com:389/????
    require valid-user
</Directory>

Where the ???? is is where I do not know how to make my LDAP syntax line up with my LDAP directory. I have tried all sorts. What happens is I navigate to the URL http://magneto.acme.com/authpage (magneto is my hostname for the server in this case, I at least know that works), and I am prompted for credentials. Nothing I put in works. I have tried combinations of ou= and o= and dc=, along with ?uid as the query parameter.

When I check my Apache error_log, I see this line:

[Wed Sep 10 11:00:51 2014] [error] [client 10.78.182.243] access to /authpage failed, reason: verification of user id 'bjones' not configured
[Wed Sep 10 11:00:54 2014] [error] [client 10.78.182.243] access to /authpage failed, reason: verification of user id 'asmith' not configured

Assuming my LDAP directory works, and that Apache is correctly trying to authenticate to it, 1. How do I write correct syntax to authenticate to all users, or just a specific group? 2. Is there any additional configuration required to configure verification of users, based on what the error_log said?