Post i wrote back in 2013. I know Putty doesn't work for you, but here it is anyway. Keep in mind the replacement window for these faulty UC modules is well and truly over. So, either:
1) reimage the thing with an upgrade and hope for the best
or
2) Deploy VMPRO on a windows machine/ Application server and use the presence of the UC module in the system to provide you with an ongoing Preferred Edition license.
or
3) Migrate your licensing to PLDS and get the real version of the Preferred Edition license. Then see step 2.
SOLN236726
Customer is viewing the System Status Application and has noticed the UC Module is showing over 90% full. They are seeing alarms that UC Module is over 90% full.
To confirm the issue, access the UC Module operating system using a ssh client such as PuTTY.
• Login using the Administrator login, then the Admin login and then finally as the root user.
There are several nohup.out files that are growing more than they should.
run the following command from ./
• find -iname nohup.out
This will return the location of all nohup.out files on the hard drive.
Location of the nohup.out files:
./nohup.out (3.3GB)
./opt/vmpro/nohup.out (1.8 GB)
./opt/Avaya/oneXportal/openfire/bin/nohup.out (<100KB)
File sizes will vary depending on system size and configuration.
PROBLEM CLARIFICATION
nohup.out files are being written to incorrectly which is causing the UC Module HDD to fill up unnecessarily.
CAUSE
software
SOLUTION
The nohup.out files can be deleted and a UC Module reboot will be required to recover the disk space.
**WARNING**
Please note that deleting system files should only be completed by knowledgeable personnel as deleting the wrong files can cause irrevocable system damage.
The nohup.out files will continue to be written to even after being deleted as they are recreated on boot. The deletion of these files is only intended to provide interim relief until the available Critical Patch or software solution can be applied to the UC Module.
A Critical Patch has been created to resolve this issue.
CP vmpro-8.1-9302.1_el6.i586.rpm
CP cli-8.1.99-50738.el6.i586.rpm
CP cli-commands-8.1.99-50738.el6.i586.rpm
All 3 critical patches are required to completely resolve the nohup.ot files from being written to the UCM HDD
Referencing:
See also:
thread940-1726121
thread940-1728150
thread940-1723433
thread940-1711367
thread940-1785910
thread940-1723433
thread940-1726346
Depending on the URI configuration the ICR can be completely ignored.
If your URI is configured to use internal data then the IP Office will look into the user's SIP tab and if you have *'s it will look into ICR.
A madman with a taste for speed.
