all docker up state and ping are down as of today

[IIIdefconIII]

📑 I have found these related issues/pull requests

i habe not but can unselect it

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

👟 Reproduction steps

just open my internatl page and all is down

👀 Expected behavior

seeying docker containers and pings up

😓 Actual Behavior

see scrensit, noit rplying to docker containers an htpp/hptps local links wihle portainer say all it up and evyerhting works locallt

🐻 Uptime-Kuma Version

latest

💻 Operating System and Arch

Docker DSM Synology latest

🌐 Browser

Chomr

🖥️ Deployment Environment

• Runtime:
• Database:
• Filesystem used to store the database on:
• number of monitors:

📝 Relevant log output

i have  no atm

[IIIdefconIII]

hi dev, by any change saw my message here? other users i have spoken to personally dont have this problem

[CommanderStorm]

Could you clarify what i have no atm means in regards to logs?
Could you please also clarify the Deployment Environment which you omitted above?

Above you stated that you are using http to monitor other docker containers. How have you configured your docker network

[IIIdefconIII]

Could you clarify what i have no atm means in regards to logs? Could you please also clarify the Deployment Environment which you omitted above?

Above you stated that you are using http to monitor other docker containers. How have you configured your docker network

sure hes 1 example

The test says OK

its almsot like they pushed an update and since all monitors arew down even ping or docker socks

[IIIdefconIII]

it still all down for some reaon it also doesnt talk to the docker envirmont anymore like this one:
As exmaple this container runs fine...
uptime just doesnt talk to the docker containers anymore ...

[IIIdefconIII]

[IIIdefconIII]

ther still down and even the docker up doesnt work so im kinda disappointed in the support here

[IIIdefconIII]

Could you clarify what i have no atm means in regards to logs? Could you please also clarify the Deployment Environment which you omitted above?

Above you stated that you are using http to monitor other docker containers. How have you configured your docker network

yes i have, even the CF is up and running but all stays offline in the uptimekuma page

[IIIdefconIII]

Could you clarify what i have no atm means in regards to logs? Could you please also clarify the Deployment Environment which you omitted above?

Above you stated that you are using http to monitor other docker containers. How have you configured your docker network

hi at that moment i didnt had acces to the logs, i have aquired brain injury so i takes some time for me to keep up everything

Here is a snap from the log files

[2023-04-06 03:14:08] [Error: insert into `heartbeat` (`down_count`, `duration`, `important`, `monitor_id`, `msg`, `ping`, `status`, `time`) values (0, 60, false, 11, '200 - OK', 920, 1, '2023-04-06 01:14:06.466') - SQLITE_BUSY: database is locked] {
  errno: 5,
  code: 'SQLITE_BUSY'
}
[2023-04-08 03:14:06] [Error: insert into `heartbeat` (`down_count`, `duration`, `important`, `monitor_id`, `msg`, `ping`, `status`, `time`) values (0, 60, false, 10, '200 - OK', 9, 1, '2023-04-08 01:14:05.745') - SQLITE_BUSY: database is locked] {
  errno: 5,
  code: 'SQLITE_BUSY'
}
[2023-04-08 03:14:08] [Error: insert into `heartbeat` (`down_count`, `duration`, `important`, `monitor_id`, `msg`, `ping`, `status`, `time`) values (0, 60, false, 22, '200 - OK', 66, 1, '2023-04-08 01:14:06.889') - SQLITE_BUSY: database is locked] {

[IIIdefconIII]

is there any one that might be able to helpe me try to solve this issue?

[CommanderStorm]

kinda disappointed in the support here

Sorry, but that is the level of support that I can offer in my free time, next to the other projects...

Here is a snap from the log files

Please have a look at the solutions in #4500
=> the issue will be resolved in v2.0, but in v1.x, you will need to apply the noted bandaid-fixes like getting faster storage, reducing retention or ping rate.

i have aquired brain injury

get well soon

[IIIdefconIII]

kinda disappointed in the support here

Sorry, but that is the level of support that I can offer in my free time, next to the other projects...

Here is a snap from the log files

Please have a look at the solutions in #4500 => the issue will be resolved in v2.0, but in v1.x, you will need to apply the noted bandaid-fixes like getting faster storage, reducing retention or ping rate.

i have aquired brain injury

get well soon

hi, trhank for your answer and will look further in it tonight,
you also got ABI? hope you get better soon, i took me 2 years before getting real improvement

God bless!

[IIIdefconIII]

is there a way to already pull the v2 beta?

# UptimeKuma: Services Status__________
  uptimekuma:
    container_name: uptimekuma
    image: louislam/uptime-kuma:latest
    restart: always
    security_opt:
      - no-new-privileges:true
    ports:
      - 3001:3001
    environment:
      PUID: 0
      PGID: 0
      UMASK: $UMASK
      TZ: $TZ
      DOZZLE_LEVEL: info
      DOZZLE_TAILSIZE: 300
      DOZZLE_FILTER: "status=running"
    volumes:
      - $DOCKERDIR/uptimekuma:/app/data
      - /var/run/docker.sock:/var/run/docker.sock

What image url should i use here?

[CommanderStorm]

is there a way to already pull the v2 beta?

The beta is currently not ready.
Please see #4500 for further context.
You can subscribe to said issue or to our releases to get notifications when this is published.

We will publish a beta once all the harsh bugs are done and migration from v1 to v2 is possible (See #5075 for further context)

[IIIdefconIII]

is there a way to already pull the v2 beta?

The beta is currently not ready. Please see #4500 for further context. You can subscribe to said issue or to our releases to get notifications when this is published.

We will publish a beta once all the harsh bugs are done and migration from v1 to v2 is possible (See #5075 for further context)

thanks for ur readings and answer, i just removed all an setup it up again from the backup, while it does say its depricated, its now workign again