Thank you for your suggestion, Inside the broker container i saw
/opt/activemq-artemis-broker/data so the journal folder was not created. My
colleague suggested setting
podSecurityContext:
fsGroup: 0
and it seem to work, i suppose it is due to the volume security
Regards
Thai Le
podSecurityContext: fsGroup: 0podSecurityContext: fsGroup: 0podSecurityContext:
fsGroup:
On Mon, 20 Mar 2023 at 12:48, Dondorp, Erwin <erwin.dond...@cgi.com.invalid>
wrote:
> Thai Le,
>
> Likely one of the intermediate directories is missing, but many other
> reasons are possible.
> Has the broker instance already been created inside your image?
> The usual trick is to add a long pause after the broker startup command,
> so e.g. ".../bin/artemis run; sleep 3600"
> That gives you one hour to investigate what the situation is inside the
> still running container.
> Use "docker exec" to create a new shell (or a menu item from your favorite
> Kubernetes tool, e.g. OpenLens) to begin the investigation.
>
> e.
>
> -----Original Message-----
> From: Thai Le <lnthai2...@gmail.com>
> Sent: maandag 20 maart 2023 16:56
> To: users@activemq.apache.org
> Subject: artemis operator: MQ222141: Node Manager can not open file
> /opt/activemq-artemis-broker/data/journal/server.lock
>
>
> EXTERNAL SENDER: Do not click any links or open any attachments unless
> you trust the sender and know the content is safe.
> EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce
> jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous
> ayez l'assurance que le contenu provient d'une source sûre.
>
> Hello,
> I asked the question in artemis cloud github discussion but I got no reply
> so maybe I will get better luck here. I am trying to enable persistence for
> my broker, here is the deployment plan section:
> ```
> deploymentPlan:
> size: {{ .Values.replicas }}
> image: placeholder
> requireLogin: true
> persistenceEnabled: {{ .Values.persistence.enabled }}
> {{- if .Values.persistence.enabled }}
> storage:
> size: {{ .Values.persistence.size }}
> storageClassName: {{ .Values.persistence.storageClass }}
> {{- end }}
> resources:
> requests:
> cpu: {{ .Values.resources.requests.cpu }}
> memory: {{ .Values.resources.requests.memory }} ```
>
> I am running k3s and i created a persistence volume as follow:
> ```
> apiVersion: v1
> kind: PersistentVolume
> metadata:
> name: my-pv
> spec:
> storageClassName: gp2-ncp
> capacity:
> storage: 2Gi
> accessModes:
> - ReadWriteOnce
> hostPath:
> path: /data/my-pv
> ```
> however, when i deploy the plan, i got this error:
> `MQ222141: Node Manager can not open file
> /opt/activemq-artemis-broker/data/journal/server.lock
> java.io.IOException: No such file or directory` I'm not sure if this is
> due to my PV not set up correctly or i am missing a config in my
> deploymentPlan. Hope to get some hint on this.
> Thai Le
>
> --
> Where there is will, there is a way
>
--
Where there is will, there is a way
