sweeper.log: Error writing blob...Cannot create...Read-only

All documents from the original Software Support Library (SSL)

Moderators: Leon van Heerden, Luanda_Junzi, Belinda Frick, Lee Hendricks

sweeper.log: Error writing blob...Cannot create...Read-only

Postby Belinda Frick » Tue Feb 07, 2012 3:34 pm

I cannot find my recordings, when I checked under 'View Call History' no calls loaded and last successfully sweeped recording is in the past. When I click on the Sweeper log link and scroll down, it lists the following:

Code: Select all
[2012-02-03 17:56:09]  Version [1.6.4.3]Error writing blob :63_ADCDE45A9C98B1.gsc:Cannot create file "/mnt/drive3/20120203/63_adcde45a9c98b1.gsc". Read-only file system
[2012-02-03 17:56:09]  Version [1.6.4.3]Moved to new drive : /mnt/drive3/
[2012-02-03 17:57:09]  Version [1.6.4.3]Error writing blob :63_ADD6A5B79C98B1.gsc:Cannot create file "/mnt/drive3/20120203/63_add6a5b79c98b1.gsc". Read-only file system
[2012-02-03 17:57:09]  Version [1.6.4.3]Moved to new drive : /mnt/drive3/
[2012-02-03 17:57:09]  Version [1.6.4.3]Error writing blob :63_ADD6A5B79C98B1.gsc:Cannot create file "/mnt/drive3/20120203/63_add6a5b79c98b1.gsc". Read-only file system
[2012-02-03 17:57:09]  Version [1.6.4.3]Moved to new drive : /mnt/drive3/
[2012-02-03 17:57:09]  Version [1.6.4.3]Sweeper stopped, last 10 recordings gave errors.


Try the following:

  • Log into AMETHYST webadmin.
  • Click on 'Available Diskspace' to see if space available to sweep recordings to Exclusive drive.
  • If enough space, click on Configure Sweeper.
  • Check that all your settings is in place for the exclusive drives. We have had in the past if one of the Exclusive drives is not configured, it will give this error message.
  • If this is not the problem, try to Stop/start the sweeper by clicking on the stop sweeper/start sweeper link (top right-hand block on the HOME page).
  • To see if calls are now being loaded, click on 'View Call History' on the AMETHYST webadmin Home page.
  • Click on the sweeper link and scroll down to last entries to see if it stopped again with the same error message. If so, it could be that the drive noted in the message is faulty/corrupted. A Checkdisk needs to be run. You can shut the AMETHYST server down outside recording hours and power it up. On startup it will run the checkdisk. Alternatively, Datatex Support can do a site visit or remote check, without the AMETHYST needed to be shutdown.

Under investigation!
Belinda Frick
 
Posts: 3808
Joined: Fri Nov 12, 2010 4:25 pm

Return to Support Archive's (Amethyst)

Who is online

Users browsing this forum: No registered users and 1 guest

cron