The installation of Metwork 2.3 does not take into account the Metwork context/environment in the different Metwork accounts.

[FENGEvan]

During the Metwork installation/update:

I removed all existing packages: sudo yum remove metwork-*
I deleted all Metwork accounts with: userdel mfxxxx along with their folders.
I installed all Metwork modules and layers to version 2.3:
sudo yum -y install metwork-mfext-2.3
sudo yum -y install metwork-mfbase-2.3
sudo yum -y install metwork-mfdata-2.3
sudo yum -y install metwork-mfserv-2.3
sudo yum -y install metwork-mfext-layer-devtools-2.3
sudo yum -y install metwork-mfext-layer-scientific_core-2.3
sudo yum -y install metwork-mfext-layer-python3_scientific-2.3;
sudo yum -y install metwork-mfext-layer-python3_mapserverapi-2.3;
sudo yum -y install metwork-mfext-layer-python3_devtools-2.3;
sudo yum -y install metwork-mfext-layer-mapserver-2.3;
sudo yum -y install metwork-mfext-layer-python3_mapserverapi-2.3;
sudo yum -y install metwork-mfext-layer-nodejs-2.3;
sudo yum -y install metwork-mfext-layer-java-2.3

The mfxxx acounts is not recreated as before,

and in other possibility, i haven't deleted all Metwork accounts during installation,
Then restart and switch accounts with: sudo -u mfxxxx -i
and I cannot use Metwork commands automatically. as plugins.list; mfxxx.xxx etc
It does not create the default metwork environment

Please check here: d1245c1

[thebaptiste]

It seems that you forgot to install :

metwork-mfserv
metwork-mfdata
metwork-mfbase

(without the 2.3 suffix)

To install mfserv "from scratch", you must install metwork-mfserv (metwork-mfserv-2.3 is not enough) as explained in the documentation .
Same thing for mfdata, mfbase...

[FENGEvan]

[matthieumarrast]

I agree with @lionjohnFENG
Our system administrators installed today metwork v2.3 as they usually do, but for each module the module environment is not loaded:

[user@server~]$ su - mfdata
Dernière connexion : lundi 20 avril 2026 à 12:20:43 GMT sur pts/1
[mfdata@mgnnm31-sidev ~]$

[user@server ~]$ su - mfserv
Dernière connexion : lundi 20 avril 2026 à 11:35:27 GMT
[mfserv@mgnnm31-sidev ~]$

[user@server ~]$ su - mfbase
Dernière connexion : lundi 20 avril 2026 à 12:19:26 GMT sur pts/1
[mfbase@mgnnb31-sidev ~]$

The administrators did not change the way they update metwork. For me it's a regression.

[FENGEvan]

Actually, I configured the repository with metwork version 2.3, so whether I run sudo yum -y install metwork-mfdata-2.3 or sudo yum -y install metwork-mfdata, it's the same thing.
the issue is always presented

[thebaptiste]

Sorry but I can't reproduce

• I tried an install "from scratch" : yum install metwork-mfdata with release_2.3 in metwork.repo : it's ok
• I tried an install "from scratch" with release_2.2 in metwork.repo, then change to release 2.3 in metwork.repo and update : yum update metwork-mfdata : it's ok too
• I tried an install "from scratch" with release_2.2 in metwork.repo, then remove all metwork rpms, then change to release 2.3 in metwork.repo and yum install metwork-mfdata: it's ok too

So please explain to me what you (or your administrators) are doing and a way to reproduce the issue...

The install (or the update in case of installation of a new release) of the rpm metwork-mfdata (or metwork-mfserv or metwork-mfbase) has always been necessary for the mfdata (or mfserv or mfbase) environment to be loaded, nothing new I think with Metwork 2.3.

I think the only way to explain your problem would be to have metwork-mfdata-2.3 installed but metwork-mfdata not installed or from a previous install.

[thebaptiste]

On a correct install of mfdata 2.3 you should have, on /opt

lrwxrwxrwx 1 root root   23 Jan 13 16:14 metwork-mfdata -> /opt/metwork-mfdata-2.3
drwxr-xr-x 7 root root 4096 Apr 20 13:45 metwork-mfdata-2.3
drwxr-xr-x 7 root root 4096 Apr 20 13:45 metwork-mfext-2.3

If the link is missing or incorrect (not linking to /opt/metwork-mfdata-2.3), it can't work (the link is done by the install or the update of metwork-mfdata)