SME Server:9.0Alpha
Back to SME Server 9.0 Development
SME 9 Alpha (Feb 13 2013 version) ISO Testing
An overview of related SME9 development pages can be found here.
User Feedback
The Alpha ISO will not give you a working system out of the box. There are steps here to follow after you install, but this will get you to a point that the other developers are at, and then you can report bugs and suggest fixes. Any issues that require developers attention should be logged in our Bug Tracker. (See below)
Bugs
Installing SME9 Alpha
- We suggest you use a virtual machine, like Virtualbox - [1]. The advantage is that you can save snapshots at important stages of testing and revert to them quickly. Some tips for virtualbox: The default settings for a Redhat virtual machine are fine, but you will want to change the Network settings to add a second network interface and be bridged adapters if you want to test Server-Gateway mode. The 1st adapter is local, the 2nd adapter is external.
- Download the SME9 Alpha ISO from [2]. Use the x86_64 version if your hardware supports it.
- Start the machine and choose the ISO image to boot from.
After first reboot
- Save a snapshot
- Login as root and enable networking:
ifup eth0 ifup eth1
- enable ssh for access from Putty or other SSH client
echo "ALL:ALL" >> /etc/hosts.allow service sshd reload
- Configure SME9 repositories
Download a repo file that will enable the SME9 repo's as a temporary measure until the SME9 yum.conf settings are enabled. Only the packages from SME8 which have not been built for SME9 are 'included' in the repo file, as some packages in smeos8,smeupdates8 are higher versions than in el6 - The necessity of doing this has been reported in bugzilla:???
wget -O /etc/yum.repos.d/sme9.repo http://bugs.contribs.org/attachment.cgi?id=3682
- Yum install some packages not installed by the CD
- The necessity of doing this has been reported in bugzilla:???
yum --enablerepo=smeos8,smeupdates8 install smeserve\* e-smit\* aspell aspell-en at audit-libs-python autoconf automake bc bind-libs bind-utils cronie cronie-anacron crontabs cyrus-sasl-md5 dhcp dosfstools ed eject elfutils elfutils-libs fetchmail ftp gettext glib gpm hesiod hmaccalc imake iptraf iptstate isdn4k-utils libXdmcp libgomp libselinux-python libsmbclient libsysfs libxml2-python lm_sensors lockdev lsof lvm2 m2crypto man mcstrans minicom mkbootdisk mlocate mod_ssl mtools mt-st mutt neon net-snmp net-snmp-utils openldap-servers patch pcmciautils postgresql-libs pyxf86config rpm-build rp-pppoe setserial strace sudo sysfsutils syslinux tcpdump telnet time tmpwatch traceroute unzip usbutils usermode vim-common vim-enhanced wget wodim xz zip zlib php-pear-Net-URL perl-Compress-Raw-Bzip2 perl-IO-Compress-Bzip2 rsync tnef freeradius-ldap --nogpg
(todo: fix the repo file and instructions to not have to add --nogpg)
- Yum upgrade to see if there are other updates available
yum upgrade
- Save another snapshot
- post-upgrade / reboot
/sbin/e-smith/signal-event post-upgrade /sbin/e-smith/signal-event reboot
- Save another snapshot
- Configure the server
- log in as root and run 'console' and select 'configure this server', will reboot to apply changes
- Re-enable ssh access (the lazy not-so-secure way)
db configuration setprop sshd status enabled db configuration setprop sshd PermitRootLogin yes db configuration setprop sshd acccess public db configuration setprop sshd PasswordAuthentication yes /sbin/e-smith/signal-event remoteaccess-update
- Enable easier access to the server manager (modify as needed for your network)
db configuration setprop httpd-admin access public db configuration setprop httpd-admin PermitPlainTextAccess yes db configuration setprop httpd-admin ValidFrom '192.168.1.0/255.255.255.0' /sbin/e-smith/signal-event remoteaccess-update
Should be able to access https://yourserverip/server-manager/ now in a browser
- Save another snapshot
- Look for things to fix & Report bugs/problems
- If you have followed these steps and you are up to date with 'yum upgrade', go ahead and look for problems, and report them to the bug tracker. Currently there are many issues, but lots have been reported and fixed already, so report issues you find right away.
Some ideas for things to look for:
- Services not starting
- Config files (templates) that need changes, especially if the major version of the package has changed
- Look in the various log files for clues to problems
- add more generic ideas here....specific issues to the bugtracker please
- Please consult/subscribe to the devs list for more information. devinfo mailinglist and in particular all threads starting with " SME on CentOS 6"
- There is a IRC channel where people who are interested in this effort 'hang out'. You're most welcome to drop by and/or join. It's free! ;-)
- You do not have to install anything to pay the channel a visit. All you need is a nice nickname and right click here to open the channel in a new browser window or tab.