Hi,
Sorry to bump it, but I've yet to receive even one reply to my question the other day about Dsync ? Everyone else seems to have been receiving replies to their questions and so I'm feeling a little lonely out in the cold.
I can't believe nobody on-list uses Dsync ?
Ben
Hi,
Sorry to bump it, but I've yet to receive even one reply to my question the other day about Dsync ? Everyone else seems to have been receiving replies to their questions and so I'm feeling a little lonely out in the cold.
I can't believe nobody on-list uses Dsync ?
Ben Maybe everyone is waiting for someone smarter than themselves to answer
On 08/20/2013 11:57 AM, Ben wrote: this.. :-)
So.. hoping I read and understood your email correctly ...
The first thing you tried failed because only root can change permissions, except for using the setuid bit which is probably not what you want here. The second might have failed because of:
userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file }
dsync is using userdb and not authdb because it's not checking a password here. Can it be that its-virtmail doesn't have permission to read /etc/dovecot/users ?
Maybe everyone is waiting for someone smarter than themselves to answer this.. :-)
Maybe... but at the same time, there's a risk of me abandoning Dsync for rsync or something else that I know I could have implemented by now with far less frustration ! However I'm keen to learn how to utilise the power within Dsync.... ;-)
So.. hoping I read and understood your email correctly ...
Hoping that email wasn't too confusing ;-(
The first thing you tried failed because only root can change permissions, except for using the setuid bit which is probably not what you want here. The second might have failed because of:
userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file }
dsync is using userdb and not authdb because it's not checking a password here. Can it be that its-virtmail doesn't have permission to read /etc/dovecot/users ?
hmmm ... its chmod 640 root:dovecot on the primary server and the same on the backup box. Do I need to mess around with permissions on both or just the backup box ?
I was under the impression that Dsync was just a more modern version of a doveadm tool that went by a similar name and hence assumed it would use dovecot permissions.
But then again, who knows... I was getting very confused at the end of a long day trying to make it work !
Am 20.08.2013 17:57, schrieb Ben:
Hi,
Sorry to bump it, but I've yet to receive even one reply to my question the other day about Dsync ? Everyone else seems to have been receiving replies to their questions and so I'm feeling a little lonely out in the cold.
I can't believe nobody on-list uses Dsync ?
Ben
perhaps many people are on holidays in summer, however seems in your orig post you used 2.0.19 version there were a lot of updates perhaps first update 2.1.17 or 2.2.5 then retry
also seems you have some permission problems
failed: Permission denied (euid=1002(its_scripts) egid=1002(its_scripts) missing +r perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755)
Best Regards MfG Robert Schetterer
-- [*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
perhaps many people are on holidays in summer, however seems in your orig post you used 2.0.19 version there were a lot of updates perhaps first update 2.1.17 or 2.2.5 then retry
True true... although from my point of view its hard not to be tempted to use rsync or something else that I know. But as I said to a previous respondent, I'm keen to get to know (and hopefully love) my new dovecot install !
I'm on an Ubuntu LTS release so the dovecot came from their release. I'd prefer to stay that way unless I really have to...especially if the only reason for doing so is to fix Dsync. 2.0.19 seems to otherwise working ok ! Maybe I'll have a look through the release notes on a rainy day !
also seems you have some permission problems
failed: Permission denied (euid=1002(its_scripts) egid=1002(its_scripts) missing +r perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755)
Hmmm... I think I tried that at some point, I think that was when the problem might have morphed into ...
dsync(its-virtmail): Error: user test@somewhere.example.com: Initialization failed: mail_location not set and autodetection failed: Mail storage autodetection failed with home=/srv/mail/example.com/test dsync(its-virtmail): Fatal: User init failed dsync-local(test@somewhere.example.com): Error: read() from worker server failed: EOF
But I'll give it another go tomorrow.
Hi
I'm on an Ubuntu LTS release so the dovecot came from their release. I'd prefer to stay that way unless I really have to...
Everyone is entitled to their own opinions, but "IMHO" this kind of attitude is a huge detriment to most software projects. I see very little reason to take such policies personally...
- I use virtualisation (especially lightweight virtualisation such as vservers) so that each service is in its own container. Now if I have no interest in some container and want to let it rot (ie as per LTS), then I can just do so.
- I use a fast moving rolling distro (gentoo in my case, Arch is probably a good choice also) so that I have the option to stay up to date when I want to
The end result is you can be as up to date as you want, or let things rot, as you please.
Unfortunately if you want to use a very old bit of software, then you also get to keep all it's bugs... Sorry.
Good luck! Hope this inspires you to try a different route!
Ed W
participants (4)
-
Ben
-
Ed W
-
Gedalya
-
Robert Schetterer