Troubleshooting - Modify the Interface Name - Fluid Topics - 3.6

Install Fluid Topics on a Single Server

Product
Fluid Topics
FT_Version
3.6
Platform
Debian
Category
Technical Notes

If a server has specific interfaces, such as "ens160", at least one daemon is not launched, and the following error is displayed in its logs:

no such file or directory : can not find local ip adress

It is necessary to modify the server conf.xml configuration file accordingly.

  1. Retrieve the interface name by running the following command:

    ifconfig -a

    The following lines are displayed. In this example, the interface is called ens60:

    ens60: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
    inet 172.31.4.97 netmask 255.255.240.0 broadcast 172.31.15.255
    inet6 fe80::433:37ff:fe93:bb26 prefixlen 64 scopeid 0x20<link>
    ether 06:33:37:93:bb:26 txqueuelen 1000 (Ethernet)
    RX packets 60383 bytes 83796882 (79.9 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 16902 bytes 1642151 (1.5 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1000 (Boucle locale)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  2. Edit the following file:

    As root user

    /usr/local/afs7/conf/conf.xml

  3. Add the following lines in the <afs:conf> element:

    <?xml version='1.0' encoding='iso-8859-1'?>
    <afs:conf xmlns:afs="http://ref.antidot.net/v7/afs#">
    ...
    <afs:OS>
    <afs:networkInterfaces>
    <afs:listItem value="ens160"/>
    </afs:networkInterfaces>
    </afs:OS>
    </afs:conf>