Hey
I have no idea where to ask a question about Panopticon. I have it running with four websites, all works well for three sites, but when I try to open one site, I get this:
What can I do?
Thanks a lot
Rolf
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by nicholas on Friday, 17 May 2024 09:12 CDT
Hey
I have no idea where to ask a question about Panopticon. I have it running with four websites, all works well for three sites, but when I try to open one site, I get this:
What can I do?
Thanks a lot
Rolf
You have some invalid backup records on those sites.
Go to each site's backend, Components, Akeeba Backup, Manage Backups. Delete all entries which are shown with a status other than OK (checkmark in green background) or Remote (cloud in blue background).
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hey
Thanks, that did the trick.
Another panopticon question (sorry!)
For one site, it claims:
I spoke to the people at my provider and they say it's nowhere near 100%. I have a fairly big package with 10 CPUs and not much sharing. Is there a way to find out if panopticon is wrong or the web server support?
Thanks
Rolf
This is what Linux itself reports in /proc/stat
or through top
.
When parsing /proc/stat we read user, nice, system, idle, iowait, irq, and softirq from the cpu line. Then we report the following values back to Panopticon:
where total = user + nice + system + idle + iowait + irq + softirq. Note that the System percentage reported contains the system, irq, and softirq timings reported by Linux. The System line includes all processes running in user mode, regardless of whether they are run as-is (user) or niced (nice). The values are reported within two floating points of precision e.g. 12.34 means 12.34%.
If access to /proc/stat is denied, the read value is empty, or there is no cpu line we fall back to running the system wide utility top using the command line LC_ALL=C top -n 1 -b
. We then look for the CPU usage line. There are two possibilities.
If you have the BSD (also macOS) version of top, the line reads something like this:
CPU usage: 12.65% user, 17.72% sys, 69.62% idle
We then parse these values, reporting user as User, sys as System, and idle as Idle. In this case we do not report Iowait; we instead set it to NULL to indicate to Panopticon this information cannot be collected.
If you have the Linux version of top, the line reads something like this:
%Cpu(s): 0.6 us, 0.9 sy, 0.0 ni, 98.2 id, 0.3 wa, 0.0 hi, 0.0 si, 0.0 st
In this case we have the user, system, nice, idle, waiting, hardware interrupts, software interrupts, and stolen by hypervisor components. We sum them up as:
If parsing the top
output fails we return NULL for all values.
Panopticon checks these values. If there are no values reported (all NULL) the CPU part of the Server Information page is not displayed at all.
When one or more values are non-NULL, it checks their values. When Idle is under 10.00 we print the message with the value between parentheses being 100 - Idle.
What you get means that either /proc/stat or top returned at least one non-zero value, and the reported Idle time is zero. I cannot think of any case where either /proc/stat or top would only report user and system but not idle times. If they get something else in /proc/stat or the top output as a non-privileged user I'd like to see it.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.
Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!