Management
Highlighted
Management

NSMXpress Upgarde failed because of insufficient disk space

[ Edited ]
‎03-26-2012 07:43 AM

When I tried to upgrade the NSMXpress applinace from version 2011.1 to 2011.4 i run into the following issue.

 insufficient disk space. Could you pls help me to find a resolution to this space issue. I have found few backup files and need advise to delete them (see below output). Any advise to free up space for retry the installation would be appriciated

 

[root@NSMXpress-1 tmp]# sh upgrade-os.sh nsm2011.4_servers_linux_x86.sh offline

......

......

.......

Running preinstallcheck...

Checking if platform is valid...............................ok

Checking for correct intended platform......................ok

Checking for CPU architecture...............................ok

Checking if all needed binaries are present.................ok

Checking for platform-specific binaries.....................ok

Checking for platform-specific packages.....................ok

Checking in System File for PostgreSQL and XDB parameters...ok

Checking for PostgreSQL.....................................ok

Checking if user is root....................................ok

Checking if user nsm exists.................................ok

Checking if iptables is running.............................ok

Checking if installed Device Server is newer................ok

Checking if installed GUI Server is newer...................ok

Checking if installed HA Server is newer....................ok

Checking if system meets RAM requirement....................ok

Checking for sufficient disk space..........................FAILED

ERROR: Need 8633MB more space on partition: /var for the following directories:  /var/netscreen/i                                           nstallerbackup

Specify a directory with adequate

disk space using -niSTAGINGDIR=directory.

Eg: nsm2011.4_servers_linux_x86.sh -niSTAGINGDIR=/var

See nsm2011.4_servers_linux_x86.sh -h for all command-line options.

 

Please correct the error(s) above and run again

Removing staging directory..................................ok

[root@NSMXpress-1 tmp]# df -k

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/sda2              5036316   2833348   1947136  60% /

none                   2075688         0   2075688   0% /dev/shm

/dev/sda10             4032092     45256   3782012   2% /tmp

/dev/sda8             20161172   9182744   9954288  48% /usr

/dev/sda6             85032152  73512168   7200512  92% /var

/dev/sda5             50394964  34476752  13358256  73% /var/cores

/dev/sdb2            235215768 221790332   1477096 100% /var/netscreen/DevSvr

/dev/sda3             50394996   3681612  44153428   8% /var/netscreen/DevSvr/profiler_data

/dev/sda7             20161172   9091904  10045128  48% /var/netscreen/GuiSvr

 

 

-----------------------------------------------------------------

[root@NSMXpress-1 installerbackup]# ls -l

total 3561396

-rw-r-----  1 root nsm   450281546 Apr 27  2010 DevSvr_backup_2007.3r4.tar.gz

-rw-r-----  1 root nsm   445523451 Jun 28  2011 DevSvr_backup_2010.1.tar.gz

-rw-r-----  1 root nsm   197106145 Apr 28  2010 GuiSvr_backup_2007.3r4.tar.gz

-rw-r-----  1 root nsm  1322092893 Jun 28  2011 GuiSvr_backup_2010.1.tar.gz

-rw-r-----  1 root root 1223658471 Jun 28  2011 GuiSvr_backup_.tar.gz

-rw-r-----  1 root nsm      625079 Apr 28  2010 HaSvr_backup_2007.3r4.tar.gz

-rw-r-----  1 root nsm     1965377 Jun 28  2011 HaSvr_backup_2010.1.tar.gz

-rw-r-----  1 root root    1965710 Jun 28  2011 HaSvr_backup_.tar.gz

 

Thx in advance

5 REPLIES 5
Highlighted
Management

Re: NSMXpress Upgarde failed because of insufficient disk space

[ Edited ]
‎03-26-2012 08:20 AM

I'd look at /var/cores and clean up there, as well. Likely core files from software failures, you don't need or want those around.

 

Then, run

 

find /var -type f -size +100000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'

 

Fiddle with the size parameter as desired. That one finds anything bigger than 100MB, you may want to adjust. You should see some legitimate files - firmware and schemas, mostly - and it should also help you find the stuff that's currently cluttering /var.

 

 As for the backup files: Those look like auto-created backups from previous upgrades. I'd say delete all of those. Take a manual backup before upgrade (KB explains how), move that backup off-box. Then clean up other large files that are clutter, see above, then re-run upgrade.

 

 

Highlighted
Management

Re: NSMXpress Upgarde failed because of insufficient disk space

‎03-27-2012 03:46 AM

Thank you for your support. I have manage to remove some of .tar .gz files and free up some space but still requires more spaces. could you please advise is it safe to remove below files / directly from /var folder?

 

########## PERFORMING PRE-INSTALLATION TASKS ##########
Creating staging directory...ok
Running preinstallcheck...
Checking if platform is valid...............................ok
Checking for correct intended platform......................ok
Checking for CPU architecture...............................ok
Checking if all needed binaries are present.................ok
Checking for platform-specific binaries.....................ok
Checking for platform-specific packages.....................ok
Checking in System File for PostgreSQL and XDB parameters...ok
Checking for PostgreSQL.....................................ok
Checking if user is root....................................ok
Checking if user nsm exists.................................ok
Checking if iptables is running.............................ok
Checking if installed Device Server is newer................ok
Checking if installed GUI Server is newer...................ok
Checking if installed HA Server is newer....................ok
Checking if system meets RAM requirement....................ok
Checking for sufficient disk space..........................FAILED
ERROR: Need 1554MB more space on partition: /var for the following directories: /var/netscr een/installerbackup
Specify a directory with adequate
disk space using -niSTAGINGDIR=directory.
Eg: nsm2011.4_servers_linux_x86.sh -niSTAGINGDIR=/var
See nsm2011.4_servers_linux_x86.sh -h for all command-line options.

Please correct the error(s) above and run again
Removing staging directory..................................ok
[root@NSMXpress-1 tmp]# find /var -type f -size +100000k -exec ls -lh {} \; | awk '{ print $ 9 ": " $5 }'
/var/cores/core..devSvrManager.1297928815.11.4421: 179M
/var/tmp/nsm2011.4_servers_linux_x86.sh: 1.3G
/var/tmp/nsm2011.4_servers_upgrade_rs.zip: 1.3G
/var/netscreen/DevSvr/be/schema-binary/nsm.schema.bin: 107M
/var/netscreen/DevSvr/profiler_data/data/base/16384/2619: 969M
/var/netscreen/DevSvr/profiler_data/data/base/16384/2696: 154M
/var/netscreen/DevSvr/logs/20120223/varData.0: 422M
/var/netscreen/DevSvr/logs/20120223/logs.0: 861M
/var/netscreen/DevSvr/logs/20120223/srcPort.index: 130M
/var/netscreen/DevSvr/logs/20120327/varData.0: 231M
/var/netscreen/DevSvr/logs/20120327/logs.0: 454M
/var/netscreen/DevSvr/logs/20120224/varData.0: 288M
/var/netscreen/DevSvr/logs/20120224/logs.0: 603M
/var/netscreen/DevSvr/logs/20120225/varData.0: 293M
/var/netscreen/DevSvr/logs/20120225/logs.0: 612M
/var/netscreen/DevSvr/logs/20120226/varData.0: 434M
/var/netscreen/DevSvr/logs/20120226/logs.0: 880M
/var/netscreen/DevSvr/logs/20120226/srcPort.index: 131M
/var/netscreen/DevSvr/logs/20120102_0.tar.gz: 209M
/var/netscreen/DevSvr/logs/20120206/varData.0: 482M
/var/netscreen/DevSvr/logs/20120206/logs.0: 959M
/var/netscreen/DevSvr/logs/20120206/srcPort.index: 145M
/var/netscreen/DevSvr/logs/20120207/varData.0: 435M
/var/netscreen/DevSvr/logs/20120207/logs.0: 869M
/var/netscreen/DevSvr/logs/20120207/srcPort.index: 130M
/var/netscreen/DevSvr/logs/20120208/varData.0: 462M
/var/netscreen/DevSvr/logs/20120208/logs.0: 920M
/var/netscreen/DevSvr/logs/20120208/srcPort.index: 138M
/var/netscreen/DevSvr/logs/20120209/varData.0: 432M
/var/netscreen/DevSvr/logs/20120209/logs.0: 873M
/var/netscreen/DevSvr/logs/20120209/srcPort.index: 127M
/var/netscreen/DevSvr/logs/20120210/varData.0: 316M
/var/netscreen/DevSvr/logs/20120210/logs.0: 655M
/var/netscreen/DevSvr/logs/20120211/varData.0: 331M
/var/netscreen/DevSvr/logs/20120211/logs.0: 680M
/var/netscreen/DevSvr/logs/20120212/varData.0: 468M
/var/netscreen/DevSvr/logs/20120212/logs.0: 941M
/var/netscreen/DevSvr/logs/20120212/srcPort.index: 136M
/var/netscreen/DevSvr/logs/20120213/varData.0: 500M
/var/netscreen/DevSvr/logs/20120213/logs.0: 999M
/var/netscreen/DevSvr/logs/20120213/srcPort.index: 153M
/var/netscreen/DevSvr/logs/20120214/varData.0: 336M
/var/netscreen/DevSvr/logs/20120214/logs.0: 691M
/var/netscreen/DevSvr/logs/20120215/varData.0: 431M
/var/netscreen/DevSvr/logs/20120215/logs.0: 877M
/var/netscreen/DevSvr/logs/20120215/srcPort.index: 128M
/var/netscreen/DevSvr/logs/20120216/varData.0: 395M
/var/netscreen/DevSvr/logs/20120216/logs.0: 804M
/var/netscreen/DevSvr/logs/20120216/srcPort.index: 119M
/var/netscreen/DevSvr/logs/20120217/varData.0: 276M
/var/netscreen/DevSvr/logs/20120217/logs.0: 575M
/var/netscreen/DevSvr/logs/20120218/varData.0: 271M
/var/netscreen/DevSvr/logs/20120218/logs.0: 566M
/var/netscreen/DevSvr/logs/20120219/varData.0: 389M
/var/netscreen/DevSvr/logs/20120219/logs.0: 793M
/var/netscreen/DevSvr/logs/20120219/srcPort.index: 118M
/var/netscreen/DevSvr/logs/20120220/varData.0: 424M
/var/netscreen/DevSvr/logs/20120220/logs.0: 866M
/var/netscreen/DevSvr/logs/20120220/srcPort.index: 129M
/var/netscreen/DevSvr/logs/20120221/varData.0: 386M
/var/netscreen/DevSvr/logs/20120221/logs.0: 792M
/var/netscreen/DevSvr/logs/20120221/srcPort.index: 118M
/var/netscreen/DevSvr/logs/20120222/varData.0: 441M
/var/netscreen/DevSvr/logs/20120222/logs.0: 900M
/var/netscreen/DevSvr/logs/20120222/srcPort.index: 135M
/var/netscreen/DevSvr/logs/20120323/varData.0: 280M
/var/netscreen/DevSvr/logs/20120323/logs.0: 575M
/var/netscreen/DevSvr/logs/20120324/varData.0: 290M
/var/netscreen/DevSvr/logs/20120324/logs.0: 592M
/var/netscreen/DevSvr/logs/20120325/varData.0: 433M
/var/netscreen/DevSvr/logs/20120325/logs.0: 862M
/var/netscreen/DevSvr/logs/20120325/srcPort.index: 129M
/var/netscreen/DevSvr/logs/20120326/varData.0: 484M
/var/netscreen/DevSvr/logs/20120326/logs.0: 961M
/var/netscreen/DevSvr/logs/20120326/srcPort.index: 144M
/var/netscreen/DevSvr/logs/20120227/varData.0: 505M
/var/netscreen/DevSvr/logs/20120227/logs.0: 1013M
/var/netscreen/DevSvr/logs/20120227/srcPort.index: 148M
/var/netscreen/DevSvr/logs/20120228/varData.0: 507M
/var/netscreen/DevSvr/logs/20120228/logs.0: 1017M
/var/netscreen/DevSvr/logs/20120228/srcPort.index: 148M
/var/netscreen/DevSvr/logs/20120229/varData.0: 428M
/var/netscreen/DevSvr/logs/20120229/logs.0: 868M
/var/netscreen/DevSvr/logs/20120229/srcPort.index: 131M
/var/netscreen/DevSvr/logs/20120301/varData.0: 462M
/var/netscreen/DevSvr/logs/20120301/logs.0: 936M
/var/netscreen/DevSvr/logs/20120301/srcPort.index: 139M
/var/netscreen/DevSvr/logs/20120108_0.tar.gz: 221M
/var/netscreen/DevSvr/logs/20120302/varData.0: 296M
/var/netscreen/DevSvr/logs/20120302/logs.0: 615M
/var/netscreen/DevSvr/logs/20120303/varData.0: 270M
/var/netscreen/DevSvr/logs/20120303/logs.0: 558M
/var/netscreen/DevSvr/logs/20120305/varData.0: 453M
/var/netscreen/DevSvr/logs/20120305/logs.0: 905M
/var/netscreen/DevSvr/logs/20120305/srcPort.index: 136M
/var/netscreen/DevSvr/logs/20120306/varData.0: 455M
/var/netscreen/DevSvr/logs/20120306/logs.0: 908M
/var/netscreen/DevSvr/logs/20120306/srcPort.index: 137M
/var/netscreen/DevSvr/logs/20120307/varData.0: 421M
/var/netscreen/DevSvr/logs/20120307/logs.0: 860M
/var/netscreen/DevSvr/logs/20120307/srcPort.index: 128M
/var/netscreen/DevSvr/logs/20120308/varData.0: 413M
/var/netscreen/DevSvr/logs/20120308/logs.0: 829M
/var/netscreen/DevSvr/logs/20120308/srcPort.index: 122M
/var/netscreen/DevSvr/logs/20120309/varData.0: 280M
/var/netscreen/DevSvr/logs/20120309/logs.0: 582M
/var/netscreen/DevSvr/logs/20120310/varData.0: 300M
/var/netscreen/DevSvr/logs/20120310/logs.0: 613M
/var/netscreen/DevSvr/logs/20120311/varData.0: 474M
/var/netscreen/DevSvr/logs/20120311/logs.0: 947M
/var/netscreen/DevSvr/logs/20120311/srcPort.index: 141M
/var/netscreen/DevSvr/logs/20120312/varData.0: 415M
/var/netscreen/DevSvr/logs/20120312/logs.0: 840M
/var/netscreen/DevSvr/logs/20120312/srcPort.index: 127M
/var/netscreen/DevSvr/logs/20120313/varData.0: 427M
/var/netscreen/DevSvr/logs/20120313/logs.0: 860M
/var/netscreen/DevSvr/logs/20120313/srcPort.index: 127M
/var/netscreen/DevSvr/logs/20120121_0.tar.gz: 154M
/var/netscreen/DevSvr/logs/20120314/varData.0: 416M
/var/netscreen/DevSvr/logs/20120314/logs.0: 841M
/var/netscreen/DevSvr/logs/20120314/srcPort.index: 126M
/var/netscreen/DevSvr/logs/20120315/varData.0: 464M
/var/netscreen/DevSvr/logs/20120315/logs.0: 937M
/var/netscreen/DevSvr/logs/20120315/srcPort.index: 141M
/var/netscreen/DevSvr/logs/20120316/varData.0: 282M
/var/netscreen/DevSvr/logs/20120316/logs.0: 582M
/var/netscreen/DevSvr/logs/20120317/varData.0: 284M
/var/netscreen/DevSvr/logs/20120317/logs.0: 587M
/var/netscreen/DevSvr/logs/20120318/varData.0: 426M
/var/netscreen/DevSvr/logs/20120318/logs.0: 860M
/var/netscreen/DevSvr/logs/20120318/srcPort.index: 129M
/var/netscreen/DevSvr/logs/20120319/varData.0: 411M
/var/netscreen/DevSvr/logs/20120319/logs.0: 832M
/var/netscreen/DevSvr/logs/20120319/srcPort.index: 128M
/var/netscreen/DevSvr/logs/20120320/varData.0: 415M
/var/netscreen/DevSvr/logs/20120320/logs.0: 840M
/var/netscreen/DevSvr/logs/20120320/srcPort.index: 127M
/var/netscreen/DevSvr/logs/20120321/varData.0: 437M
/var/netscreen/DevSvr/logs/20120321/logs.0: 883M
/var/netscreen/DevSvr/logs/20120321/srcPort.index: 132M
/var/netscreen/DevSvr/logs/20120322/varData.0: 436M
/var/netscreen/DevSvr/logs/20120322/logs.0: 875M
/var/netscreen/DevSvr/logs/20120322/srcPort.index: 130M
/var/netscreen/DevSvr/logs/20120304/varData.0: 262M
/var/netscreen/DevSvr/logs/20120304/logs.0: 541M
/var/netscreen/DevSvr/logs/20120101_0.tar.gz: 188M
/var/netscreen/DevSvr/logs/20120103_0.tar.gz: 206M
/var/netscreen/DevSvr/logs/20120104_0.tar.gz: 281M
/var/netscreen/DevSvr/logs/20120105_0.tar.gz: 239M
/var/netscreen/DevSvr/logs/20120106_0.tar.gz: 170M
/var/netscreen/DevSvr/logs/20120107_0.tar.gz: 158M
/var/netscreen/DevSvr/logs/20120109_0.tar.gz: 249M
/var/netscreen/DevSvr/logs/20120110_0.tar.gz: 272M
/var/netscreen/DevSvr/logs/20120111_0.tar.gz: 291M
/var/netscreen/DevSvr/logs/20120112_0.tar.gz: 257M
/var/netscreen/DevSvr/logs/20120113_0.tar.gz: 158M
/var/netscreen/DevSvr/logs/20120114_0.tar.gz: 154M
/var/netscreen/DevSvr/logs/20120115_0.tar.gz: 245M
/var/netscreen/DevSvr/logs/20120116_0.tar.gz: 237M
/var/netscreen/DevSvr/logs/20120117_0.tar.gz: 258M
/var/netscreen/DevSvr/logs/20120118_0.tar.gz: 262M
/var/netscreen/DevSvr/logs/20120119_0.tar.gz: 209M
/var/netscreen/DevSvr/logs/20120120_0.tar.gz: 150M
/var/netscreen/DevSvr/logs/20120122_0.tar.gz: 244M
/var/netscreen/DevSvr/logs/20120123_0.tar.gz: 274M
/var/netscreen/DevSvr/logs/20120124_0.tar.gz: 278M
/var/netscreen/DevSvr/logs/20120125_0.tar.gz: 268M
/var/netscreen/DevSvr/logs/20120126_0.tar.gz: 249M
/var/netscreen/DevSvr/logs/20120127_0.tar.gz: 149M
/var/netscreen/DevSvr/logs/20120128_0.tar.gz: 156M
/var/netscreen/DevSvr/logs/20120129_0.tar.gz: 240M
/var/netscreen/DevSvr/logs/20120130_0.tar.gz: 221M
/var/netscreen/DevSvr/logs/20120131_0.tar.gz: 232M
/var/netscreen/DevSvr/.latest-db-backup/dbbackup.tgz: 1.5G
/var/netscreen/DevSvr/temp/DevSvr/logs/20090623/logs.0: 118M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090613/logs.0: 118M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090619/logs.0: 116M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090601/logs.0: 112M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090627/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090629/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090620/logs.0: 116M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090628/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090622/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090621/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090606/logs.0: 117M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090605/logs.0: 111M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090602/logs.0: 113M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090610/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090609/logs.0: 116M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090614/logs.0: 119M
/var/netscreen/DevSvr/temp/DevSvr/logs/20090626/logs.0: 120M

 

 

Highlighted
Management

Re: NSMXpress Upgarde failed because of insufficient disk space

‎03-27-2012 06:22 AM

Hi,

 

to clean the DevSvr Logs you can use the NSM GUI.

 

Goto "Tools" -> "Log Management" -> "Purge Logs on NSM".

 

It's also possible to archive the logs to a remote server via scp if you want.

Highlighted
Management

Re: NSMXpress Upgarde failed because of insufficient disk space

‎03-30-2012 09:10 AM

I am having the same problem when upgrading to 2011.4.  I am short 1.5GB on the /usr partition.  Cleaning the database doesn't do any good because that's on the /var/netscreen/DevSvr partition.  I've opened a case with JTAC and they gave up trying to find anything else to clean out of /usr.  The biggest problem is that the current DMI Scheme uses over 12GB and the /usr partition is only 20GB total.  Juniper is either going to have to provide a utility to repartition the NSMXpress or move the DMI Schema files over to /var.

 

Did you have any luck with this?  If so, I'd be interested.

 

Nick

Highlighted
Management

Re: NSMXpress Upgarde failed because of insufficient disk space

‎04-03-2012 01:05 AM

Hi Nick,

 

I'm on 2010.4s3 with NSMxpress

 

Filesystem            Size  Used Avail Use% Mounted on

/dev/sda8              20G   14G  4.3G  77% /var/netscreen/GuiSvr

The current schema 226 taks 9 GB:

8.9G    /usr/netscreen/GuiSvr/var/dmi-schema-stage

 

Perhaps you can free some space with KB13555 by deleting old schema information. 

With this KB I was able to update from 2010.4 to 2010.4s3.

 

You can also take a look at KB13955 for general Information about NSM Schema.

 

bye

Markus

Feedback