G4 and XSan 1.4

I've seen conflicting info as to whether G4's are compatible with XSan 1.4. Anyone running Dual 1.25 G4 with 1.4?
G4's and G5's and Mac Pro Mac OS X (10.4.7)

The answer appears to differ depending on whether you mean 1.4 or 1.4.1.
The Xsan 1.4 update release notes:
http://docs.info.apple.com/article.html?artnum=304100
Specifically mention G4s of 800 MHz and better are supported.
The Xsan 1.4.1 release notes:
http://docs.info.apple.com/article.html?artnum=304423
Mention Xserve, Xserve G5, and Mac Pro. They specifically do not mention tower G4s, so that's a change.
Now, "Xserve" is a G4-based system. So would it work? Not sure. I don't know whether there's an explicit hardware check.
Is it supported? Looks like the answer there is no.

Similar Messages

File Permission problems FCP and XSAN

We have 5 Mac Pros connected to our XSAN (2 Xserves and 2 Promise arrays.). When a file is created on one of the FCP Macs and saved on the XSAN, the permission are OK (Individual - R/W, Group - R/W & Everyone RO.)
The problem is when a file, generally audio (from our sound booth or music from an outside source) or a graphic (usually Photoshop from our Graphics folks) is brought in over the LAN and save to the XSAN volume, the permissions are Individual - R/W, no group is listed and Everyone - No Access.
If they try work on something that another user started, they get permission errors if the sequence contains a file that was brought in from the outside.
I know we can change permissions on a file, but there are so many of them that it is slowing down production.
Is there anything we can do to either eliminate this happening, or have something like a drop folder they can place a file in to automatically change the file permissions?
Any help with this would be greatly appreciated.
The MacPros are running OS X 10.5.8 and FCP 7.0.3 and the XSAN is running Mac OS X Server 10.5.8 and XSAN 2.2.
Thanks.

If files saved to the AFP reshare are inaccessible by the fibre clients try this in terminal on your AFP re-share...
sudo serveradmin settings afp:lock_manager = no
Then restart AFP (or reboot), and re-propagate permissions back to where you need them. This will hand off file locking duties from AFP to the Xsan, which will help keep your permissions correct.
JM
(Thanks to Shane for showing me this)

Lost IP address on G5 w/ OS X server 1.4 and XSAN 1.3

I attempted to change the DHCP setting via Chicken of the VNC on a G5 loaded with OS X 1.4 and Xsan 1.3 and now am unable to determine what the IP address is. I had my network manager revert the port to a set IP range and sniffed that with Ethereal with no luck. I can start the G5 with firm ware control so that is shows up via firewire on my ibook laptop as two server HDs but is there a way to determine its IP from searching the server HDs or is there another way to get full access to the server via firewire. I guess what would be ideal is if there is a way to fully manage the G5 over firewire. I am pretty new at this so any help would be appreciated even if it seems painfully obvious to you all.
Call Center Mac OS X (10.4.6) 4 XSAN G5s with 8 XRAID Arrays

connected via firewire and re-configured the preferences plist to correctly pull the IP via IP allowing me to collect the IP useing ethereal.

Can't mount 3rd party DAS storage and Xsan volume simutaneously

Xsan client(MacPro) equipped an Apple FC HBA card can't mount SGI TP9300 DAS storage and Xsan volume simutaneously when powering on or restarting.
Among 2 FC ports, one port is used for Xsan volume using Xserve RAID, and the other port is used for SGI TP9300 storage which is directly connected to that Mac.
When booting, Xsan volume is always mounted normally, but SGI TP9300 volume is not.
Sometimes TP9300 volume is mounted about 20~30 minutes later.(I attached system.log file)
The LUN of TP9300 is seen at Disk Utility, so it's not physical problem.
It seems that actual volume information is not correctly processed at booting time.
While, after booting the system with the FC cable for TP9300 disconnected and confirming that Xsan volume mounted normally, then connecting the FC cable for TP9300, the TP9300 volume is mounted immediately.
Mac OS X 10.4.8, Xsan 1.4 is being used.

Yes, I think you screwed your xsan volume. You can not remove luns from pools, and you can not remove volumes from volumes.
How important is your existing data? In your case I would concentrate on that. This is not trivial. Theorotically you have lost your data allready. In practise you might have luck.
Once I was in your kind of twilight zone, and managed to keep the data. It is a complete cli job. You have to be very carefull about with your config files. You could hire an experienced xsan consultant. If that is not possible, read the manpages very carefully before doing anything on the volume.
Regards
Donald

How to upgrade to 10.4 Tiger and Xsan 1.3

I am running Xsan 1.1 on and Xserve G5/RAID running OS X 10.3.9. I need to get everything up to date so that client machines can be running 10.4.x Tiger. What is the best upgrade path? ie...
- do I upgrade server to Tiger first, still running Xsan 1.1 (for 10.3.9)?
- do I upgrade to Xsan 1.3 on 10.3.9 first, and then upgrade to 10.4?
Also.. I still have to upgrade the RAID firmware to 1.5 because after downloading and installing RAID 1.5, it won't launch. Anybody have ideas on that? It just bounces in the doc twice and then quits. So.. I can't update the firmware.

Thanks for everyone's guidance on this process. I completed my upgrade yesterday. All is running smoothly. I thought I would post a brief description of my experience which may help others.
Background:
I have a very basic Xsan setup: 1ea Xserve G5 controller, 2ea G5/Dual 2.5GHz clients, a Sanbox fibre switch, and 2ea Linksys gigabit switches. All three machines were running Xsan 1.1 on OS X 10.3.9 Panther. I needed to get one of my two client machines running Tiger. So... due to Xsan compatibility issues, I had to upgrade everything to OS X 10.4.6 Tiger and Xsan 1.3. I also needed to upgrade my Xserve RAID to the latest firmware (v1.5).
Upgrade Process:
I began this process with all three machines running. Although the Xsan volume was 'running', it was not mounted on any of the machines. My Xserve is designated as the primary controller (High priority); both clients are backup controllers (Med and Low priority).
Here's what I did to get to 10.4.6 and Xsan 1.3:
1) Upgraded the XServe to OS X Server 10.4 using install DVD. This required a server restart which caused Xsan to switch to my 'Med' client machine as the controller. I verified this by running Xsan Admin 1.1 on the client machine; it saw only the two clients (just as it should).
2) After restart, used Software Update on the Xserve to bring it up to OS X Server 10.4.6. This included the 'Xsan 1.2 Update for 10.4' and 'Xsan Admin 1.2 Update' along with a bunch of other misc updates (Java, WebObjects, Security..). Restarted.
3) Ran Xsan Admin 1.2 on the server. It was controlling the Xsan volume (which was still running). Both clients were still visible as backup controllers. I did not attempt to mount the Xsan volume
4) Installed OS X 10.4.3 Tiger Upgrade from DVD on Client1. Restarted.
5) After restart, used Software Update to bring Client1 up to OS X 10.4.6. This included the 'Xsan 1.2 Update for 10.4' and 'Xsan Admin 1.2 Update' along with a bunch of other misc updates (Java, Garageband, QuickTime). Restarted.
6) Used Software Update to bring Client2 up to OS X 10.4.6. This included the 'Xsan 1.2 Update for 10.4' and 'Xsan Admin 1.2 Update' along with a bunch of other misc updates (Java, Garageband, QuickTime). Restarted.
7) So.. at this point everything is running OS X 10.4.6 (the latest OS) and Xsan 1.2. And.. Xsan Admin 1.2 still running on the server. But... for some unknown reason, the 'Clients' tab no longer shows the Server as an available client. It only shows my two G5's as clients. Wierd and scary!! I quit and relaunched Xsan Admin 1.2, did a 'Refresh, but it made no difference. The '1. Computers' tab for the SAN itself does show all three computers (as controllers), but the 'Clients' list for this volume only shows my two client workstations (both 'Not mounted'). I decided to hold my nose and continue (such is life with Xsan...).
8) Used Xsan Admin 1.2 on the Server to 'Stop' the Xsan volume.
9) Launched Terminal on the Server and ran the 'cvfsck' disk utility on my Xsan volume. Here is what I typed into terminal:
sudo cvfsck Napoleon
(my volume is named 'Napoleon') I did have to authenticate with an Admin-level password. The utility took 5-10 min to run on my 5TB raid. Most of the time is just showed a static cursor in the Terminal window, but then the errors appeared. It reported 50+ errors, all of the same type. Here is a sample of what each error was like:
Error: Inode 0x804caa865e6e nsubnirs count is 34 - should be 18. Fixed.
The utility completed with all errors 'fixed.' Quit out of Terminal.
10) Used Xsan Admin 1.2 on the Server to 'Start' the Xsan volume back up.
11) Used Software Update on the Xserve to install the 'Xsan 1.3 Update for 10.4' and 'Xsan Admin 1.3 Update'. Restarted.
12) Ran Xsan Admin 1.3 on the Server. Now.. the Server does show in both the Computers list (as the primary controller) and in the Clients list (still not mounted, of course).
13) On Client1, used Software Update to install the 'Xsan 1.3 Update for 10.4' and 'Xsan Admin 1.3 Update' along with a bunch of other misc updates (iCal, iDVD, etc). Restarted.
14) On Client2, used Software Update to install the 'Xsan 1.3 Update for 10.4' and 'Xsan Admin 1.3 Update' along with a bunch of other misc updates (iCal, iDVD, etc). Restarted.
15) So.. now everything is running OS X 10.4.6 Tiger and Xsan 1.3. Xsan Admin 1.3 on the Server shows all three machines as both Controllers and Clients. The Xsan volume is 'running' but not mounted on any of the machines.
16) Used Xsan Admin 1.3 on the Server to 'Stop' the Xsan volume.
17) Launched Terminal on the Server and ran the 'cvfsck' disk utility on the Xsan volume. Here is what I typed into terminal:
sudo cvfsck Napoleon
This time no errors were reported, although terminal did produce a very nice report detailing what was going on as the Xsan volume was checked (thank you Apple!). Quit Terminal.
18) Used Xsan Admin 1.3 on the Server to 'Start' the Xsan volume back up.
19) And now for the big moment... Used Xsan Admin 1.3 on the Server to mount the Xsan volume on Client1. It took a little longer than nomal, but it did mount. I immediately browsed through the volume and copied a large folder to the Client1 desktop. Worked great. Copied the same folder back to the Xsan volume. Worked great. Deleted the folder in both places and emptied Trash. Worked great. I repeated this same mount/copy/delete process with Client2. Everything was working great!!
Now it was time to upgrade the RAID firmware to v1.5:
20) Used Xsan Admin 1.3 to unmount the Xsan volume on both clients. I then 'stopped' the volume and quit out of Xsan Admin.
21) Downloaded the RAID Admin 1.5 update and installed it.
22) Ran RAID Admin 1.5 and connected to my Xserve RAID. Used the menu command 'Update firmware...' to begin the process. It asks you to locate the firmware source file on disk. The entire update process took about 15 min to complete. The RAID restarted after the update. After seeing all green lights on the RAID, I quit RAID Admin 1.5.
23) Launched Xsan Admin 1.3 on the Server to 'Start' the Xsan volume.
24) Used Xsan Admin 1.3 on Server to mount the Xsan volume on both clients. Both mounted just fine.
And now I'm up to date
I know this is a long description, but I wish that I had had someone else's detailed log before I headed into this overly complex upgrade process (Apple... please make this easier going forward!). Hope it helps someone else.
John Christensen
[email protected]
817.690.8385
G5 Mac OS X (10.3.9) XServe, XServe Raid, Xsan

FCP and Xsan

Is anyone working with FCP and XSAN?
I working on building a new Server, XSAN system and I am curious on how your workflow is working.

Our workflow is working fine. This discussion is best left for the XSAN forum.

10.6.7 and XSAN 2.2.1

Hi all,
Is there anybody able to run server 10.6.7 and Xsan 2.2.1?

Not yet. We are still on 10.6.4 as each new update has had some sort of significant issue. These things don't directly effect the function of an MDC, but since your clients have to run an equivalent version of OS X or older, we haven't recommended that any of our clients update their MDCs to accomodate an OS update on their client machines.
10.6.5, Wifi: https://discussions.apple.com/thread/2644274?start=0&tstart=0
10.6.6, FCP/ ProKit6: http://www.digitalrebellion.com/blog/posts/mac_os_x_10.6.6_breaking_final_cut_st udio.html
10.6.7, Fonts in FCP: https://discussions.apple.com/thread/2792142?start=30&tstart=0
JM

Saving Files on FCP 6.0.2 and XSan

Hello All,
We're running into very frustrating issues as we are trying to save and open Final Cut Pro project files. We are currently using an XSan with ACLs set up to store FCP documents and related files. The six workstations aren't directly attached to the SAN, they connect via GigE to AFP shares (not an ideal solution, but it's what we can afford right now). It should be noted that our setup is currently using the "Golden Triangle" of directory services (AD user accounts and groups).
In December we upgraded our XSan to version 2 (which was a nightmare in itself), and all of our clients were upgraded to 10.5 with FCS2. After the upgrades, a few issues have arisen:
1. When a user attempts to save a FCP project, sometimes they receive the error message that the file is locked. From what I read on apples support site, this is due to permissions-- a file cannot be saved by one person, and then opened and saved by another. If the ACLs set on the folder reflect the groups that have full access to the files in which the project resides (recursively), why is this an issue? Or is this just another case of bad execution on apples part?
2. After concluding a "Save As", most of the time the alternate project file is able to be opened. We've run into several instances, however, when the project file is a very small size (16k or so), and gives the error message "Unable to open project file".. and it's pretty much trash. In these cases, the autosaves are behaving in a similar manner, being a very low size and not opening.
So my question is, does this all sound like permissions issues.. or is there something inherently wrong with the XSan at this point (e.g. corruption)? How are other people using XSan volumes in conjunction with FCP 6.0.2/FCS2 to edit and store files? Perhaps we're going about the whole setup the wrong way..
Thanks for your time and any advice you can provide..

Hi,
Thanks for taking the time to reply.
We have six producers.
Each producer has their own storage folder on the SAN: Producer 1, Producer 2, Producer 3, Producer 4, Producer 5, Producer 6. Each of these folders are located in One sharepoint called "Producers".
So we have one main producer, Well call Joan Smith. Joan has full access, recursively throughout her folder, which is producer 1. Joan has interns that work for her, who use an account called pro1edit1. Pro1edit1 has full access to Producer 1's folders as well, recursively. Joan and her intern never work on the same project at the same time from two different workstations. Each project is edited by one and only one user from one workstation.
Either Joan or her intern logs into the Mac (using either Joan's username/password, or the intern using their generic username and password [pro1edit1]). These accounts are AD Accounts. After a login, OD sends MCX policies to the clients (such as auto-mounting the AFP share points ["Producers", for instance] with their username and password). The user browses to their folder. If they create a new project, the create a folder with the project name. They then open FCP and set the settings (scratch, etc) to point to that folder. They save a project file with the name of the project within this same folder, keeping everything as one general "package" in the folder. For instance: /Volumes/Producers/Producer\ 1/5-Minute-Piece/FiveMinutePiece.fcp. All of the other folders are also located in here, scratch disks, autosaves, captures, etc.
When the user is done, they save, close final cut, and quit.
The next say, either Joan or her intern come in to do some work on the project. They log into one of the workstations, and they open the file. They conclude some edits, and upon trying to save the file they receive the error message that the file is locked. They then save the file as an alternate filename. Sometimes this works. Sometimes it says it saves it fine, but the next attempt at opening the file yields the error that the project cannot be opened. Upon inspection of the file, it's about 16k in size.
Using Producers folder/sharepoint, the permissions are as follows:
Producers:
<AD Domain>\grpStaffProduction: Allow: Read Only: This folder. *
<AD Domain\grpProEdit: Allow: Read Only: This folder. **
<AD Domain\grpProduction: Allow: Read Only: This folder. *
<AD Domain\grpEditAdmins: Allow: Full Control: This Folder, Children, all descendants. [inherited]
<AD Domain\grpDomainAdmins: Allow: Full Control: This Folder, Children, all descendants. [inherited]
Local Administrator: Allow: Full Control: This Folder, Children, all descendants. [inherited]
POSIX:
admin: RW: This Folder
staff: R: This folder
Others: None: This folder
Using Producer 1 (within the above folder), the permissions are as follows:
<AD Domain>\JoanSmith: Allow: Full control: This Folder, Children, all descendants.
<AD Domain>\pro1edit1: Allow: Full Control: This Folder, Children, all descendants.
<AD Domain\grpEditAdmins: Allow: Full Control: This Folder, Children, all descendants. [inherited]
<AD Domain\grpDomainAdmins: Allow: Full Control: This Folder, Children, all descendants. [inherited]
Local Administrator: Allow: Full Control: This Folder, Children, all descendants. [inherited]
POSIX:
admin: RW: This folder.
staff: R: This folder.
Others: R: This folder.
+* This group is used for another producer folder. This allows AFP to mount the share, and for the users to see their producer folder.+
+** This group is used for another producer folder. This allows AFP to mount the share, and for the users to see their producer folder.+
+* Joan, all other users in production, and their interns are apart of this group. This allows them to mount the AFP share and see which folders they have access to.+
So that's some more detail on our permissions and general workflow. We're up for suggestions. I appreciate your response!
-M

Scanner Photosmart c309a and Xsane problem

hi guys i think i am going mad with my stupid scanner. i have scan over 5000 pages with xsane and the HP C309a scanner. Yesterday the time i was scanning some docs, my scanner suddenly stopped i mean the bar with the lights stopped at a point and i cannot scan anymore. i have try everything i could find in the net but the scanner does not work. i have hard reset it 4 times nothing. this happened after kernel update. the weird thing is that on the screen of my scanner it says that scanner, copy ,fax does not work. i cannot scan from windows either. do you know anything similar situation and any solution for this? my printer works like a charm only the scanning abilities are dead.
thats the report
scanimage -T
scanimage: sane_start: Device busy
it is always busy and the bar does not move. is it a hardware problem or a software one i mean xsane friezed my scanner?
scanimage -LIt
device `hpaio:/net/Photosmart_C309a_series?ip=170.250.101.150' is a Hewlett-Packard Photosmart_C309a_series all-in-one
Last edited by EnterTheDragon2007 (2010-09-29 12:39:47)

The akjackson was right. This is a cost savings and revenue generating move by HP. Sure at the time of announcement the costs were based with a reduced price* to be consistent with the current estimated cost per page based on ISO yield. But for how long. They don't have to hold the standard for any given time. There is no law to hold them to that. So good business accounting would tell you that from a bottom line aspect, the more you use, the faster you run out, the more you buy. Why would HP change a cartridge for two new printers they are going to come out with in the future when the old one works on six current models? Why not just make another cartridge? I will tell you why not. They can save money by shutting down a line of cartridges that do not sell as often because they last longer and are just slightly more expensive to consumers. When a Company tells you "Its not about the money" remember "Its always about the money."
Your statement "Because of the way the printhead has to move across the page any reduction in width of the black cartridge can result in a 2X reduction in the width of the printer." is flawed. The cartridge feeds into a well head that supplies a printhead carriage that moves across the page. You can have one that holds 5 times more ink and not effect the size of the printer as long as the size of the cartridge does not exceed the size of the printhead carriage. A smaller cartridge has no sigificant value in reduction of the printer unless you change the size of the printhead carriage.

Photoshop and XSAN

Hi,
I can not save image from Photoshop CS5 and CS6 to XSAN 3 disk (both client and server are updated to latest versions)
I get "Could not save "filename.psd" because of a disk error.
File permissions are OK
All other Adobe applications are saving just fine (after effects reads and writes to the same directory, Illustrator also)
Regards,
Borko

Hi,
I tried to ask adobe... no luck...
http://feedback.photoshop.com/photoshop_family/topics/photoshop_cs6_can_not_over write_files_on_xsan_storage_files_lost?utm_content=topic_link&utm_medium=email&u tm_source=reply_notification
Better workaround is to use network shares to write from Photoshop
B.

Qmaster and XSAN?

I'm trying to set up Final Cut Server on our fibre server and in the setup and installation menu it mentions creating quickclusters and custom clusters. Are these settings meant only for the server computer or all computers connected to the network? What are some best practices with this? If I am sending bits to other computers directly I'm definitely going over giga-ethernet, but if I'm going fibre, wouldn't I have to copy once to the server computer, then again to the cluster computers?

You are correct. I only do the Gig-E configuration when customer don't care about how long the comnpression takes.
But normally all my deployment are done over Xsan.
So the tips for Xsan are as follows:
On the cluster controller, point the cluster storage to a folder on the Xsan volume, make sure that all the other nodes users and group account in the cluster have full read/write access to this location. On the other nodes configure there cluster storage to that directory as well. This way no copying of source media is ever made to the cluster node.
Does this make sense?

QT movies corruption and XSAN

Hi everyone,
I've tried using compressor 2.0.1 to encode multiple FCP self-contained movies to our XSAN, from two different computers and both attempts failed. I end up with a corrupted QT movie file that hangs on a white frame at the very beginning of the clip when I try to open it on QT player.
Whe I use the same compression settings to my internal drive or to a direct attached device, it works though. So I'm pretty sure it's something between my XSAN and compressor...
Does anyone have any idea why this is happening?
Thanks in advance,
Marcos H.

I also do get on occasional -2048 error that the QT files coming out of compressor over xsan are incomplete. While they happen occasionally with most files, I did find out that they are ALWAYS corrupted if trying to compress a video that has a 24 bit audio channel attached to it.
I found that compressing using a codec with the audio disabled fixes the problem and i simply attach a seperate audio codec to the batch.
As far as the other corruptions, it seems to be either a hit or miss.. not quite sure...

Non Unix friendly characers and Xsan searches

from a project orginally digitized on firewire and moved to Xsan volume.... everything runs fine, except if you do a reconnect or a search for files with names like "a03/b02" it won't find them. Finder Search reveals the file on the Xsan as "a03:b02" BUT if you navigate a new finder window to that file, or even Locate with Final Cut, the file shows up as "a03/b02" and reconnects just fine.
This is only a problem sharing XML's between the guy with Firewire copy and the Xsan setup. XML's between Xsan clients have no reconnect issues.
Obviously we need to rename these files, I'm assuming the '/' is causing the problem. Any ideas for an easier fix?
thanks

This is similar to the behaviour the colon and slash characters have on HFS+ and most other local and network filesystems.
try the following to see this IRL:
open your home folder in the Finder
open a new Terminal session
create a new file by typing the following command in the Terminal:
touch firstTestFile
verify that firstTestFile shows up in the Terminal by typing:
ls -l
verify that firstTestFile shows up in the Finder
rename firstTestFile to first/TestFile in the Finder
type the following command in the Terminal
ls -l
notice that first/TestFile shows up as first:TestFile in the Terminal
try to rename first/TestFile to first:TestFile in the Finder
notice that the colon character is not allowed in the Finder
the colon is the character for folder structure separations on Mac OS systems since somebody at Apple decided it would be nice to have a filesystem that supports folders
the slash is used in UNIX systems since their first incarnations
For backwards compatibility with both ancestors the character is mapped hence and forth between the two different environments on local filesystems, Apple made a nice wrapper that does this invisible to the end user.
However, a likewise wrapper is not implemented in Xsan and one can either see this as a bug or a concession inherent to the way Xsan works. I personally don't have enough in-depth knowledge to know is the second is the case.
Maybe someone deeply involved in Xsan can enlighten us?
Or maybe you could file it as a Xsan bug to bugreport.apple.com if you have a developer account and see from the feedback if this is normal behaviour or an unimplemented feature.
If it is normal behaviour for Xsan, you should file it as a bug report for Final Cut Pro, if Xsan is not expected to translate these characters, translation should be implemented at the application level.
Of course you can just decide not to use colons or slashes in filename, which imho is a good idea anyway..
happy editing,
Dirk

Clipping of log and xsan error...don't worry it's brief

this is the error I get when I boo the xsan admin app and I try to link to my bumdc. the san works fine but it's just getting into the admin app thats the problem. I thought that maybe someone has seen this before and can give me some ideas. thanks.
9/26/08 7:27:33 AM /usr/sbin/ocspd[35330] starting
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:34 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:35 AM Xsan Admin[35320] ERROR: -[SANKeychainAccess userNameAndPasswordForServiceName:outUserName:allowInteraction:outModDate:]: Unknown error -25293
9/26/08 7:27:53 AM Xsan Admin[35320] gotServerError:kNetworkError forTransaction:<XSAdminTransaction: 0x5a800a0>
9/26/08 7:28:05 AM [0x0-0x224224].com.apple.ServerAdmin[35097] * ERROR: -[GRAxes computeLayout]:1124 - plotRect height = 0.000000 <= 0.0 *
9/26/08 7:28:05 AM [0x0-0x224224].com.apple.ServerAdmin[35097] * ERROR: -[GRChartView computeLayout]:1194 - Layout for overlay axes (0x68174d0) failed. *
9/26/08 7:28:05 AM [0x0-0x224224].com.apple.ServerAdmin[35097] * ERROR: -[GRAxes computeLayout]:1124 - plotRect height = 0.000000 <= 0.0 *
9/26/08 7:28:05 AM [0x0-0x224224].com.apple.ServerAdmin[35097] * ERROR: -[GRChartView computeLayout]:1194 - Layout for overlay axes (0x6819690) failed. *
9/26/08 7:28:14 AM Xsan Admin[35320] task controller close?

Are you working in a word processing document or a page layout one? The process is pretty much the same for either, but in word processing you will need to ⌘-click outside of the layout first to enter object mode. Click & drag the cursor toward the object until you see its handles. If any other objects get selected, hold down the ⌘ key & click on them to deselect them. Now, with just this object selected you can delete it or move it to the front.

10.6.2 Server Xsan 2.2.1 and SNFS 3.1.2 MDC

I'm trying to connect an Xserve running 10.6.2 and Xsan 2.2.1 to a Linux MDC running StorNext 3.1.2, but Xsan can't connect to the fsmpm. I receive the following entries in system.log:
Feb 25 17:52:49 engOSX106Svr xsand[1186]: Synchronizing with fsmpm.
Feb 25 17:52:49 engOSX106Svr sandboxd[1191]: portmap(1190) deny network-outbound /private/var/tmp/launchd/sock
Feb 25 17:54:49 engOSX106Svr xsand[1186]: Failed to synchronize with fsmpm (error 2).
Feb 25 17:54:49 engOSX106Svr fsmpm[1189]: NSS: Name Server '192.168.171.1' (192.168.171.1) heartbeat lost, unable to send message.
Feb 25 17:54:55 engOSX106Svr xsand[1186]: fsm shutdown after 0 seconds
Feb 25 17:54:55 engOSX106Svr com.apple.launchd[1] (com.apple.xsan[1186]): Exited with exit code: 1
I am able to ping the MDC (192.168.171.1) and the OS X firewall is disabled. Other Linux and Windows cvfs clients are able to connect.
Can anyone provide me some insight into this problem? My hunch is some sort of port filtering but I can't figure out what service might be blocking the traffic.
Thanks,
Kevin Wright.

Here is my config.plist with the code and Company X'd out.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>computers</key>
<array/>
<key>metadataNetwork</key>
<string>192.168.171.0/24</string>
<key>role</key>
<string>CLIENT</string>
<key>serialNumbers</key>
<array>
<dict>
<key>license</key>
<string>XSAN-XXX-XXX-X-XXX-XXX-XXX-XXX-XXX-XXX-X</string>
<key>organization</key>
<string>XXXXXXXXXXX</string>
<key>registeredTo</key>
<string>ProductionIT</string>
</dict>
</array>
</dict>
</plist>
I was afraid of 10.6.2 Server... We'd like to stick with Snow Leopard, does 10.6.0 or .1 handle Xsan better?

G4 and XSan 1.4

Similar Messages

Maybe you are looking for