On 08/09/2010 04:31 AM, Jan de Groot wrote:
On Mon, 2010-08-09 at 04:19 -0500, David C. Rankin wrote:
(98)Address already in use: make_sock: could not bind to address [::]:443 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
Maybe you should read the error messages and check out with tools like lsof what process is using that port.
OK Googling help: [04:38 nirvana:/home/david] # lsof -i tcp:443 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME cupsd 1896 root 8u IPv4 7293 0t0 TCP *:https (LISTEN) cupsd 1896 root 9u IPv6 7294 0t0 TCP *:https (LISTEN) cups?? Now the question is what do I do to fix it? Currently, cups is started as one of the last things: DAEMONS=(syslog-ng network hal named @netfs @ntpd @sshd @dhcpd @crond @avahi-daemon @postfix @mysqld @dovecot @httpd @hylafax @samba @cups @sensors @upsd kdm) I guess I'll try taking them out of background processing. The over 'Arching' point (no pun intended) is how can we make sure that updates, that do not change any packages by adding/deleting, do not kill a primary part of a box? And, why this box and not the backup? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com