[cobalt-users] RE: Problems with RaQ3-en-OSUpdate-5.0.pkg

[Chae <chae@xxxxxxxxxxxx>]

Hi Yah,

Okay what I did was on the initial install I had the GUI pointed to the 
Cobalt FTP site and I thought that this may have caused the error, so I did 
a wget of OS update to the packages folder and then used the GUI to install 
again, this time I watched up top and seen lots of things happening. 
Eventually the GUI returned a screen message of "Package Already Installed" 
but this time the GUI refreshed and the majority of the older version 4 
updates disappeared from the file list...but again no "Reboot" as stated on 
Sun's RaQ3 page.

This is what I currently have installed...

Arpanet Cobalthosting.ch PHP 4.1.2 module for Cobalt RaQ3Release 4.1.2
Gossamer Threads FileMan Release 2.0.0-Raq
Cobalt MySQL Release 3.23.37-1
Cobalt OS Release 5.0
RaQ3-All-CMU Release 2.27
RaQ3-All-System Release 3.0.1-6375
RaQ3-All-Security Release 3.0.1-6579
RaQ3-All-Security Release 3.0.1-6650
RaQ3-All-Security Release 3.0.1-6682
RaQ3-All-System Release 3.0.2-6449
raqpak.com RaQ3-custom-mx Release 1.0
RaQ3-en-OSUpdateRelease 5.0
RaQ34-Solarspeed.net-Bind Release 8.3.3-2
RaQ34-Solarspeed.net-Qpopper Release 4.0.4
CMU-SNMP Update Release 3.7.1
Neomail Release 1.25-5
OpenSSH Release 3.4p1-PM4
POP-Authenticated SMTP Relaying Release 1.2
Linuxnetworking.co.uk Portsentry Release 1.1-fr5
Webalizer Release 1.30-04-7GIF
webmin Release 1.0

Now I might just go do a reboot to finish the install off properly - any 
suggestions?
Don't want to totally kill the server by doing this though. Have just had 
one of our hourly logcheck reports come through and now I see this...

Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.124:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.188:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.123:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.187:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.199:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.217:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.218:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.63:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.64:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.216:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.122:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.186:21 to server 'ProFTPD', already bound to 'ProFTPD'.
Dec 18 17:00:03 ns proftpd[20872]: ns.ourservername.com - cannot bind 
xxx.xxx.xxx.121:21 to server 'ProFTPD', already bound to 'ProFTPD'.

Didn't see anything about changing FTP in the OS update blurb?

Regards

Chae