All Collections
Knowledge Base
Endpoint and SaaS Apps
How To - Endpoint and SaaS Apps
How to change log location on UNIX-based operating systems running inSync On-Premise
How to change log location on UNIX-based operating systems running inSync On-Premise
Updated over a week ago

This article applies to:

  • OS: UNIX

  • Product edition: inSync On-Premise

Overview

At times you may be running low on disk space and would need to change the default log location on UNIX-based servers running inSync On-premise server. The default log location on UNIX servers running inSync On-premise is /var/log/inSyncCloud/.

Procedure to change the log location

To change the log location, you need to create a soft link and point the default location to any desired location where you want the logs to be stored. Perform the following steps:

  1. Create a directory using the mkdir command. For example, Here we will create a “log” folder under /tmp directory

[root@druva-centos7 log]# cd /tmp/

[root@druva-centos7 tmp]# mkdir log

  1. Now we will create a soft link using the ln -s command.

[root@druva-centos7 ~]# ln -s /var/log/inSyncCloud/ /tmp/log/

  1. Verify that the soft link is created successfully by running the following command on the destination directory.

[root@druva-centos7 ~]# ls -al /tmp/log/

lrwxrwxrwx. 1 root root 21 Aug 8 19:19 inSyncCloud -> /var/log/inSyncCloud

  1. Stop inSync Master services by running the following command.

[root@druva-centos7 ~]# systemctl stop inSyncMasterAll

5. Start inSync Master services by running the following command.

[root@druva-centos7 ~]# systemctl start inSyncMasterAll

6. Navigate to the new location to verify that the logs are available by running the following commands.

[root@druva-centos7 ~]# cd /tmp/log/

[root@druva-centos7 inSyncCloud]# pwd

/tmp/log/inSyncCloud

[root@druva-centos7 inSyncCloud]# ls -al

total 524

drwxrwxr-x. 2 insyncserver insyncserver 4096 Aug 6 19:25 .

drwxr-xr-x. 8 root root 4096 Aug 6 20:40 ..

-rw-r--r--. 1 insyncserver insyncserver 1788 Aug 8 19:23 AuthDB.log

-rw-r--r--. 1 insyncserver insyncserver 46057 Aug 8 19:53 BJCron.log

-rw-r--r--. 1 insyncserver insyncserver 60999 Aug 8 19:53 BJWorker.log

-rw-r-----. 1 insyncserver insyncserver 47802 Aug 8 19:23 CPortal.log

-rw-r-----. 1 insyncserver insyncserver 2762 Aug 8 19:23 Cron.log

-rw-r--r--. 1 insyncserver insyncserver 708 Aug 8 19:26 bynamo.1.log

-rw-r-----. 1 insyncserver insyncserver 114778 Aug 8 19:52 inSyncCloudServer.log

-rw-r--r--. 1 insyncserver insyncserver 169545 Aug 8 19:23 inSyncConfigDBDumpNode.log

-rw-r-----. 1 insyncserver insyncserver 243 Aug 8 19:21 inSyncConfigDBMonitor.log

-rw-r--r--. 1 insyncserver insyncserver 1574 Aug 8 19:26 inSyncStorage1.log

-rw-r--r--. 1 root insyncserver 280 Aug 6 19:25 inSyncStoragePerms.log

-rw-r-----. 1 insyncserver insyncserver 33264 Aug 8 19:43 inSyncSyncServer.log

-rw-r--r--. 1 root root 11901 Aug 8 19:53 sharedb.log

The logs are now written in the new location.


📝 Note
The commands to start and stop Druva master services will differ depending on the UNIX OS version.Refer to How to start and stop inSync services on Windows and Linux devices for commands to start and stop the inSync services.


Did this answer your question?