Xsan 4

tycen's picture

Open Directory not starting on XSAN metadata controller

Help! Everything with our metadata controllers have been running fun. I have two MDC and am on XSAN 4.1/El Cap. I have added a client to the XSAN since the upgrade so I'm pretty sure nothing bad happened during the upgrade.

One of my MDC's has been acting funky - I think it's an issue with the 8 Promise Pegasus2 arrays I have connected it it via Thunderbolt - and I've had to do a few hard reboots over the last couple of weeks.

Well, yesterday I went to add a new client to the XSAN (we had to wipe and reinstall the OS on a previous client). It failed and the error led me to find that my MDC that's been giving me trouble doesn't have Open Directory running. OD won't start and from other searching it seems that the database has become corrupted. Running sudo /usr/libexec/slapd -Tt gives the error:
57880743 bdb(cn=authdata): /var/db/openldap/authdata/id2entry.bdb: unexpected file type or format
57880743 bdb_db_open: database "cn=authdata": db_open(/var/db/openldap/authdata/id2entry.bdb) failed: Invalid argument (22).
57880743 backend_startup_one (type=bdb, suffix="cn=authdata"): bi_db_open failed! (22)

I've tried recovering it using various methods posted on different forums but am having no luck at all. I did not know to be archiving my OD Master - so I do not have an archive.

The XSAN environment seems to be working fine otherwise - all the clients are happy. I just can't add the new client.

I'm only using OD for the XSAN environment - I don't use it for users or groups (the XSAN clients just have a local user).

Environment: 2 XSAN MDCs; 7 XSAN clients; all running 10.11.5.

Here's some questions:
1) is there anyway to add a client with the XSAN in this state?
2) Does Time Machine help me at all (I have had it running)?
3) How do I get this fixed long term?

Thanks for any help!

rgerman's picture

XSan 3 Mavericks 10.9.5 to XSAN 4 El Capitan 10.11.3

Tags: 

Hello,

I am about to upgrade to Xsan 4 from Xsan 3 and was wondering is it possible to go directly from 10.9.5 to 10.11.3 and Xsan 4 on the MDC's or do I need to upgrade to Yosemite, then El Capitan? Also, I see that the primary MDC must be an OD Master, and the backup MDC a OD replica. Do fiber attached edit stations need to be bound to the OD Master in order to connect or does the config profile I create for the Xsan take care of that?

Thanks in advance!
Ray

Corrupted Xsan4 setup on OS X Server app on primary and secondary MDC

Tags: 

Primary and Secondary metadata controllers GUIs stopped showing all the XSAN volumes in the Server App.

Primary and secondary controllers were showing missing OD replica as well.

Used cvadmin to stop and unmount the volumes
Removed secondary controller from Xsan
Backup Xsan Config - sudo cp -r /Library/Preferences/Xsan /Library/Preferences/Xsan.old
Destroy the OD MASTER in Server App GUI
Move Server App to the Trash
Destroy any remnants of OD - sudo slapconfig -destroyldapserver
Remove Certs - sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority
Remove Kerberos - sudo rm -R /var/db/krb5kdc
Remove Xsan Config - sudo rm -r /Library/Preferences/Xsan
Move Server app back to Applications
In Server App Created New OD MASTER
In Server App turned on Xsan (For SAN NAME used the exact same name [SAN_NAME])
Close Server app

Opened up the new Xsan config file (config.plist) at /Library/Preferences/Xsan and copied and pasted the following into the original config file from our old Xsan configuration:

certSetRevision [ID]
sanRevision [ID]
sanUUID [ID]

Copy the original Xsan config files and fsmlist I made a backup of into /Library/Preferences/Xsan
Copy those config files into LDAP - sudo xsanctl pushConfigUpdate

Got this error after executing command
2015-10-15 05:03:05.570 xsanctl[36615:130261] buildSanConfig started
2015-10-15 05:03:05.570 xsanctl[36615:130261] buildSanConfig about to check LDAP
2015-10-15 05:03:05.589 xsanctl[36615:130261] buildSanConfig step 4 with {
globals = {
certSetRevision = "632228D9-C182-4E6F-A1B0-B729BCCB640A";
controllers = {
"30CDC770-A2A1-5F0D-970F-22FBBE04C72B" = {
IPAddress = "10.0.0.11";
hostName = "md.prestonwood.org";
};
};
fsnameservers = (
{
addr = "10.0.0.11";
uuid = "30CDC770-A2A1-5F0D-970F-22FBBE04C72B";
}
);
notifications = {
FreeSpaceThreshold = 20;
};
revision = "6D28EF16-9BCE-4672-A7A6-86582921257B";
sanAuthMethod = "auth_secret";
sanConfigURLs = (
"ldaps://md.prestonwood.org:389"
);
sanName = pbcxsan;
sanState = active;
sanUUID = "D6CB40CB-7AA4-4DF4-AF84-B751AB436C79";
sharedSecret = "********";
};
volumes = {
};
}
2015-10-15 05:03:05.593 xsanctl[36615:130261] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[1]'

      • First throw call stack:

(
0 CoreFoundation 0x00007fff8f02a03c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff91fc476e objc_exception_throw + 43
2 CoreFoundation 0x00007fff8ef15e3f -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 383
3 CoreFoundation 0x00007fff8ef2babb +[NSDictionary dictionaryWithObjects:forKeys:count:] + 59
4 acfs 0x000000010f6d3bb9 read_fsnameservers + 358
5 acfs 0x000000010f6cf5d9 buildSanConfig + 3012
6 acfs 0x000000010f6ce98e buildSanConfigC + 155
7 xsanctl 0x000000010f66de21 command_pushConfigUpdate + 61
8 xsanctl 0x000000010f66d623 main + 247
9 libdyld.dylib 0x00007fff984bf5c9 start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Open server app and volumes do not appear in the Server App

Volumes do mount on Primary MDC via xsanctl mount volume_name

I even reinstalled OS X and attempted the steps above and the result was the same. I could mount the SAN volumes and access the data on the SAN volumes only on the MDC; however the MDC would not show the volumes in the GUI. The only way I was able to get it back up and running was that I had a disk image backed up of the MDC and restored it back to the HD. That obviously brought everything back. For my knowledge, I would like to avoid restoring the disk image in case this happens again.

Is there anything else that I could have done?

blakej's picture

Instructions for setting up a second MDC for Xsan failover

Hi Everyone,

Are there any instructions available about how to configure for example a Mac Mini to act as a secondary MDC incase the primary MDC fails?

jpkang's picture

Xsan4 with StorNext Windows Client Configuration Help!

I wish there was training available or at least more online documentation than what I have found for Xsan4, but there was not and so I wanted to share with you all my story and knowledge. I only had experience with Xsan2 and Xsan4 is completely different. They simplified configuration and do not provide a granular configuration in the GUI, as they did in Xsan2.

It had taken me over 3 weeks to troubleshoot and resolve my issue. Only because I have found that some of the new hardware that we had purchased were at fault. We always assume that new hardware is in good working order straight out of the box.

My advice to you ... always keep in mind that EVERY component that you have in your implementation can be FAULTY/BAD! Never overlook any possibility!!

Because I have ran into issues immediately during my initial setup, I immediately blamed Xsan version 4, but guess what!? ... I'm now using it and it's doing everything I need it to do!!

amarino's picture

XSAN 4 Pane in Server not showing Volumes after Upgrading to Yosemite

So After upgrading to Yosemite and going through the migration pdf the XSAN 4 pane is not showing my volumes to administer but what's really weird is when I turn the service on they show up on the server desktop and they also mount on my 3 clients running 10.9.5 but not on my Yosemite client mac. please help

cutmoney's picture

Xsan 4 - Volumes not appearing in Server app after Open Directory reconfig

Tags: 

I'm running Xsan 4 and here is my issue. I've been having issues with my open directory settings in that I was unable to make any changes, I believe something became corrupted in some way. In any case, failover to my backup MDC was not working properly and I could not successfully add new profiles to clients as it would not authenticate. I had to destroy and recreate my open directory config on my primary MDC (I did archive everything). When I turned Xsan back on in Server app, the SAN volume mounted on the primary MDC, but the all of the data in the Server app is blank. It shows the connection as active, but shows that no volumes are configured, and also shows no servers.

So, the volume mounted on the primary MDC and it mounts successfully on one other machine that has an old config file. I've since deleted the config files on the other clients with the plan of installing the new config files after I fixed the open directory issue. Has anyone else had this issue and do you know of a way to get Server app to recognize that the volume is present and mounted. I'm not sure, but I'm assuming if I recreate the volume fresh it will destroy the data. Alternatively, is it possible to delete the /Library/Preferences/Xsan, create a new volume, and then replace it with my existing .cfg file (which I still have archived).

roykristoffersen76's picture

Reset password in XSAN 4?

Tags: 

I just upgraded both Meta data controllers to 10.10

My metadata controller MD1 is online with Xsan.
My second metadata controller Videoserver is not connected with XSAN.

I try to turn XSAN on at the second metadata controller Videoserver and i get promted to join excisting XSAN.
I click next and i choose MD1 as the controller to join.
I then get promted to write in the Admin name and admin password.
Is this the admin account name and password of the metacontroller - ore is there a specific password created for XSAN?
Couse i can not get it to work with the password for the admin account.
Is there any way to change the XSAN password? If there is such a password.

Thanks in advance!

Roy

OS X Yosemite (10.10.1)

smashfacekeybrd's picture

Xsan 4

Tags: 

OS X 10.10 Yosemite includes Xsan 4. There are some ch-ch-changes.

Subscribe to RSS - Xsan 4