×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

how to clean /dev/sd1

how to clean /dev/sd1

how to clean /dev/sd1

(OP)

Hi Everybody, we have CS1000 7.6, we have full Dev/sd1 directory, somebody know how to clean it.

Regrads

RE: how to clean /dev/sd1

I haven't worked on Nortel / Avaya systems for many years, but still have access to an old database that might help with this record that I've found?

Problem
Increasing the log file rotation on a linuxbase signalling server

Solution Summary
Log in to the server in question at root level and use the VI commands
This applies to Any linuxbase sig server hosting Avaya/nortel applications

Details:
Sometimes Avaya request debug log file collection to assist in problem resolution and it may be necesary to increase the amount of historical ss_common.log file held on the affected server.
To do this do the following
1. log in to the server CLi and expedite to root user
2. Navigate to /etc/logrotate.d directory
3. cat the existing file ss_common_syslog (It will show the default value as per below)
/var/log/nortel/ss_common.log
{
nocompress
daily
rotate 5
create 640 root nortel
olddir /var/log/nortel/old_logs/
size=5M
missingok
sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/rsyslogd.pid 2> /dev/null` 2> /dev/null || true
endscript
}
4. Using the VI editor modify the file to read as per below
/log/nortel/ss_common.log
{
compress
daily
rotate 30
create 640 root nortel
olddir /var/log/nortel/old_logs/
size=5M
missingok
sharedscripts
postrotate
/bin/kill -HUP `cat /var/run/rsyslogd.pid 2> /dev/null` 2> /dev/null || true
endscript
}
5. Then restart the services, for example

$ /sbin/service rsyslog restart
EXAMPLE:
[root@netsucm ~]# /sbin/service rsyslog restart
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
[root@netsucm ~]#




Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = http://somertel.net
linkedin

RE: how to clean /dev/sd1

Look in Folder patch too
There sometime forgotten uploaded Service packs

RE: how to clean /dev/sd1

(OP)
Good Morning, thanks for you help, this is the message that we had on the CS1000 7.6:


linuxbase: (EMERG) Base: alarm(817): PID[18133]: WARNING SET: '/dev/sda11' disk is getting full and has passed the 85% threshold. Only 309837824 bytes remain.

We have trouble to clean this partition.

Thanks

RE: how to clean /dev/sd1

What Hardware has you run ?
CPDC? CPPM ?
Login over ssh
Type DF -h and present output here

RE: how to clean /dev/sd1

(OP)

Thanks for your answers.

~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda11 2.0G 1.6G 294M 85% /
/dev/sda5 257G 9.8G 234G 5% /var
/dev/sda10 48G 510M 45G 2% /var/log
/dev/sda9 24G 173M 23G 1% /var/coredump
/dev/sda8 20G 1.4G 18G 8% /opt
/dev/sda7 20G 173M 19G 1% /tmp
/dev/sda6 7.8G 148M 7.3G 2% /home
/dev/sda2 69G 955M 65G 2% /admin
/dev/sda1 93M 43M 46M 48% /boot
tmpfs 2.0G 16K 2.0G 1% /dev/shm

NTDW99CAE5 14C4296001J6 CP-PM CS

Regards

RE: how to clean /dev/sd1

Hi i saw your answer late
A bit strange because active logs and traces are actually stored in the /var partition and cause a disruption.
I've never seen the sda11 on our systems like this.
You should go into the system with the browser and check the "Software Loads".
Check if the file ".nai " still on system .
If yes delete it
I think there are still all the installation files on it
Is that a hardware CPDC , CPPM

RE: how to clean /dev/sd1

(OP)
CPPM

RE: how to clean /dev/sd1


Wich system is installed there ?
Callserver or signaling server ?

RE: how to clean /dev/sd1

Follow those steps to clean up

How to free up disk space for Service Pack installation.
If during SP installation you get an error message like “There is no enough disk space on “/var” partition”, you should follow these steps to free up additional disk space.
If you want to free up disk space on “/admin” partition:
Remove *.nai file(s) from the system. Log in to UCM and go to Software Deployment Software Loads. Select *.nai load(s) and click ‘Delete’ button. ->
If you want to free up disk space on “/var” partition:
1. Remove patching content.
Log in to UCM and go to Patches -> Patches and select one of the three targets:
Service Packs & Deplists – if you want to remove Service Packs/Deplists;
Patches – if you want to remove patches;
Loadware – if you want to remove Loadware file(s);
Select unnecessary Patch Content and click ‘Delete’ button.
2. Clean up backup archives.
Log in to UCM and go to Software Deployment -> Backups page, select backup(s), and click ‘Delete’ button. You can save your backup files on remote servers (SFTP backup).
3. Remove any files from “/var/opt/nortel/patch/sp”. Login as nortel/admin2 on CS1000 and invoke:
cd /var/opt/nortel/patch/sp
rm *
4. Empty the /var/opt/nortel/base/RecoveryCache folder. Login as nortel/admin2 on CS1000 and invoke:
cd /var/opt/nortel/base/RecoveryCache
rm *
5. To free up temporary disk space consumed by patching operations.
It is necessary to clear completed activities in Patching Manager. All ongoing operations on targets can be viewed in the "In Progress" tab. Options are given to proceed with patching activation once patching impact assessment is completed (in manual mode) or to clear completed operations. Both should be done promptly to free up space and allow other patching of any other targets to proceed.
6. Clean up old logs from “/var/log/nortel/old_logs/”. Login as nortel/admin2 user on CS1000 and invoke:
cd /var/log/nortel/old_logs
rm *
7. Clean up two Jboss log folders on the Primary UCM:
“/var/opt/nortel/Jboss-Quantum/conf/quantum-config/securityserver/stats/” and “/var/opt/nortel/Jboss-Quantum/conf/quantum-config/securityserver/log/”
Login as nortel/admin2 user on CS1000 and invoke:
[nortel@kwei]$ cd /var/opt/nortel/Jboss-Quantum/conf/quantum-config/securityserver/stats/
[nortel@kwei stats]$ ll
total 60104
-rw-r--r-- 1 nortel nortel 5735784 Jul 9 09:04 amMasterSessionTableStats
-rw-r--r-- 1 nortel nortel 39464614 Jul 9 09:04 amPolicyStats
-rw-r--r-- 1 nortel nortel 16263642 Jul 9 09:04 idRepoCacheStat
[nortel@kwei stats]$ touch tempstat
[nortel@kwei stats]$ chmod 644 tempstat
[nortel@kwei stats]$ cp tempstat amMasterSessionTableStats
[nortel@kwei stats]$ cp tempstat amPolicyStats
[nortel@kwei stats]$ cp tempstat idRepoCacheStat
[nortel@kwei stats]$ ll
total 0
-rw-r--r-- 1 nortel nortel 0 Jul 9 09:08 amMasterSessionTableStats
-rw-r--r-- 1 nortel nortel 0 Jul 9 09:08 amPolicyStats
-rw-r--r-- 1 nortel nortel 0 Jul 9 09:08 idRepoCacheStat
-rw-r--r-- 1 nortel nortel 0 Jul 9 09:05 tempstat
[nortel@kwei stats]$ cd /var/opt/nortel/Jboss-Quantum/conf/quantum-config/securityserver/log/
[nortel@kwei log]$ ll
total 12800
-rw-r--r-- 1 nortel nortel 99825 Jul 9 08:51 amAuthentication.access
-rw-r--r-- 1 nortel nortel 130734 Jul 9 09:10 amAuthentication.error
-rw-r--r-- 1 nortel nortel 11149768 Jul 9 08:51 amPolicy.access
-rw-r--r-- 1 nortel nortel 1302741 Jul 9 08:50 amPolicyDelegation.access
-rw-r--r-- 1 nortel nortel 7738 Jul 9 08:49 amPolicy.error
-rw-r--r-- 1 nortel nortel 181853 Jul 9 08:51 amSSO.access
-rw-r--r-- 1 nortel nortel 181524 Jul 9 08:51 ecm-administration.access
[nortel@kwei log]$ touch templog
[nortel@kwei stats]$ chmod 644 templog
[nortel@kwei log]$ cp templog amAuthentication.access
[nortel@kwei log]$ cp templog amAuthentication.error
[nortel@kwei log]$ cp templog amPolicy.access
[nortel@kwei log]$ cp templog amPolicyDelegation.access
[nortel@kwei log]$ cp templog amPolicy.error
[nortel@kwei log]$ cp templog amSSO.access
[nortel@kwei log]$ cp templog ecm-administration.access

8. Clean up SPS logs (if NRS applications are deployed). Login as nortel/admin2 user on CS1000 and invoke:
cd /var/opt/nortel/sps/LOG/old_logs/
rm *
9. Uninstall previously applied patches.
delete the files as mentioned above. if still warning is seen then the only way we have is to increase the size of hard disk or change the hardware to CPDC



You may also find large log old files in the following directory:

/var/opt/nortel/Jboss-Quantum/conf/quantum-config/old_logs

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close