MediaBin Server Hang - Not responding

Hi All,

MediaBin Server hang and was not responding for long time. CPU was utilizing 100%. Did a hard re-boot to resolve the issue.

But found the following on the MBP.Log file:

11/07/07 13:12:23 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:12:23 GetImageById: Failed in querying database or fetching results.
11/07/07 13:13:31 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:13:31 GetImageById: Failed in querying database or fetching results.
11/07/07 13:14:39 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:14:39 GetAllMetaData&colon; Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{CCB052C6-13B2-41FD-9586-3169F13623D5}\{FC99CC0A-442D-4EFE-856E-3B7606E551B5}.mbf.
11/07/07 13:14:39 GetImageById: Failed in querying database or fetching results.
11/07/07 13:15:47 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:15:47 GetImageById: Failed in querying database or fetching results.
11/07/07 13:16:56 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:16:56 GetAllMetaData&colon; Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{CCB052C6-13B2-41FD-9586-3169F13623D5}\{FC99CC0A-442D-4EFE-856E-3B7606E551B5}.mbf.
11/07/07 13:16:56 GetImageById: Failed in querying database or fetching results.
11/07/07 13:18:04 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:18:04 GetImageById: Failed in querying database or fetching results.
11/07/07 13:19:13 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.
11/07/07 13:19:13 GetImageById: Failed in querying database or fetching results.
11/07/07 13:20:20 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B57F8AA3-DD55-466A-8D7A-7AF3EB96E586}.mbf.
11/07/07 13:20:20 GetImageById: Failed in querying database or fetching results.
11/07/07 13:21:29 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B57F8AA3-DD55-466A-8D7A-7AF3EB96E586}.mbf.
11/07/07 13:21:29 GetImageById: Failed in querying database or fetching results.
11/07/07 13:22:37 GetImageById: Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B57F8AA3-DD55-466A-8D7A-7AF3EB96E586}.mbf.
11/07/07 13:22:37 GetImageById: Failed in querying database or fetching results.

Does this means that the DB connection failed?

Also found the following on SYSTEM LOG on MB Ent. Manager:

Fatal	11/7/2007 13:18	Create of transfer job failed	Transfer create failed
Fatal	11/7/2007 13:18	Create of transfer job failed	Transfer create failed
Fatal	11/7/2007 13:18	Create of transfer job failed	Transfer create failed
Fatal	11/7/2007 13:18	Create of transfer job failed	Transfer create failed
Fatal	11/7/2007 13:17	Create of transfer job failed	Transfer create failed

Kindly advice.

Thanks
John

Find more posts tagged with

Comments

msrinivas

First open a support case. Do you have any backup/synch that goes on while the server is running? Do you see those files in the location? Did anyone change the permissions on the MBDataDirectory? Do you run DB indexing? Is the server back up and running fine on the hard reboot? Does this happen often?

jstephan

First open a support case. Do you have any backup/synch that goes on while the server is running? Do you see those files in the location? Did anyone change the permissions on the MBDataDirectory? Do you run DB indexing? Is the server back up and running fine on the hard reboot? Does this happen often?

Its not happening often. The server is running fine after the hard reboot. The files are there and no change at anything on the DB and MB Server side.

lyman

The message:

Failed to open file \\FNMBPROD\MBDataDirectory\ImageDB\{DF3337EC-2C8B-4E37-9B76-6C71B2A826F3}\{B0CEFBFB-CE03-4B18-BF21-EF8EBAF0AC2F}.mbf.

usually has one of a few causes. First verify by hand that the file names actually does exist. If it does not then you have problems since data has been lost and you will need to run the reconciliation scripts available via support to see what you have. We have never seen this problem having an internal cause (i.e., it has always historically been caused by running out of disk space or a faullty medium or connection).

If it does exist, then the file may have been locked. Often this is caused by a run-a-way antivirus scan or backup program that is lot allowing MediaBin to open files in ImageDb.

The last possibility is a problem with the disk itself or the connection to it.

Cheers,

Lyman

jstephan

Thank you Lyman. The file exists and no backup was running at the time. But when checked the db log files, an Inbound memeory error found because of not getting response from client (MB Server). Other than that nothing found on the connection and db server.

Migrateduser

The server had disk i/o issues, we would reboot and it would be okay for a day or so and then the issue started appearing again.

Finally one day, the RAID controller logged a message in the Windows Event Viewer that it could not read from disk, we ran a TPF trace and found that one of the hardware components were failing. Hot swapped that drive bay out for a new one and the errors went away.

Don't know if this helps but, good luck anyways.

jstephan

The server had disk i/o issues, we would reboot and it would be okay for a day or so and then the issue started appearing again.

Finally one day, the RAID controller logged a message in the Windows Event Viewer that it could not read from disk, we ran a TPF trace and found that one of the hardware components were failing. Hot swapped that drive bay out for a new one and the errors went away.

Don't know if this helps but, good luck anyways.

Thanks Stacy. I have checked the event log and checked the RAID. Everything looks good. But your information was quite useful. Thanks again.