After logging in it freezes

[mike1]

Hi,

I did the installation in windows 10 and after verifying that it worked I migrated it to windows server. The installed versions and procedure has been the same

But on the windows server once you start the session it freezes.

Anyone know what can it be?I do not see errors in the console of chrome, and during the installation

Screenshot

thanks

[justinz]

I get this too, but on Fedora 34 Linux. This is just after installing a development instance. I finished all the admin tasks (clone, install-cli.php, test install, create database, install applications, setup users, setup header, etc), and this after first login.
Here’s a photo of Firefox console:

[RalfBecker]

You’re using the master branch, where we’re working on modernizing our JavaScript loading and eventually replacing jQuery(UI).

Do NOT use master for production, at least not currently!

Use ./install-cli.php 21.1 to switch to our stable release. Unfortunately that will give conflicts with the generated .min.* files, which you have to deal with (eg. by deleting them bevor running install-cli.php).

Ralf

[justinz]

./install-cli.php 21.1

Thank you! That worked great. I cleaned up the .min. files with:
egroupware]# find . -name *.min.* -exec rm -f {} \;

Then ran:
egroupware]# ./install-cli.php 21.1

I got some errors, but i don’t know if they’re benign or serious. But so far the interface seems to be working fine! . If you think these errors might cause problems, can you suggest corrective steps? Do I then just run the install-cli.php command again afterward?

egroupware]# ./install-cli.php 21.1
Updating to: 21.1
Switched to a new branch '21.1'
Branch '21.1' set up to track remote branch '21.1' from 'origin'.
Already up to date.
Removing pixelegg/theme/supersized.shutter.min.js
Auto-merging package-lock.json
CONFLICT (content): Merge conflict in package-lock.json
Removing api/js/offline/offline.min.js
Removing api/js/jquery/blueimp/js/jquery.blueimp-gallery.min.js
Removing api/js/jquery/blueimp/js/blueimp-gallery.min.js
Removing api/js/jquery/blueimp/css/blueimp-gallery.min.css
Removing api/js/jquery/barcode/jquery-barcode.min.js
Removing api/js/es6-promise.min.js
The stash entry is kept in case you need it again.
activesync: Switched to a new branch '21.1'
Branch '21.1' set up to track remote branch '21.1' from 'origin'.
Already up to date.
bookmarks: Switched to a new branch '21.1'

... <snip> ...

In PearRepository.php line 30:

  The PEAR repository has been removed from Composer 2.0


npm WARN conflict A git conflict was detected in package-lock.json. Attempting to auto-resolve.
npm WARN conflict To make this happen automatically on git rebase/merge, consider using the npm-merge-driver:
npm WARN conflict $ npx npm-merge-driver install -g
added 111 packages from 47 contributors, removed 202 packages, updated 26 packages and audited 232 packages in 7.955s

6 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Loading "terser.js" tasks...ERROR
>> Error: Cannot find module '/var/www/egroupware/node_modules/terser/dist/bundle.min.js'. Please verify that the package.json has a valid "main" entry

Running "newer:terser" (newer) task

Running "newer:terser:api" (newer) task
Fatal error: Task "terser:api" not found.
npm ERR! missing script: build

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-07-30T12_04_27_042Z-debug.log

14 tasks successful run, 6 failed: egroupware, phpbrain, phpgwapi, composer, grunt, rollup (npm run build)

[RalfBecker]

Because of the dropped Pear repository support (we require for Horde IMAP code), you need to use the latest version 1 eg. run:

composer selfupdate 1.10.22

And again ./install-cli.php

Ralf

[justinz]

Yeah, I saw that early on and had switched from version 2.x to 1x with:
composer self-update --1
So I was already on version 1.10.22, 2021-04-27

[RalfBecker]

You are saying you fixed your problem yourself and forgot to post your solution here?

Ralf

[justinz]

No. When I started down the road of installing via cloning and install-cli.php – when I ran install-cli.php the first time I saw lots of errors. Notably, at the end of the script I got:
4 tasks successful run, 1 failed: composer
This said to me that composer was not working. The instructions include an alternate method:
composer install
So I ran that and got a very familiar message:
The PEAR repository has been removed from Composer 2.0 "revert" 1.x ...
(Actually, that message was in the output log of of install-cli.php – shame on me for missing it the first time!!)
So i downgraded to composer 1.x and then re-ran install-cli.php. (I didn’t notice if development instructions say that this method relies on PEAR and that composer needs to be at 1.x for compatibility, I just saw the errors and drew conclusions.)
So despite the remaining errors I tried loading the login page and got the frozen icons-loading page similar to mike1’s post. So I posted a “me too” with a screenshot of Firefox console.
This takes me to your suggestion to downgrade composer. I had already done that in order to get a partially-working system.
So it seems like I could start over and clone the stable branch from the start, rather than master. That seems like a good exercise. I’ll do that and report back. BTW, mike1 doesn’t say what his install method was, and I’m curious if he’s on master too.

[RalfBecker]

Two different problems:

• JS errors with chunks --> use 21.1 branch instead of master
• composer 2 error not supporting PEAR repos --> use composer version 1

Ralf

[justinz]

Ralph,

Hmmm… yeah, there it is again. I had originally installed composer via yum, then:

# which composer
/usr/local/bin/composer

# composer --version
Composer version 1.10.22 2021-04-27 13:10:45

But if I look for all the composer binaries, as below, I see several are installed in egroupware/vendor/… When I run the one in vendor/sebastian/type/tools/composer is see that it’s 2.0.2.

# /var/www/egroupware/vendor/sebastian/type/tools/composer --version
Composer version 2.0.2 2020-10-25 23:03:59

More importantly, the one called in install-cli.php is /usr/bin/composer, which turns out is also 2.x

$bins = array(
        'composer' => ['/usr/bin/composer', '/usr/bin/composer.phar'],

So I symlinked that to /usr/local/bin/composer. No more “PEAR repository has been removed from Composer 2.0” error, but I still get some others, so I’ll go back to beginning again. (Tho I now have a running system, I’d like to close the loop here and give you feedback on what exactly tripped me up.)

Thanks again!

All composer binaries:

# find / -name composer -exec file {} \;

find: ‘/run/user/1000/gvfs’: Permission denied
/root/.cache/composer: directory
/root/.config/composer: directory
/root/.local/share/composer: directory
/usr/bin/composer: Ruby script, ASCII text
/usr/local/bin/composer: a /usr/bin/env php script executable (binary data)
/usr/share/doc/composer: directory
/usr/share/licenses/composer: directory
/usr/share/composer: directory
/var/www/egroupware/vendor/composer: directory
/var/www/egroupware/vendor/egroupware/z-push-dev/src/vendor/composer: directory
/var/www/egroupware/vendor/sebastian/type/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/recursion-context/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/object-reflector/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/object-enumerator/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/global-state/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/exporter/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/environment/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/diff/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/comparator/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/code-unit/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/cli-parser/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/lines-of-code/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/complexity/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/sebastian/code-unit-reverse-lookup/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/phpunit/php-timer/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/phpunit/php-text-template/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/phpunit/php-invoker/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/phpunit/php-file-iterator/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/phpunit/php-code-coverage/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/vendor/phpunit/phpunit/tools/composer: a /usr/bin/env php script executable (binary data)
/var/www/egroupware/swoolepush/vendor/composer: directory

[justinz]

Hi,
I reinstalled from the beginning (Fedora 34 linux), using the Development instructions, and I got the freeze behavior on login (Firefox, Chrome, Opera). However after rebooting, this cleared up.

Below is a pic of the console when the login froze.

I used: ./install-cli.php 21.1 and tho I got some errors for missing php extentions, the script finished with:

npm ERR! missing script: build

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-07-29T21_13_46_852Z-debug.log

3 tasks successful run, 2 failed: composer, rollup (npm run build)

It says composer failed, but there were no composer errors in the script output or debug log. Just this:
4 verbose stack Error: missing script: build

I installed the missing PHP modules, and re-ran install-cli.php again. No errors, it downloaded all the eGroupware modules and dependencies, and setup went fine.
Thank you!

Here’s a screenshot of FF console:

[justinz]

I setup another EGW instance on Windows10, PHP 7.4, Apache 2.4.46 w/ all needed extensions including OPcache, and Cygwin for composer, grunt, nodejs (is node called only during install-cli.php?). The entire install went well, but I got the same freeze situation after user login, with the exact same errors as above (I got past the Security Policy, which is due to self-signed cert). After a few hours of debugging, I didn’t find a solution.
It seems to be a problem with how JQuery is loaded. Could it be due to minified JS? I see a few posts here–spanning the years–that seem similar.

[justinz]

This instance started working after I cleared all the .min. files and re-ran ./install-cli.php 21.1 - Yay! (although it’s missing the pixelegg/images/dhtmlxtree graphic, even after entering host information in setup)

The last hurtle is getting CalDAV and CardDav sync (android) working. I’m piecing together the needed rewrites for .htaccess and apache via the current nginx.conf, the Jan’18 doc/rpm-build/apache.conf, and a few old posts.