In current design, the group change at "new active" node just takes effective
when getting an write action, otherwise the log file permission still remains.
As above case, the group was not changed to file
"saLogNotification_20160323_135207.log" because no write action to that file
took place.
So, there would be a problem to "log reader" application if the app tries to
read the log file which so far not get any write action to it.
---
** [tickets:#1730] LOG: group ownership of log file is not correct after
failover**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Wed Apr 06, 2016 09:16 AM UTC by Quyen Dao
**Last Updated:** Wed Apr 06, 2016 09:16 AM UTC
**Owner:** nobody
*Steps to reproduce*
1. Create test_data_group_1 on active SC
2. Create test_data_group_2 then test_data_group_1 on standby SC
3. Add user who owned the osaflogd process to test_data_group_1 on both SC
4. Configure log data group to test_data_group_1 by immcfg command
5. Reboot the active SC
6. On standby SC, list the log files with group name and it results like below.
Result: The group ownership of notifcation log stream is test_data_group_2
instead test_data_group_1 after failover.
Note:
* The saflog directory is in the shared file system.
* opensafd is started as root
root@SC-2:~# ll /srv/shared/saflog/
total 44
drwxrwxrwx 4 root root 4096 Mar 23 13:53 ./
drwxrwxrwx 7 ubuntu ubuntu 4096 Mar 22 14:51 ../
drwxrwxr-x 2 ubuntu ubuntu 4096 Mar 23 13:51 repo/
-rw-r--r-- 1 root root 138 Mar 23 13:53 saLogAlarm.cfg
-rw-r--r-- 1 root root 138 Mar 22 17:35
saLogAlarm_20160322_173951.cfg
-rw-r----- 1 root test_data_group_1 200 Mar 23 13:53
saLogAlarm_20160323_135207.log
-rw-r--r-- 1 root root 138 Mar 23 13:52 saLogNotification.cfg
-rw-r----- 1 root test_data_group_2 0 Mar 23 13:52
saLogNotification_20160323_135207.log
-rw-r--r-- 1 root root 143 Mar 23 13:53 saLogSystem.cfg
-rw-r----- 1 root test_data_group_1 6876 Mar 23 13:53
saLogSystem_20160323_135207.log
root@SC-2:~#
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
