UnixRonin
commented
3 years ago On 4/15/21 11:08 AM, Paul Menzel wrote:
Thank you. The issue is about missing steps in the installation though. Are there any missing? If not, could you close this issue, and create a new one for creating an OpenRC file? That’d be great.
Actually TODAY, I managed to find time to look at this further, and found a workaround for the wwsympa init file. That workaround is, on Gentoo, don't use the wwsympa service per se; use www-servers/spawn-fcgi instead.
Do the following:
-
symlink /etc/init.d/spawn-fcgi to /etc/init.d/spawn-fcgi.sympa
-
create /etc/conf.d/spawn-fcgi.sympa with these contents:
FCGI_SOCKET=/var/run/sympa/wwsympa.socket FCGI_ADDRESS=127.0.0.1 FCGI_PORT= FCGI_PROGRAM=/usr/libexec/sympa/wwsympa.fcgi FCGI_CHILDREN=1 FCGI_CHROOT= FCGI_CHDIR= FCGI_USER=sympa FCGI_GROUP=sympa FCGI_EXTRA_OPTIONS='-s /var/run/sympa/wwsympa.socket -M 0600 -U apache' ALLOWED_ENV="PATH"
- modify /etc/init.d/sympa as follows:
depend() { use logger mysql postgres ldap before apache apache2 lighttpd need spawn-fcgi.sympa <=== add these two lines after spawn-fcgi.sympa <=== }
- Add spawn-fcgi and sympa to the default runlevel:
rc-update add default spawn-fcgi.sympa rc-update add default sympa
- Start the sympa server:
rc-service sympa start
-- Phil Stracchino Babylon Communications @. @. Landline: +1.603.293.8485 Mobile: +1.603.998.6958
I am endeavoring to migrate a couple of small private mailing lists from Mailman to Sympa for technical reasons. I've gotten most of the way through installation without major problems, but run into a roadblock at initializing the database. Database permissions are working, and sympa.pl --health_check correctly created the sympa schema. I'm at the point of starting sympa for the first time, but it will not start, insisting that I must run sympa.pl --upgrade first. However, sympa.pl --upgrade fails — badly — because it has no old version to upgrade from.
minbar:root:~:2 # sympa.pl --upgrade notice main:: Sympa 6.2.56 Started notice main:: Upgrade process... Use of uninitialized value $options{"from"} in string eq at /usr/sbin/sympa.pl line 861. notice main:: Upgrading from to 6.2.56... Use of uninitialized value $v2 in split at /usr/lib64/sympa/Sympa/Upgrade.pm line 2215. Use of uninitialized value $tab2[0] in pattern match (m//) at /usr/lib64/sympa/Sympa/Upgrade.pm line 2228. Use of uninitialized value $tab2[0] in pattern match (m//) at /usr/lib64/sympa/Sympa/Upgrade.pm line 2230. Use of uninitialized value in string eq at /usr/lib64/sympa/Sympa/Upgrade.pm line 2234. Use of uninitialized value in numeric lt (<) at /usr/lib64/sympa/Sympa/Upgrade.pm line 2240. Use of uninitialized value $v1 in split at /usr/lib64/sympa/Sympa/Upgrade.pm line 2214. ...
It appears that what is missing is a step to initially populate the new, empty sympa database for the first time. Is this something that sympa.pl --upgrade or sympa.pl --health_check SHOULD be doing, but isn't? Or is there a step missing from the install documentation?
Either way, it appears the --upgrade option does not include any check for a valid "old" version and fails on an empty database.