Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with npm in qryn 3.2.9 #472

Closed
mk-raven opened this issue Feb 27, 2024 · 2 comments
Closed

Error with npm in qryn 3.2.9 #472

mk-raven opened this issue Feb 27, 2024 · 2 comments

Comments

@mk-raven
Copy link

mk-raven commented Feb 27, 2024

After update qryn to 3.2.9 in kubernetes by helm chart we had a problem with qryn when stared pod.

Logs in container:

2345678910111213> qryn@3.1.1 start
node qryn.mjs

npm ERR! code EROFS
npm ERR! syscall open
npm ERR! path /home/qryn/.npm/_cacache/tmp/a6592e19
npm ERR! errno -30
npm ERR! rofs EROFS: read-only file system, open '/home/qryn/.npm/_cacache/tmp/a6592e19'
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

npm ERR! Log files were not written due to an error writing to the directory: /home/qryn/.npm/_logs
npm ERR! You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

Helm values:

affinity: {}
autoscaling:
  enabled: false
  maxReplicas: 100
  minReplicas: 20
  targetCPUUtilizationPercentage: 400
  targetMemoryUtilizationPercentage: 600
env:
  BULK_MAXAGE: 4000
  BULK_MAXCACHE: 100000
  BULK_MAXSIZE: 10000000
  CLICKHOUSE_AUTH: user:pass
  CLICKHOUSE_DB: qryn
  CLICKHOUSE_PORT: 9090
  CLICKHOUSE_PROTO: http
  CLICKHOUSE_SERVER: chproxy.chproxy.svc
  CLICKHOUSE_TIMEFIELD: record_datetime
  CLUSTER_NAME: data
  DISTINGUISH_LOGS_METRICS: 1
  FASTIFY_BODYLIMIT: 524288000
  FASTIFY_MAXREQUESTS: 0
  FASTIFY_METRICS: true
  FASTIFY_REQUESTTIMEOUT: 30000
  HOST: 0.0.0.0
  LABELS_DAYS: 7
  LOG_LEVEL: error
  NODE_OPTIONS: --max-old-space-size=61440
  PORT: 3100
  SAMPLES_DAYS: 7
fullnameOverride: qryn-write
image:
  repository: qxip/qryn
  tag: 3.2.9
imageCredentials: {}
imagePullSecrets:
  nameOverride: ""
ingress:
  annotations: {}
  className: ""
  enabled: false
  hosts:
  - host: chart-example.local
    paths:
    - path: /
      pathType: ImplementationSpecific
  tls: []
kubernetesClusterDomain: ""
livenessProbe:
  enabled: true
  endpoint: /metrics
nameOverride: ""
nodeSelector: {}
podAnnotations: {}
podLabels:
- qryn
podSecurityContext:
  fsGroup: 999
replicas: 1
resources:
  limits:
    cpu: 5
    memory: 4096Mi
  requests:
    cpu: 1
    memory: 512Mi
securityContext:
  capabilities:
    drop:
    - ALL
  readOnlyRootFilesystem: false
  runAsNonRoot: true
  runAsUser: 999
service:
  port: 3100
  type: ClusterIP
serviceMonitor:
  enabled: true
  interval: 30s
  path: /metrics
  port: 3100
  portName: http
  scheme: http
  type: ClusterIP
tolerations: []

@lmangani
Copy link
Collaborator

Thanks for the report @mk-raven we'll try replicate
Which qryn version were you upgrading from? Does the issue disappear when downgrading?

npm ERR! rofs EROFS: read-only file system, open '/home/qryn/.npm/_cacache/tmp/a6592e19'

have you tried clearing the npm cache entirely?

@akvlad
Copy link
Collaborator

akvlad commented Feb 27, 2024

@mk-raven should work in 3.2.10 . The bug is widely discussed in npm/cli#5183
Let's try applying workaround suggested npm/cli#5183 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants