Modifying the UForge IPΒΆ
Note
This procedure is only valid for mono node UForge platforms.
To modify the UForge IP you will need to:
Stop the following services:
service tomcat stop service oar-server stop service squid stop service rabbitmq-server stop service eventcontroller stop
Clean the squid cache as follows:
[root@db ~]# grep cache_dir /etc/squid/squid.conf cache_dir ufs /data/proxy 10000 16 256 [root@db ~]# rm -rf /data/proxy/*
Modify all occurences of the old IP to the new IP in the following files:
/etc/UShareSoft/uforge/uforge.conf
/var/opt/UShareSoft/uforge-client/gwt/uforge/templates/forge-config.xml
/etc/httpd/conf.d/uforge-ui.conf
/etc/squid/squid.conf
For example:
sed -i.bak "s/192\.168\.2\.177/192.168.2.200/g" /etc/UShareSoft/uforge/uforge.conf /var/opt/UShareSoft/uforge-client/gwt/uforge/templates/forge-config.xml /etc/httpd/conf.d/uforge-ui.conf /etc/squid/squid.conf
Modify all occurences of the old IP to the new IP in the following files:
/etc/sysconfig/network-scripts/ifcfg-ens160
/etc/hosts
For exemple:
sed -i "s/192\.168\.2\.177/192.168.2.200/g" /etc/sysconfig/network-scripts/ifcfg-ens160 /etc/hosts
Restart the network service:
service network restart
Note
You will need to open a new terminal and connect to the machine using the new IP.
Restart the services as follows:
$ /opt/UShareSoft/uforge/tools/update_scripts/uforge_update.sh $ /opt/UShareSoft/uforge-client/bin/uforge_ui_update.sh $ service oar-server start
Note
While oar-server is down, root user may receive emails with an error message about UForge cron execution.