Topic: Upgrade and move to new server failed.

[Paperguides]

I have just moved my installation from a old server to a newer HP micro server.  The old server was running a fully patched 8.x and I took a workstation backup to a network share on a client.  I built the new server using 9.1, installed all the updates and restored from the backup.  The restore appeared to have completed successfully and I can access the server from a web browser and thru winscp.

I found that I could not send a test email and nor access the server from the 'outside'.  When I opened a terminal window with winscp I could not ping the gateway router nor the workstation I was running the winscp session on.

I went to the server, logged in as admin and ran thru the config screens.  The only odd thing I found was on the screen to select the network interface; there were two interfaces shown.  The system only has one.   The second one is clearly labelled as 'Fake'.  The previous server, a dell 1U computer, had two but only one was connected.

Anyone point me in a direction to solve this?

Thanks

[Stefano]

if your server is in server-only mode, just reconfigure it using the real interface you see..

the dummy interface is needed when you have only one phisycal nic but you need your server in server and gateway mode (for example when you install it on a VPS)

[Paperguides]

Sorry missed that bit.  The server is 'server only' and I chose the 'real' interface.

See attached screenshot

[Stefano]

can you post the result of

Code: [Select]

ifconfig

and

Code: [Select]

config show | grep -i gateway


[Paperguides]

root@main ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 3C:4A:92:74:2B:D0
          inet addr:192.168.200.10  Bcast:192.168.200.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5081 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53026 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:520455 (508.2 KiB)  TX bytes:5360751 (5.1 MiB)
          Interrupt:18

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:4845 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4845 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:478914 (467.6 KiB)  TX bytes:478914 (467.6 KiB)

[root@main ~]# config show | grep -i gateway
GatewayIP=192.168.200.1
[root@main ~]#

[Stefano]

everything seems ok..

can you confirm that you can't ping the GW and any other internal/external IP/host?

what is your GW? is there any rule on it that may prevent your server to access the lan/wan?

[Paperguides]

The result of pings:

[root@main ~]# config show | grep -i gateway
GatewayIP=192.168.200.1
[root@main ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8. 56(84) bytes of data.

^C
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6837ms

[root@main ~]# ping 192.168.200.1
PING 192.168.200.1 (192.168.200.1) 56(84) bytes of data.
^C
--- 192.168.200.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4301ms

[root@main ~]#


The gateway router (Draytek 2830n) hasn't changed since -well before the change in server.

I have another SME server on the same network switch which works OK.

[root@the-shed ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8. 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=9.51 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=9.41 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=9.66 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2969ms
rtt min/avg/max/mdev = 9.418/9.532/9.667/0.129 ms
[root@the-shed ~]#


Thanks for your help on this.

[Stefano]

ok.. the new hw is an HP microserver, right?

try just unplugging and re plugging the cable, wait some secs and retry..

I have (only one, in a dozen) a microserver that after rebooting is unable to access the lan, even if connected..

is there anything between the server and the GW? maybe a switch? if so, try changing the port

I'm quite sure your is not a SME issue

[Paperguides]

Yes, it's one of the HP microservers that they had the cash back offer on.  It has run SME server successfully before but this installation is on a 'new' disk.  I have re-cabled the path to the gateway and it is now cable directly into one of the ports on the Draytek router.

I've powered down the server and restarted it.

I cannot logically see how I can communicated with the server with a web browser - port 80 and winscp - port 22 without it being a configuration problem.  I was hoping some-one would point out an obvious error on my part.

Thanks again, Stefano, for all your thoughts on this

[janet]

Paperguides

Have you powered off (& on) your Draytek router ?

Can you send & receive email messages from/to existing users email accounts (locally)
ie send from local user1 to local user2 etc.
(to prove the mail system is functional).

Have you ran through the various server manager configuration options & reselected them & then saved ?

Did you actually run Configure this server from the console menu ie run through all the options selecting as appropriate & then save & restart ?

Have you issued the master reconfiguration command
signal-event post-upgrade
signal-event reboot

Have you checked port forwards & port openings on your Draytek ?

[Paperguides]

Paperguides

Have you powered off (& on) your Draytek router ? Yes, produced no change

Can you send & receive email messages from/to existing users email accounts (locally)
ie send from local user1 to local user2 etc.
(to prove the mail system is functional).Yes, if I use webmail.

Have you ran through the various server manager configuration options & reselected them & then saved ?  ???  Not sure what you are asking here

Did you actually run Configure this server from the console menu ie run through all the options selecting as appropriate & then save & restart ?

I have been through the admin screen options several times and checked them. The only screen which looks out of place is the network card screen see above. Where does the 'Use dummey Fake Network Interface' come from? Are you suggesting I change all the parameters, save them then change them back?

Have you issued the master reconfiguration command
signal-event post-upgrade
signal-event reboot

Yes,  Had no effect

Have you checked port forwards & port openings on your Draytek ?

Nothing on the Draytek was changed between the two servers.  I have checked the set up and it appears to be OK

I did another error message see below.  Is it relevant?


ERST: Failed to get Error Log Address Range.
r600_dp: Failed to load firmware "radeon/R600_rlc.bin"
[drm:r600_init] *ERROR* Failed to load firmware!
radeon 000:01:05.0: Fatal error during GPU init


didn't think it was see:
https://bugs.centos.org/view.php?id=6296


Thanks for your time.

[Paperguides]

I decided to do a bit of testing.

I downloaded the latest ISO and burnt a new DVD.  I then installed this on the same hardware including using the test media function.  I did not restore my data.  I still have the R600 error and cannot ping from the system.

I will report this as a bug and see they think.

[janet]

Paperguides

Please provide the bug number here.

Re your Radeon error, as that appears to be your graphics card, typically you would disable advanced features for your graphics card in the system BIOS.

With the mail test I meant for you to initially test using webmail, & as that has proven OK, then additionally test by setting up the email client on a connected workstation or two workstations.
Set up 2 different user accounts in the email client(s), & try to send email from one to the other & vice versa, making sure you use the SME server mail server IMAP & SMTP servers. Do this via the LAN connection.
If it does not work then you probably have a connectivity issue.

Re server manager, I mean to login as admin to the server manager & run through the various configuration panels, particularly the one relating to workgroup & such like.

[Michail Pappas]

This doesn't sound like a gateway issue, since the user can't even ping the client system he SSH's from (even though a
firewall could be running on the latter).

With my rather limited knowledge, it feels perhaps like a network card/switch/vlan issue.

@Paperguides: can you try booting from a Linux livecd and possibly also from a Windows live cd to check if you are able to browse/ping? Write down the ip address used (if ip address is taken automatically via DHCP). If possible, try to configure the ip address on these livecd's to be the same as the one you use for browsing.

Also, do you have some special switch or VLAN configuration to the best of your knowledge?

[Paperguides]

Unfortunately this problem is going to be unsolved.  I tried to upgrade the system BIOS to correct a known bug which may have been the cause and, although it seem to have completed successfully, I now have a 'brick'    I have spent a considerable time trying to rectify this without success. ((

Thanks for all the input and advice.

Tony