Advertisement
Guest User

Untitled

a guest
Jan 30th, 2012
61
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.69 KB | None | 0 0
  1. root@30006545:~# sudo service postfix stop
  2. root@30006545:~# tail -f /var/log/mail.log
  3. Jan 30 21:55:41 30006545 citadel: Startup Problems
  4. Jan 30 21:55:41 30006545 citadel: Posting crash message
  5. Jan 30 22:17:03 30006545 citadel: Can't connect to seeder.us:25: Connection refused
  6. Jan 30 22:20:53 30006545 citadel: citserver: Can't bind: Address already in use
  7. Jan 30 22:20:53 30006545 citadel: TCP port 0.0.0.0:25: (SMTP-MTA) FAILED.
  8. Jan 30 22:20:53 30006545 citadel: citserver: Can't bind: Address already in use
  9. Jan 30 22:20:53 30006545 citadel: TCP port 0.0.0.0:587: (SMTP-MSA) FAILED.
  10. Jan 30 22:20:53 30006545 citadel: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by citadel server. This means, citadel won't be the service provider for a specific service you configured it to. If you don't want citadel to provide these services, turn them off in WebCit via Admin->System Preferences->Network. The failed ports and sockets are: TCP port 0.0.0.0;25; (SMTP-MTA) s TCP port 0.0.0.0:587: (SMTP-MSA) If you want citadel to provide you with that functionality, check the output of "netstat -lnp" on linux Servers or "netstat -na" on *BSD and stop the programm, that binds these ports. You should eventually remove their initscripts in /etc/init.d so that you won't get this trouble once more. After that goto Administration -> Shutdown Citadel to make Citadel retry to bind this port. To make both ways actualy take place restart the citserver with "sendcommand down" The errors returned by the system were: citserver: Can't bind: Address already in usec ;
  11. Jan 30 22:20:53 30006545 citadel: Startup Problems
  12. Jan 30 22:20:53 30006545 citadel: Posting crash message
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement