This article describes two known issues in Aspera On Demand 3.5.4 when restoring Console configuration files and their workarounds.
Console Database Emptied After Restoring Console's Configuration File
In Shares On Demand (SHOD), Aspera Platform On Demand / Server On Demand (APOD / SOD), and Aspera Platform On Demand / Server On Demand with Shares (APOD / SOD -ws), restoring a large Console configuration file empties the Console database. To prevent this from occurring, please do the following prior to restoring the Console configuration file:
- Use a text editor to open the nginx.conf file
# vi /opt/aspera/shares/etc/nginx/nginx.conf
- Find client_body_timeout and client_header_timeout. The default values for each is 10s. Change the value for each to 60s.
- Restart nginx
# /opt/aspera/shares/sbin/sv restart nginx
- You may now proceed with the restore.
User Home Directories are Occasionally Deleted After Restoring Console's Configuration File
In SHOD, APOD / SOD, and APOD / SOD -ws, restoring Console's configuration file deletes the home directory of any users in the aspusers group, with the exception of aspadmin. To back up these directories prior to restoring the Console configuration file please do the following:
- Create a backup directory and change to this directory
# mkdir /your_backup_dir
# cd /your_backup_dir
- Backup the home directory. In this example, mybackup is the name being used, but any name may be used.
# tar czvfp mybackup.tar.gz /home
- The home directory has been backed up. You may now restore Console's configuration file.
- If the user directories are deleted during the restore, change to the / directory and restore the backed up home directory
# cd /
# tar xzvf /your_backup_dir/mybackup.tar.gz
- The user directories are now restored.