When adding a watermark, Lightroom crashes

Anytime I try to export a file and add a watermark, Lightroom crashes. I can export without adding a watermark just fine. Lightroom also crashes when I try to edit a current watermark - as soon as I click the drop down menu to choose which watermark to edit, down goes Lightroom. I have both text watermarks and a small jpeg as a watermark (same thing happens with both) and I am running Lightroom 4.3.

It does sleep eventually, but not while I'm using the watermark feature? And it's not like I move the file around, it stays put. At any rate, I've moved it over to my internal hard drive to test that theory and it seems to be working thus far
As a side note, I'm wondering if it's ok that my raw files are on my internal hard drive but the catalog is on my external? When I import new images, they go to my "Pictures" folder by default but the catalog itself is located on my external. So when I back it up, it backs up to my external, which is the whole point...but since I wasn't sure if you're supposed to be referencing the files from the same place and THEN backing them up somewhere separate? Sorry if that's confusing!

Similar Messages

Prevent all page color from becoming opaque when adding a watermark with opacity

It looks like when I create a watermark AND change the opacity to something low the entire PDF becomes slightly opaque and colors are not that vivid (even if the actual text watermark is very small in the corner).
The only way I noticed fixes this problem is if I check the option to "Keep position and size of watermark text constant when printing on different page sizes".
See difference here:
-- Normal - http://screencast.com/t/5bCfSP5Fba
--Opaque - http://screencast.com/t/03qXJhR1ydh
--This is the difference in black when zooming in: http://screencast.com/t/PPsMJiLiS
Does anyone know what could be causing this? Is there a way to fix it without checking "Keep position and size of watermark text constant when printing on different page sizes"?
Thanks!

ALMOOOST!
It did work but I don't understand why it worked on some pages and not on others. So when using this method, its worked completely fine when the watermark is applied to visible page. However, when the watermark is applied only to printed pages, some of those pages lose the water mark completely on print during the flatten/change blend space. I cant tell whats special about those pages that it works that way.
Maybe it will be just easier to use the "Keep position and size of watermark text constant when printing on different page sizes" option when adding the watermark and then everything looks evenly perfect(just need to manually center the watermark position for each file). Curiously though, any idea what could be the correlation between the "Keep position and size of watermark text constant when printing on different page sizes" and the opacity of page when adding an watermark?

Embed fonts when adding a watermark

Acrobat 8.1:
Please help me embed a font when adding a watermark. I'm using the addwatermarkastext() method, using C#:
args = new System.Object[] { text, 1, fontName, size, jsoColor, -1, -1, true, true, true, horizontalAlign, verticalAlign, horizontalValue, verticalValue, false, 1.0, false, watermarkRotation, 1.0 };
jso.GetType().InvokeMember("addWatermarkFromText", System.Reflection.BindingFlags.Default | System.Reflection.BindingFlags.InvokeMethod, null, jso, args);
This works great, but I need to embed the font into the PDF. I'm using a barcode font that must be embedded, since the downstream viewer is not acrobat reader (and the user may not have the barcode font installed) and has a hard time with non-standard fonts. We are using a barcode font with an free license, so licensing won't be an issue.
When I add a watermark manually through the Acrobat pro interface, Acrobat DOES embed the font. I can't rely on users to enter the information accurately, so I must have an automated solution.
Is there a setting on Addwatermarkfromtext that I'm missing, or is there another way to embed just that one font? I don't want to embed all fonts in the document, just the barcode font.
I've tried adding a dummy watermark with text that is not visible (I saw somewhere online that someone recommended this approach). It did not work..

addWatermarkAsText() will always embed the font, provided that the font is licensed for embedding. have you verified that the font vendor has granted you those rights? I know you said it's "free", but perhaps it's not embeddable. You can easily check that using Distiller or the Microsoft Font Panel.
If you were to upgrade to Acrobat 9, then there is an EmbedFont function you use to embed just that font after the fact - though, again, it shoudl be embedded as is.

Solution to "Black image when adding a watermark in Aperture"

Hi,
I read an archived topic about people having issues with adding a watermark to their exported images using Aperture 1.5.2. I think the solution lies with what your current Display color profile (System Preferences > Display > Color) is set to and what color profile you used to create your watermark.
I created my original watermark using Photoshop CS2 and I believe that the watermark was saved using the sRGB Profle. However, I then calibrated my monitor using a Pantone Huey and it changed the color profile in my System Preferences. So every time I tried to export an image with a watermark from Aperture, I would get a black image with my watermark in the correct spot.
To solve the problem, I changed my Color Profile to sRGB Profile, then started Aperture. When I exported my image, everything came out properly.
Hope this is helpful to others.

I also just ran into this problem...my solution was an issue with the RAW fine tuning.
Images that used the new RAW fine tuning 2.0 (with Aperture 2) exported watermarks (I used a .psd file) just fine, but when exporting images with RAW fine tuning 1.1, a black box would show up around my watermark. So I migrated my images to RAW fine tuning 2.0 and it fixed the black box issue.

Every time I try to upload an image to watermarks lightroom crashes

I have been trying to load an image for my watermark. It seems any image I try to load, regardless of the type png/jpeg/, it crashes my lightroom. I am running lightroom 5 for PC and have had all the recent updates. Would anyone have any ideas why?

With that type of description of the problem, get set for some really funny responses.

Final Cut Pro X crashes when adding transitions, throughout the entire program.

I've had FCP X installed for a few weeks now, and I decided to hold back asking my question and see if anybody else is experiencing the same problems.
I did find one matching problem on the discussions forum, but the user found a solution which I tried, and did it did not work.
Everytime I try to add a very simple transition to my video in Final Cut Pro X, it gives me the spinning colorwheel, hesitates for a few seconds and then crashes.
It only does it with transitions, I can add effects, adjust color, etc. but only when adding transitions does it crash.
I've tried deleting events and original media, I've reimported using optimized media, I've tried both ways of keeping files in original locations and also copying to final cut events folder.
The video I'm using is full 1080p mov files from a Canon 5D Mark II.
It does it in the timeline as well as the secondary timeline.
I've tried the solution that the previous asker did, which was copying the content to another FCP event, and it didn't work for me. Still crashes whether I try to drag the transition to my timeline, use the keyboard shortcut, or double click.
I have a Early 2010 15 inch MBP i5 with 8gb of RAM running newest version of Snow Leopard.
Hope I've provided enough information
Thanks,
-Jon

Same Issue: Added a transition and then beach ball from **** and crash. Also lost two hours of work when it restarted and reverted to the last planned quit.
FCPX is benched until Lion and updates. Don't have time to be a beta tester on what might end up being a hobbyists toy.
MacPro Quad 3.0, 10G RAM.
Mark

Lightroom crashes on launch when installed through CC

I tried installing Lightroom through CC. I already had it installed as a stand-alone product before I got CC. When I do that, Lightroom crashes on launch. Even deleting it entirely, and then installing through CC has the same result. Only by downloading the latest version and installing with a serial number can I get it to work. This happened with both 5.5 and 5.6, on a Mac running Mavericks.

MY answer was thst i was subscribed to "one application" in creative cloud. I thought i could get the Photographers Program ( Photoshop and Lightroom for the same price as Photoshop alone) by just downloading LR. But, no you have to call cust service and change your subscription.
so, even tho creative cloud said i could "install" i coukdnt make it work.
hope that helps someone

Acrobat Pro 9.3 crash when adding watermark

Hi All, my acrobat crash when I add watermark. I am running Window 7 and have check the compatibility box thinking this will resolve the issue.
Any solution to this issue?

Acrobat Pro 9.4.2 (CS5) is doing the same thing on my Windows XP SP3 with 3.5 GB of ram and 206 GB of my brand new 300 GB hard drive free.
It starting doing this at the end of last year before my hard drive died. Then after rebuilding the entire system on this new drive it worked fine, until I downloaded all the updates and now it is broken again. Anytime I open more than one PDF, Acrobat crashes. I send the error report every time.

Lightroom crashes at start up with the error message "Lightroom encountered an error when reading from its preview cache and needs to quit". Please advise on how to fix this error. Thanks

Lightroom crashes at start up with the error message "Lightroom encountered an error when reading from its preview cache and needs to quit". Please advise on how to fix this error. Thanks

You probably need to delete your preview cache. See here
Why And How To Clear Your Lightroom Cache - Lightroom Fanatic
Preference and other file locations in Lightroom 5

Lightroom crashes when rendering Develop preview under Vista 64-bit

I'm running Windows Vista Ultimate 64-bit and Lightroom 1.1 crashes every time I click the "Develop" pane. My images are DNG files without the original RAW embedded.
Lightroom ONLY crashes when I load an image in Develop. If I open Develop without any image selected, it's fine (no image is displayed). I can zoom in to 100% in Library and it works fine. Exporting images to JPG works fine. Editing photos in the Library pane is fine. The crash data is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 1.1.0.0
Application Timestamp: 4677e8e1
Fault Module Name: MFC80U.DLL
Fault Module Version: 8.0.50727.163
Fault Module Timestamp: 4484afec
Exception Code: c0000005
Exception Offset: 0002511c
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
I've uninstalled LR 1.1 and reinstalled and it does the same thing. When I uninstall LR 1.1 and the install LR 1.0 (the previous version) Develop does open, but it doesn't render the images correctly - it looks like it misinterprets the white balance by about 1,500k degrees (very ugly), but Library shows the correct image/white-balance.
I've updated my nVidia 7900 graphics drivers to the latest version, appropriate to my OS and architecture. I've disabled XMP creation and Adobe Photo Downloader, as well as all other running applications (Antivirus, spyware, itunes, etc).
This USED to work fine in Vista and I did not make any significant changes, but I expect it's an issue with WindowsUpdate causing an incompatibility. I can't roll-back to my Vista state when it worked a month ago (that's another Vista frustration).
Anyway advice or comments would be GREATLY appreciated since this is an integral part of my professional workflow. I own a legitimate, licensed copy of both Lightroom and Vista, yet neither company is willing to talk to me unless I pay them money, which I think is complete extortion, but I digress.
Thanks in advance for your help.

Has anyone got a resolution on this? I have the same issue. Lightroom crashes when I click develop and the develop module begins to render the image. Clicking develop with no image selected allows the develop module to load however selecting develop on the menu bar and choosing either previous photo or next photo causes lightroom to crash while rendering an image.
I have a 64 bit capable HP XW8400 workstation with 2 dual core Xeon processors, 4 GB RAM, and a nVidia FX 4400 graphics card. This video card was put in as a test. the original video card was an nVidia quadra NVS something. When I ran the NVS card I used the drivers certified for Adobe CS2. I am running 32 bit Windows XP SP2 with all current updates. I do not have any MS office components installed on this system.
I read of some troubles around the Realtek HD audio driver and some Adobe applications (not Lightroom). Since I have this sound device I disabled it and removed the drivers...still crashes.
I also disabled the Intel VT in the system bios (I believe this is required to run 64 bit XP or Vista)... no change. Also disabled the NX feature...no change.
I also loaded VMware workstation 6.0 and installed Lightroom in a 32bit Windows XP SP2 VM. In the VM Lightroom works perfectly on the same machine...just not as snappy...
This stinks...Lightroom works perfectly on my poky laptop.

Bridge CS6 crashes when adding tags or ratings

Bridge CS6 crashes when adding tags or ratings. Someone suggested upgrading video driver. It resolved the problem for a short time and then started crashing again when adding tags or ratings. Sometimes it works fine but lately it crashes almost every time I tag or rate one image. I have upgraded my video driver and reset cache and reset preferences.
Never had a crash with Photoshop CS6 or RAW ...only with Bridge when Tagging or Rating
AMD Phenom II X4 810 2.60GHz
8.0 GB RAM
Windows 7 64 bit
Thanks for your help Paul

Curt Y ....saw your response to another person with the same problem.....video, printer, or scanner drivers could be the problem???? Really? My computer never crashes until I installed Bridge.
Faulting application name: Bridge.exe, version: 5.0.1.23, time stamp: 0x505aad8f
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xd78
Faulting application start time: 0x01cdf793e58dd872
Faulting application path: C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 2d3487d6-6387-11e2-9bb4-00265549541e
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T04:58:21.000000000Z" />
<EventRecordID>54203</EventRecordID>
<Channel>Application</Channel>
<Computer>Paul-PC</Computer>
<Security />
</System>
- <EventData>
<Data>Bridge.exe</Data>
<Data>5.0.1.23</Data>
<Data>505aad8f</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.17725</Data>
<Data>4ec4aa8e</Data>
<Data>c0000374</Data>
<Data>00000000000c40f2</Data>
<Data>d78</Data>
<Data>01cdf793e58dd872</Data>
<Data>C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>2d3487d6-6387-11e2-9bb4-00265549541e</Data>
</EventData>
</Event>

Moving from Bridge to Lightroom, when adding existing files on hard drive, will metadata transfer? Should I choose embed sidecar in file handling or will it automatically happen if I choose standard?

Moving from Bridge to Lightroom. Will metadata in existing files be recognized by Lightroom, and should I select embed+sidecar when adding files to library for the first time.

Thanks guys, appreciate the feedback.
CHRIS - you are exactly right about my FUTURE workflow. What I'm trying to figure out now is how to best handle images already processed. My import should be OK based on the way I have duplicates in separate directories, BUT I'm wondering how to avoid seeing all of these duplicates in LR when I search by keyword, etc.? I guess I can somehow flag the RAW files and only get them in my results.
One question though - Stacks, etc. sounds great for the LR processed images. But what about variations based on processing in Photoshop after the LR Develop stage? I guess in this case I will just have to keep duplicate images if I have multiple versions from my PS work?
ISAAC - Thanks for clarifying that LR will recognize my XMP files from Bridge. What about the opposite direction . . . if I edit something in LR and capture this via XMP, it won't prohibit Bridge from recognizing XMP info if I access a file via Bridge, will it?
ALSO - Do you know where I can find info about tracking via XMP vs. the central database? You mentioned a couple of valid points, but I'm not sure I have a full handle on the pros/cons of these options.
Thanks!
Mark

InDesign CS5 crashes when adding pages - is there an answer yet?

Having scouted around I can see lots of people have this (or a similar) problem, but with far more specific circumstances than mine - e.g. in templates, or with documents created in previous versions, or when adding more than 10 pages, etc.
Mine is a 'virgin' CS5 install, I've been away since PageMaker 6.5 and I'm not trying to salvage any of that stuff! Every time I try to add pages in the middle of a document it crashes, regardless of how many I try to add. A work around which sometimes works is to add them at the end of a document and then drag them to where they are needed.
Looks like this problem is widespread, I see lots of people talking about it going back almost a year, but can find no mention of it or possible solutions from Adobe. Are these forums just a sop to the user, a place to moan and vent without ever getting answers or acknowledgement that a problem exists? No offence Adobe, but I don't have time to join a community or spend hours on forums, I'm too busy. I need software that works and timely answers.

Pixate wrote:
Looks like this problem is widespread, I see lots of people talking about it going back almost a year, but can find no mention of it or possible solutions from Adobe. Are these forums just a sop to the user, a place to moan and vent without ever getting answers or acknowledgement that a problem exists? No offence Adobe, but I don't have time to join a community or spend hours on forums, I'm too busy. I need software that works and timely answers.
First, I don't recal more than one or two threads reporting a problem like this that wasn't related to some sort of configuration issue on the user's machine (notably the 3-column master issue that John has mentioned), and that hardly qualifies as "widespread" around here. Poviding full details about what version of ID, including the patch level, and your OS, along with exactly what you are doing, what happens, and any error messages you receive, and what you've already tried to solve the problem, will get you better help faster.
Second, you are not talkint to Adobe here. If you want to waste your time talking to tech support, you need to do that on the phone. The people here are user volunteers. We don't write the code and have no influence over what happens in engineering, but we do have a lot of collective real world experience that gladly share, and there are very few problems other than genuine bugs that we don't solve. But if you don't have time to participate in the community there's a pretty good chance the community won't find time for you.

Full server pool crashes when adding new iSCSI server

Hi,
we have a Pool Group with 2 machines (1 Server Pool Master + Server Virtual Machine + Utility Server and another 1 Server Virtual Machine). Both have a iSCSI Shared Disk which builds /OVS partition.
This is working, we can use High Availability, Migrate guests etc.
But when adding new Server Virtual Machines to the pool (with guests running), current machines in the Pools get restarted.
My question is, can server virtual machines be "hot added" to the pool group while guests are running?
Thanks and regards,
Marc

Hi,
hosts file seems to be correct.
Messages logs during the crash time are the following:
Node vmserver15 = Server Pool Master, Utility Master and Server Virtual Machine
Dec 10 12:40:02 vmserver15 kernel: vlan500: port 3(vif6.0) entering disabled state
Dec 10 12:40:02 vmserver15 kernel: device vif6.0 left promiscuous mode
Dec 10 12:40:02 vmserver15 kernel: type=1700 audit(1260445202.434:16): dev=vif6.0 prom=0 old_prom=256 auid=4294967295 ses=4294967295
Dec 10 12:40:02 vmserver15 kernel: vlan500: port 3(vif6.0) entering disabled state
Dec 10 12:40:02 vmserver15 kernel: loop10: dropped 10114 extents
Dec 10 12:40:03 vmserver15 udhcpc: udhcp client (v0.9.8) started
Dec 10 12:40:03 vmserver15 udhcpc: Lease of 193.109.175.25 obtained, lease time 172800
Dec 10 12:40:04 vmserver15 kernel: device vif7.0 entered promiscuous mode
Dec 10 12:40:04 vmserver15 kernel: type=1700 audit(1260445204.774:17): dev=vif7.0 prom=256 old_prom=0 auid=4294967295 ses=4294967295
Dec 10 12:40:04 vmserver15 kernel: vlan500: topology change detected, propagating
Dec 10 12:40:04 vmserver15 kernel: vlan500: port 3(vif7.0) entering forwarding state
Dec 10 12:40:05 vmserver15 kernel: loop10: fast redirect
Dec 10 12:40:06 vmserver15 kernel: blkback: ring-ref 770, event-channel 9, protocol 1 (x86_32-abi)
Dec 10 12:53:35 vmserver15 kernel: o2net: no longer connected to node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:36 vmserver15 kernel: (4989,0):o2hb_do_disk_heartbeat:776 ERROR: Device "sdb1": another node is heartbeating in our slot!
Dec 10 12:53:37 vmserver15 kernel: o2net: accepted connection from node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:38 vmserver15 kernel: (4989,0):o2hb_do_disk_heartbeat:776 ERROR: Device "sdb1": another node is heartbeating in our slot!
Dec 10 12:53:50 vmserver15 last message repeated 6 times
Dec 10 12:53:51 vmserver15 kernel: o2net: no longer connected to node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:52 vmserver15 kernel: (4989,0):o2hb_do_disk_heartbeat:776 ERROR: Device "sdb1": another node is heartbeating in our slot!
Dec 10 12:53:53 vmserver15 kernel: o2net: accepted connection from node vmserver10.pic.es (num 1) at 193.109.174.110:7777
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlm_send_remote_convert_request:393 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000001050c00000000: bad lockid+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_inode_lock_full:2064 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_inode_lock_atime:2193 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):__ocfs2_file_aio_read:2434 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlm_send_remote_convert_request:393 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000001050c00000000: bad lockid+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_inode_lock_full:2064 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_write_begin:1845 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):ocfs2_file_buffered_write:2016 ERROR: status = -22+
Dec 10 12:53:53 vmserver15 kernel: (5638,0):__ocfs2_file_aio_write:2173 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):dlm_send_remote_convert_request:393 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000000020744c1370e: bad lockid+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_inode_lock_full:2064 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_reserve_suballoc_bits:449 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_reserve_cluster_bitmap_bits:682 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_local_alloc_reserve_for_window:930 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_local_alloc_slide_window:1063 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_reserve_local_alloc_bits:537 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):__ocfs2_reserve_clusters:725 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_lock_allocators:677 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_write_begin_nolock:1751 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_write_begin:1861 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):ocfs2_file_buffered_write:2016 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: (7923,0):__ocfs2_file_aio_write:2173 ERROR: status = -22+
Dec 10 12:53:58 vmserver15 kernel: loop: Write error at byte offset 37644512256, length 4096.+
. <the above bold and cursive text is repetead few times>
Dec 10 12:58:29 vmserver15 kernel: (5638,3):dlmconvert_remote:327 ERROR: dlm status = DLM_IVLOCKID
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_cluster_lock:1206 ERROR: DLM error DLM_IVLOCKID while calling dlmlock on resource M000000000000000001050c00000000: bad lockid
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_inode_lock_full:2064 ERROR: status = -22
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_write_begin:1845 ERROR: status = -22
Dec 10 12:58:29 vmserver15 kernel: (5638,3):ocfs2_file_buffered_write:2016 ERROR: status = -22
Dec 10 12:58:29 vmserver15 kernel: (5638,3):__ocfs2_file_aio_write:2173 ERROR: status = -22
Dec 10 13:01:16 vmserver15 syslogd 1.4.1: restart.
Node vmserver10: Virtual Server Machine
Dec 10 12:53:35 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:35 vmserver10 kernel: (5029,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 0
Dec 10 12:53:35 vmserver10 kernel: (20996,0):dlm_get_lock_resource:844 E3FE9E5767CA457FA697980EB637E93B:M000000000000000000022044c1370e: at least one node (0) to recover before lock mastery can begin
Dec 10 12:53:36 vmserver10 kernel: (5344,4):dlm_get_lock_resource:844 E3FE9E5767CA457FA697980EB637E93B:$RECOVERY: at least one node (0) to recover before lock mastery can begin
Dec 10 12:53:36 vmserver10 kernel: (5344,4):dlm_get_lock_resource:878 E3FE9E5767CA457FA697980EB637E93B: recovery map is not empty, but must master $RECOVERY lock now
Dec 10 12:53:36 vmserver10 kernel: (5344,4):dlm_do_recovery:524 (5344) Node 1 is the Recovery Master for the Dead Node 0 for Domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 12:53:36 vmserver10 kernel: (20996,0):ocfs2_replay_journal:1183 Recovering node 0 from slot 0 on device (8,17)
Dec 10 12:53:37 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:38 vmserver10 kernel: (8672,1):dlm_get_lock_resource:844 ovm:$RECOVERY: at least one node (0) to recover before lock mastery can begin
Dec 10 12:53:38 vmserver10 kernel: (8672,1):dlm_get_lock_resource:878 ovm: recovery map is not empty, but must master $RECOVERY lock now
Dec 10 12:53:38 vmserver10 kernel: (8672,1):dlm_do_recovery:524 (8672) Node 1 is the Recovery Master for the Dead Node 0 for Domain ovm
Dec 10 12:53:40 vmserver10 kernel: kjournald starting. Commit interval 5 seconds
Dec 10 12:53:51 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:53 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:53:53 vmserver10 kernel: (3761,0):dlm_convert_lock_handler:489 ERROR: did not find lock to convert on grant queue! cookie=0:92+
Dec 10 12:53:53 vmserver10 kernel: lockres: M000000000000000001050c0000000, owner=1, state=0+
Dec 10 12:53:53 vmserver10 kernel:   last used: 0, refcnt: 3, on purge list: no+
Dec 10 12:53:53 vmserver10 kernel:   on dirty list: no, on reco list: no, migrating pending: no+
Dec 10 12:53:53 vmserver10 kernel:   inflight locks: 0, asts reserved: 0+
*Dec 10 12:53:53 vmserver10 kernel:   refmap nodes: [ ], inflight=0*+
Dec 10 12:53:53 vmserver10 kernel:   granted queue:+
Dec 10 12:53:53 vmserver10 kernel:     type=5, conv=-1, node=1, cookie=1:243, ref=2, ast=(empty=y,pend=n), bast=(empty=y,pend=n), pending=(conv=n,lock=n,cancel=n,unlock=n)+
Dec 10 12:53:53 vmserver10 kernel:   converting queue:+
Dec 10 12:53:53 vmserver10 kernel:   blocked queue:+
. <the above bold and cursive text is repetead few times>
Dec 10 12:57:18 vmserver10 modprobe: FATAL: Module ocfs2_stackglue not found.
Dec 10 12:57:18 vmserver10 kernel: (3761,0):dlm_convert_lock_handler:489 ERROR: did not find lock to convert on grant queue! cookie=0:92+
Dec 10 12:57:18 vmserver10 kernel: lockres: M000000000000000001050c0000000, owner=1, state=0+
Dec 10 12:57:18 vmserver10 kernel:   last used: 0, refcnt: 3, on purge list: no+
Dec 10 12:57:18 vmserver10 kernel:   on dirty list: no, on reco list: no, migrating pending: no+
Dec 10 12:57:18 vmserver10 kernel:   inflight locks: 0, asts reserved: 0+
*Dec 10 12:57:18 vmserver10 kernel:   refmap nodes: [ ], inflight=0*+
Dec 10 12:57:18 vmserver10 kernel:   granted queue:+
Dec 10 12:57:18 vmserver10 kernel:     type=5, conv=-1, node=1, cookie=1:243, ref=2, ast=(empty=y,pend=n), bast=(empty=y,pend=n), pending=(conv=n,lock=n,cancel=n,unlock=n)+
Dec 10 12:57:18 vmserver10 kernel:   converting queue:+
Dec 10 12:57:18 vmserver10 kernel:   blocked queue:+
. <the above bold and cursive text is repetead few times>
Dec 10 12:58:32 vmserver10 kernel: (3761,0):dlm_unlock_lock_handler:511 ERROR: failed to find lock to unlock! cookie=0:1849
Dec 10 12:58:33 vmserver10 modprobe: FATAL: Module ocfs2_stackglue not found.
Dec 10 12:59:02 vmserver10 kernel: o2net: connection to node vmserver15.pic.es (num 0) at 193.109.174.115:7777 has been idle for 30.0 seconds, shutting it down.
Dec 10 12:59:02 vmserver10 kernel: (0,0):o2net_idle_timer:1503 here are some times that might help debug the situation: (tmr 1260446312.830107 now 1260446342.828243 dr 1260446312.830066 adv 1260446312.830319:1260446312.830320 func (b9f5fd13:506) 1260446312.830109:1260446312.830303)
Dec 10 12:59:02 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 12:59:32 vmserver10 kernel: (3761,0):o2net_connect_expired:1664 ERROR: no connection established with node 0 after 30.0 seconds, giving up and returning errors.
Dec 10 13:01:42 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 13:01:45 vmserver10 kernel: ocfs2_dlm: Node 0 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:01:45 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 0 1
Dec 10 13:01:51 vmserver10 kernel: o2net: accepted connection from node vmserver16.pic.es (num 2) at 193.109.174.116:7777
Dec 10 13:01:56 vmserver10 kernel: ocfs2_dlm: Node 2 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:01:56 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 0 1 2
Dec 10 13:09:05 vmserver10 modprobe: FATAL: Module ocfs2_stackglue not found.
Dec 10 13:16:45 vmserver10 kernel: o2net: connection to node vmserver16.pic.es (num 2) at 193.109.174.116:7777 has been idle for 30.0 seconds, shutting it down.
Dec 10 13:16:45 vmserver10 kernel: (0,0):o2net_idle_timer:1503 here are some times that might help debug the situation: (tmr 1260447375.655426 now 1260447405.655712 dr 1260447375.655413 adv 1260447375.655427:1260447375.655427 func (b9f5fd13:503) 1260446516.75600:1260446516.75608)
Dec 10 13:16:45 vmserver10 kernel: o2net: no longer connected to node vmserver16.pic.es (num 2) at 193.109.174.116:7777
Dec 10 13:17:15 vmserver10 kernel: (3761,0):o2net_connect_expired:1664 ERROR: no connection established with node 2 after 30.0 seconds, giving up and returning errors.
Dec 10 13:17:19 vmserver10 kernel: (5029,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 2
Dec 10 13:17:20 vmserver10 kernel: (3761,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 2
Dec 10 13:29:05 vmserver10 kernel: o2net: no longer connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 13:29:05 vmserver10 kernel: (5029,0):ocfs2_dlm_eviction_cb:98 device (8,17): dlm has evicted node 0
Dec 10 13:29:06 vmserver10 kernel: (5344,4):dlm_get_lock_resource:844 E3FE9E5767CA457FA697980EB637E93B:$RECOVERY: at least one node (0) to recover before lock mastery can begin
Dec 10 13:29:06 vmserver10 kernel: (5344,4):dlm_get_lock_resource:878 E3FE9E5767CA457FA697980EB637E93B: recovery map is not empty, but must master $RECOVERY lock now
Dec 10 13:29:06 vmserver10 kernel: (5344,4):dlm_do_recovery:524 (5344) Node 1 is the Recovery Master for the Dead Node 0 for Domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:29:06 vmserver10 kernel: (28412,0):ocfs2_replay_journal:1183 Recovering node 0 from slot 0 on device (8,17)
Dec 10 13:29:09 vmserver10 kernel: kjournald starting. Commit interval 5 seconds
Dec 10 13:29:16 vmserver10 kernel: o2net: accepted connection from node vmserver16.pic.es (num 2) at 193.109.174.116:7777
Dec 10 13:29:20 vmserver10 kernel: ocfs2_dlm: Node 2 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:29:20 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 1 2
Dec 10 13:32:08 vmserver10 kernel: o2net: connected to node vmserver15.pic.es (num 0) at 193.109.174.115:7777
Dec 10 13:32:11 vmserver10 kernel: ocfs2_dlm: Node 0 joins domain E3FE9E5767CA457FA697980EB637E93B
Dec 10 13:32:11 vmserver10 kernel: ocfs2_dlm: Nodes in domain ("E3FE9E5767CA457FA697980EB637E93B"): 0 1 2
Dec 10 13:36:10 vmserver10 shutdown[28681]: shutting down for system reboot+
I will investigate what seems to be going on and post it here.
Thanks for your help.
Edited by: Marc Caubet on 11-Dec-2009 02:05
Edited by: Marc Caubet on 11-Dec-2009 02:07

Lightroom crashing when Photoshop is running??

I need help! I am running Windows 7, 4GB RAM. When I have both Photoshop CS4 64bit and Lightroom 3.3 64bit open Lightroom crashes. The moment I close Photoshop, Lightroom is fine. This is something that just started, I use to work with both of them all the time.
Thanks in advance!

First off, did you really mean PS CS4? Because PS CS4 and LR 3 are not fully compatible, and you don't get all the features of LR with CS4.
I do not know if CS4 would cause LR to crash. I worked for a while with CS3 and LR 3 and both worked fine, except that CS3 can not open the RAW images processed in LR 3.
Secondly, what do you mean by "crashes" - do you get a Windows message that LR has to close? Or is it that LR seems the be "frozen", i.e. un-responsive?
If LR becomes unresponsive, the reason might be that do don't have enough RAM. Try the following:
How large is your page file? Increae your page file (Control Panel > Administrative Tools > Performance) How large is your LR Cache. Set the Cache size in LR to very large (mine is set at 75 GB) - it might help (Edit > Preferences > File Handling). Also, move your LR Cache to a different drive than the drive on which LR sits .
Finally, if LR closes down on you and if both programs worked before then one or the other has become somehow corrupted.
Since it is LR that crashes, try to re-install LR.
Before you do that, backup your Catalog, so that you can open it with the newly re-installed LR and don't lose anything.
WW

When adding a watermark, Lightroom crashes

Similar Messages

Maybe you are looking for