CustomBuild 2.0 stuck

W

warg

Verified User
Joined
Nov 30, 2020
Messages
183
Hello,

I tried to update Let's Encrypt. During the update process the download and installation of the new version was stuck. After refreshing the page, I got told that there's a build process running and that I can view it's log. After viewing the log, I saw an updated log where the install was fine. Then I tried to update Custombuild via the UI but I got this:

  • Executing /usr/local/directadmin/plugins/custombuild/admin/build update...
  • --2021-02-27 00:15:10-- https://files-de.directadmin.com/services/custombuild/2.0/custombuild.tar.gz
  • Resolving files-de.directadmin.com (files-de.directadmin.com)... [ips removed]
  • Connecting to files-de.directadmin.com (files-de.directadmin.com) [ips removed]... connected.
  • HTTP request sent, awaiting response... 200 OK
  • Length: 260014 (254K) [application/octet-stream]
  • Saving to: './custombuild.tar.gz'
  • 0K .......... .......... .......... .......... .......... 19% 7.77M 0s
  • 50K .......... .......... .......... .......... .......... 39% 2.58M 0s
  • 100K .......... .......... .......... .......... .......... 59% 118M 0s
  • 150K .......... .......... .......... .......... .......... 78% 167M 0s
  • 200K .......... .......... .......... .......... .......... 98% 83.8M 0s
  • 250K ... 100% 7477G=0.03s
  • 2021-02-27 00:15:10 (9.37 MB/s) - './custombuild.tar.gz' saved [260014/260014]
  • Extracting custombuild.tar.gz...
  • Done!
Click to expand...

As you can see, it is stuck at extracting but says it's done. No install was done. I think I somehow got into a state where CustomBuild is finally stuck. This was caused by a bad system performance I think (network or IO wise). When I try to close the CustomBuild dialog, it won't work and I have 2 overlapping CustomBuild dialogs.

This happens on Debian 10 for the first time and I suspect it's a timeout/bad performance issue in combination with CustomBuild v2.0 rev2670.

I will take a look at the logs to see if there's something of interest.

Best Regards,
 
This might be related to this issue:

2021:02:27-00:06:24: [error] proxy request error error=context canceled url=http://unix/CMD_WIDGET?json=yes
2021:02:27-00:06:24: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:06:25: [error] proxy request error error=context canceled url=http://unix/assets/img/favicon.png
2021:02:27-00:07:34: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:07:34: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:07:34: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:07:35: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:07:35: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:07:37: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the p$
2021:02:27-00:10:11: File ./data/users/admin/user.usage has been written to after this process read it. Not going to overwrite it.
2021:02:27-00:10:11: File ./data/users/admin/reseller.usage has been written to after this process read it. Not going to overwrite it.
2021:02:27-00:10:11: ConfigFile::writeFile(./data/users/admin/reseller.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:11: File ./data/admin/admin.usage has been written to after this process read it. Not going to overwrite it.
2021:02:27-00:10:11: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:12: File ./data/users/admin/user.usage has been written to after this process read it. Not going to overwrite it.
2021:02:27-00:10:12: File ./data/users/admin/reseller.usage has been written to after this process read it. Not going to overwrite it.
2021:02:27-00:10:12: ConfigFile::writeFile(./data/users/admin/reseller.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:12: File ./data/admin/admin.usage has been written to after this process read it. Not going to overwrite it.
2021:02:27-00:10:12: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:23: ConfigFile::writeFile(./data/users/admin/reseller.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:23: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:23: ConfigFile::writeFile(./data/users/admin/reseller.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:23: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:24: ConfigFile::writeFile(./data/users/admin/reseller.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:24: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:24: ConfigFile::writeFile(./data/users/admin/reseller.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:10:24: ConfigFile::writeFile(./data/admin/admin.allocation) : Timestamp from when it was read is different, overwriting anyway
2021:02:27-00:13:26: [error] proxy request error error=context canceled url=http://unix/CMD_PLUGINS_ADMIN/custombuild/vue/admin.js
Click to expand...
 
Updating only CustomBuild 2.0 causes this:

  • Executing /usr/local/directadmin/plugins/custombuild/admin/build update_script...
  • --2021-02-27 00:27:30-- https://files-de.directadmin.com/services/custombuild/2.0/custombuild.tar.gz
  • Resolving files-de.directadmin.com (files-de.directadmin.com)... ...
  • Connecting to files-de.directadmin.com (files-de.directadmin.com)|...... connected.
  • HTTP request sent, awaiting response... 200 OK
  • Length: 260014 (254K) [application/octet-stream]
  • Saving to: './custombuild.tar.gz'
  • 0K .......... .......... .......... .......... .......... 19% 6.62M 0s
  • 50K .......... .......... .......... .......... .......... 39% 6.95M 0s
  • 100K .......... .......... .......... .......... .......... 59% 134M 0s
  • 150K .......... .......... .......... .......... .......... 78% 8.11M 0s
  • 200K .......... .......... .......... .......... .......... 98% 33.3M 0s
  • 250K ... 100% 7477G=0.02s
  • 2021-02-27 00:27:30 (11.1 MB/s) - './custombuild.tar.gz' saved [260014/260014]
  • 0K .......... .......... .......... .......... .......... 19% 8.13M 0s
  • 50K .......... .......... .......... .......... .......... 39% 3.69M 0s
  • 100K .......... .......... .......... .......... .......... 59% 2.34M 0s
  • 150K .......... .......... .......... .......... .......... 78% 213M 0s
  • 200K .......... .......... .......... .......... .......... 98% 2.53M 0s
  • 250K ... 100% 7477G=0.06s
  • 2021-02-27 00:27:30 (4.16 MB/s) - './custombuild.tar.gz' saved [260014/260014]
  • Extracting custombuild.tar.gz...
  • mv: cannot stat 'options.conf': No such file or directory
Click to expand...
 
Is it easy to reproduce that "hanging" issue? I'd like to check it there (if possible) :)
 
Yes, just try to update Custombuild itself or check for updates for both (managed software + CustomBuild). I can send you access details via private message for the server. Right now, there's nothing private on it.
 
I just updated my local pre-release binaries and made a full config rewrite. Look like it's not stuck/broken anymore. I will watch this out further.
 
Good evening,

We are experiencing this same issue with our DirectAdmin instance. The logs posted earlier by @warg in post #1 and #3 of this thread appear to be the same as the ones we have when performing the same tasks. Are you experiencing the issues since your attempted fix yesterday @warg? If so, is it possible to share the steps you performed to fix the issue?

Thanks in advance!
 
So far it looks good again but I got no update yet to verify it @12128489canadainc. Go to the customer portal, select your license and then click on the link to download the pre-release binaries. I did download/update them + did the full config rewrites at the end of the page. This did help. On a productive system, I wouldn't try this.
 
I just updated CustomBuild, phpMyAdmin and dovecot. It worked flawless. So yep, seems like it's fixed.
 
You must log in or register to reply here.
Back
Top