Socket.<anonymous> (/app/server/server.js:934:17)

[KaMaToZzz]

📑 I have found these related issues/pull requests

Hello, I have some errors in logs of docker container

If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
Trace: TypeError: callback is not a function
    at Socket.<anonymous> (/app/server/server.js:934:17)
    at process.unexpectedErrorHandler (/app/server/server.js:1905:13)
    at process.emit (node:events:517:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
Trace: TypeError: callback is not a function
    at Socket.<anonymous> (/app/server/server.js:934:17)
    at process.unexpectedErrorHandler (/app/server/server.js:1905:13)
    at process.emit (node:events:517:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

🛡️ Security Policy

• [X] I agree to have read this project Security Policy

Description

Im just run latest container, thats all

👟 Reproduction steps

Run latest container

- name: Start uptime-kuma project with inline definition
  community.docker.docker_compose:
    project_name: uptime_kuma
    definition:
      services:
        uptime-kuma:
          image: louislam/uptime-kuma:1
          container_name: uptime-kuma
          environment:
            SSL_CERT: /app/data/ssl/domain.crt
            SSL_KEY: /app/data/ssl/domain.key
            PORT: 443
          volumes:
            - /src/uptime-kuma-data:/app/data
            - /src/uptime-kuma-data/ssl:/app/data/ssl
          ports:
            - 443:443  # <Host Port>:<Container Port>
          restart: always

👀 Expected behavior

dont know

😓 Actual Behavior

dont know

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

ubuntu 22.04

🌐 Browser

safari

🖥️ Deployment Environment

• Runtime: containerd
• Database: sqllite
• Filesystem used to store the database on: ext4
• number of monitors: 28

📝 Relevant log output

No response

[CommanderStorm]

What did you do before that? Is it reproducible?

callback, as called here

https://github.com/louislam/uptime-kuma/blob/1185b259c2f171758e75d92e6843c5efec652f04/server/server.js#L934

is definitively a function as far as I can see

https://github.com/search?q=repo%3Alouislam%2Fuptime-kuma+pauseMonitor%22&type=code

[KaMaToZzz]

What did you do before that? Is it reproducible?

callback, as called here

https://github.com/louislam/uptime-kuma/blob/1185b259c2f171758e75d92e6843c5efec652f04/server/server.js#L934

is definitively a function as far as I can see

https://github.com/search?q=repo%3Alouislam%2Fuptime-kuma+pauseMonitor%22&type=code

Stopped old container 1.23.5, clear all data from - /src/uptime-kuma-data:/app/data Removing img, remove container Play playbook for run container. Thats all

UPD: after stop start container no errors at all. Cant reproduce for now