Looks like Artico logs are not collected in the Stornext snapshot. Heres a way to gather Artico logs:

Per Jonathan McNerny/SPS

 

 Thanks Kevin.  This applies to any appliance running the NAS stack of course so not just ‘Aritico’. 

 

The log collection is designed to put the support bundle into a SMB share created when you enable NAS functionality from the service.sh script as the admin user (./service.sh –admin).  If you look at the smb.conf file you’ll see there is a share named ‘support’.

 

[root@spsgw1 ~]# cat /etc/samba/smb.conf | grep -A6 "support"

[support]

    path            = /var

    comment         = "Quantum Support"

    browseable      = yes

    writeable       = no

    printable       = no

    veto files      = /account/ /agentx/ /cache/ /ctdb/ /cvs/ /db/ /DXi/ /empty/ /games/ /lib/ /local/ /lock/ /lost+found/ /mail/ /nis/ /opt/ /pancetera/ /preserve/ /run/ /spool/ /upgrade/ /tmp/ /www/ /yp/

 

Here is what the share looks like from a UNC path in windows.

 

 

The log file can be easily copied and pasted from here and usually is small enough to email directly.

 

You’ll also notice a snnas-db-package tar file in this directory if you’ve done a backup.  You do this from the same NAS shell by running ‘system backup’.

 

G300:spsgw1> system backup

 

Creating configuration backup /var/snnas-db-package.tar.bz2.enc (17 KB)

Finished configuration backup /var/snnas-db-package.tar.bz2.enc (17 KB)

Backup of configuration successful

 

This will let you make changes to the NAS stack for troubleshooting, but gives you an easy way to revert back.

 

G300:spsgw1> system restore

Are you sure you want to restore the configuration from backup (Yes/no)? yes

 

Restore of configuration in-progress ...

Restore of configuration successful

Restarting services ...

Stopping all services . . .

Shutting down SAMBA winbindd :                             [  OK  ]

smbd stop/waiting

initctl: Unknown instance:

snnas_controller stop/waiting

Starting all services . . .

snnas_controller start/running, process 5877

console start/running, process 5993

smbd start/running, process 6008

Starting SAMBA winbindd :                                  [  OK  ]

 

G300:spsgw1>

 

The /var/ directory of course has many files/directories in it, but most of them are in the veto files list so they are hidden from the user in the SMB presentation.

 

veto files      = /account/ /agentx/ /cache/ /ctdb/ /cvs/ /db/ /DXi/ /empty/ /games/ /lib/ /local/ /lock/ /lost+found/ /mail/ /nis/ /opt/ /pancetera/ /preserve/ /run/ /spool/ /upgrade/ /tmp/ /www/ /yp/

 

The other subdirectories (crash and log) in the SMB share can help with live troubleshooting or if you just want a specific log.

 

Jon

 

 

 

From: Kevin Poole
Sent: Tuesday, December 01, 2015 7:55 AM
To: DL-Service - SW Support
Subject: Artico log collection

 

All,

 

Paul Gerrish put together a very nice set of instructions for gathering Artico logs:

 

Artico logs are NOT included in the StorNext snapshots and need to be gathered separately. They contain such goodies as the winbindd logs but beware, the winbindd log in the snapshot we recently collected covered less than 5 hours so you need to be quick in running the supportbundle.

 

To get the logs, log in then:

 

      su – sysadmin

      supportbundle create

 

This will generate a file of the form:

 

/var/snnas_auto_support.sh.tar.bz2

 

Not only does the “snapshot” look completely different, the content does as well. The only similarity I see with the StorNext snapshot is that it collects a lot of the same files :^)

 

CR59673 will add it to the StorNext collection, hopefully after removing the duplicated files.

 

Also opened CR61004 to add winbindd to the log rolling so we get a decent history of it.

 

 

Thank you Paul!

 

Kevin Poole StorNext Escalation Manager
719.536.5819 | Kevin.Poole@Quantum.com | Quantum.com