Analyzer upgrade from 5.6 to 6.0 becomes unresponsive after 8 hours

The box will complete it's database rebuild as per the documentation but after about 8 hours of running, most of the processes go into a zombie state and the web gui becomes unavailable. You can ssh onto the box but an execute reboot just sits there and you have to physically power cycle the device. I've tried completely removing the db and rebuilding it but I continue to have the same issues.

Are there any commands that can be used to see what the box is actually doing (something like view /var/log/messages) or something similar. The diagnose test application commands sometimes work and sometimes don't and not having access to the actual unix cli is quite frustrating.

The box is swapping a lot and execute iotop shows sqllogd being the main culprit. It looks like the box is running out of memory

It seems it hit the bug#502046(initd has a bug to deadlock in certain situations and stop responding to signals/respawing crashed daemons) which was fixed on B279. and it had sqllogd high memory issue, Is it possible to get some more info as below for investigation?

I've been watching the box over the last 24 hours and it's definitely just before 8 hours during the database rebuild that the box begins to swap and inserts into the database start taking up to 30 minutes. The only way to resolve is to disable sql, reboot and re-enable sql.I've now removed the db and restarted and just let the box run without rebuilding from the archive logs.

Is there an email address or something I can send the output of those commands to as diag log device for example will include firewall hostnames and serial numbers which I don't really want floating around on the internet :)