archiver how to start
-
Hi @byteschubser ,
@byteschubser said in archiver how to start:
How to create an archive store? no hint found in the docs.
https://documentation.kopano.io/kopano_archiver_manual/archive_management.html
The short version is that you should use
--auto-attach. This will create an archive store once the first message is scheduled to be archived for the processed user. If you don’t want to auto attach, you can hook manually hook a store as explained in https://documentation.kopano.io/kopano_archiver_manual/archive_management.html#hooking-an-archive-store.@byteschubser said in archiver how to start:
archiver.cfg: server_socket points to the user server or to the archive server? No hint found in the docs. I configured the user server.
That essentially does not matter, as when the configured server is not the one that is the target he will do a redirect to the right server. you could save yourself from this redirect by configuring the archiver as the first server to connect to.
@byteschubser said in archiver how to start:
Does it mean archifer.cfg should point to the db of the archive server or is it another, a 3rd database?
The archive configured in the archiver.cfg is a helper database to manage single instance attachment data. it needs to be a dedicated database, that is reachable by all kopano-archiver processes.
-
Thank you @fbartels
Unfortunately, kopano-archiver does nothing. The oldest mail in the test environment is from last year. I would expect, archiver should copy all mails to the archive that are older than 1 day.
from archiver.log:
Wed Apr 18 10:09:47 2018: [debug ] Initializing provider "Kopano Directory Service" Wed Apr 18 10:09:47 2018: [debug ] Initializing provider "Private Folders" Wed Apr 18 10:09:47 2018: [debug ] Initializing provider "Public Folders" Wed Apr 18 10:09:47 2018: [info ] Startup command: "kopano-archiver" "-A" "--auto-attach" Wed Apr 18 10:09:47 2018: [crit ] Version 8.6.80.590 Wed Apr 18 10:09:47 2018: [crit ] Config settings: Wed Apr 18 10:09:47 2018: [crit ] * archive_after = '1' Wed Apr 18 10:09:47 2018: [crit ] * archive_enable = 'yes' Wed Apr 18 10:09:47 2018: [crit ] * auto_attach_writable = 'no' Wed Apr 18 10:09:47 2018: [crit ] * cleanup_action = 'store' Wed Apr 18 10:09:47 2018: [crit ] * cleanup_follow_purge_after = 'yes' Wed Apr 18 10:09:47 2018: [crit ] * delete_after = '366' Wed Apr 18 10:09:47 2018: [crit ] * delete_enable = 'yes' Wed Apr 18 10:09:47 2018: [crit ] * delete_unread = 'no' Wed Apr 18 10:09:47 2018: [crit ] * enable_auto_attach = 'yes' Wed Apr 18 10:09:47 2018: [crit ] * log_buffer_size = '0' Wed Apr 18 10:09:47 2018: [crit ] * log_file = '/var/log/kopano/archiver.log' Wed Apr 18 10:09:47 2018: [crit ] * log_level = '6' Wed Apr 18 10:09:47 2018: [crit ] * log_method = 'file' Wed Apr 18 10:09:47 2018: [crit ] * log_timestamp = 'yes' Wed Apr 18 10:09:47 2018: [crit ] * mysql_database = 'kopano_archiver' Wed Apr 18 10:09:47 2018: [crit ] * mysql_engine = 'InnoDB' Wed Apr 18 10:09:47 2018: [crit ] * mysql_host = 'XXXXXX' Wed Apr 18 10:09:47 2018: [crit ] * mysql_password = '********' Wed Apr 18 10:09:47 2018: [crit ] * mysql_port = '3306' Wed Apr 18 10:09:47 2018: [crit ] * mysql_socket = '' Wed Apr 18 10:09:47 2018: [crit ] * mysql_user = 'XXXXX' Wed Apr 18 10:09:47 2018: [crit ] * pid_file = '/var/run/kopano/archiver.pid' Wed Apr 18 10:09:47 2018: [crit ] * purge-soft-deleted = 'no' Wed Apr 18 10:09:47 2018: [crit ] * purge_after = '3660' Wed Apr 18 10:09:47 2018: [crit ] * purge_enable = 'no' Wed Apr 18 10:09:47 2018: [crit ] * server_socket = 'https://XXXXXXXXXXXXXX:237' Wed Apr 18 10:09:47 2018: [crit ] * sslkey_file = '/etc/kopano/XXXXXXXX.pem' Wed Apr 18 10:09:47 2018: [crit ] * sslkey_pass = '********' Wed Apr 18 10:09:47 2018: [crit ] * stub_after = '2' Wed Apr 18 10:09:47 2018: [crit ] * stub_enable = 'yes' Wed Apr 18 10:09:47 2018: [crit ] * stub_unread = 'no' Wed Apr 18 10:09:47 2018: [crit ] * track_history = 'no' Wed Apr 18 10:09:47 2018: [debug ] Archiver mode: 8: (Auto attach) Wed Apr 18 10:09:47 2018: [debug ] Archiver action: Autoattach flags: 0 Wed Apr 18 10:09:47 2018: [debug ] ArchiverImpl::AutoAttach() function entry Wed Apr 18 10:09:47 2018: [debug ] ArchiverImpl::AutoAttach() about to create collector Wed Apr 18 10:09:47 2018: [debug ] ArchiverImpl::AutoAttach() about to get state updater Wed Apr 18 10:09:47 2018: [debug ] ArchiverImpl::AutoAttach() about to call update all Wed Apr 18 10:09:47 2018: [debug ] ArchiveStateUpdater::UpdateAll() function entry Wed Apr 18 10:09:47 2018: [debug ] Archiver result 0 (Success)If I force a user name, the log ends by:
Wed Apr 18 10:28:24 2018: [debug ] Archiver mode: 8: (Auto attach) Wed Apr 18 10:28:24 2018: [debug ] Archiver action: Autoattach for user user@example.com, flags: 0 Wed Apr 18 10:28:24 2018: [debug ] For 'user@example.com': ArchiveManageImpl::AutoAttach(): function entry Wed Apr 18 10:28:24 2018: [debug ] For 'user@example.com': ArchiveManageImpl::AutoAttach(): about to create ArchiveStateCollector Wed Apr 18 10:28:24 2018: [debug ] For 'user@example.com': ArchiveManageImpl::AutoAttach(): about to get ArchiveStateUpdater Wed Apr 18 10:28:25 2018: [debug ] For 'user@example.com': ArchiveManageImpl::AutoAttach(): about to call ArchiveStateUpdater::Update Wed Apr 18 10:28:25 2018: [debug ] For 'user@example.com': ArchiveStateUpdater::Update(): function entry Wed Apr 18 10:28:25 2018: [debug ] For 'user@example.com': Unable to find entry for user 'user@example.com', trying to resolve. Wed Apr 18 10:28:25 2018: [error ] For 'user@example.com': Unable to find entry for userid XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX. Wed Apr 18 10:28:25 2018: [debug ] For 'user@example.com': ArchiveManageImpl::AutoAttach(): function exit. Result: 0x8004010F (not found) Wed Apr 18 10:28:25 2018: [debug ] Archiver result 1 (Failure) -
On your primary (to be archived) system, does the primary show up with kopano-admin --details <user> --type archive? This is mandatory so that an archive run can work. It seems it is not configured properly yet which is why kopano-archiver can not find the store. Auto-attach simply just does the job and creates the store for you with the first run of archiver. Is multi-server setup correctly?
-
@mkromer said in archiver how to start:
On your primary (to be archived) system, does the primary show up with kopano-admin --details <user> --type archive? This is mandatory so that an archive run can work. It seems it is not configured properly yet which is why kopano-archiver can not find the store. Auto-attach simply just does the job and creates the store for you with the first run of archiver. Is multi-server setup correctly?
How to check, if multi-server setup is correctly? Webapp Logon works fine. Sending and reciving also… No other errors.
[uwe@node3 ~]# kopano-admin --detail testuser@example.com --type archive No archive found for user 'testuser@example.com'. Using the -v option (possibly multiple times) may give more hints.and without “–type archive”
[uwe@node3 ~]# kopano-admin --detail testuser@example.com User object id: 00000000AC21A95040D3EE48B319FBA75330442501000000060000003B0000004F546B354F513D3D00000000 User store id: 0000000038A1BB1005E5101AA1BB08002B2A56C200007A617261666136636C69656E742E646C6C000000000040051E87833D466ABBE1792C8340EC530100000001000000E1482BC6DA8E4A03A117D086670A013070736575646F3A2F2F4 B6F70616E6F2D53657276657200 Username: testuser@example.com Fullname: Test User Emailaddress: testuser@example.com Active: yes Administrator: no Address book: Visible Auto-accept meeting req:no Home server: Kopano-Server Out Of Office: disabled Mapped properties: 0x8C6D0102 48 bytes PR_SURNAME Test User PR_EC_ENABLED_FEATURES imap; mobile; outlook; pop3; webapp PR_EC_DISABLED_FEATURES PR_EC_ARCHIVE_SERVERS Archiv-Server Current user store quota settings: Quota overrides: no Warning level: unlimited Soft level: unlimited Hard level: unlimited Current store size: 2.91 MB Groups (1): Everyone Archive details on node 'Archiv-Server': No archive found for user 'testuser@example.com'. -
For Multi-Server I recommend you check https://documentation.kopano.io/kopanocore_administrator_manual/special_kc_configurations.html#multi-server-setup on how to set it up accordingly. Basically in very short summary, you need to setup 2 multi-server nodes. 1 primary, 1 archive server. on the archive server you also install kopano-archiver packages. with configuration of archiver.cfg you create a second db on archive system for (as @fbartels outlined) dedup data. you have to setup ssl (and even though optional) you can also create an admin.cfg (you can check our man kopano-admin for that). this way, you would be able to communicate in “multi-server” fashion, so that the primary node for example is able to communicate with the archive server. With the corresponding multi-server setup correctly (see link above), you should also then have a valid configuration visible with kopano-stats --servers. with all that in place, also with archiver setup accordingly, auto-attach will automatically create your archive stores and you then are able to do --details --type archive also from the primary node.
- mike
-
Also, don’t forget to setup the right archive server in LDAP for the user (Attribute kopanoUserArchiveServer) to the CN of the kopano-server object you created. This is actually what kopano-admin uses to identify to which archive server it should connect, since you can have as many archive servers as you want and can define which archive server a user should use.
-
Yes I have worked according these docs.
1 Server called Kopano-Server and DB called kopano
1 Server called Archiv-Server and DB called kopano_archi
additional db for kopano-archiver called kopano_archiverboth server dbs are populated with tables, the extra db of kopano-archiver is empty.
kopano-stats shows me both servers Kopano-Server
ssl works fine
servers communicating together, I see ssl accept in the server.log of the archive server if I submit the kopano-admin --detail commandLDAP server objects are present
LDAP user attribute is set, please see kopano-admin --detail output abovealthough all these steps, kopano-archiver --auto-atach does not create the archive store
-
So this is the moment where traditionally the support kicks in, because to be honest, at least I’m currently out of ideas what can be wrong. May I ask - Do you have a valid subscription? This would give me the chance to dispatch this to our support team so it can have a look and walk through and check what is missing. I can tell you for sure: It must be something small and obvious, but I recommend a session to walk through instead of walking it the hard way here in forums.
- mike
-
-
@byteschubser Maybe you should have a look some more details… I just remember when I started with archiver and it was hard to find out what exactly is the problem if it is actually your first time to setup this part of Kopano server.
For me first of all it is interesting if you’re using AD oder OpenLDAP. I ask you this because in AD with its plugin on windows some things are easier to setup and to identify. With OpenLDAP i.e. you have to enter some server names and here was my issue. The Servername in there is the one thing - the other thing is what CN to use in Certificate… This is actually not really clear documented in Kopano Manuals. I ended with adding Alternative DNS Entries in certificate to stop thinking about this ;-) Actually this was the main issue what I had with my setup.
Andreas
-
@byteschubser said in archiver how to start:
No, I don’t have a subscription.
I’ll give it a last try in a fresh and clean environment.
Just to inform you: A fresh LDAP and Kopano Installation lead also in failure with the same behavior. The archive store will not be created. There is no debug output at server side an there is no usable debug output at archiver site.
Archive map has no entry for user
ArchiveManageImpl::AutoAttach(): funktion exit. Result: 0x8004010F (not found) -
ok, I gave it a very last try without hosted (multiple companies) - now it works
Question: is archiving not possible in hosted installation?
-
@byteschubser said in archiver how to start:
Question: is archiving not possible in hosted installation?
No, that feature should indeed also work when running multi tennant installations.
But since you are running a hosting business on top of the Kopano software I would recommend once more to get in contact with our support, so that you have a reliable fallback in case you run into problems. your customers will thank you for it.
