Hi
We are running proiv on 2 seperate Unix servers for our development and live environments (let's call them server 1 and server 2). Releases to the live environment are done exporting to a transfer file on a directory /proiv/prx on server 1 which is actually a link to server 2 - I'm sure most of you are probably familiar with this concept. The problem I have is that server 2 has moved and now the link no longer works. I'm guessing that we have to re-configure the link or map with the new IP address but being pretty clueless about the Unix side of things I don't know how to do this. Our Unix admin guy is on holiday and I'm unable to do any software releases for our customers until this is resolved so it's kind of urgent.... can anyone help? Or suggest a workaround?
Thanks in advance!
Kate
Click the link below to see the new game I'm developing!
Exporting between servers in Superlayer - question from a Unix dummy&#
Started by kateinscotland, Apr 23 2007 11:08 AM
5 replies to this topic
#2
Chris Mackenzie
-
- Members
-
- 372 posts
ProIV Guru
- Gender:Male
- Location:Bristol, United Kingdom
Posted 23 April 2007 - 11:19 AM
Hi
We are running proiv on 2 seperate Unix servers for our development and live environments (let's call them server 1 and server 2). Releases to the live environment are done exporting to a transfer file on a directory /proiv/prx on server 1 which is actually a link to server 2 - I'm sure most of you are probably familiar with this concept. The problem I have is that server 2 has moved and now the link no longer works. I'm guessing that we have to re-configure the link or map with the new IP address but being pretty clueless about the Unix side of things I don't know how to do this. Our Unix admin guy is on holiday and I'm unable to do any software releases for our customers until this is resolved so it's kind of urgent.... can anyone help? Or suggest a workaround?
Thanks in advance!
Kate
If you don't want to reconfigure samba/nfs or whatever, you should be able
to simply copy the prx or vpx files from server 2 to some other directory on server 1 using ftp or rcp
and then import from there.
e.g. log onto server 1, you will be in your home directory test with the pwd command.
use the ftp command to connect to server 2
get the file
import into p4.
e.g.
The content and views expressed in this message are those
of the poster and do not represent those of any organisation.
of the poster and do not represent those of any organisation.
#3
kateinscotland
-
- Members
-
- 4 posts
Newbie
Posted 23 April 2007 - 11:25 AM
Hi Chris
I had thought of that, however I need to transfer a number of ProIv functions between the servers and I'm not sure what directory they reside in in Unix, or how to find this out. Are they named the same as within ProIV?
I had thought of that, however I need to transfer a number of ProIv functions between the servers and I'm not sure what directory they reside in in Unix, or how to find this out. Are they named the same as within ProIV?
#4
Chris Mackenzie
-
- Members
-
- 372 posts
ProIV Guru
- Gender:Male
- Location:Bristol, United Kingdom
Posted 23 April 2007 - 12:14 PM
Hi Chris
I had thought of that, however I need to transfer a number of ProIv functions between the servers and I'm not sure what directory they reside in in Unix, or how to find this out. Are they named the same as within ProIV?
The function defs are stored in Pro-isam files and are not easily transferred directly
from outside pro-iv environment.
With the P4 environment, run the pro-iv export facility ($XFR) or the
VIP export tool to export your list of functions from the P4 environment
to a transfer file. Call it what you like (e..g 23apr07.prx or 23apr07.vpx) .
These files are by default created in PRODATA directory but you can create
or import from elsewhere.
Then copy this file to the other server and use the p4 import facility. You should
also regen (rebuild) the function list after import.
Edited by Chris Mackenzie, 23 April 2007 - 12:16 PM.
The content and views expressed in this message are those
of the poster and do not represent those of any organisation.
of the poster and do not represent those of any organisation.
#5
Guest_David Allen_*
Guest_David Allen_*
-
- Guests
Posted 23 April 2007 - 12:38 PM
I'm assuming that the folders on Server1 have been mounted on Server2.
On server1 edit the file '/etc/exports'. This should contain an entry simillar to the below:
"foldername" server2(rw,async,no_root_squash)
If server2 is the actual machine name then there is nothing to do here, if it's an IP address then you should edit this to the IP address of your new server2.
If you make a chenge to the file then issue the command 'exportfs-a' to update the export list.
If the case of the actual machine name you must edit '/etc/hosts' to have the correct association i.e.
server2 10.0.0.1 (IP addess of new machine)
and run 'exportfs -a'.
Switching to server2, you will have to remount your newly exported folders. Issue the command 'mount' and a list of mounted folders will be displayed. You might see the mount you are looking for (it depends on machine up/down order), if it's there it will be obvious.
If it's not there you will have to find and issue the 'mount' command again, if your system is anything like ours it will be located in the file '/etc/rc5.d/S99local'. Do a 'more' for the file and from the listing enter the displayed command directly and it should mount the drive once again. If it does you should be able to use the system as before.
If you don't have an S99local, look in the folder for other 'S' files, there may be a SXXmounts or something similar.
If you still can't find anything then the mount must have been done manually so you will need to issue it yourself, the format is:
mount server1:/foldername /mnt/foldername
I can't help you too much here as to what the foldernames are, you'll have to poke around in the '/mnt' folder or look at your settings in pro-iv for where you import the files from.
Good luck
David
On server1 edit the file '/etc/exports'. This should contain an entry simillar to the below:
"foldername" server2(rw,async,no_root_squash)
If server2 is the actual machine name then there is nothing to do here, if it's an IP address then you should edit this to the IP address of your new server2.
If you make a chenge to the file then issue the command 'exportfs-a' to update the export list.
If the case of the actual machine name you must edit '/etc/hosts' to have the correct association i.e.
server2 10.0.0.1 (IP addess of new machine)
and run 'exportfs -a'.
Switching to server2, you will have to remount your newly exported folders. Issue the command 'mount' and a list of mounted folders will be displayed. You might see the mount you are looking for (it depends on machine up/down order), if it's there it will be obvious.
If it's not there you will have to find and issue the 'mount' command again, if your system is anything like ours it will be located in the file '/etc/rc5.d/S99local'. Do a 'more' for the file and from the listing enter the displayed command directly and it should mount the drive once again. If it does you should be able to use the system as before.
If you don't have an S99local, look in the folder for other 'S' files, there may be a SXXmounts or something similar.
If you still can't find anything then the mount must have been done manually so you will need to issue it yourself, the format is:
mount server1:/foldername /mnt/foldername
I can't help you too much here as to what the foldernames are, you'll have to poke around in the '/mnt' folder or look at your settings in pro-iv for where you import the files from.
Good luck
David
#6
kateinscotland
-
- Members
-
- 4 posts
Newbie
Posted 23 April 2007 - 03:34 PM
Thanks guys for your help. I'm not sure about the mount stuff but we don't seem to have all of the files you mentioned on our system.
However I managed to find a workaround by exporting to a transfer file from ProIV, using ftp to transfer it direct to the IP address of the other server, and then importing, as Chris suggested.
I'll pass your message to the Unix admin guy when he comes back David.
Thanks again!
However I managed to find a workaround by exporting to a transfer file from ProIV, using ftp to transfer it direct to the IP address of the other server, and then importing, as Chris suggested.
I'll pass your message to the Unix admin guy when he comes back David.
Thanks again!
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
