Changes

From SME Server
Jump to navigationJump to search
1,130 bytes removed ,  07:12, 4 December 2024
Line 1,195: Line 1,195:  
{{Warning box|WIP inspired from [[Sme10BuildQueue#Bare install test]]}}
 
{{Warning box|WIP inspired from [[Sme10BuildQueue#Bare install test]]}}
   −
Install minimal iso for rocky 8  
+
* Install server environment group from minimal iso for rocky 8  
    
https://download.rockylinux.org/pub/rocky/8/isos/x86_64/Rocky-8-latest-x86_64-minimal.iso
 
https://download.rockylinux.org/pub/rocky/8/isos/x86_64/Rocky-8-latest-x86_64-minimal.iso
Line 1,201: Line 1,201:  
Configure network access during installation with option to restore. Configure only root user.
 
Configure network access during installation with option to restore. Configure only root user.
   −
Install EPEL8 repo.
+
* if needed reconfigure network using nm
dnf install epel-release
  −
Install remi 8 repos
  −
dnf install <nowiki>https://rpms.remirepo.net/enterprise/remi-release-8.rpm</nowiki>
  −
 
  −
Update, and install those package, as the might get handy (nb iptraf is now iptraf-ng)
  −
dnf update -y
  −
dnf install mc htop iftop iptraf screen wget vim ppp traceroute setserial traceroute cyrus-sasl-md5 cyrus-sasl device-mapper-multipath dhcp-client fetchmail ftp iscsi-initiator-utils lm_sensors minicom mt-st sysfsutils tcpdump telnet wodim
      
* Disable SELinux
 
* Disable SELinux
  −
SELinux is enabled by default. We want to disable it for there are a few services (e.g. httpd) that get blocked by SELinux. To check the status of SELinux you can enter the command:
  −
getenforce
   
SELinux uses policies that conflict with some of the SME Server services ports like https. One can adjust the allowed ports, or remove the SELinux policies and disable SELinux by the following commands:
 
SELinux uses policies that conflict with some of the SME Server services ports like https. One can adjust the allowed ports, or remove the SELinux policies and disable SELinux by the following commands:
 
  setenforce 0
 
  setenforce 0
 
  sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
 
  sed -i -e 's/SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
 
  dnf remove selinux-policy-targeted
 
  dnf remove selinux-policy-targeted
 +
 +
* Install epel repo
 +
dnf install epel-release
 +
 +
* Install remi 8 repos
 +
 +
dnf install <nowiki>https://rpms.remirepo.net/enterprise/remi-release-8.rpm</nowiki>
 +
 +
* install openfusion 8
 +
 +
dnf install http://repo.openfusion.net/centos8-x86_64/openfusion-release-0.8-2<nowiki/>.of.el8.noarch.rpm
 +
 +
* Update, and install those package, as the might get handy (nb iptraf is now iptraf-ng)
 +
 +
# TO REMOVE NOT NEEDED
 +
dnf update -y
 +
dnf install mc htop iftop iptraf screen wget vim ppp traceroute setserial traceroute cyrus-sasl-md5 cyrus-sasl device-mapper-multipath dhcp-client fetchmail ftp iscsi-initiator-utils lm_sensors minicom mt-st sysfsutils tcpdump telnet wodim
    
* SSH
 
* SSH
Line 1,233: Line 1,240:  
  vim /etc/yum.repos.d/smeserver11.repo
 
  vim /etc/yum.repos.d/smeserver11.repo
 
and paste
 
and paste
  [smedev]
+
  [smeos]
 +
enabled=1
 +
MirrorList=http://mirrorlist.contribs.org/mirrorlist/smeos-11
 +
name=SME Server - os
 +
gpgcheck=1
 +
enablegroups=1
 +
 +
[smeupdates-testing]
 
  enabled=0
 
  enabled=0
  MirrorList=http://mirrorlist.contribs.org/mirrorlist/smedev-11
+
  MirrorList=[http://mirrorlist.contribs.org/mirrorlist/smeos-11 http://mirrorlist.contribs.org/mirrorlist/smeupdates-testing-11]
  name=SME Server - dev
+
  name=SME Server - update testing
 
  gpgcheck=1
 
  gpgcheck=1
 
  enablegroups=1
 
  enablegroups=1
 +
 
  [smetest]
 
  [smetest]
 
  enabled=0
 
  enabled=0
Line 1,245: Line 1,260:  
  gpgcheck=1
 
  gpgcheck=1
 
  enablegroups=1
 
  enablegroups=1
[smeos]
  −
enabled=0
  −
MirrorList=http://mirrorlist.contribs.org/mirrorlist/smeos-11
  −
name=SME Server - dev
  −
gpgcheck=1
  −
enablegroups=1
  −
   
   
 
   
 
  [koji-sme11]
 
  [koji-sme11]
  enabled=1
+
  enabled=0
 
  name=koji-sme11
 
  name=koji-sme11
 
  baseurl=<nowiki>http://koji.koozali.org/kojifiles/repos-dist/dist-sme11-os/latest/x86_64/</nowiki>
 
  baseurl=<nowiki>http://koji.koozali.org/kojifiles/repos-dist/dist-sme11-os/latest/x86_64/</nowiki>
Line 1,261: Line 1,269:  
  enablegroups=1
 
  enablegroups=1
 
   
 
   
[koji-contribs11]
+
 
enabled=0
+
* install SME10 and 11 keys
name=koji-contribs11
+
 
baseurl=http://koji.koozali.org/kojifiles/repos-dist/smecontribs11-testing/latest/x86_64/
  −
gpgcheck=0
  −
enablegroups=1
  −
install SME10 and 11 keys
  −
wget <nowiki>http://mirror.koozali.org/releases/10/smeos/x86_64/RPM-GPG-KEY-koozali</nowiki>
  −
rpm --import RPM-GPG-KEY-koozali
   
  wget <nowiki>https://src.koozali.org/staging/sme-release/raw/branch/master/RPM-GPG-KEY-sme11</nowiki>
 
  wget <nowiki>https://src.koozali.org/staging/sme-release/raw/branch/master/RPM-GPG-KEY-sme11</nowiki>
 
  rpm --import RPM-GPG-KEY-sme11
 
  rpm --import RPM-GPG-KEY-sme11
    +
* install Remi el8 key
   −
install openfusion 8
+
  rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-remi.el8
  dnf install http://repo.openfusion.net/centos8-x86_64/openfusion-release-0.8-2<nowiki/>.of.el8.noarch.rpm
   
then
 
then
 
  dnf --enablerepo=* clean all
 
  dnf --enablerepo=* clean all
 
   
 
   
try installing SME11 packages, you might need to enable some repo using --enablerepo=smedev,epel,elrepo ... e.g.
+
try installing SME11 packages, you might need to enable some repo using  
 
  dnf module switch-to php:remi-8.3 -y
 
  dnf module switch-to php:remi-8.3 -y
 
  dnf module switch-to mariadb:10.5 -y
 
  dnf module switch-to mariadb:10.5 -y
 
  dnf module switch-to python36:3.6 -y
 
  dnf module switch-to python36:3.6 -y
 
  dnf module install php:remi-8.3
 
  dnf module install php:remi-8.3
  dnf install smeserver-* --enablerepo=koji-sme11,epel,remi,remi-safe,of,baseos,appstream,powertools 
+
  dnf install @smeserver  
    
{{Warning box| If you get PGPKEY failures, then just add "--nopgpcheck" to the dnf install command }}
 
{{Warning box| If you get PGPKEY failures, then just add "--nopgpcheck" to the dnf install command }}
   −
{{Warning box|we will drop horde support, so we have no limitation in keeping php 8.1 which is obsolete, I suggest to go with  8.3 EOL 23 Nov 2026}}
+
et voilà, you have a <u>non functional SME 11 over Rocky 8 minimal</u>.
et voilà, you have a non functional SME 11 over Rocky 8 minimal.
     −
Also remember that the legacy server manager (SM1) is not installed by the above, so, perhaps:
     −
  dnf install e-smith-manager
+
'''<nowiki>##</nowiki> This is safer to be done directly on tty, not via ssh:'''
   −
If you then find you get an SM1 login but the login just clears the fields and does not login, then you can fix this with:<syntaxhighlight lang="shell">
+
* Get rid of Network-Manager NOW!
expand-template /etc/e-smith/web/common//cgi-bin/AuthTKT.cfg
  −
</syntaxhighlight>You also need to stop dnf using the old repos when doing an update:<syntaxhighlight lang="shell">
  −
mkdir -p /etc/e-smith/templates-custom/etc/dnf/dnf.conf
  −
echo ‘#rem by custom template’> /etc/e-smith/templates-custom/etc/dnf/dnf.conf/20main_reposdir
  −
expand-template /etc/dnf/dnf.conf
  −
signal-event dnf-update
  −
 
  −
</syntaxhighlight>
  −
 
  −
 
  −
'''<nowiki>##</nowiki> This is safer to  be done directly on tty, not via ssh:'''
     −
Get rid of Network-Manager NOW!
   
  systemctl stop NetworkManager
 
  systemctl stop NetworkManager
 
  systemctl disable NetworkManager  
 
  systemctl disable NetworkManager  
Line 1,314: Line 1,302:  
  systemctl disable NetworkManager-wait-online.service
 
  systemctl disable NetworkManager-wait-online.service
 
  systemctl start networking
 
  systemctl start networking
  dnf remove NetworkManager* --noautoremove
+
  dnf remove NetworkManager* --noautoremove  
 +
 
 +
* some cleanup
 +
 
 +
dnf remove @headless-management @hardware-support
 
then you could try, (you might have no network form there), unlink this to avoid root password locking
 
then you could try, (you might have no network form there), unlink this to avoid root password locking
 
   
 
   
Line 1,327: Line 1,319:  
then try to configure using console
 
then try to configure using console
 
  /sbin/e-smith/console
 
  /sbin/e-smith/console
To get better information from Server Manager 2 (this replaces the barfing dinosaur):<syntaxhighlight lang="shell">
  −
mkdir -p /etc/e-smith/templates-custom/usr/share/smanager/conf/srvmngr.conf/
  −
cat <<EOF > /etc/e-smith/templates-custom/usr/share/smanager/conf/srvmngr.conf/30Other
  −
    modules_dir => 'lib/SrvMngr/Controller',
  −
    webapp => 'smanager',
  −
    mode => 'development',
  −
    debug => 1,
  −
\}
  −
EOF
  −
expand-template /usr/share/smanager/conf/srvmngr.conf
  −
signal-event smanager-refresh
  −
</syntaxhighlight>
        Line 1,353: Line 1,333:  
'''<nowiki>##</nowiki> end of the part better on tty than on sshd'''
 
'''<nowiki>##</nowiki> end of the part better on tty than on sshd'''
   −
if you want to test the new (partial) postfix changes, then please follow the instructions here:
     −
https://src.koozali.org/smeserver/smeserver-postfix
+
from there if you are lucky it worked and you can try to test , report as bug or even create a patch
   −
you can also tidy a little (40Mo)
+
'''at the moment of the update UPS nut and qpsmtpd-postfix-qmail are work on progress.'''
  dnf remove @headless-management @hardware-support
  −
you might need avoid using sme* repo except for koji builsdsystem one as long as they are not populated to do so:
     −
(this is also mentioned above)
+
=== optional parts for testing ===
   −
<syntaxhighlight lang="shell">
+
==== Koji repos ====
mkdir -p /etc/e-smith/templates-custom/etc/dnf/dnf.conf/
+
also you might want to plan ahead and put the koji repo for when you will have deleted the custom template.
echo "#rem custom"> /etc/e-smith/templates-custom/etc/dnf/dnf.conf/20main_reposdir
  −
expand-template /etc/dnf/dnf.conf
  −
</syntaxhighlight>also you might want to plan ahead and put the koji repo for when you will have deleted the custom template.
   
  vim /etc/yum.smerepos.d/koji.repo
 
  vim /etc/yum.smerepos.d/koji.repo
 
and paste:
 
and paste:
Line 1,385: Line 1,359:  
  enablegroups=1
 
  enablegroups=1
    +
==== Ye ol e-smith-manager ====
 +
Also remember that the legacy server manager (SM1) is not installed by the above, so, perhaps:
 +
dnf install e-smith-manager
    +
If you then find you get an SM1 login but the login just clears the fields and does not login, then you can fix this with:<syntaxhighlight lang="shell">
 +
expand-template /etc/e-smith/web/common//cgi-bin/AuthTKT.cfg
 +
</syntaxhighlight>
    +
==== debug mode of new smanager ====
   −
 
+
To get better information from Server Manager 2 (this replaces the barfing dinosaur):<syntaxhighlight lang="shell">
 
+
mkdir -p /etc/e-smith/templates-custom/usr/share/smanager/conf/srvmngr.conf/
from there if you are lucky it worked and you can try to test , report as bug or even create a patch
+
cat <<EOF > /etc/e-smith/templates-custom/usr/share/smanager/conf/srvmngr.conf/30Other
 
+
    modules_dir => 'lib/SrvMngr/Controller',
 +
    webapp => 'smanager',
 +
    mode => 'development',
 +
    debug => 1,
 +
\}
 +
EOF
 +
expand-template /usr/share/smanager/conf/srvmngr.conf
 +
signal-event smanager-refresh
 +
</syntaxhighlight>
 
== Notes ==
 
== Notes ==
 
we will have horde 6 in remi Horde 6 requires PHP 8.1 or PHP 8.2 versions.  Support for PHP 8.3 is in development. https://wiki.horde.org/Doc/Dev/H6/Installation/PHP?referrer=Doc%2FDev%2FH6%2FInstallation
 
we will have horde 6 in remi Horde 6 requires PHP 8.1 or PHP 8.2 versions.  Support for PHP 8.3 is in development. https://wiki.horde.org/Doc/Dev/H6/Installation/PHP?referrer=Doc%2FDev%2FH6%2FInstallation
Super Admin, Wiki & Docs Team, Bureaucrats, Interface administrators, Administrators
3,299

edits

Navigation menu