EDB Advanced Server compatibilites

[dirkkrautschick-edb]

Hi,

should pgbasenv also be capable to scan EDB Advanced Server installations including clusters as well?
As far I could test it doesn't find a EPAS Home at all (installed for e.g. Red Hat derivates at /usr/edb/as14 for version 14).
A created cluster was found by the installation but it somehow doesn't recognized the full status.

LAST_START_HOME and LAST_START will be shown in pgup but the cluster isn't marked a running with STAT=UP, PID, PORT etc.
Maybe it is because there are wrappers or symlinks called like edb-postmaster as a starting process.

Thanks and best regards

Dirk

[rolandstirnimann]

Hi Dirk, could you already test it with the change from @mmuehlbeyer? Download bin/pgup.sh from the master branch to your VM. If there are still issues we will look into that again. Thank you.
Regards
Roli

[dirkkrautschick-edb]

Hi Roland,

that solves the problem getting the status of the existing cluster. So that one is solved. But at least in my environment it still do not find the HOME. Actually I haven't found the point in the source yet where and how you scan the folders for the home directories.

Cheers

Dirk

[rolandstirnimann]

Hi Dirk, can you provide me an EDB installation or the source resp. access to the yum repo? If yes, I will fix it.
Cheers Roli

[dirkkrautschick-edb]

Hi Roli, didn't you have an own access key to the EDB repo? Or is not not available anymore? Cheers Dirk

…

On 23.03.23 13:37, Roland Stirnimann wrote: Hi Dirk, can you provide me an EDB installation or the source resp. access to the yum repo? If yes, I will fix it. Cheers Roli — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A26BNMHGXW2O3VY7A6MF6MLW5Q7ZVANCNFSM6AAAAAASH6MLVQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dirkkrautschick-edb]

Hi Roli, with v2.2 it didn't find my EPAS homes and I do not know why..... [Mi Apr 12 23:31:24 ***@***.*** ~ pgd15G]# pgup pgBasEnv v2.2 by Trivadis AG Installation homes: ┌────────┬─────────┬─────────────────┬───────────────┐ │ALIAS   │     VER │         OPTIONS │ HOME DIR      │ ├────────┼─────────┼─────────────────┼───────────────┤ │pgh1214 │   12.14 │ ssl:1G:8K │ /usr/pgsql-12 │ │pgh1310 │   13.10 │ ssl:1G:8K │ /usr/pgsql-13 │ │pgh9624 │  9.6.24 │ ssl:1G:8K │ /usr/pgsql-9.6│ │pgh1119 │   11.19 │ ssl:1G:8K │ /usr/pgsql-11 │ │pgh1023 │   10.23 │ ssl:1G:8K │ /usr/pgsql-10 │ │pgh147  │    14.7 │ ssl:1G:8K │ /usr/pgsql-14 │ │pgh152  │    15.2 │ ssl:1G:8K │ /usr/pgsql-15 │ └────────┴─────────┴─────────────────┴───────────────┘ Cluster data directories: ┌───────┬───────┬──────┬───────┬─────────┬───────┬─────────────────────────────────┬──────────────────┬────────────────┐ │ALIAS  │   VER │ STAT │  PORT │     PID │  SIZE │ PGDATA                          │       LAST START │ LAST START HOME│ ├───────┼───────┼──────┼───────┼─────────┼───────┼─────────────────────────────────┼──────────────────┼────────────────┤ │pgd14G │    14 │   UP │  5444 │    8218 │  2,2G │ /u00/edb/14/data                │ 2023-04-12 11:27 │ /usr/edb/as14  │ │pgd14F │    14 │   UP │  5445 │    8223 │   92M │ /u00/edb/14/data_redwood        │ 2023-04-12 11:27 │ /usr/edb/as14  │ │pgd15G │    15 │   UP │  5446 │    8204 │  1,1G │ /u00/edb/15/data                │ 2023-04-12 11:27 │ /usr/edb/as15  │ │pgd15F │    15 │ DOWN │       │         │   87M │ /u00/edb/15/data_redwood        │ │                │ │pgd10  │    10 │ DOWN │       │         │  2,2G │ /u00/postgres/10/data           │ 2022-05-24 15:34 │ /usr/pgsql-10  │ │pgd11  │    11 │ DOWN │       │         │   39M │ /u00/postgres/11/data           │ │                │ │pgd12  │    12 │ DOWN │       │         │   40M │ /u00/postgres/12/data           │ │                │ │pgd13  │    13 │ DOWN │       │         │  122M │ /u00/postgres/13/data           │ 2023-04-12 11:27 │ /usr/pgsql-13  │ │pgd14A │    14 │   UP │ 50140 │    8229 │  755M │ /u00/postgres/14/data           │ 2023-04-12 11:27 │ /usr/pgsql-14  │ │pgd14B │    14 │ DOWN │       │         │   42M │ /u00/postgres/14/data_efm       │ │                │ │pgd14E │    14 │ DOWN │       │         │   42M │ /u00/postgres/14/data_patroni   │ 2022-10-22 17:16 │ /usr/pgsql-14  │ │pgd14D │    14 │ DOWN │       │         │   87M │ /u00/postgres/14/data_pglogical │ 2022-10-22 17:16 │ /usr/pgsql-14  │ │pgd14C │    14 │ DOWN │       │         │  122M │ /u00/postgres/14/data_pgoperate │ 2022-10-22 17:16 │ /usr/pgsql-14  │ │pgd14  │    14 │ DOWN │       │         │  1,4G │ /u00/postgres/14/data_repmgr    │ 2023-02-27 22:43 │ /usr/pgsql-14  │ │pgd15A │    15 │   UP │ 50150 │    8234 │  2,7G │ /u00/postgres/15/data           │ 2023-04-12 11:27 │ /usr/pgsql-15  │ │pgd15B │    15 │ DOWN │       │         │   39M │ /u00/postgres/15/data_efm       │ │                │ │pgd15E │    15 │   UP │ 50152 │    1998 │  324M │ /u00/postgres/15/data_patroni   │ 2023-04-12 11:25 │ /usr/pgsql-15  │ │pgd15D │    15 │ DOWN │       │         │   39M │ /u00/postgres/15/data_pglogical │ │                │ │pgd15C │    15 │ DOWN │       │         │   39M │ /u00/postgres/15/data_pgoperate │ │                │ │pgd15  │    15 │   UP │ 50151 │    8225 │  245M │ /u00/postgres/15/data_repmgr    │ 2023-04-12 11:27 │ /usr/pgsql-15  │ │pgd96  │   9.6 │ DOWN │       │         │   38M │ /u00/postgres/9.6/data          │ │                │ └───────┴───────┴──────┴───────┴─────────┴───────┴─────────────────────────────────┴──────────────────┴────────────────┘ [Do Apr 13 16:06:56 ***@***.*** ~ pgd15G]# I have two EPAS versions (14,15) installed. The Cluster Homes are found and located correctly, it is only the install homes which are not working (not a bad thing but still weird) The installations are located here [Do Apr 13 16:10:08 ***@***.*** /usr/edb pgd15G]# pwd /usr/edb [Do Apr 13 16:10:14 ***@***.*** /usr/edb pgd15G]# ls -alh total 4,0K drwxr-xr-x.  7 root root   70 31. Mär 15:45 . drwxr-xr-x. 22 root root 4,0K 13. Okt 16:42 .. *drwxr-xr-x.  6 root root  127 23. Feb 12:24 as14** **drwxr-xr-x.  6 root root  127 12. Apr 11:13 as15* drwxr-xr-x.  5 root root   41 22. Nov 02:36 efm-4.5 drwxr-xr-x.  5 root root   71  5. Okt 2022  llvm-9 drwxr-xr-x.  3 root root   52 31. Mär 16:53 pem [Do Apr 13 16:10:17 ***@***.*** /usr/edb pgd15G]# Cheers Dirk

…

On 27.03.23 16:43, Dirk Krautschick wrote: Hi Roli, didn't you have an own access key to the EDB repo? Or is not not available anymore? Cheers Dirk On 23.03.23 13:37, Roland Stirnimann wrote: > > Hi Dirk, can you provide me an EDB installation or the source resp. > access to the yum repo? If yes, I will fix it. > Cheers Roli > > — > Reply to this email directly, view it on GitHub > <#13 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A26BNMHGXW2O3VY7A6MF6MLW5Q7ZVANCNFSM6AAAAAASH6MLVQ>. > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[rolandstirnimann]

Hi Dirk, I did some tests and found the reason for the behavior. I installed EDBAS on a new VM (only EDB no community PostgreSQL). The it works without any problems.

[opc@lpg02 ~]$ sudo su - enterprisedb
Last login: Fri Apr 21 12:11:04 GMT 2023 on pts/1

pgBasEnv v2.2 by Trivadis AG

Installation homes:
┌────────┬─────────┬─────────────────┬──────────────┐
│ALIAS   │     VER │         OPTIONS │ HOME DIR     │
├────────┼─────────┼─────────────────┼──────────────┤
│pgh1520 │  15.2.0 │       ssl:1G:8K │ /usr/edb/as15│
└────────┴─────────┴─────────────────┴──────────────┘

Cluster data directories:
┌──────┬───────┬──────┬───────┬─────────┬───────┬────────────────────────┬──────────────────┬────────────────┐
│ALIAS │   VER │ STAT │  PORT │     PID │  SIZE │ PGDATA                 │       LAST START │ LAST START HOME│
├──────┼───────┼──────┼───────┼─────────┼───────┼────────────────────────┼──────────────────┼────────────────┤
│pgd15 │    15 │   UP │  5444 │  165411 │   88M │ /var/lib/edb/as15/data │ 2023-04-21 11:36 │ /usr/edb/as15  │
└──────┴───────┴──────┴───────┴─────────┴───────┴────────────────────────┴──────────────────┴────────────────┘


---[pgd15]:

         Installation home: /usr/edb/as15
    Cluster data directory: /var/lib/edb/as15/data
              Cluster port: 5444
            Cluster status: UP
           Cluster version: 15
        Cluster start time: 2023-04-21 11:36
   Size of all tablespaces: 56MB
      Cluster archive mode: off
               Cluster age: 9
         Autovacuum status: ACTIVE
         Cluster databases: postgres,edb,template1,template0

---[21.04.2023 12:11]

lpg02:/var/lib/edb [pgd15]$

Once you have EDB and community PostgreSQL on the same VM installed it depends if your OS users postgres and enterprisedb can read the PGDATA of each other. If yes, the tool does not work properly. Our current cluster home and cluster instance detection behaves not consistent.

• The home detection (pghometab) distinguishes between the two users resp. the homes and detects only homes that belong to the currently logged on user. Therefore, you see in your output above only homes from community PostgreSQL since you are logged in with postgres user.
• The cluster instance detection on the other hand does currently not distinguish between the two OS users resp. EDB and community. If the two users can read each others PGDATA the tool shows you the clusters for both users. In my case, where the two users have no permission to each others PGDATA it works since the cluster instance detection cannot look into PGDATA.

My proposal
I change the pgBasEnv detection the way that it behaves consistent. This means, it display you only the clusters and homes belonging to the current user you are logged in. Furthermore, with enterprisedb user you see only EDB homes and instances and with postgres community user you see only homes and instances belonging to it.
Does that make sense for you?

I think we should not display homes and clusters from other vendors resp. OS users since you can anyway not use it properly.

[rolandstirnimann]

@dirkkrautschick-edb, small update. I implemented the fix that only clusters of the same user are detected. Please download the latest pgbasenv.sh and test it.
If you have v2.2 installed please execute pgbasenv --clean-pgclustertab or just delete $PGBASENV_BASE/etc/pgclustertab and re-login. Then you should see with postgres user only the community stuff and with enterprisedb user only the EDBAS stuff.

[dirkkrautschick-edb]

Hi Roli, I basically use the postgres user for all HOMEs and CLUSTERS...but I'll test it. At least the CLUSTER are detected correctly all the time. Only the HOMETAB is not proper scanned. Thanks and cheers Dirk

…

On 21.04.23 17:09, Roland Stirnimann wrote: @dirkkrautschick-edb <https://github.com/dirkkrautschick-edb>, small update. I implemented the fix that only clusters of the same user are detected. Please download the latest pgbasenv.sh <https://github.com/Trivadis/pgbasenv/blob/master/bin/pgbasenv.sh> and test it. If you have v2.2 installed please execute |pgbasenv --clean-pgclustertab| or just delete $PGBASENV_BASE/etc/pgclustertab and re-login. Then you should see with postgres user only the community stuff and with enterprisedb user only the EDBAS stuff. — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A26BNMBQWUFQ4G3FDKQ6E2TXCKPMLANCNFSM6AAAAAASH6MLVQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>