Scalix Forums

Hi,

I am trying to install Scalix 10 on a fresh installed OpenSuSE10.0.

Error in var/log/ scalix install log file:

2006-02-17 10:23:54,935 ERROR Operation failed: Network check failed -- Hosts file is not configured with fully qualified domain name (FQDN)
2006-02-17 10:23:54,940 ERROR Operation failed: Network check failed -- Invalid FQDN 'scalix.pgt.athome'
2006-02-17 10:23:55,129 INFO Network interface is eth1

My DNS server is resolving scalix and scalix.pgt.athome perfectly, I have nothing in the etc/hosts, hostname is showing scalix and nslookup is finding scalix and scalix.pgt.athome.

In my understanding it should be working.

Is it because I have my interface as eth1 ??? Is this a bug???

brgds,

Papick G. Taboada

ps: scalix community edition is installed on the free opensuse which is installed on the free vmware server. it was a nice week.
ps2: friend of mine got it running, same architecure (vmware, opensuse). I have the image of the vmware here, its not running because name of server had change. is there any way to move scalix installations to other names afterwards?

In the --debug modus of the installer I found it is searching for

/etc/sysconfig/network/ifcfg-eth-id-(...) for dhcp settings

the problem is, the file is called

/etc/sysconfig/network/ifcfg-eth-bus-pci-(...)

so I get an error at build/py24/sxsyschecks.py line 210 in perform_net_check

AttributeError: IOError instance has no attribute 'split'

creating a symbolic link from one to another solved the problem - at first - the installer now fails, I an checking the logs...

brgds,

papick

Hi,

please note the error message the installer gave you is not related to your network interface. Can you post your /etc/hosts, please?

Sascha.

Hi,

I tried several configs, here is the acutal /etc/hosts

127.0.0.1 localhost
192.168.57.244 mailserver.pgt.athome mailserver
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts


hostname<enter>
mailserver

nslookup mailserver<enter>

Server: 192.168.57.245
Address: 192.168.57.245#53

Name: mailserver.pgt.athome
Address: 192.168.57.244


The install log says:

2006-02-17 12:00:35,384 ERROR Operation failed: Network check failed -- Hosts file is not configured with fully qualified domain name (FQDN)
2006-02-17 12:00:35,385 ERROR Operation failed: Network check failed -- Invalid FQDN 'mailserver.pgt.athome'
2006-02-17 12:00:35,580 INFO Network interface is eth1


The output window from the installer (with --debug) says:


ERROR:merlin:Operation failed: Network check failed -- Hosts file is not configured with fully qualified domain name (FQDN)
ERROR:merlin:Operation failed: Network check failed -- Invalid FQDN 'mailserver.pgt.athome'
DEBUG:root:This host has the following IP addresses: ['192.168.57.244']
DEBUG:root:This machine's host name 'mailserver.pgt.athome' and IP address '192.168.57.244' is set in DNS correctly
INFO:merlin:Network interface is eth1


Strange, isn't it?

brgds,

Papick

I have now turned off dhcp and set the ip address fixed. my /etc/hosts now reads

127.0.0.1 localhost
192.168.57.244 mailserver.pgt.athome mailserver

Network check still fails, still says my hosts file is not configured with fully qualified name (FQDN)


brgds,

Papick

p.g.taboada wrote:ps2: friend of mine got it running, same architecure (vmware, opensuse). I have the image of the vmware here, its not running because name of server had change. is there any way to move scalix installations to other names afterwards?

Yes, there is. Please use sxmodfqdn -o old.host.com -n new.host.com

man sxmodfqdn has more. sxmodfqdn makes the minimum necessary modifications to the Scalix server to ensure that, after the host name is
changed, Admin Console will continue to function. This involves changing the SYSTEM directory so that entries
owned by this server will have the correct HOST-FQDN attribute value, and changing the Admin Console sxqueryadmin
user so that the authentication id will have the correct domain. Note that this command does not make any change
for other server settings that may be related to, or affected by, the host name - these settings must be manually
checked and corrected individually.

This command should only be run on the Scalix server that has host name change, any other Scalix server within the
network should be taken care of by directory synchronization when the next update is due.





Cheers,

Sascha.

Thanks for that, I am still - unfortunately - not able to install on my own system.

Any help on this issue?

brgds,

Papick G. Taboada

Got it running, but I am not sure what it was.

Could it be that you have a maximum length for tld in you network check? I hat the tld "athome". After switching to "xyz" I got it running.

But, in fact, I am not sure if this was the problem - I tried almost every config possibility...

brgds,

Papick

Well, it would appear that there is some sort of limitation on the TLD length. I have tested this scenario on SuSE 10 OSS using two different TLD names. The first name is .office and it fails consistently. The second name .local works fine. Not sure what the deal is, but this seems to be the problem.

I've done some checking...

The limit appears to be 5 characters in the TLD. I have raised a bug report against this and it will be scheduled against all the other priorities that engineering currently has so I can't give timescales.

Cheers

Dave.