Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > Installation/Configuration
Reload this Page Various errors after clean install
Register FAQ Members List Social Groups Calendar Search Today's Posts Mark Forums Read

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 5th June 2009, 12:58
Slowhand Slowhand is offline
Member
  
Join Date: Sep 2007
Posts: 96
Thanks: 6
Thanked 0 Times in 0 Posts
Default Various errors after clean install
I'm getting some errors I wanted to run past you guys...

Once logged in to ISPc3 under Monitor Show mail warn log I get

Code:
Jun 5 09:03:40 sierra postfix/postalias[23325]: warning: /etc/aliases.db: duplicate entry: "root"
Jun 5 11:21:15 sierra postfix/postalias[7337]: fatal: open /etc/aliases.db: Permission denied
My /etc/aliases file looks like this:
Code:
#Added by installer for initial user
postmaster: root
clamav: root
root: server@myregularemailaddress.co.uk
webmaster: root
Is that setup not acceptable?

If I do
Code:
sudo newaliases
I don't get an error.

Under Monitor/mail-log I'm also seeing
Code:
Jun 5 10:15:01 sierra postfix/smtpd[6336]: disconnect from localhost.localdomain[127.0.0.1]
Jun 5 10:20:01 sierra pop3d: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:20:01 sierra pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jun 5 10:20:01 sierra imapd: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:20:01 sierra imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jun 5 10:20:01 sierra postfix/smtpd[6389]: connect from localhost.localdomain[127.0.0.1]
Jun 5 10:20:01 sierra postfix/smtpd[6389]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jun 5 10:20:01 sierra postfix/smtpd[6389]: disconnect from localhost.localdomain[127.0.0.1]
Jun 5 10:25:01 sierra imapd: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:25:01 sierra imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jun 5 10:25:01 sierra pop3d: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:25:01 sierra pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jun 5 10:25:01 sierra postfix/smtpd[6439]: connect from localhost.localdomain[127.0.0.1]
Jun 5 10:25:01 sierra postfix/smtpd[6439]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jun 5 10:25:01 sierra postfix/smtpd[6439]: disconnect from localhost.localdomain[127.0.0.1]
over and over, logged every five minutes.

Presumably not right?

I can't find any other refs to this in the forums. Any ideas?

S
Reply With Quote
Sponsored Links
  #2  
Old 6th June 2009, 10:24
falko falko is offline
Super Moderator
  
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,685
Thanks: 1,899
Thanked 2,599 Times in 2,448 Posts
Default
Quote:
Originally Posted by Slowhand View Post
If I do
Code:
sudo newaliases
I don't get an error.
I guess this means you won't see that error again in ISPConfig.

Quote:
Originally Posted by Slowhand View Post
Under Monitor/mail-log I'm also seeing
Code:
Jun 5 10:15:01 sierra postfix/smtpd[6336]: disconnect from localhost.localdomain[127.0.0.1]
Jun 5 10:20:01 sierra pop3d: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:20:01 sierra pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jun 5 10:20:01 sierra imapd: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:20:01 sierra imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jun 5 10:20:01 sierra postfix/smtpd[6389]: connect from localhost.localdomain[127.0.0.1]
Jun 5 10:20:01 sierra postfix/smtpd[6389]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jun 5 10:20:01 sierra postfix/smtpd[6389]: disconnect from localhost.localdomain[127.0.0.1]
Jun 5 10:25:01 sierra imapd: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:25:01 sierra imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
Jun 5 10:25:01 sierra pop3d: Connection, ip=[::ffff:127.0.0.1]
Jun 5 10:25:01 sierra pop3d: Disconnected, ip=[::ffff:127.0.0.1]
Jun 5 10:25:01 sierra postfix/smtpd[6439]: connect from localhost.localdomain[127.0.0.1]
Jun 5 10:25:01 sierra postfix/smtpd[6439]: lost connection after CONNECT from localhost.localdomain[127.0.0.1]
Jun 5 10:25:01 sierra postfix/smtpd[6439]: disconnect from localhost.localdomain[127.0.0.1]
over and over, logged every five minutes.

Presumably not right?

I can't find any other refs to this in the forums. Any ideas?

S
That's ISPConfig's monitoring module which tries to check which services are running and which are not. There's nothing wrong with this.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
The Following User Says Thank You to falko For This Useful Post:
Numerizen (14th December 2010)
  #3  
Old 6th June 2009, 20:50
Slowhand Slowhand is offline
Member
  
Join Date: Sep 2007
Posts: 96
Thanks: 6
Thanked 0 Times in 0 Posts
Default
Quote:
Originally Posted by falko View Post
I guess this means you won't see that error again in ISPConfig.
Falko,

Thanks as always...

I do still see the error.

In fact, since I installed fail2ban and ran the ISPc update I see
Code:
Jun 5 09:03:40 sierra postfix/postalias[23325]: warning: /etc/aliases.db: duplicate entry: "root"
Jun 5 11:21:15 sierra postfix/postalias[7337]: fatal: open /etc/aliases.db: Permission denied
Jun 5 13:21:15 sierra postfix/smtpd[969]: warning: SASL authentication failure: Couldn't find mech GSSAPI
Jun 5 13:21:15 sierra postfix/smtpd[969]: warning: sierra.myserver.com[192.168.0.55]: SASL GSSAPI authentication failed: no mechanism available
'newaliases' in the terminal still gives no error.

I'm assuming these errors are still current, although they are dated yesterday...?

Are the additional lines because I haven't configured fail2ban?

I was going to follow this:
http://www.howtoforge.com/fail2ban_debian_etch

... although I'm on Ubuntu 8.04...

S
Last edited by Slowhand; 6th June 2009 at 20:59.
Reply With Quote
  #4  
Old 7th June 2009, 14:24
till till is offline
Super Moderator
  
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 32,066
Thanks: 697
Thanked 4,248 Times in 3,260 Posts
Default
Quote:
Jun 5 09:03:40 sierra postfix/postalias[23325]: warning: /etc/aliases.db: duplicate entry: "root"
Jun 5 11:21:15 sierra postfix/postalias[7337]: fatal: open /etc/aliases.db: Permission denied
The aliases db is not part of a ispconfig 3 setup and not managed or changed by ispconfig, so this must have been wrong already before you installed ispconfig. To fix this, just edit the aliases file, remove the duplicate entrys for root and then run the "newaliases" command.

Quote:
Jun 5 13:21:15 sierra postfix/smtpd[969]: warning: SASL authentication failure: Couldn't find mech GSSAPI
Jun 5 13:21:15 sierra postfix/smtpd[969]: warning: sierra.myserver.com[192.168.0.55]: SASL GSSAPI authentication failed: no mechanism available
ISPConfig supports only plain and ogin as authentication mechanisms. Please reconfigure your mail client to use plain or login for smtp authentication.
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #5  
Old 7th June 2009, 18:45
Slowhand Slowhand is offline
Member
  
Join Date: Sep 2007
Posts: 96
Thanks: 6
Thanked 0 Times in 0 Posts
Default
Quote:
Originally Posted by till View Post
The aliases db is not part of a ispconfig 3 setup and not managed or changed by ispconfig, so this must have been wrong already before you installed ispconfig. To fix this, just edit the aliases file, remove the duplicate entrys for root and then run the "newaliases" command.



ISPConfig supports only plain and ogin as authentication mechanisms. Please reconfigure your mail client to use plain or login for smtp authentication.
Till,

Thanks for your reply...

So the aliases file above isn't acceptable? Why don't I get an error when I run 'newaliases' in the terminal?

The second error only appeared after I installed fail2ban and ran the ISPc update command.

I haven't tried to actually use the mailserver by logging in with a client. Could the error have been triggered by the nessus scan I ran? Or by fail2ban?

Edit: I seem to be error free by making my aliases file look like this:
Code:
#Added by installer for initial user
postmaster: server@myregularemailaddress.co.uk
clamav: server@myregularemailaddress.co.uk
root: server@myregularemailaddress.co.uk
webmaster: server@myregularemailaddress.co.uk
Not sure what was wrong with the original setup though...

Thanks :-)

S
Last edited by Slowhand; 7th June 2009 at 18:55.
Reply With Quote
  #6  
Old 14th December 2010, 08:52
Numerizen Numerizen is offline
Member
  
Join Date: Dec 2007
Location: Cherbourg -FRANCE
Posts: 43
Thanks: 14
Thanked 3 Times in 2 Posts
 
Default
Quote:
Originally Posted by falko View Post
I guess this means you won't see that error again in ISPConfig.

That's ISPConfig's monitoring module which tries to check which services are running and which are not. There's nothing wrong with this.
Two hours spent wondering what was wrong with that 'lost connection from localhost' mess !

Once again : it's not a bug, it's a feature !

Thanks for the relief.
Reply With Quote
Reply

Bookmarks

« Previous Thread | Next Thread »
Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Clean install after some testings bzzik Installation/Configuration 3 16th October 2008 15:42
getting dependency errors on libmysqlclient install dagg Installation/Configuration 8 9th September 2008 18:00
Errors when trying to install sshd stackahumanoid Installation/Configuration 2 4th September 2008 16:29
Need help with Postfix Install joelee HOWTO-Related Questions 6 14th September 2007 18:11
VMWare Server Free License - Invalid bardgd HOWTO-Related Questions 6 19th November 2006 17:50


All times are GMT +2. The time now is 06:12.

Contact Us - HowtoForge - Linux Howtos and Tutorials - Archive - Top

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.