this is the messages i get
Code:Message: system failure: exception during auth {RemoteManager: mail.server.com->zimbra@mail.server.com.:22} Error code: service.FAILURE Method: GetServerNIfsRequest Details:soap:Receiver
this is the messages i get
Code:Message: system failure: exception during auth {RemoteManager: mail.server.com->zimbra@mail.server.com.:22} Error code: service.FAILURE Method: GetServerNIfsRequest Details:soap:Receiver
Assuming you're using the standard ssh port:
1. Check /etc/sshd_config and be sure it's set to 22
2. stop/start/restart sshd
3. su - zimbraCode:/etc/init.d/ssh restart
4. Be sure zimbra's ssh port is set to 22
5. Generate new ssh keysCode:zmprov ms server.domain.com zimbraRemoteManagementPort 22
6. Deploy the keysCode:cd /opt/zimbra/bin/ ./zmsshkeygen
To test this, you can run the following command:Code:./zmupdateauthkeys
-Shouldn't prompt you for a password at this point...then check the admin console mail queues area/servers/certificates.ssh -vi .ssh/zimbra_identity -o strictHostKeyChecking=no zimbra@server.domain.com -p 22
If you continue to get that error please see this doc for some more ideas Mail Queue Monitoring - Zimbra :: Wiki
-Mike Morse (MCode151)
ZCS-to-ZCS Migrations & Moves | Admin Tools & Tidbits » ZimbraBlog.com | ZimbraCommunity.com
i am using standard ssh port but i'm wondering if it's because i have it locked down to certain users. i don't remember if i noticed this before so i'm not sure of the change.
i will follow your advice and report back.
Thanks.
Hello Mike,
If for some reason, we need to change the SSH port to something else (e.g. 2222), what should we do?
Thanks.
Rgds,
Kevin
Pretty much the same steps as Mike has already provided; though using a different port a quick search would have found :- Change Port 22.
There are currently 1 users browsing this thread. (0 members and 1 guests)