guam (0.9.4) crash after update

JP Horst | ScienceBridge jphorst at sciencebridge.de
Wed Jul 18 16:46:04 CEST 2018


Hi Christoph,

indeed which is not a word but the command in that error message...
It is a separate package in CentOS.

 yum install which

solves the problem.

This package should probably be added to the requirements of the guam package.

Thank you for your help.
JP


Am Mittwoch, 18. Juli 2018, 12:53:45 CEST schrieb Christoph Erhardt:
> Hi JP,
> 
> this is interesting... it looks like the "which" binary is missing on your 
> system. I used to assume "which" was either a shell builtin or part of the 
> coreutils package - but apparently it's a separate project shipped in its own 
> package.
> 
> Could you check if the "which" package is indeed missing on your system? If 
> so, please try installing it and see if that fixes your problem.
> 
> Best regards,
> Christoph
> 
> On Wednesday, 18 July 2018 10:40:55 CEST JP Horst wrote:
> > After updating Kolab16 (on Centos7) yesterday and again this morning.
> > IMAP is not accessible presumably because guam doesn't start due to a
> > crash.
> > 
> > In messages ist says:
> > guam: /usr/lib64/erlang/lib/kolab_guam-0.9.4/bin/guam: line 25: which:
> > command not found
> > 
> > Using the new /etc/guam/sys.config or rerunning setup-kolab guam does
> > not change this.
> > 
> > Does anyone know how to solve this problem?
> > 
> > Thanx
> > JP
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> 
> 




More information about the users mailing list