mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Why after I insert data through the database, the UI can see the inserted data, but it seems that the ping action will not be executed and the status is unknown? #3008
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3008
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HaoY-l on GitHub (Jan 8, 2024).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
Why after I insert data through the database, the UI can see the inserted data, but it seems that the ping action will not be executed and the status is unknown?
📝 Error Message(s) or Log
Why after I insert data through the database, the UI can see the inserted data, but it seems that the ping action will not be executed and the status is unknown?
🐻 Uptime-Kuma Version
/
💻 Operating System and Arch
/
🌐 Browser
/
🐋 Docker Version
/
🟩 NodeJS Version
/
@chakflying commented on GitHub (Jan 8, 2024):
Have you tried restarting the server?
@HaoY-l commented on GitHub (Jan 8, 2024):
The service data can be refreshed after restarting the service, but the service cannot be restarted every time a monitoring item is added.
I now use the API to add it, so I don’t need to insert data into the database.
@CommanderStorm commented on GitHub (Jan 9, 2024):
Closing as resolved