The server control panel is currently being updated. Please try again later. [SOLVED]

[LastSavingGrace]

This has been mentioned before, but the previous topic is locked.
viewtopic.php?t=10305

The server control panel is currently being updated.

Please try again later.

This is all I have seen now when trying to log in. I ran the following code as per the previous post:

Code: Select all

cat /home/keyhelp/.lock/repo-update.lock

But receive the following:

cat: /home/keyhelp/.lock/repo-update.lock: No such file or directory

I rebooted the server, but still the same. Any other ideas?

I am running Debian 12, 64Bit.

Thank you.

[Alexander]

For the next time

1) Have a look, what job is blocking the update:

Code: Select all

tail /var/log/keyhelp/cronjob/panel-update.log

(it is very likely, that the virus scan is still running)

You might see something like this:

Code: Select all

[09-Feb-2024 09:54:52] INFO | cronjob "avscan" still running
[09-Feb-2024 09:54:52] INFO | sleeping till next check...
[09-Feb-2024 09:55:22] INFO | cronjob "avscan" still running
[09-Feb-2024 09:55:22] INFO | sleeping till next check...

2) Now either wait until the running job is done or kill the blocking process.
If it is just the anti-virus scan, it is no problem to kill it. If an other job is running, than you probably would like to wait.

3) If you have decided to kill the blocking job, head to

Code: Select all

ls -la /home/keyhelp/.lock/

and have a look into the file with the matching name of the job you want to kill (very likly avscan.lock). Inside the file, you will see the process ID.

4) Kill the process with the command:

Code: Select all

kill <PROCESS-ID>

5) You will now see that the panel update starts and /var/log/keyhelp/cronjob/panel-update.log is filled with update-related logs.
After a few minutes, the update is complete.


---

In your case, as you have rebootet the server, just calling

Code: Select all

keyhelp run panel-update

should be enough, or waiting until the next sheduled update check around 03:00 - 04:00 o'clock.

[LastSavingGrace]

Thanks Alexander, but nearly 10 days later and it is still the same. I've tried all the commands, none work.

Another weird thing is the keyhelp.backup directory was 50G and as far as I'm aware I have no backups enabled. I had to clear that directory before Debian could update due to disk errors.

So now if I run "keyhelp run panel-update" I get:

[PID-2787] [18-Feb-2024 11:18:44] INFO | maintenance connection okay
[PID-2787] [18-Feb-2024 11:18:44] INFO | forced to run "panel_update.php"

Fatal error: Uncaught TypeError: ProcessManager::isRunning(): Argument #1 ($pid) must be of type int, string given, called in /home/keyhelp/www/keyhelp/cronjob/mastercronjob.php on line 322 and defined in /home/keyhelp/www/keyhelp/core/System/ProcessManagement/ProcessManager.php:32
Stack trace:
#0 /home/keyhelp/www/keyhelp/cronjob/mastercronjob.php(322): ProcessManager::isRunning()
#1 {main}
thrown in /home/keyhelp/www/keyhelp/core/System/ProcessManagement/ProcessManager.php on line 32

Not sure what's going on really. Running "ls -la /home/keyhelp/.lock/" gives me:

drwxr-xr-x 2 root root 4096 Feb 12 06:32 .
drwxr-x--- 6 keyhelp www-data 4096 Jul 31 2023 ..
-rw-r--r-- 1 root root 0 Feb 12 06:32 panel-update.lock

[Alexander]

Hello,

send me the SSH login data for a root account via private message, i will have a look.

[LastSavingGrace]

Thanks Alexander, appreciate the help, but no need. I cleared the lock and ran the update again but it gave me a long list of errors. I'll just wipe everything and re-install, that should do it.