Unable to resolve service "symfony_cli" to a factory during update

[Pyr0technicien]

Hello,

i'm trying to update our version of monarc to the latest but i'm encoutering this error :

Any idea of what i'm doing wrong ?

[ruslanbaidan]

Hello,

Could you describe the steps you do to perform the update.

[Pyr0technicien]

I'm just changing the owner of all the folders : sudo chown -R myuser .
As the user of the folder is www-data, then i launch the update script :

./scripts/update-all.sh -c

[ruslanbaidan]

Could you try without the option "-c".

[Pyr0technicien]

I'm already using the option -c

[ruslanbaidan]

you can clear cache manually, could be an issue with permission as before the data was created by www-data.

[Pyr0technicien]

It goes a bit further but I'm still stuck at the end :

When I remove the cache & restart apache2, the main page is loading but as soon as i want to login with my user, it loads for ever and never logs me in.

These are the errors I get in my browser console :

[ruslanbaidan]

The error message on the screen don't provide any useful information.
It only tells that there is another argument was passed to the script that is not supported, but it supposed to be run without any arguments.

The login problems could be related to missing migrations. You can try to run upgrade-db.sh

Regarding error messages: we need browser console Response tab errors.

[ruslanbaidan]

Browser Network tab Response. Previously was written not correctly. With the red line in focus.

[ruslanbaidan]

There are no laminas commands run when you run the update-all.sh script without arguments.

[Pyr0technicien]

I run it with the arguments " -c " as mentionned ealier

[Pyr0technicien]

That's the last thing I can see

[ruslanbaidan]

It means you did not have any login issues.
If the Monarc UI is not loaded then the issue is another. Search for red line in the list.
Have you run "upgrade-db.sh" after pulling the repo (git pull) and reinstalling all the dependencies (composer ins) ?

[Pyr0technicien]

So I restored a backup and did the process all over again.
I'm having the same issue :

But then I'm allowed to login.
However the monarc version is still 2.11.1 so the update didn't complete

[ruslanbaidan]

Did you do "git pull" of the repository ?

[Pyr0technicien]

Git pull is up to date, the update script does it for me

[ruslanbaidan]

If you see the version 2.11.1 then it could fail.
you can "cat package.json" version is stored there.
If it is not 12.2.2 then there is an issue.

[Pyr0technicien]

@ruslanbaidan, Ok well your messages helped me a lot.
I restoreed my VM to a previous state and ran as follow :

Delete cache
Re-Create cache folder
change owner of all files
run : ./scripts/update-all.sh (no args)
Change back owner to www-data
restart apache2

So definitely the arg " -c " that was failing everything for some reason.

Now the version is correct v 2.12.2.

[ruslanbaidan]

Good news.
Hope Monarc works for you now ?

[ruslanbaidan]

I think the reason was with the permissions. Perhaps some directories or files did not have sufficient access to make "git pull", install dependencies and clean cache.

[Pyr0technicien]

Might have been the problem indeed, if that can maybe help someone :

The official guide says
"rm -Rf ./data/cache"

But this will erase the folder "cache" itself too, that will make the update script fail because the folder doesn't exist.

When you create that folder back, you need to be sure not to use sudo and you need to be sure to change the owner back to www-data after running the script.
I might have missed some steps everytime i ran it again. I ended up running the update script without "-c" argument so lamina stops failing.

I'm suprise the guide doesn't say anything about changing the owner of the folders before running the script, it would fail for me if I didn't change that. Also composer tells me I shouldn't run it as "sudo".

[ruslanbaidan]

The list of command to clean cache:

rm -rf ./data/cache/*
rm -rf ./data/DoctrineORMModule/Proxy/*
rm -rf ./data/LazyServices/Proxy/*

"composer ins -o --no-dev" should not be run with sudo, but the user should have write access to "vendor" and "bin" directories.

[Pyr0technicien]

Not sure where I was suppose to see all of this, I can't read anything about composer in the official documentation, therefore I never ran it.

I'm following the guide (literally has 3 command to update):
https://www.monarc.lu/documentation/technical-guide/#monarc-update

The script is failling if all the folders are owned by www-data (git error if I remember correctly)

[ruslanbaidan]

The steps are described in the installation guide,
including composer install. --no-dev is a preferred param to avoid installing dev dependencies.

The other approach with deleting and recreating of the cache directories defined in the ansible playbook.
Ansible is used to manage update for multiple clients.

[Pyr0technicien]

Well, hapiness was short, we can't connect to our instance anymore (only one account can).

For all other account we have the same issue as previously, when we click on connect, the loading ring never stops and we never get to enter monarc. no logs, nothing to be seen in the browser developer tools.

I performed the update-db.sh too but that doesn't solve the problem either. Any help would be appreciated as we are stuck here @ruslanbaidan

[ruslanbaidan]

What is the output of the git status command when you are in node_modules/ng_client and node_modules/ng_anr ?
If there is a tag or some branch, you need to execute git checkout master and git pull.

[Pyr0technicien]

No there is a waf in between but it's not caching anything. Also the issue is the same if we access directly monarc

[ruslanbaidan]

If the previous advise doesn't work, it would be better to reinstall the application.
To do this simply extract config from config/autoload/local.php somewhere, install the app and copy the config back.
Can be created a copy of the whole Monarc application folder before.
You only need to follow point 2.1
https://github.com/monarc-project/MonarcAppFO/blob/master/INSTALL/INSTALL.ubuntu1804.md#21-monarc-source-code

[Pyr0technicien]

Thanks for the time you spent with me on this.

I rolled back to 2.11 with our backup. We were assessing the need of keeping monarc on prem, we are going to decide if we go for the SAS option, if that's the case I won't need to update the application anymore.

Thanks anyway

[ruslanbaidan]

Welcome.
The new installation normally takes 15 - 20 minutes. You don't need to configure the db, make any other system packages installation. The step 2.1 includes only the repos cloning, installing the dependencies (execute update-all.sh) creation of the data cache folders and the config copy from the current app.
So it's faster than downgrade and on some servers we perform upgrade by creating a new Monarc folder and just switching symlinks (the same what was suggested to you).