IBM Security QRadar

 View Only
Expand all | Collapse all

Can't update Qradar CE

  • 1.  Can't update Qradar CE

    Posted Fri March 25, 2022 09:03 AM
    Hello,

    today I managed to install Qradar CE and all is working fine so far. Only problem is, that I can't auto-update.

    [root@qradar ~]# /opt/qradar/bin/UpdateConfs.pl -testConnect 1 0



    [AUTOUPDATE] [TESTCONNECT] Testing Internet Connection
    [AUTOUPDATE] [TESTCONNECT] ------- Debug DownloadFile -------
    [AUTOUPDATE] [WARN] Could not read company
    [AUTOUPDATE] [DEVEL] Recorded license info as "?version=7.3.3&iv=2019.14.0.20191031163225&lastau=0&lastpatch=0&vendor=Q1%20Labs"
    [AUTOUPDATE] [DEVEL] Downloading "manifest_list_512" and placing in "/store/autoupdates/".
    [AUTOUPDATE] [TESTCONNECT] Verify ssl is turned on
    [AUTOUPDATE] [DEVEL] Attempting to retrieve https://qmmunity.q1labs.com/autoupdates/manifest_list_512?version=7.3.3&iv=2019.14.0.20191031163225&lastau=0&lastpatch=0&vendor=Q1%20Labs
    [AUTOUPDATE] [TESTCONNECT] AU Proxy server setting - no proxy settings found


    -----------------Summary-----------------

    [AUTOUPDATE] [TESTCONNECT] PERL_LWP_SSL_VERIFY_HOSTNAME: 1
    [AUTOUPDATE] [TESTCONNECT] PERL_NET_HTTPS_SSL_SOCKET_CLASS: IO::Socket::SSL
    [AUTOUPDATE] [TESTCONNECT] Proxy Server:
    [AUTOUPDATE] [TESTCONNECT] Status Line: 500 Can't connect to qmmunity.q1labs.com:443
    [AUTOUPDATE] [TESTCONNECT] Content Line:

    Can't connect to qmmunity.q1labs.com:443

    Connection refused at /usr/share/perl5/LWP/Protocol/http.pm line 51.

    -----------------------------------------

    [AUTOUPDATE] [WARN] Could not retrieve "manifest_list_512": 500 Can't connect to qmmunity.q1labs.com:443
    [AUTOUPDATE] [TESTCONNECT] Could not download manifest list.


    I double checked the firewall logs (Pfsense) and I found no firewall deny/block event for Qradar.
    I do not use any kind of proxy configuration.
    Qradar is installed as a Proxmox VE KVE-VM. Qradar has a static public IP and LAN IP to use, 256GiB drive and 10 GB RAM with 6 CPUs.

    If you need any more info about my deployment let me know.

    Can anybody help me with this?

    ------------------------------
    M. Offermann
    ------------------------------


  • 2.  RE: Can't update Qradar CE

    Posted Mon March 28, 2022 04:03 AM
    Maybe too obvious, but the URL in this output is pointing out to the old update server (qmmunity.q1labs.com); the new URL/IP (auto-update.qradar.ibmcloud.com/) was announced quite a while ago:    QRadar: Important auto update server changes for administrators

    ------------------------------
    Dusan VIDOVIC
    ------------------------------

    Original Message


  • 3.  RE: Can't update Qradar CE

    Posted Mon March 28, 2022 08:00 AM
    Hello,

    You have to to change update server. Please see details in following technote:
    https://www.ibm.com/support/pages/qradar-important-auto-update-server-changes-administrators

    Kind regards,
    Robert

    ------------------------------
    Robert Karpiński
    ------------------------------

    Original Message


  • 4.  RE: Can't update Qradar CE

    Posted Mon March 28, 2022 09:53 AM
    Edited by M. Offermann Mon March 28, 2022 09:53 AM
    I tried that but it still doesn't work:
    Could not retrieve "dau/dau.manifest.xml.asc": 404 Not Found
    Could not retrieve signature for the manifest file.







    ------------------------------
    M. Offermann
    ------------------------------

    Original Message


  • 5.  RE: Can't update Qradar CE

    Posted Mon March 28, 2022 10:26 AM
    Not sure from the screenshot - make sure you have the trailing / in the webserver line https://auto-update.qradar.ibmcloud.com/

    ------------------------------
    Dusan VIDOVIC
    ------------------------------

    Original Message


  • 6.  RE: Can't update Qradar CE

    Posted Mon March 28, 2022 12:37 PM
    Yes I have the trailing "/" (otherwise it would not let me set the URL anyway)

    ------------------------------
    M. Offermann
    ------------------------------

    Original Message


  • 7.  RE: Can't update Qradar CE

    Posted Tue March 29, 2022 10:35 AM
    Any idea what it could be?

    ------------------------------
    M. Offermann
    ------------------------------

    Original Message


  • 8.  RE: Can't update Qradar CE

    IBM Champion
    Posted Fri April 01, 2022 08:09 AM
    have you checked for certificate errors in your system messages?
    This tip might help:
    https://www.ibm.com/support/pages/apar/IJ23059

    ------------------------------
    [Karl] [Jaeger] [Business Partner]
    [QRadar Specialist]
    [pro4bizz]
    [Karlsruhe] [Germany]
    [4972190981722]
    ------------------------------

    Original Message


  • 9.  RE: Can't update Qradar CE

    Posted Mon September 26, 2022 10:04 AM
    Hi, everyone. 

    I have the same error. I am trying to update it because it is a nightmare to integrate QRadar CE with Azure Event Hubs. It is timing out for no reason.

    Manifest does not exist: HTTP 404 
    No files there 404


    It seems to be all good here in terms of the certificate.
    Sep 24 10:29:01 vw-op-qradarce-01 AUTOUPDATE[28911]: Autoupdate 8.9 initialized.
Sep 24 10:29:01 vw-op-qradarce-01 AUTOUPDATE[28911]: Do we need to turn on SSL Cert
Sep 24 10:29:01 vw-op-qradarce-01 AUTOUPDATE[28911]: SSl cert is set correctly
Sep 24 10:29:07 ::ffff:192.168.1.223 [masterdaemon.masterdaemon] [a8be2f23-1330-4696-bd5c-cf165429a8b2/SequentialEventDispatcher] com.ibm.si.ep.filters.EPEntryRoutingFilter: [INFO] [NOT:0000006000][192.168.1.223/- -] [-/- -]MPC Event Rate: 0 eps.  Central Processing Event
 Rate: 0 eps.
Sep 24 10:29:07 vw-op-qradarce-01 AUTOUPDATE[28911]: Could not retrieve "dau/dau.manifest.xml.asc": 404 Not Found
Sep 24 10:29:07 vw-op-qradarce-01 AUTOUPDATE[28911]: Could not retrieve signature for the manifest file.
​


    The version:

    About QRadar CE Version



    The main issue is the Azure Event Hub configuration. It is timing out. And I can't understand the reason. The host where QRadar CE SIEM is deployed had all the access to it. 

    Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] com.q1labs.semsources.sources.microsoftazureeventhubs.MicrosoftAzureEventHubsProvider: [ERROR] [NOT:0000003000][192.168.1.223/- -] [-/- -]Ensure that there are no network related issues pre
venting the connection. Additionally ensure that the Event Hub and Storage Account Connection Strings are valid.
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] java.util.concurrent.ExecutionException: com.microsoft.azure.eventhubs.IllegalEntityException: Failure getting partition ids for event hub
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:368)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1906)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.microsoftazureeventhubs.host.MicrosoftAzureEventHubsHostRunner.registerHost(MicrosoftAzureEventHubsHostRunner.java:112)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.microsoftazureeventhubs.host.MicrosoftAzureEventHubsHostRunner.start(MicrosoftAzureEventHubsHostRunner.java:119)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.microsoftazureeventhubs.MicrosoftAzureEventHubsProvider.preExecuteConfigure(MicrosoftAzureEventHubsProvider.java:79)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.base.SourceProvider.run(SourceProvider.java:181)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] Caused by: com.microsoft.azure.eventhubs.IllegalEntityException: Failure getting partition ids for event hub
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventprocessorhost.PartitionManager.lambda$cachePartitionIds$4(PartitionManager.java:80)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventprocessorhost.PartitionManager$$Lambda$72.00000000DC15DB90.apply(Unknown Source)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:833)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:808)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:453)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.FutureTask.run(FutureTask.java:277)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:191)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.lang.Thread.run(Thread.java:812)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] Caused by: com.microsoft.azure.eventhubs.TimeoutException: Management request timed out on the client - enable info level tracing to diagnose.
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventhubs.impl.ManagementChannel$1.onEvent(ManagementChannel.java:64)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventhubs.impl.DispatchHandler.onTimerTask(DispatchHandler.java:12)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:233)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventhubs.impl.MessagingFactory$RunReactor.run(MessagingFactory.java:620)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    ... 7 more
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] com.q1labs.frameworks.naming.FrameworksNaming: [INFO] [NOT:0000006000][192.168.1.223/- -] [-/- -]Loaded singleton: NotificationLightDAO/com.q1labs.core.dao.notif.light.Notification/2362fca7
-2e58-4604-b2f3-7755ca91e4f9
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] com.q1labs.semsources.sources.microsoftazureeventhubs.MicrosoftAzureEventHubsProvider: [ERROR] [NOT:0070003100][192.168.1.223/- -] [-/- -]An error occured when trying to configure a source
connection for provider class com.q1labs.semsources.sources.microsoftazureeventhubs.MicrosoftAzureEventHubsProvider69
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] java.util.concurrent.ExecutionException: com.microsoft.azure.eventhubs.IllegalEntityException: Failure getting partition ids for event hub
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:368)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1906)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.microsoftazureeventhubs.host.MicrosoftAzureEventHubsHostRunner.registerHost(MicrosoftAzureEventHubsHostRunner.java:112)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.microsoftazureeventhubs.host.MicrosoftAzureEventHubsHostRunner.start(MicrosoftAzureEventHubsHostRunner.java:119)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.microsoftazureeventhubs.MicrosoftAzureEventHubsProvider.preExecuteConfigure(MicrosoftAzureEventHubsProvider.java:79)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.q1labs.semsources.sources.base.SourceProvider.run(SourceProvider.java:181)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] Caused by: com.microsoft.azure.eventhubs.IllegalEntityException: Failure getting partition ids for event hub
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventprocessorhost.PartitionManager.lambda$cachePartitionIds$4(PartitionManager.java:80)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventprocessorhost.PartitionManager$$Lambda$72.00000000DC15DB90.apply(Unknown Source)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:833)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:808)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:453)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.FutureTask.run(FutureTask.java:277)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:191)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at java.lang.Thread.run(Thread.java:812)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633] Caused by: com.microsoft.azure.eventhubs.TimeoutException: Management request timed out on the client - enable info level tracing to diagnose.
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventhubs.impl.ManagementChannel$1.onEvent(ManagementChannel.java:64)
Sep 24 10:08:50 ::ffff:192.168.1.223 [ecs-ec-ingress.ecs-ec-ingress] [Thread-1633]    at com.microsoft.azure.eventhubs.impl.DispatchHandler.onTimerTask(DispatchHandler.java:12)


    When I tried to install python 3.7 to write a simple consumer and verify deeply I got this:
    For a Community Edition. This is a  self-Learning environment, but  I can't install tools. 

    [root@vw-op-qradarce-01 Python-3.7.11]# yum install python3
Loaded plugins: product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
No package python3 available.
Error: Nothing to do


    ------------------------------
    Thiago Fonseca Born da Silva
    ------------------------------

    Original Message


  • 10.  RE: Can't update Qradar CE

    IBM Champion
    Posted Mon September 26, 2022 11:59 AM
    Thiago,

    too many issues here mixed into one question.
    1. your screenshot doesnt show your are using IBM cloud for updates. Pls refer to Dusans comment from March 22nd.
    2. CE version is fine, no major update to this avalable yet
    3. MS azure is a different building site. Pls refer to community discussion there, e.g. https://community.ibm.com/community/user/security/communities/community-home/digestviewer/viewthread?GroupId=2497&MessageKey=c1bd38e6-150a-47eb-9a17-5f1d0a76fd32&CommunityKey=f9ea5420-0984-4345-ba7a-d93b4e2d4864&tab=digestviewer
    4. Python version in base image used is 2.7.5 Pls dont updates this! Entitlement server is not registered and not needed. Pls use rpm --install for rpm updates. Python version in apps is newer depending on your app version installed.
    Regards
    Karl

    ------------------------------
    [Karl] [Jaeger] [Business Partner]
    [QRadar Specialist]
    [pro4bizz]
    [Karlsruhe] [Germany]
    [4972190981722]
    ------------------------------

    Original Message


  • 11.  RE: Can't update Qradar CE

    Posted Tue September 27, 2022 10:08 AM
    BTW
    Is this official?



    ------------------------------
    Zbigniew Korbutt-Madajewski
    ------------------------------

    Original Message


  • 12.  RE: Can't update Qradar CE

    IBM Champion
    Posted Tue September 27, 2022 11:17 AM
    Hi
    the next button is greyed out cause there is a minor bug in QRadar for non firefox browsers.
    Regarding CE versions I would like to now where you found that statement? Jose should know about internals I guess.
    Regards
    Karl

    ------------------------------
    [Karl] [Jaeger] [Business Partner]
    [QRadar Specialist]
    [pro4bizz]
    [Karlsruhe] [Germany]
    [4972190981722]
    ------------------------------

    Original Message


  • 13.  RE: Can't update Qradar CE

    Posted Tue September 27, 2022 02:01 PM

    No, it is not official. There is no word yet on if a new version of QRadar CE from Product Management teams at this time. If you want to vote and add a comment for the Product Management team, see https://ibmsecurity.ideas.ibm.com/ideas/SIEMCORE-I-3377.



    ------------------------------
    Jonathan Pechta
    QRadar Support Content Lead
    Support forums: ibm.biz/qradarforums
    jonathan.pechta1@ibm.com
    ------------------------------

    Original Message


  • 14.  RE: Can't update Qradar CE

    IBM Champion
    Posted Wed September 28, 2022 05:01 AM
    Hi Jonathan,
    thx for the URL. 94 votes right now!

    ------------------------------
    [Karl] [Jaeger] [Business Partner]
    [QRadar Specialist]
    [pro4bizz]
    [Karlsruhe] [Germany]
    [4972190981722]
    ------------------------------

    Original Message


  • 15.  RE: Can't update Qradar CE

    Posted Thu September 29, 2022 07:24 AM
    Thanks for answering Karl. 

    Sorry for the length of the previous message. 

    2. CE version is fine, no major update to this is available yet

    Does it justify the message I got? 
    By the way, I have updated the URL to the one point in the manual.
     
    Last update status: Manifest failed authenticity check.

Could not retrieve "dau/dau.manifest.xml.asc": 404 Not Found
Could not retrieve signature for the manifest file.​

    4. Python version in the base image used is 2.7.5 Pls don't update this! The entitlement server is not registered and is not needed. Pls, use rpm --install for rpm updates. Python version in apps is newer depending on your app version installed.

    Thanks for the tip. I kept version 2.7.5

    I will create other threads with single questions on each. So other people will find it easily if they went through the same issue. 




    ------------------------------
    Thiago Fonseca Born da Silva
    ------------------------------

    Original Message