3,250
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + Line 23:
Line 25: − + − + + Line 34:
Line 37: − + − + + − + − + Line 60:
Line 64: + + − + + + Line 73:
Line 81: − + − + Line 100:
Line 108: − + Line 178:
Line 186: − + Line 187:
Line 195: + + Line 195:
Line 205: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 209:
Line 275: − + − + + +
→only run script in a daemontool runit /service/servicename folder
This section is to be used to document problems that cannot or will not be fixed through development of SME Server 7.0.
This section is to be used to document problems that cannot or will not be fixed through development of SME Server 7.0. Much of this is obsolete for later versions but left for reference.
Plese be certain any suggestions followed apply to the version you are using!
==Backup/Restore==
==Backup/Restore==
*Realtek 8169 Ethernet is not recommended, The driver included in CentOS 5 is out of date and has problems. See [[Bugzilla:8554]] for details on a workaround using a driver package from elrepo.
*Realtek 8169 Ethernet is not recommended, The driver included in CentOS 5 is out of date and has problems. See [[Bugzilla:8554]] for details on a workaround using a driver package from elrepo.
*Two identical Realtec nic's caused a kernal panic, Model unknown
*Two identical Realtec nic's caused a kernel panic, Model unknown
*Intel 82573L Gigabit Ethernet says the e1000 driver should work but doesn't
*Intel 82573L Gigabit Ethernet says the e1000 driver should work but doesn't
*3com 905 (Cyclone) Ethernet is not recommended. This card 'may' not be detected though a site
*3com 905 (Cyclone) Ethernet is not recommended. This card 'may' not be detected though a site
has reported success (0000:00:0d.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xb800. Vers LK1.1.19).
has reported success (0000:00:0d.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xb800. Vers LK1.1.19).
*D-Link DFE-530TXS rev. A1 Ethernet adaptor not recognized (a.k.a. DL10050, Sundance) (See also [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154349 RedHat bug 154349])
*D-Link DFE-530TXS rev. A1 Ethernet adaptor not recognized (a.k.a. DL10050, Sundance) (See also [https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=154349 RedHat bug 154349])
===Systems or motherboards may need a bios update or are unsupported===
===Some systems or motherboards may need a bios update or are unsupported===
*Most of the latest generation of motherboards do not appear to be compatible (as shipped) with either SME7.5 or 7.6WIP. [[Bugzilla:6701]]
*v7.5: Latest generation of motherboards do not appear to be compatible (as shipped) with either SME7.5 or 7.6WIP. [[Bugzilla:6701]]
*Version 8.0 of SME Server is based on CentOS 5. CentOS 5 does not suppoort i586 architecture [[Bugzilla:4740]] and [[Bugzilla:6671]]
*Version 8.0 of SME Server is based on CentOS 5. CentOS 5 does not support i586 architecture [[Bugzilla:4740]] and [[Bugzilla:6671]]
*2001 CUSI-M motherboard - bios
*2001 CUSI-M motherboard - bios
*Tyan S2850G2N with AMD Opteron 160, BIOS update >= 112
*Tyan S2850G2N with AMD Opteron 160, BIOS update >= 112
*Compaq ProLiant 6400R's see [[bugzilla:2175]]
*Compaq ProLiant 6400R's see [[bugzilla:2175]]
===Unsorted===
===Unsorted===
*Losing too many ticks
*Losing too many ticks
A kernel bug with Athlon64 processors may cause the system to run slowly, possibly fixed with a later kernel
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
*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 ]]
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 | Bugzilla:236]]
*VIA EPIA CL1000 (dual LAN, single processor)
*VIA EPIA CL1000 (dual LAN, single processor)
The smp kernal fails to boot - non-smp works like a charm...
The smp kernal fails to boot - non-smp works like a charm...
slow formatting and is not a very good idea because:
slow formatting and is not a very good idea because:
# May hamper system performance.
#May hamper system performance.
# Does not provide system redundancy if you loose the IDE channel.
#Does not provide system redundancy if you loose the IDE channel.
===Why does my clock run too fast in SME Server under VMware?===
===Why does my clock run too fast in SME Server under VMware?===
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1274199&group_id=96750]] -->
[[https://sourceforge.net/tracker/?func=detail&atid=615772&aid=1274199&group_id=96750]] -->
===Raid on HP server Proliant ML330 ===
===Raid on HP server Proliant ML330===
Raid on HP server Proliant ML330 with adaptec RAID is unsupported
Raid on HP server Proliant ML330 with adaptec RAID is unsupported
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. Note however that this is no longer an issue with version 7.2. [[bugzilla:712]]
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. Note however that this is no longer an issue with version 7.2. [[bugzilla:712]]
===On first boot after installation, system name appears on terminal 1 while on terminal 2 and 3 it shows as "localhost". ===
===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?)
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?)
===Restarting NUT===
===Restarting NUT===
*My UPS doesn't work although its status says that it's running. What gives?
*My UPS doesn't work although its status says that it's running. What gives?
Rather than:
Rather than:
service nut restart
service nut restart
service nut start
service nut start
Details: [[bugzilla:2738]]
Details: [[bugzilla:2738]]
===Manualy install a service on SME 10 and newer===
Starting SME 10 systemd is in used, but there are some backward compatibility for sysvinit and daemontools managed service.
Prefered way to install a non core service is by using a contrib, but if you need to run a service without any contrib available, then here are the steps.
First check if the rpm providing the service includes either a /etc/rc.d/init.d/'''servicename''' or a /usr/lib/systemd/system/'''servicename'''.service files. Replace '''servicename''' by the appropriate name.
====Global steps====
Create a db entry in configuration db:
config set '''servicename''' service status enabled
====only systemd .service file available====
Create a dropin file to have this service available under sme-server.target as this is our target, we do not use the regular multi-user.target.
mkdir -p /etc/lib/systemd/system/'''servicename'''.service.d/
printf "[Install]\nWantedBy=sme-server.target\n" > /etc/lib/systemd/system/'''servicename'''.service.d/50koozali.conf
systemctl daemon-reload
/etc/e-smith/events/actions/systemd-default
NB: in a contrib, we would use the /usr/lib/systemd/system/'''servicename'''.service.d/50koozali.conf path as it would be provided by an rpm and not by end-user admin.
====both systemd .service and /etc/rc.d/init.d/'''servicename''' files available====
You need to hide the file in init.d from SME Server internals to be able to enable the service form systemd on reboot
mkdir -p /etc/e-smith/templates-custom/etc/systemd/system-preset/49-koozali.preset/
printf "{
\$customservice=''''servicename'''';
\$OUT="";
\$OUT .= \"enable \$customservice.service\n\" if \${\$customservice}{'status'} eq \"enabled\";
}" >> /etc/e-smith/templates-custom/etc/systemd/system-preset/49-koozali.preset/99'''servicename'''
expand-template /etc/systemd/system-preset/49-koozali.preset
/etc/e-smith/events/actions/systemd-default
====only /etc/rc.d/init.d/'''servicename''' file available====
cd /etc/rc.d/rc7.d
ln -s ../init.d/'''e-smith-service''' S85'''servicename'''
====only run script in a daemontool runit /service/'''servicename''' folder====
as previously replace servicename to the actual service name
<syntaxhighlight lang="bash" >printf "[Unit]
Description=servicename
Requires=runit.service
[Service]
Type=oneshot
ExecStartPre=/sbin/e-smith/service-status servicename
ExecStart=/usr/bin/sv u /service/servicename
ExecStop=/usr/bin/sv stop /service/servicename
ExecReload=/usr/bin/sv t /service/servicename
RemainAfterExit=yes
[Install]
WantedBy=sme-server.target" > /etc/systemd/system/servicename.service
systemctl daemon-reload
/etc/e-smith//events/actions/systemd-default
</syntaxhighlight>
==Packages==
==Packages==
This fixed the issue. Details: [[bugzilla:6857]]
This fixed the issue. Details: [[bugzilla:6857]]
<noinclude>----
<noinclude>
[[Category:SME Server]]</noinclude>
----
[[Category:SME Server]]
</noinclude>