I've encountered the same (or at least similar) problem as reported by
@xar123 above. Several of my servers failed the update:
Code:
*** An error has occurred while trying to update the software ***
This is an automated message notifying you that an error has occurred while trying to update the software.
v1.63.8 (1487dff) to v1.63.9 (3ed9f35)
The generated error message is as follows:
exit status 127
Please contact JBMC-Software, including the error message. Failure to do so could result in an inactive control panel.
When logging into DA as
admin, using the Evolution skin, I get this message:
Code:
OOPS!
Privileges needed to load the skin have not been granted for this account or unexpected issue has happened. Please contact your administrator.
If
admin is using the enhanced skin, it works fine.
Running the
update.sh script as suggsted by
@fln doesn't reveal anything suspect, and exits cleanly (exit code 0):
Code:
# bash -x /usr/local/directadmin/scripts/update.sh
+ set -e
+ DA_PATH=/usr/local/directadmin
+ DA_SCRIPTS=/usr/local/directadmin/scripts
+ DA_TQ=/usr/local/directadmin/data/task.queue
+ DA_SYSTEMD_SERVICE=/etc/systemd/system/directadmin.service
+ '[' -s /etc/systemd/system/directadmin.service ']'
+ diff --brief /usr/local/directadmin/scripts/directadmin.service /etc/systemd/system/directadmin.service
+ diff --brief /usr/local/directadmin/scripts/directadmin_cron /etc/cron.d/directadmin_cron
+ '[' -e /etc/logrotate.d ']'
+ diff --brief /usr/local/directadmin/scripts/directadmin.rotate /etc/logrotate.d/directadmin
+ /usr/local/directadmin/directadmin p
+ echo 'action=cache&value=showallusers'
+ echo 'action=cache&value=safemode'
+ echo 'action=convert&value=cronbackups'
+ echo 'action=convert&value=suspendedmysql'
+ echo action=syscheck
+ echo 'action=da-popb4smtp&value=restart'
+ echo 'action=rewrite&value=cron_path'
+ '[' -e /etc/csf/csf.allow ']'
+ '[' -x /usr/sbin/csf ']'
+ grep -q 'out|u=0' /etc/csf/csf.allow
+ csf -a 'tcp|out|u=0' 'Added by DirectAdmin'
Adding tcp|out|u=0 to csf.allow and iptables ACCEPT...
ACCEPT tcp opt -- in * out !lo 0.0.0.0/0 -> 0.0.0.0/0 owner UID match 0
+ csf -a 'udp|out|u=0' 'Added by DirectAdmin'
Adding udp|out|u=0 to csf.allow and iptables ACCEPT...
ACCEPT udp opt -- in * out !lo 0.0.0.0/0 -> 0.0.0.0/0 owner UID match 0
+ sed -i '/^directadmin=/d' /usr/local/directadmin/data/admin/services.status
After running this, Evolution still does not work.
I tried a simple
service directadmin restart, and Evolution now loads as expected. Which I must admit was a little.. unexpected.
The only relevant log lines I found are the following lines in
errortaskq.log around the same time I got the email/message about the failed upgrade:
Code:
2022:04:20-07:30:09: [error] unable to update directadmin action=map[action:[update] value:[program]] error=exit status 127
2022:04:20-07:31:01: Error getting user 'admin' domain config file for domain (null)
I also tried to restart directadmin (without running the
update.sh script first) on another server with the same problem, and Evolution now works there as well. (
Edit: Before the restart, on a third server, I noticed that the currently running version was the old one, so the restart is what caused the new version to become active. I guess this means either the restart itself failed, or something prior to the restart failed, causing the update procedure to stop?)
Also worth noting that both these servers were in fact upgraded to
1.63.9 (build 3ed9f3550d66d4892344764e6523fc474ac78fa8). One is Debian 9, the other is Debian 10.
Is there any way I can find out what caused the
exit 127, and fix it for next time, and/or re-run that operation now?
. This release adds support for 
.
