Topic: Will reconfiguring from the console affect ibays?

[tlicht]

This might be a stupid question.... still.
I have an SME 7.4 server only setup with around 500 Gb in Ibays. I have moved the disks to another computer with a different NIC. Now no networking.... The messages log file says:
Cannot bind socket FD 13 to 192.168.48.1:3130
several times. I imagine that I should reconfigure the nic in the console. Will this affect my setup in any other respect? I wouldn't want to loose the stuff stored in the ibays...

The interesting thing is that the server (=disks) was(were) originally set up on this computer and then moved to another without a hitch where they have been working last month....
Thanx for your advice.

[cactus]

Cannot bind socket FD 13 to 192.168.48.1:3130

Was this perhaps the IP address of the server you migrated from? Is the host it is trying to connect to up?

[tlicht]

Well, yes - this is supposed to remain the same server - just in slightly different 'clothes'....

[cactus]

Well, yes - this is supposed to remain the same server - just in slightly different 'clothes'....

Supposed, yes. But is this really the case? Did you check really the connection to that server? Did you really check if the IP number is up?

[tlicht]

I might have been too vague... the server in the sense of the case + mobo + the disks is changed in the sense that the server I moved from is now without disks and thus not working at all - not turned on or even connected to the network. The server I migrated to is another case+mobo + the disks from the server I moved from.....

[cactus]

I might have been too vague... the server in the sense of the case + mobo + the disks is changed in the sense that the server I moved from is now without disks and thus not working at all - not turned on or even connected to the network. The server I migrated to is another case+mobo + the disks from the server I moved from.....

Yes I already understood that, but you seem not to understand me. You do not answer the questions I raised:

Was this perhaps the IP address of the server you migrated from? Is the host it is trying to connect to up?

Perhaps I am not clear enough:
What is the output of when you run it on your server?

Code: [Select]

ping 192.168.48.1
traceroute 192.168.48.1I am trying to see if there really is an error on your server or that something else is wrong. This message could very well be a valid error message, because of the host you are somehow trying to connect to not being available at the referred IP address.

[tlicht]

It is the server's IP (old and current)
I probably took the wrong line from the messages log... maybe
ifup: sk98lin-unit doesn't seem to exist, delay initialization
and a little further down
network: starting interface eth0: failed
would have been more informative from the beginning.

I run the server in Swedish, so my translation of the messages might differ slightly from what the server would say in English....

[cactus]

network: starting interface eth0: failed

There you could have your issue.

The new server probably has a different ethernet adapter, which might not be supported or using a different driver.

You will need to login as admin and reconfigure your server (option 2 IIRC) and see if the network card is recognized properly and configure it, if it is. If that does not work your new server has a nework card that is not supported and your easiest solution would be to add another network adapter to your server that is supported, perhaps you can take one form your old server.

[Stefano]

tlich: reconfigure your server, then reboot it

you have nothing to fear

[tlicht]

Thanx!
Everything works fine now, after reconfiguring. No questions were asked regarding the new NIC - SME server figured that out quite by itself.

[cactus]

Thanx!
Everything works fine now, after reconfiguring. No questions were asked regarding the new NIC - SME server figured that out quite by itself.

Very nice, glad we could help. Please keep in mind the next time you are moving hard disks that settings for hardware for your machine are also on those disks, therefore swapping disks will not work out of the blue.

[CharlieBrady]

Supposed, yes. But is this really the case? Did you check really the connection to that server? Did you really check if the IP number is up?

Cactus, there is no other server here, and no connection. "Cannot bind" means "cannot create the listening socket". It indicates that the server has no working network interface.

tlicht is correct - he/she must reconfigure the server, to recognise the new, different NIC, so that the correct driver is used.