RE: [cobalt-users] eth1 collisions after cobalt os update

["Andy Brown" <andy.brown@xxxxxxxxxxxxx>]

<snip>
> We own a Cobalt Cube 3 Pro and are having problems with 
> collisions after
> trying to update the os from 6.2 to version 6.4. Using the 
> web interface, we
> download and presumably installed a 6.4 update, only after 
> reboot it is
> still 6.2. Besides that our secundary eth connection seems to 
> be generating
> thousands of collisions per minute, sending well over 3 GB of 
> data per day
> to the internet. We've also been informed by our provider of 
> the fact the IP
> address we have (195.18.68.5) is sending massive amounts of 
> spammail. Now,
> we don't spam, so... what's wrong and what to do about this? 
> Are there any
> email log files to check? I've disabled the secundary eth 
> connection, so the
> collisions stopped (duh!), but that's no solution...
</snip>

It sounds suspiciously like you have an open relay on email. To view the current email queue do:
mailq
and to watch what is going in/out of the mail server do:
tail -f /var/log/mail
(Just ctrl-c to stop that, as it'll constantly follow the file as its written to)


Regarding the collisions are you judging this by the interface diagnostics via ifconfig or via a switch/hub/router at the next hop up? Just curious about how a possible update could do this, since to my knowledge no new modules were deployed as part of the O/S update, however there is a different kernel for the VPN, etc so this may have sparked off the problems. Although we've been running with the latest for our Qube3 (various types) and had no problems, it may be that a hardware fault has become apparent??

Regards,

Andy
andy@xxxxxxxxxxxxxxx
http://www.raqpak.com/ <-- Raq/Qube unofficial PKGs and support advice