Discussion:
guam (0.9.4) crash after update
JP Horst
2018-07-18 08:40:55 UTC
Permalink
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
Christoph Erhardt
2018-07-18 10:53:45 UTC
Permalink
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
Post by JP Horst
After updating Kolab16 (on Centos7) yesterday and again this morning.
IMAP is not accessible presumably because guam doesn't start due to a
crash.
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
https://lists.kolab.org/mailman/listinfo/users
JP Horst | ScienceBridge
2018-07-18 14:46:04 UTC
Permalink
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
Post by 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
Post by JP Horst
After updating Kolab16 (on Centos7) yesterday and again this morning.
IMAP is not accessible presumably because guam doesn't start due to a
crash.
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
https://lists.kolab.org/mailman/listinfo/users
Christoph Erhardt
2018-07-18 15:07:52 UTC
Permalink
Done. You should see an update shortly.

Best regards,
Christoph
Post by JP Horst | ScienceBridge
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
Loading...