Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMGR SSH

Status
Not open for further replies.

wpetilli

Technical User
May 17, 2011
1,877
US
I tried logging into my SMGR using winscp and SSH with the admin account. I used the pwrd that I access the web interface with and I get a msg saying 'You are required to change your password immediately (password aged)
Changing password for admin
(current) UNIX password:

I entered the same pwrd since it said 'current' and I'm getting access denied. Tried some others I thought were it and still access denied. What can I do with this?
 
SMGR GUI and cli admin password is not always the same, unless it is set with the same password. Try to login with the default cli admin passwprd.
 
found it finally. Now I receive a 'not enough free space to perform upgrade'. This is a vmware build.. anything specific I can delete to free space? I don't know enough of what is allowed to be deleted and from where.
 
/var/log stuff

/home/useraccounts stuff - maybe someone took some DB backups for Avaya tech support to look at for problems...

/tmp
 
I also have the last 6.3.17.bin and 6.3.17 patch.2 bin still in the home/admin directory. I wasn't sure if I can remove that. Below is the log directory.. not sure what I'm allowed to delete.

root >log
bash: log: command not found
root >cd log
root >ls -l
total 11884
-rw------- 1 root root 372402 Nov 14 2012 anaconda.log
-rw------- 1 root root 28311 Nov 14 2012 anaconda.syslog
-rw------- 1 root root 47374 Nov 14 2012 anaconda.xlog
drwxr-x--- 2 root root 4096 Sep 24 09:30 audit
drwxr-xr-x 6 admin admin 4096 Sep 24 07:40 Avaya
-rw------- 1 root root 63 Feb 24 2013 boot.log
-rw-r--r-- 1 root root 18828 Jul 22 21:13 brcm-iscsi.log
-rw------- 1 root utmp 2089728 Sep 23 19:42 btmp
-rw------- 1 root root 4544195 Sep 24 19:01 cron
-rw------- 1 root root 281317 Aug 22 04:02 cron.1.gz
-rw------- 1 root root 279382 Jul 14 04:02 cron.2.gz
-rw------- 1 root root 279929 Jun 5 04:02 cron.3.gz
-rw------- 1 root root 279500 Apr 27 04:02 cron.4.gz
-rw-r--r-- 1 root root 45220 Jul 22 21:13 dmesg
-rw------- 1 root root 25088 Feb 24 2013 faillog
-rw-r--r-- 1 root root 228928 Sep 24 19:01 lastlog
-rw------- 1 root root 0 Nov 14 2012 maillog
-rw-r--r-- 1 root root 0 Nov 14 2012 mcelog
-rw------- 1 root root 1850265 Sep 24 19:01 messages
drwxr-x--- 5 nortel nortel 4096 May 28 2014 nortel
-rwx------ 1 postgres postgres 0 Nov 3 2014 pgsql
drwxr-xr-x 2 root root 4096 Nov 14 2012 pm
drwx------ 2 root root 4096 Jan 20 2009 ppp
drwxr-xr-x 2 root root 4096 Nov 1 2014 prelink
-rw-r--r-- 1 root root 18737 Sep 24 04:02 rpmpkgs
-rw-r--r-- 1 root root 18737 Sep 17 04:02 rpmpkgs.1
-rw-r--r-- 1 root root 18737 Sep 10 04:02 rpmpkgs.2
-rw-r--r-- 1 root root 18737 Sep 3 04:02 rpmpkgs.3
-rw-r--r-- 1 root root 18737 Aug 27 04:02 rpmpkgs.4
-rw------- 1 root root 228235 Sep 24 19:02 secure
-rw------- 1 root root 232198 Sep 24 04:02 secure.1.gz
-rw------- 1 root root 230915 Sep 9 04:02 secure.2.gz
-rw------- 1 root root 230981 Aug 25 04:02 secure.3.gz
-rw------- 1 root root 230884 Aug 10 04:02 secure.4.gz
-rw------- 1 root root 470791 Sep 24 15:01 slapd.log
-rw------- 1 root root 3084 Jul 22 21:44 snmpd.log
-rw------- 1 root root 0 Nov 14 2012 spooler
-rw------- 1 root root 0 Nov 14 2012 tallylog
drwxrwxrwx 14 root root 4096 Nov 3 2014 usershelllog
drwxrwxrwx 2 root root 4096 Nov 14 2012 usershellog
drwxr-xr-x 2 root root 4096 Mar 18 2015 validate
-rw-rw-r-- 1 root utmp 84480 Sep 24 19:01 wtmp
-rw------- 1 root root 0 Jan 1 2015 yum.log
-rw-r--r-- 1 root root 1006 Jan 1 2015 yum.log.1.gz
 
Yes you can delete the the SMGR .bin files. Those are the service packs applied into the system. You may wanna copy and backup those files in case you need then using winscp.

jtc22
 
Yea, I wound up doing that and I was able to do the upgrade.
 
I also had difficulties with not enough storage before update. I know case is resolved but maybe it will be helpful for someone.

Logs which can be surly deleted could be find for example:
<Istall_PATH>/install_logs/
$JBOSS_HOME/server/avmgmt/log/
$AVAYA_LOG/.../
$SPIRIT_HOME/logging/

and by default those are:
<Istall_PATH> = /opt/Avaya/
$JBOSS_HOME/ = /opt/Avaya/JBoss/
$AVAYA_LOG/ = var/log/AVAYA/mgmt
$SPIRIT_HOME/ = /opt/Avaya/SPIRIT/<rel version>

 
Aside from the previous .iso that were in home/admin there was a 6GB file called SMGR_JBOSS_HEAP.hprof in /opt/Avaya/HeapDump
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top