Removed database - CmisSync no more syncing

69 views
Skip to first unread message

federic...@fitb.it

unread,
Aug 29, 2018, 5:45:29 AM8/29/18
to CmisSync
This is the second time that happens this terrible situation…
I guess that user shutdown his Windows PC while CMISSync is working:

2018-08-21 17:44:59,176 [16] DEBUG CmisSync.Lib.SyncItem [(null)] - File.Exists(Q:\Ufficio Tecnico\Disegni\AssiemiProduzione\Piastra\Componenti\Setti PHD\PHD\superati\Strum apertura setto controllato\x brevetto\x deposito comunitario\Utensile PHD con scritte\Left Utensile PHD con scritte.jpg) = True
2018-08-21 17:44:59,180 [16] DEBUG DotCMIS.Binding.Impl.HttpUtils [(null)] - Timeout=3600000ms ReadWriteTimeout=21600000ms

2018-08-22 08:33:51,585 [1] INFO  CmisSync.Program [(null)] - Starting. Version: 2.11.3.0

The day after, when PC is restarted, CmisSync removes ALL folders from syncing and after that event, local folders and remote (Alfresco) folders are no more synced!!!


2018-08-22 08:33:51,585 [1] INFO  CmisSync.Program [(null)] - Starting. Version: 2.11.3.0
2018-08-22 08:33:53,174 [1] INFO  CmisSync.Lib.FolderLock [(null)] - Creating folder lock file: C:\Users\sscaini\CmisSync
2018-08-22 08:33:56,324 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Entering constructor.
2018-08-22 08:33:56,406 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Exiting constructor.
2018-08-22 08:34:02,094 [1] DEBUG CmisSync.Setup [(null)] - Entering constructor.
2018-08-22 08:34:02,100 [1] DEBUG CmisSync.Setup [(null)] - Exiting constructor.
2018-08-22 08:34:03,846 [5] INFO  CmisSync.ControllerBase [(null)] - Removed database: C:\Users\sscaini\AppData\Roaming\cmissync\Librerie.cmissync
2018-08-22 08:34:03,846 [5] INFO  CmisSync.ControllerBase [(null)] - ControllerBase | Removed folder 'Librerie' from config
2018-08-22 08:34:03,868 [5] INFO  CmisSync.ControllerBase [(null)] - Removed database: C:\Users\sscaini\AppData\Roaming\cmissync\Cartigli DLR.cmissync
2018-08-22 08:34:03,868 [5] INFO  CmisSync.ControllerBase [(null)] - ControllerBase | Removed folder 'Cartigli DLR' from config
2018-08-22 08:34:03,880 [5] INFO  CmisSync.ControllerBase [(null)] - Removed database: C:\Users\sscaini\AppData\Roaming\cmissync\Cataloghi info.cmissync
2018-08-22 08:34:03,880 [5] INFO  CmisSync.ControllerBase [(null)] - ControllerBase | Removed folder 'Cataloghi info' from config
2018-08-22 08:34:03,898 [5] INFO  CmisSync.ControllerBase [(null)] - Removed database: C:\Users\sscaini\AppData\Roaming\cmissync\Loghi.cmissync
2018-08-22 08:34:03,898 [5] INFO  CmisSync.ControllerBase [(null)] - ControllerBase | Removed folder 'Loghi' from config
2018-08-22 08:34:03,911 [5] INFO  CmisSync.ControllerBase [(null)] - Removed database: C:\Users\sscaini\AppData\Roaming\cmissync\Attrezzature.cmissync
2018-08-22 08:34:03,911 [5] INFO  CmisSync.ControllerBase [(null)] - ControllerBase | Removed folder 'Attrezzature' from config
2018-08-22 08:34:03,913 [5] INFO  CmisSync.ControllerBase [(null)] - Removed database: C:\Users\sscaini\AppData\Roaming\cmissync\AssiemiProduzione.cmissync
2018-08-22 08:34:03,913 [5] INFO  CmisSync.ControllerBase [(null)] - ControllerBase | Removed folder 'AssiemiProduzione' from config

2018-08-23 08:37:38,842 [1] INFO  CmisSync.Program [(null)] - Starting. Version: 2.11.3.0
2018-08-23 08:37:40,025 [1] INFO  CmisSync.Lib.FolderLock [(null)] - Creating folder lock file: C:\Users\sscaini\CmisSync
2018-08-23 08:37:43,220 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Entering constructor.
2018-08-23 08:37:43,274 [1] DEBUG CmisSync.SetupController [(null)] - SetupController - Exiting constructor.
2018-08-23 08:37:47,120 [1] DEBUG CmisSync.Setup [(null)] - Entering constructor.
2018-08-23 08:37:47,133 [1] DEBUG CmisSync.Setup [(null)] - Exiting constructor.


And then nothing happens… of course… since there are no more folders to synchronize!!

ANYONE ELSE GOT THIS PROBLEM/SITUATION?

Are there any setup and/or issue to be considered in order to avoid this situation??

Many thanks,
Federico



Nicolas Raoul

unread,
Aug 29, 2018, 6:40:16 AM8/29/18
to cmis...@googlegroups.com, Cmis...@aegif.jp
Hello Federico,

Sorry for what is happening to you.

CmisSync removes from configuration the configured folders that the user has removed manually.

Maybe the user has removed the Q:\Ufficio Tecnico folder?
Or maybe that folder was not available at that time?
Is Q: a network folder? Maybe it got disconnected briefly, just when the user was starting their PC? It is safer to use the C: drive or a drive that you know is always available.

Best regards,
Nicolas Raoul
CmisSync team
Aegif



--
You received this message because you are subscribed to the Google Groups "CmisSync" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cmissync+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

federic...@fitb.it

unread,
Aug 29, 2018, 6:52:26 AM8/29/18
to CmisSync
Thanks for your prompt answer. This is what I can tell you:
1) User didn't remove folder(s) from synchronization
2) Q:\ it's only a "logical" drive and it's only a trick to map a C:\...\AlfrescoLocal\... subfolder. So no network access for local folders

Regards, Federico

federic...@fitb.it

unread,
Oct 16, 2018, 3:07:24 AM10/16/18
to CmisSync
Hi, once again happens that CMIS Sync removes completely foders from config !!!
See what happens on 2018-10-08 08:37 on debug_log.txt that's in attachment

After that moment Alfresco content and local content are no more connected and no sync is possible !!

Please help us to fix this very hard problem 


Thanks, Federico



Il giorno mercoledì 29 agosto 2018 11:45:29 UTC+2, federic...@fitb.it ha scritto:
debug_log.txt

Nicolas Raoul

unread,
Oct 17, 2018, 2:58:58 AM10/17/18
to cmis...@googlegroups.com, federic...@fitb.it
Hello Federico,

Sorry for what is happening to your installation.

Clearly there must be times where the folder is somehow seen by Windows as non-existent, probably to the subfolder mapping trick you mentioned.

A solution could be to disable the part of CmisSync that removes the configuration elements relative to folders that do not exist anymore.

Best regards,
Nicolas Raoul
Aegif


--
You received this message because you are subscribed to the Google Groups "CmisSync" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cmissync+u...@googlegroups.com.

Jared

unread,
Apr 1, 2019, 7:34:11 AM4/1/19
to CmisSync
Hello,

I have the same problem. CMIS sync removes the folder from it's database. The folder is available, but stops syncing.
However I know reason,,, because my sync folder is inside a 'mounted volume',,, and you need to mount the volume manually when Windows starts up.
So if CMIS does not see the volume on startup, it removes it from the database... pretty annoying.

Then how do we prevent this? Can you explain please how to: "A solution could be to disable the part of CmisSync that removes the configuration elements relative to folders that do not exist anymore"?

Regards, Jared
To unsubscribe from this group and stop receiving emails from it, send an email to cmis...@googlegroups.com.

Nicolas Raoul

unread,
Apr 1, 2019, 10:24:13 PM4/1/19
to cmis...@googlegroups.com
Hello Jared,

Putting CmisSync folders on drives that are prone to disconnecting randomly (such as network volumes) is not supported.

By "A solution could be to disable the part of CmisSync that removes the configuration elements relative to folders that do not exist anymore", I mean modifying the CmisSync source code. CmisSync is open source so you can either do it by yourself, or pay a third-party company to do it, or pay us to do it, whichever you prefer.

Best regards,
Nicolas Raoul
Aegif
To unsubscribe from this group and stop receiving emails from it, send an email to cmissync+u...@googlegroups.com.

Jared

unread,
Apr 2, 2019, 6:18:48 AM4/2/19
to CmisSync
Hello Nicolas.

Thanks for quick feedback.
My 'mounted volume' is a 'TrueCrypt' volume, which gets mounted manually upon host startup. Thus it does not 'randomly' disconnect.
However, I understand the feedback you provided and will look into the options suggested.

One workaround could be: Host startup -> MountVolume -> then start CMIS application. And prevent CMIS from autostart with the OS.

All the best, 
Jared

Nicolas Raoul

unread,
Apr 2, 2019, 7:33:58 AM4/2/19
to cmis...@googlegroups.com
Hello Jared,

The workaround you found should indeed work for a TrueCrypt (or similar) volume, as long as the user does not unmount the volume accidentally (and as long as TrueCrypt does not crash).

Best regards,
Nicolas Raoul
Aegif
To unsubscribe from this group and stop receiving emails from it, send an email to cmissync+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages