Hey,
could it be that the calls to exmdb_provider/http([::1]:5000) differ when running gromox-import from an export done via
gromox-export -u $MBX --loglevel=6 -s --mt -a -r /
to the slightly reducedgromox-export -u $MBX --loglevel=6 -s --mt -a -r IPM_SUBTRE
in such a way that import will/can/might run into problems connecting to the http which then end up with a XXX-load of
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
exmdb_client: connected to [localhost]:5000 (fd 4), hnew=1
exm: write_message RPC failed
exmdb_client: disconnected from [localhost]:5000 (fd 4), hnew=0
Yes, i activated "-c"ontinue as with that count of failures most imports won't do at all. In fact the mailboxes get imported, they just have to spew like 1k silly notices before it happens. 🙈
I redone the exports with / and IPM_SUBTREE and the imports always make that noise then i used /
It is also not happening on every mailbox, just some of them (the bigger ones in comparisment).
So if you test it yourself maybe take some mailboxes that are also a bit "older" or something. I don't have any idea why and how it is happening but i can easily reproduce it and am just confused soo.... "HUHHH?!" 🙊
Or are these actual problematic folderproperties that don't get handled on the exports but only verified on the imports???
Hey,
could it be that the calls to exmdb_provider/http([::1]:5000) differ when running gromox-import from an export done via
gromox-export -u $MBX --loglevel=6 -s --mt -a -r /to the slightly reduced
gromox-export -u $MBX --loglevel=6 -s --mt -a -r IPM_SUBTREin such a way that
importwill/can/might run into problems connecting to thehttpwhich then end up with a XXX-load ofYes, i activated "-c"ontinue as with that count of failures most imports won't do at all. In fact the mailboxes get imported, they just have to spew like 1k silly notices before it happens. 🙈
I redone the exports with / and IPM_SUBTREE and the imports always make that noise then i used /
It is also not happening on every mailbox, just some of them (the bigger ones in comparisment).
So if you test it yourself maybe take some mailboxes that are also a bit "older" or something. I don't have any idea why and how it is happening but i can easily reproduce it and am just confused soo.... "HUHHH?!" 🙊
Or are these actual problematic folderproperties that don't get handled on the exports but only verified on the imports???