Removing one of SambaServer agent's port doesn't dump VCS configuration to disk and causes hacf to coredump

Article: 100015273
Last Published: 2020-11-20
Ratings: 0 0
Product(s): InfoScale & Storage Foundation

Problem

The SambaServer agent has two ports defined by default, 139 and 445. The supported configuration for this agent is to keep both of the ports or remove one, depending on customer's service needs.

 

Error Message

When trying to configure the SambaServer agent with one port only, haconf -dump will fail to save the configuration to disk and the following messages can be seen in engine_A.log after dumping the configuration:

[root@server101 ~]# hares -modify SMB Ports 139
[root@server101 ~]#
[root@server101 ~]# haconf -dump

015/03/12 04:23:48 VCS INFO V-16-1-50135 User root fired command: haconf -dump from localhost
2015/03/12 04:24:05 VCS INFO V-16-1-50135 User root fired command: hares -modify SMB  Ports  139  from localhost
2015/03/12 04:24:14 VCS INFO V-16-1-50135 User root fired command: haconf -dump from localhost
2015/03/12 04:24:16 VCS WARNING V-16-1-10454 hacf -dump failed on server102
2015/03/12 04:24:16 VCS ERROR V-16-1-10061 Config dump to disk failed with message: internal error - hacf has died.
2015/03/12 04:24:16 VCS WARNING V-16-1-10454 hacf -dump failed on server101
2015/03/12 04:24:16 VCS ERROR V-16-1-10061 Config dump to disk failed with message: internal error - hacf has died.
2015/03/12 04:24:17 VCS WARNING V-16-1-10454 hacf -dump failed on server103
2015/03/12 04:24:17 VCS ERROR V-16-1-10061 Config dump to disk failed with message: internal error - hacf has died.


Also, hacf creates a coredump in /etc/VRTSvcs/conf/config/  in all the nodes that are member of the cluster.

This same issue occurs if trying to change the configuration via VOM.
 

Cause

When we dump the configuration to save it, we call hacf binary to check that the configuration is valid. In this case, hacf is expecting two values for the attribute Ports in the Samba agent. When it only receives one, it coredumps.
 

Solution

 

The workaround for this issue is the following:


1) Backup types.cf file

# cp /etc/VRTSvcs/conf/config/types.cf /etc/VRTSvcs/conf/config/types.cf.backup

2) Modify default value for Ports attribute

# haconf –makerw
# haattr –default SambaServer Ports 139  << Change 139 for 445 if required.
# haconf –dump

3) Modify the resource level Ports value

# hares –modify <sambares> Ports <value>
# haconf –dump

 

There is no hotfix at the moment for this issue, but it will be fixed in a later version of VCS.

 

Applies To

6.1, 6.1.1, 6.2   for AIX, Linux and Solaris

Was this content helpful?