|Summary:||mail/openwebmail logins fail with "Set effective gid to mail(6) failed!"|
|Product:||Ports & Packages||Reporter:||William F. Dudley Jr. <wfdudley>|
|Component:||Individual Port(s)||Assignee:||Chris Rees <crees>|
|Status:||Closed Overcome By Events|
|Severity:||Affects Many People|
Description William F. Dudley Jr. 2019-11-18 04:35:16 UTC
Attempting to login to openwebmail returns error message: Set effective gid to mail(6) failed! I have three machines, all have this behaviour since about 3 months ago. In all cases, machines are running 11.3-RELEASE Machine 'a' is running 11.3 32 bit (on 64 bit hardware). Publicly accessible as mail.casano.com. 11.3-RELEASE-p3 kernel, p4 userland Machine 'b' is running 11.3 64 bit. 11.3-RELEASE-p3 kernel, p4 userland Machine 'c' is a VM I built 20 minutes ago. It runs 11.3 64 bit on an Ubuntu Linux host. That machine has only the minimum installed on it to test openwebmail: apache24 openwebmail p5-CGI p5-HTML-Parser p5-HTML-Tagset P5-Text-Iconv perl5-5.30.0 and whatever else was dragged in by installing that stuff. That machine has not been updated using freebsd-update. It is running the vm image as distributed from freebsd.org. To replicate the bug: fresh 11.3-RELEASE install pkg install apache24 pkg install openwebmail configure apache24 so cgi works; change default cgi-bin directory to /usr/local/www/cgi-bin (from default /usr/local/www/apache24/cgi-bin) user adduser to create one or more user accounts. open web browser to the openwebmail login page attempt to login one of the user accounts.
Comment 1 William F. Dudley Jr. 2019-11-19 23:26:52 UTC
2019 11 19: I just repeated the experiment using 12.1-RELEASE running in a VM. Fresh install, with just apache24 and openwebmail and two (empty) user accounts. Exact same failure as with 11.3-RELEASE.
Comment 2 Chris Rees 2019-11-20 11:20:02 UTC
I'll take a look.
Comment 3 William F. Dudley Jr. 2019-12-19 04:24:58 UTC
A normal pkg upgrade moved perl5 from perl5-5.30.0 to perl5-5.30.1, and now openwebmail works normally. This is on my "production" system, which is running the i386 FreeBSD. The 5.30.1 upgrade hasn't been rolled out to 64 bit (amd64) versions yet, so both my 64 bit system on real hardware, and my 64 bit system in a VM are still broken. This is obviously a problem with Perl, so I guess it should be passed on to the Perl guys, and hopefully they'll get the lead out and issue the 64bit package for perl5-5.30.1
Comment 4 Chris Rees 2020-01-05 19:25:09 UTC
Not a problem with new Perl version.