SME Server:Documentation:FAQ

Frequently Asked Questions

This Section lists Frequently Asked Questions (FAQ) for SME 7. Problems many people run into installing SME 7 for the first time or upgrading to later versions are found here.

If your question isn't listed here, it's possible it's a Rarely Asked Question (RAQ), in which case you'll be better off searching for answers in Bugzilla.

post-upgrade and reboot

• When is a post-upgrade and reboot required?

There is no way to tell unless the RPM packager tells you otherwise.

The server manager/yum installer has no way of determining whether any configuration files will change if all are re-expanded or to know which binaries have changed (or use libraries which have now changed) and therefore need to be restarted. The only safe option is to reconfigure and restart everything.

Which repositories should be enabled

You should have the following repositories enabled (blue)

CentOS
CentOS - updates
SME Server - addons
SME Server - OS
SME Server - updates.

DO NOT enable SME Server - updates testing which is considered beta, unless

• it is a TEST server NOT a production server or
• you want to be part of a bug-testing group.

Additionally

• SME Server - test is considered alpha
• SME Server - dev contains automatically built rpms. It contains lots of experimental,

incomplete and mutually incompatible packages.

	Warning:
	If upgrading from a system prior to 7.1.1 (7.1 update 1) you need to ensure you have the latest smeserver-support and smeserver-yum prior to applying the rest of the updates. The current situation is that you will pull in updates from centos that may be ahead of the distribution.

Template:DrawBoxNote

Client Computers

• Samba trust relationships lost?

This is a possible bug with an upgrade from SME6. After an upgrade, local workstations cannot log in. If you are experiencing this problem, please have a look at this bug for a fix, and provide followup: [[1]]

• Windows XP Clients - Patch to logon to SME domain

This patch can be used when Windows XP clients won't be able to log on to the SME Server domain. The registry patch is located here: http://servername/server-resources/regedit/winxplogon.reg Double click on the winxplogon.reg file and the settings will be added to the Windows Registry.

• How to disable password caching on Windows 95/98/ME/2000 Clients?

This patch can be used if you don't want Windows clients to remember password for shared folders on SME Server. The registry patch is located here: http://servername/server-resources/regedit/win98pwdcache.reg Just double click on the win98pwdcache.reg file and the settings will be added to the Windows Registry.

Note Although the filename seems to indicate that this patch will only work for Windows 98, but it also works in Windows 95, Windows ME and Windows 2000.

• LDAP Directory Gives MAPI_E_CALL_FAIL Errors on Outlook 2002 or Outlook 2003

In Outlook 2002 or 2003 when someone tries to find a contact using the LDAP server, a message stating that "Unavailable critical extension" and then a second message saying "The search could not be completed. MAPI_E_CALL_FAIL" shows up and nothing shows up from the search. The directory works beautifully in Thunderbird 1.5 as well as Outlook 2000, but not 2002 or 2003. More information can be found here:[[2]] [[3]]

• Where is the netlogon directory?

The netlogon directory is located on the SMESERVER at: /home/e-smith/files/samba/netlogon It can also be found by a client computer at: \\servername\netlogon

Firewall/Port Forwarding,Opening,Blocking

• How do I configure the firewall?

The server manager is the GUI front end for the firewall. The firewall is modified automatically in response to changes you make in the configuration, such as enabling/disabling services, marking them public/private, forwarding ports, etc. If you wish to make changes beyond those provided for by the server manager, you can do so by providing custom templates

• How do I allow public access to a service I've added to SME Server 7?

The procedure has changed and is now much simpler in SME Server 7. For this example the service you have installed is called 'manta' and 'nnn' is the TCP port number that needs to be opened. Watch your capitalization with the command below:

 config set manta service access public status enabled TCPPort nnn

For UDP services, use UDPPort instead of TCPPort. Note that you can also set restrictions with ~AllowHosts and ~DenyHosts:

 config setprop manta ~AllowHosts 1.2.3.4,10.11.12.0/24 
 config setprop manta ~DenyHosts 16.17.18.18
 

Then, to activate, do:

 signal-event remoteaccess-update

• I want to block traffic from some ip-addresses to my server on some port.

config setprop httpd-e-smith DenyHosts a.b.c.d,w.x.y.z
signal-event post-upgrade
signal-event reboot

• I want to have two WAN addresses; one for the SMESERVER and another that needs to be treated like a "Local Network". I can't set any address from the WAN subnet as a "Local Network".

This is intended behaviour as SMESERVER is secure by design. If you need to do something like this, you should know what you are doing and understand what to poke under the covers.

Web Applications

• chmod 777

Using 777 is always wrong (despite the fact that many howtos recommend it). 0770 is sufficient, as long as www is a member of the group owning the directory, and is safer.

Use chown www /path/to/dir
and preferably put your app in /opt/app not in an ibay

• Wasn't mod_perl installed in previous versions? How do I install it?

It may have been, but it was not used so it is no longer included. If you do want to install it do the following:

Note The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.

 yum install mod_perl
 config setprop modPerl status enabled
 signal-event post-upgrade ; signal-event reboot

• The directory structure is visible. How do I disable indexes in ibays?

SME Server 6.0, 6.0.1, and 6.5 all had the following for the ibays/html directory - "Options Indexes Includes". This would indicate that indexes were allowed for html directories. In SME Server 7.0 this is made a parameter and it defaults to enabled to be compatible with SME Server releases before SME Server 7.0 installations.

To disable indexes for an ibay in SME Server 7.0 do the following:

 db accounts setprop //ibayname// Indexes disabled 
 signal-event ibay-modify //ibayname// 

This issue was first reported here: [[4]]

• I need to create (or install) a PHP application that needs access to the /tmp directory.

db accounts setprop ibayname PHPBaseDir /tmp/:/home/e-smith/files/ibays/ibayname/
signal-event ibay-modify ibayname

By default if you have PHP code in an IBAY, it can only run in that IBAY. The above commands will allow PHP code in the IBAY to run outside of its installed directory.

Here is a list of all the IBAY specific settings: [[5]]

Reset the root and admin password

1. Restart your server and at the beginning of the boot-up use the arrow keys to select the kernel you would like to boot into.

2. Press A , to allow you to append parameters to your grub boot settings.

3. Be careful not to change anything, only add the following after the A (Be sure to put a space before single):

  single

4. Press enter. you will be presented with a prompt.

5. At this prompt type the following two commands (each followed by a return). You will be asked to provide a new password. Reset both your root and your admin password and set them to the same value:

 passwd root
 passwd admin

Reboot your server and everything should be okay now.

Log Messages

• Log message regarding permissions on /var/spool/qpsmtpd/

You may see messages similar to this in your log file:

@400000004326e9472eccc42c 3243 trying to get config for spool_dir @400000004326e9472ed518fc 3243 Permissions on spool_dir /var/spool/qpsmtpd/ are not 0700

They can be safely ignored. Clamav runs under a different user and needs read access to the spool area to avoid copying the file. [[6]]

• I get messages that look like: (pam_unix)[31705]: session opened for user root by (uid=0)

Most likely these messages coming from a package called SYSSTAT. The package was included in the previous versions of SMESERVER but were removed from the final version of V7. If you see the messages, most likely you had a previous version and upgraded. SYSSTAT isn't needed unless you have a contrib package called SME7ADMIN.

You can safely remove the package by:

yum remove sysstat

Please note that these messages may be caused by other cron jobs (tasks that run automatically) or packages authenticating as root.

• I get a message saying that: the RSA server certificate CommonName (CN)`servername.domainname.tld' does NOT match server name!

If you change the servername, you will be prompted to reboot. When you do, the SMESERVER will generate a certificate for the new servername-domainname combination and httpd.conf will now reference that new name. References to other virtual domains and hosts will generate warnings in the log.

• I get: server squid[3145]: WARNING: Disk space over limit: 148412 KB 102400 KB.

This message is just log noise. The message is informational and squid takes care of the issue itself.

• I get in the radius log: Info: Using deprecated naslist file. Support for this will go away soon.

This is just the radius daemon (a computer program that runs in the background, rather than under the direct control of a user) complaining about a file that exists in the directory. We don't use it.

• I get in the clamd log: Error: cli_untar: only standard TAR files are currently supported

Clam (the antivirus portion of SMESERVER) has found a file type which it can't deal with, and so is telling you that it can't scan that file.

Nothing to be concerned about. The fix, if any arrives, will come from the Clam team if they Determine this file format is worthy of their attention.

• I get in the smeserver-clamscan.log: LibClamAV Warning: Multipart/alternative MIME message contains no boundary header.

This is just log noise. Clamav is scanning badly formatted MIME mail.

Virtual Domains

• When I create a VIRTUAL DOMAIN, I don't see anything listed in the HOSTNAMES AND ADDRESSES panel for that VIRTUAL DOMAIN.

For a virtual domain to be effective (for email or web), it needs to be configured as INTERNET DNS SERVERS (this is the default value). Since the domain resolves via INTERNET DNS SERVERS, no hostnames or addresses are created locally. For more info please visit the Administration Manual section regarding Domains: [[7]]

Shell Access

• I need to give a user shell access to the SMESERVER.

Shell access should only be provided to users who have a *need* for it and can be trusted. You can enable shell access for a user by:

db accounts setprop username Shell /bin/bash
chsh -s /bin/bash username

Upgrading

• What's the best way to upgrade from previous versions?

An article is written for this subject. Please visit: http://wiki.contribs.org/UpgradeDisk

Users

• I can't delete a user for some reason. What do I do now?

If for some reason you can't delete a user try:

signal-event user-delete <username>
db accounts delete <username>

• I was looking in the home directory of a user and I see a hidden directory called ".junkmail". Do I need that? Can I delete it?

Don't remove or rename .junkmail folders.

Yum

• Yum doesn't seem to be working correctly. What do I do now?

If for some reason you can't get yum to work correctly, try:

yum clean metadata
yum update

• Fix for 'Metadata file does not match checksum'

Typical error message

http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz: 
[Errno -1] Metadata file does not match checksum Trying other mirror.
Error: failure: repodata/primary.xml.gz from dag: [Errno 256] No more mirrors to try.

To flush the up stream proxies, using wget, run:

wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/repomd.xml
yum update

• Also, see the warning about updating yum if you are running a version earler than SME 7.1.1

under Which_repositories_should_be_enabled

• An unclean shutdown during a system update can put the system into a state where it's difficult to recover.

Try not to kick the power cord and use a UPS

• Where can I go to learn more about yum, and about how SME uses it?

SME_Server:Documentation:Technical_Manual:Chapter6#Yum_Repositories

Hard Drives, RAID's, USB Hard Drives

• How should I setup my hard-drives?

We never recommend anything other than a single disk install or multiple disks of the same type. Anything else and you are following an unrecommended setup and you will need to navigate for yourself. Repeat, we never recommend anything other than a single disk install or multiple disks of the same type. If you're thinking of doing anything else (setup your own partitions), read this section again.

• How should I setup my RAID?

A full article on RAID is found here: [[8]]

• I want to use a hardware RAID. What do you suggest?

Please see the notes in the RAID article: [[9]]

• I'm installing a RAID 5 but it seems to take a long time. Is there something wrong?

RAID 5 systems (those with 3+ disks) can take a long time during and after the install for everything to sync. Reportedly, it takes almost 2 hours before the disks finally finish syncing on 4 X 80GB disks.

• If I boot my SMESERVER with a USB hard drive attached, it recognizes the drive. However, after unplugging the drive, then replugging, it no longer exists. Any ideas why?

Reportedly, some external usb hd's must be completely powered up before connecting the usb cable.

Known Problems

This section is to be used to document problems that cannot or will not be fixed through development of SME7.

Backup/Restore

• Using a combination of hardware and software compression for tape backup causes errors

You should use only one of software or hardware compression. Doing both may exercise bugs, and won't reduce the size of data on the tape - it is more likely to increase it. [[10]]

• Backup to desktop 4GB limit

As in previous versions of SME Server, the backup to desktop function has a limit of 4GB. It's not fixable until we know where the limit or limits are. All these components are involved in transferring the backup file, and at least one of them is truncating at 4GB: tar, perl, mod_proxy, apache, TCP stack, browser at desktop end. See this bug listing for details Bugzilla:701

Hardware

• Problem with NIC card or integrated NIC.

If your NIC card isn't working, replace it with a different one. If your integrated NIC isn't working, disabling onboard lan and inserting pci network card works.

Problem reports have been submitted with the following NIC's:

VIA EPIA board network card has issues associated to a beta version of SME, upstream fix from Centos could not be confirmed from reporter. Bugzilla:333

Realtek 8169 Ethernet is not recommended The driver included in ~CentOS 4.1 is out of date and has problems. See this bug listing for details, and please update the bug if you have a solution (i. e. updated drivers): [[11]]

Intel 82573L Gigabit Ethernet says the e1000 driver should work but doesn't [[12]].

• Losing too many ticks

A kernel bug with Athlon64 processors may cause the system to run slowly, possibly fixed with a later kernel

• VGA problem with VIA EPIA board

Once the installer loads the VGA display loses sync and it is impossible to read what is being displayed. There is a workaround, see this bug report for details: Bugzilla:236

• Slow Disk Format

Installing 2 discs as Primary and Secondary on the same IDE channel may cause slow formatting and is not a very good idea because:
1-May hamper system performance.
2-Does not provide system redundancy if you loose the IDE channel.

• Why does my clock run too fast in SME Server under VMware?

If you are testing SME Server on VMware, you may notice the clock doen't keep time accurately. See this bug report for details and a possible fix. [[13]]

• D-Link DFE 530TXS rev. A1 Ethernet adaptor not recognized (a.k.a. DL10050, Sundance)

Redhat doesn't support this ethernet adapter, so unfortunatly it won't work with SME7. See the Redhat Bugzilla entry below for more information. [[14]] [[15]]

• Boot failure after install if you have enabled hardware raid

There sometimes seem to be conflicts with the SME Server automatic software raid setup in combination with hardware raid. Disabling the hardware raid in your motherboard or controller card's bios is the suggested fix. See these bug reports for details: [[16]] [[17]]

• 3com 905 (Cyclone) Ethernet is not recommended

This card is not detected

• These motherboards may need a bios update

2001 CUSI-M motherboard
Tyan S2850G2N with AMD Opteron 160, BIOS update >= 112
Boards using a Dual Pentium Pro are unlikely to work

• Booting in SMP mode results in kernel panic with certain hardware

The combination of a 2MB Cache P4 3.0GHZ CPU, and a Giga-byte GA-81848P775-G (Intel 848P chipset) motherboard produces this problem. Other simialar hardware may be affected. If you encounter this problem, see this bug report for a workaround. [[18]]

• Legacy ~MegaRAID driver is no longer included

Certain raid cards that worked under SME Server 6, do not work under SME Server 7. Adapters with the following PCI vendor ID and device ID pairs are not supported by the megaraid_mbox driver: vendor, device = 0x101E, 0x9010; 0x101E, 0x9060; 0x8086, 0x1960. The lspci -n command can be used to display the IDs for adapters installed in a particular machine. Products with these IDs are known by (but not limited to) the following model names: Broadcom 5820, Dell PERC (dual-channel fast/wide SCSI) RAID controller, Dell PERC2/SC (single-channel Ultra SCSI) RAID controller, Dell PERC2/DC (dual-channel Ultra SCSI) RAID controller, Dell CERC (four-channel ATA/100) RAID controller, DRAC 1, ~MegaRAID 428, ~MegaRAID 466, ~MegaRAID Express 500, HP NetRAID 3Si and 1M. Both Dell and LSI Logic have indicated that they no longer support these models in the 2.6 kernel. As a result, these adapters are no longer supported in Red Hat Enterprise Linux 4 Update 1, upon which SME Server 7 is based. See this bug listing for details, there is an unsupported workaround if needed: [[19]]

• aic7xxx driver hangs on installation boot

On some Compaq Proliant servers (specifically an ML370 G2), & possibly others, the aic7xxx driver will hang if there is nothing connected to the adaptor or if it is not terminated correctly. On most Proliants you can tell the BIOS to not allocate an IRQ to the device which effectively disables it; the ML370 G2 uses an AIC-7899 chip on the motherboard. This problem also exists in the ~CentOS 4.3 base. SME 6.0 loads fine which would seem to indicate that the newer driver in ~CentOS 4.3 can't handle the older system (this Proliant is probably 5 years old). Bugzilla:373

• older systems stop at reboot

This may be an issue from the older P2 and early P3 era BIOS'es but the problem may also occur on some newer chipsets, that don't follow the "specs" for power saving features. Also, this problem seems to be more prevalent in multi-CPU machines. Only a kernel change could provide a real fix to this issue. For some motherboards, there may be a workaround by adding appropriate text to the grub config. The addition of the noapic and acpi=off to etc/grub.conf might solve the problem of reboots failing.

• Installation hangs and the last screen shown is "Welcome to SME Server". The last item is "*trying to mount CD device...". What should I do?

Hold shift key at boot time, then when you see the boot: prompt 
type: linux ide=nodma

• Install on IBM IntelliStation M Pro stalls

Hold shift key at boot time, then when you see the boot: prompt 
type: sme acpi=off

• I'm burning the SMESERVER cd. When I check the md5sum on this burner, it returns an *incorrect* value. What gives?

Try a different cd burner. We've found in the past that some drives provide an extra garbage block when reading back the image. This results in an incorrect md5sum value.

• I'm trying to use an old tape drive with my SMESERVER but I can't get it working. What gives?

SMESERVER does not provide ide-tape (which is deprecated by Dell and RedHat).

• My Adaptec DPT raid controller is not migrated on upgrade. What gives?

The Adaptec DPT raid controller won't work for upgrades. However, the Adaptec DPT raid controller works on new installs. For details visit: [[20]]

• I've loaded the SMESERVER into my hardware without problems. Now my SMESERVER freezes when I reboot. What gives?

Most likely this is a problem with the video card or sound card. The best fixes are to replace the video/sound card, disable the video/sound in the bios (if it's integrated on the motherboard) or remove the video/sound card altogether. Video/sound isn't needed on the SMESERVER and can be managed via the SERVER-MANAGER.

Please note that other hardware devices such as CD-ROM drives as well as mismatched IDE cables may cause a problem, (i.e. kernel panic on reboot after installation). For details, visit:[[21]]

• My SMESERVER suddenly stopped working. I look in the log messages I see: kernel: ata1: command 0x35 timeout, stat 0x50 host_stat 0x1. Any ideas what could be causing this?

Most likely, this is either a hardware or BIOS problem or a kernel bug. It's very unlikely we can fix any of those. However, you can try editing /etc/grub/grub.conf. In this file, close to the top, you'll see the latest kernel. It looks like this:

kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/vg_primary/lv_root

Add "noapic" to the end. It should look like this:

kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/vg_primary/lv_root noapic

Then reboot. Hopefully the problem goes away.

• Is there a problem installing SMESERVER with my NFORCE motherboard?

Submitted reports claim that nForce boards based on the 410 or 430 chipset won't work [[22]].

• Is there a problem installing SMESERVER with my ZIP drive?

Submitted reports claim that installing SMESERVER on a system with a ZIP drive won't work [[23]].

• Is there a problem installing SMESERVER with my laptop?

SME Server has never supported laptop PCMCIA network adaptors. This being said, some possible workarounds have been identified in Bugzilla:1246

• When I try to install SMESERVER, it gets to SATA Driver installation and I get "Disabling INT 10)" and the system hangs.

Try holding SHIFT while the CD boots. At the boot: prompt, type:

boot: sme acpi=off

Installation (not hardware related) & Initial Configuration

• Why is there a delay after verifying administrator password?

There is a delay (2-5 seconds) after verifying administrator password. This is because the password is actually set and checked at this point. Everything else we wait until the script is done to perform any actions. [[24]]

• Use /server-manager, not /e-smith-manager

In previous versions, both aliases worked, but in SME Server 7 you must use /server-manager to access the server manager. [[25]]

• Why can the system not be named 'mail', 'ftp' or 'www'?

If you choose one of these for the hostmane of your server, the atalk (Appletalk) service will have errors and fail. See these bug listings for details: [[26]] [[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1264588&group_id=96750

• Why is there no option to create reinstallation disk?

There is no option to create a reinstallion disk during installation or later from the Administration section of the server-manager. This is intentional, since it required too much effort to keep it up-to-date as kernels change. The CD contains a rescue mode, which is a better environment for fixing problems, and a reinstall followed by a restore of the configuration works well without us supporting another method. Additionally, the kernel has grown too large for a floppy plus initrd. Even Redhat installs no longer offer to create a boot floppy at install time. More details can be found in Bugzilla:792.

• 4 disk install - md1 is raid1 and md2 is raid5

Even if you have 4 (or more) disks, which are supported by your motherboard and ~CentOS, md1 is always set up as a 4 disk raid1. This is, because you can't boot off a raid-5. md1 is the boot partition and must either be non-raid or raid-1. md2 will be set up as a 4 disk raid5 as expected. More information can be found in Bugzilla:759.

• Anaconda crash from rescue mode when starting network interfaces

There is a problem with the installer and as networking is not essential for a rescue function it won't be fixed any time soon. Bugzilla:712

• On first boot after installation, system name appears on terminal 1 while on terminal 2 and 3 it shows as "localhost".

This is because the gettys on tty2 and tty3 are started before the configuration wizard runs, and therefore before the system name has been set. Also note that the correct system name is displayed after someone logs out from VT2 or VT3?)

• The installation gave an exception when trying to format already formatted disks.

In some cases, you may have to manually wipe re-used disks.