FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: error action 4 not completed, err -1, will try again later

error action 4 not completed, err -1, will try again later 17 Oct 2007 11:43 #34

  • jos.dewijngaert
  • jos.dewijngaert's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 28
  • Thank you received: 0
We get the following errors on many of our clients and with different filesets:
Wed Oct 17 13:39:49 CEST 2007 [167]: downloading file 18317 F to /var/FileWave/Fileset18317v17, expected bytes 6680
Wed Oct 17 13:39:50 CEST 2007 [167]: Fileset Container ID 18317 has version 17. It contains 40 files and 4 folders
Wed Oct 17 13:39:50 CEST 2007 [167]: Done processing Fileset Container ID 18317
Wed Oct 17 13:39:50 CEST 2007 [167]: starting to delete obsolete fileset containers with versions


Err -1; FileSet Container Issue 17 Oct 2007 15:55 #356

  • FileWave
  • FileWave's Avatar
  • Offline
  • User is blocked
  • User is blocked
  • Posts: 218
  • Thank you received: 0
Jos,

This is a known issue that happened as a result of the 3.0.0 client. I can see that you've upgraded to 3.0.1. The error you're seeing, unfortunately, means that the catalog file record (on the client) for that fileset is corrupted.

You have two options to get that client back up and running:

1. Delete the Association to that fileset (Match the IDs). Once you're sure the clients all got the model update, you can reassociate it. There are some more options for this procedure, email eval(unescape('%64%6f%63%75%6d%65%6e%74%2e%77%72%69%74%65%28%27%3c%61%20%68%72%65%66%3d%22%6d%61%69%6c%74%6f%3a%73%75%70%70%6f%72%74%40%66%69%6c%65%77%61%76%65%2e%63%6f%6d%22%3e%73%75%70%70%6f%72%74%40%66%69%6c%65%77%61%76%65%2e%63%6f%6d%3c%2f%61%3e%27%29%3b')) for those.

2. Delete the client's Catalog file:
/var/FileWave/theCatalog

Then, restart the client; it will re-download all of its filesets and be back to normal.
  • Page:
  • 1